Trouble setting up IIS

[dav3]

I'm trying to set up an internal webserver on my home PC so I can access Terminal Services through IE. I'm on cox broadband in Orange County and am using an SMC7004ABR router with dhcp enabled. In my current setup I have IIS, Terminal Services (Remote Admin mode) and the ActiveX control installed in Windows 2000 AS. My router is configured to pass through port 80 and port 3??? for terminal services. When on the internal LAN I can access the home page and get access to terminal service through IE. When I try to connect to the server from the outside, I can't get the homepage to load at all, just get an error that the page cannot be loaded.

I am able to access Terminal Services using the client connection manager without any problems, and I can even get the ActiveX control to work if I first connect to another webserver running the control (does that make sense?). For some reason however, I cannot connect to a normal webpage from outside my LAN. I have tried using different ports with IIS but nothing seems to work. Anyone have any ideas what I might be doing wrong?

Thanks,
Dave

 

[Poontos]

Cox broadband may be blocking any type of HTTP (port 80) traffic to their subscribers (you). Check there support/FAQ site and let us know your findings.

Port 80 = default HTTP
Port 3 = compressnet #Compression Process - whatever the hell this is, but it does not related to terminal services.

You need the TS ports, see support.microsoft.com for this info.

Keep us posted.

 

[HDRick]

Poontos is right cox does block port 80 go into your server and set it for port 8080 and see if you can get to it use the ip address and put :8080 at the end.

 

[dav3]

Does it need to be port 8080 specifically? I've tried using other random port numbers but have not had any luck with those. I'll give port 8080 a shot and see what that does for me.

Thanks,
Dav3

 

[Poontos]

Originally posted by: dav3
Does it need to be port 8080 specifically? I've tried using other random port numbers but have not had any luck with those. I'll give port 8080 a shot and see what that does for me.

Thanks,
Dav3

Any random port above 1024 ain't going to hurt anyone on your home PC, as long as another application is not utilizing the port. Hey, if one don't work, try another. Discliamer: For those reading this looking for production or real world information on this subject, please start a new thread.

P.S. Cox may be blocking HTTP traffic, no matter what port. HTTP traffic does not necessarily require port 80, although it is the default port.

 

[blstriker]

Terminal Services Server and Client talk to each other over port 3389.

Terminal Services Advanced Client Configuration (Web Client)

 

[dav3]

Originally posted by: blstriker
Terminal Services Server and Client talk to each other over port 3389.

Terminal Services Advanced Client Configuration (Web Client)

That's right for terminal services, but in order to run the web based client I need to be able to hit the webserver and load the htm page which is where I am having the problem. I've tried several different ports and port forwarding schemes to try and access IIS from outside my lan without any luck. It must be something that COX is able to block absolutely, cause http access is the only thing that will not work.
I have found a workaround to my problem by using an external web server, it's not my ideal solution but at least it will allow me to access my system if I need to. If anybody out there has successfully implemented a webserver on COX's network, I'd like to hear how you did it.

Dav3

 

[HDRick]

Yes I do now people that run a webserver on cox but on coxs its not allow . but if you change the port from 80 it will run have you went into your webserver setting and go under documents and tell it to open index.html or index.htm files by default it won't open them.I hope this helps.

 

[dav3]

There's got to be something I'm missing or haven't configured properly. As of right now I have configured IIS to respond to http requests on port 200 for now. I've gone into my router and set it up to forward public port 200 requests to my private ip address; port 200. I am also using an external DNS service (no-ip.com) to forward a dns name to my wan ip. Does this all sound right so far?

When I'm on the internal lan everything works (at least it seems to) . I can type in my dns name (xxx.no-ip.com:200) and it takes me to my webpage. I won't be able to check external access until tomorrow but in the meantime if anyone has anymore suggestions/recommendations I would appreciate it.

Thanks to those who have given me ideas so far.
Dav3

 

[ojai00]

I had that same problem. I would type "http://domain.dyndns.org:200/tsweb" and that wouldn't work. I changed the router to forward port 80 to the IIS server and it works now. I just type in "http://domain.dyndns.org/tsweb" and I can get to the terminal services screen. I can't log in, but at least I can get to the screen . Since you say that Cox doesn't allow it, I don't know what to do

 

[Bleep]

xxx.no-ip.com:200)

Here is the problem. I do not know of any ip forwarding service that will do the IP this way unless you pay a extra fee for this service. They will only forward to your .com address and the 200 will be ignored or will not allow anything to happed.

Try and just type in your IP numbers :200 and it will probably work.

Bleep