teknetics
asked on
Win2K Terminal Server over Internet
Here's the layout.
W2K Terminal Server runs on a private subnet. TSAC is installed on an IIS5 server (with software firewall) that is multihomed on the privatesubnet as well as the public subnet. The web site that TSAC was installed to has IP addresses for both subnets.
From the private subnet, clients can surf to the Remote desktop Connection page and connect to the Terminal Server.
When clients try to coonnect from the Internet, they get to the Remote Desktop Connection page. But cannot connect to the terminal server by FQDN, Netbios name or private subnet IP address. This is the case with the firewall on or off. Port 3389 is open in both directions.
Depending on the address/name used to attempt connection, they get one of two messages. All are VBScript: Remote Desktop Disconnected errors.
Netbios name or FDQN
"The specified remote computer could not be found. Verify that you have typed
the correct computer name or IP address, and then try connecting again."
IP Address
"The client could not connect to the remote computer. Remote connections might
not be enabled, or the computer may be too busy to accept new connections. It
is also possible that network problems are preventing your connection. Please try
again later. If the problems continue to occur, contact your administrator."
Why can my clients not connect from the internet?
W2K Terminal Server runs on a private subnet. TSAC is installed on an IIS5 server (with software firewall) that is multihomed on the privatesubnet as well as the public subnet. The web site that TSAC was installed to has IP addresses for both subnets.
From the private subnet, clients can surf to the Remote desktop Connection page and connect to the Terminal Server.
When clients try to coonnect from the Internet, they get to the Remote Desktop Connection page. But cannot connect to the terminal server by FQDN, Netbios name or private subnet IP address. This is the case with the firewall on or off. Port 3389 is open in both directions.
Depending on the address/name used to attempt connection, they get one of two messages. All are VBScript: Remote Desktop Disconnected errors.
Netbios name or FDQN
"The specified remote computer could not be found. Verify that you have typed
the correct computer name or IP address, and then try connecting again."
IP Address
"The client could not connect to the remote computer. Remote connections might
not be enabled, or the computer may be too busy to accept new connections. It
is also possible that network problems are preventing your connection. Please try
again later. If the problems continue to occur, contact your administrator."
Why can my clients not connect from the internet?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
delgadoj answered this perfectly.
Be aware that TSAC is just an ActiveX control, that replaces the WIN32 client, you still need RDP access to the Terminal Server.
What will be happening in your instance is you will browse to the IIS box and get teh TSAC screen. You then put ??? address in of your terminal server. If it is an RFC1918 address, it won;t route through the Internet, so the connection will fail.
If you do what delgadoj said, it will work.
Be aware that TSAC is just an ActiveX control, that replaces the WIN32 client, you still need RDP access to the Terminal Server.
What will be happening in your instance is you will browse to the IIS box and get teh TSAC screen. You then put ??? address in of your terminal server. If it is an RFC1918 address, it won;t route through the Internet, so the connection will fail.
If you do what delgadoj said, it will work.
I've done TS between states, TS client, never dealt with it via browser, although I might take the time to find out how.
Sounds like the problem is dns related.
add the url of the servers public ip to the hosts amd lmhosts files of the server its self and resolve it to the servers internal ip.
Shep