TSWeb error

[Rob Moulton]

I have just setup a development Windows 200 server in a
workgroup with Terminal Server Web on it. I can connect
just fine (using IE) from computers on my local LAN, but
clients that try to connect from the internet get the
login page (where you select the screen size), and then
the following error when they click Connect:

"The client could not connect to the remote computer.
Remote connections might not be enabled or the computer
might be too busy to accept new connections. It is also
possible that network problems are preventing your
connection.".

I think it's a security issues with the TSInternetUser
account not having permissions to connect. But I've set
it up in the local Administrators group. I've tried
Remote Administration Mode and Application User Mode; same
problem. Any ideas? Thanks.

 

[Guest]

You might have a similar question to what I asked a few posts below. What are the allowed TCP ports that your firewall/router allows your incoming "internet" http requests to come in on? Until I modified my firewall to forward port 3369, along with 80 or 443, I was getting exactly the same messages.

James...

----- Rob Moulton wrote: -----

I have just setup a development Windows 200 server in a
workgroup with Terminal Server Web on it. I can connect
just fine (using IE) from computers on my local LAN, but
clients that try to connect from the internet get the
login page (where you select the screen size), and then
the following error when they click Connect:

"The client could not connect to the remote computer.
Remote connections might not be enabled or the computer
might be too busy to accept new connections. It is also
possible that network problems are preventing your
connection.".

I think it's a security issues with the TSInternetUser
account not having permissions to connect. But I've set
it up in the local Administrators group. I've tried
Remote Administration Mode and Application User Mode; same
problem. Any ideas? Thanks.