Web Enabled Terminal Server and firewalls

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

Can anyone tell me if the web enabled terminal services for W2K is capable of running completely in http or does it still require the client to have a connection? I have a problem where I have put a terminal server on the public internet and cannot access the logon screen from behind the corporate firewall. Do I need to open a port up or is there a way to do it where it looks like plain web traffic?
 
The initial connection to the Remote Desktop Web
Connection page is over port 80 http (which therefore
involves IIS), but the connection to the terminal server
is over port 3389 for RDP. So yes, you'll need to open up
port 80 to your IIS server and port 3389 to your terminal
server.

-M
-----Original Message-----
Hi,

Can anyone tell me if the web enabled terminal services
Click to expand...
for W2K is capable of running completely in http or does
it still require the client to have a connection? I have a
problem where I have put a terminal server on the public
internet and cannot access the logon screen from behind
the corporate firewall. Do I need to open a port up or is
there a way to do it where it looks like plain web traffic?
 
I have terminal web services installed in a server. When using the browser to connect from within the intranet it works great. But when trying to access it from outside the intranet it wont. I have a firewall that is routing the port 80 and port 3389 external request to my internal server IP address. The initial screen shows fine on the external browsers. But when placing the server name and trying to log on, it delays for about a minute or so, and then sends a message that the server may be too busy to accept more calls, but when I connect from within the intranet it works ok.

Any suggestions?
 
you are using the servername? if you said the firewall is setup that tells
me that you most likely have a NAT, try using the outside IP of the NAT
instead fo the name, if that works you jsut need a resolvable name

Ron

Jerry said:
I have terminal web services installed in a server. When using the browser
Click to expand...
to connect from within the intranet it works great. But when trying to
access it from outside the intranet it wont. I have a firewall that is
routing the port 80 and port 3389 external request to my internal server IP
address. The initial screen shows fine on the external browsers. But when
placing the server name and trying to log on, it delays for about a minute
or so, and then sends a message that the server may be too busy to accept
more calls, but when I connect from within the intranet it works ok.
 
Back
Top