Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cannot access Terminal Server on Port 80 externally

Status
Not open for further replies.

niallo32

IS-IT--Management
Apr 29, 2004
404
IE
I have a Windows 2000 Terminal Server that has a public IP NAT'd to it's internal address

Users from the outside connect to the TS through a browser
We can no longer connect using this address.

We can connect externally on Port 3389 by using Remote Desktop and entering the Public IP

Our ISP has confirmed that requests on Port 80 are being blocked by the Terminal Server, though I can connect to web pages locally.

We have a WAN connection to the TS from sites around Europe and they can login via the WAN connection without problem.

No configuration has changed on our side.

There is nothing in the Event Logs to indicate a problem.

Anyone seen this before?

Thanks
 
Can you get to it from your internal network? if so it's not the terminal server and sounds like a NAT or firewall issue
 
I cant get to it from the Internal Network, though I never could.

Can you suggest anything else?

Thanks
 
Hi niallo32. you mention

"Our ISP has confirmed that requests on Port 80 are being blocked by the Terminal Server, though I can connect to web pages locally"

What are these web pages ? If they are your web site then maybe you need to change the port of the web server to something other than port 80.
 
I need to get clarification on what they mean by that. I can Telnet to Port 80 on the TS and can connect to the Internet locally.

I have ran Ad-Aware, Spybot, Stinger and cannot find any viruses/spyware

There are no suspect processes running

How do I change the Port of the Web Server from Port 80?

Thanks for the help
 
Hi Moorethan - thanks for the help.

This suggestion would appear to be the solution but unfortunatly, I cannot get to the initial WebPage where you would normally hit 'Connect'

I cant see what could be causing this as the Public IP NAT'ing is ok as I can connect using Remote Desktop.

I can connect to the Internet locally on the Terminal Server.

Anyone else had a similar problem?
 
If you can connect with the RDP client and you can't connect via a Web Browser from outside or inside your network it sounds like a IIS problem. On the terminal server open IE and type that sould bring up the connect page. If it doesn't it's IIS
 
Thanks for all the help. It was an IIS problem and I've resovled it. I'll know how to troubleshoot the problem for future reference.

Cheers
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top