'VBScript: Remote Desktop Diconnected' Error

[Nathan Thomas Sr]

I am able to connect to TSWeb from within the lan using the public IP.
However, users from outside are getting this error message

VBScript: Remote Desktop Diconnected
The specified remote computer coul dnot be found. Verify that you have
typed the correct computer name or IP address, and then try connecting
again.

No errors are showing in the event logs. I have found this question
asked many times through Google searches, but I have yet to find one
answered and resolved.

Can anyone help?

Thanks

[TP]

Do you have port 3389 on your public ip forwarded to
the internal ip of your ts?

Thanks.

-TP

Post by Nathan Thomas Sr
I am able to connect to TSWeb from within the lan using the public IP.
However, users from outside are getting this error message
VBScript: Remote Desktop Diconnected
The specified remote computer coul dnot be found. Verify that you have
typed the correct computer name or IP address, and then try connecting
again.
No errors are showing in the event logs. I have found this question
asked many times through Google searches, but I have yet to find one
answered and resolved.
Can anyone help?
Thanks

[Nathan Thomas Sr]

Do you have port 3389 on your public ip forwarded to the internal ip of
your ts?
Thanks.
-TP

Post by Nathan Thomas Sr
I am able to connect to TSWeb from within the lan using the public IP.
However, users from outside are getting this error message
VBScript: Remote Desktop Diconnected
The specified remote computer coul dnot be found. Verify that you have
typed the correct computer name or IP address, and then try connecting
again.
No errors are showing in the event logs. I have found this question
asked many times through Google searches, but I have yet to find one
answered and resolved.
Can anyone help?
Thanks

Yes, port 3389 is being fwd'd to the TS.

Thanks,
Nathan

[TP]

Are you typing the public ip address or publicly
resolvable fully qualified domain name?

What happens if you simply click the connect
button on the web page instead of entering a
name?

For example, if the server's internal name is
tsweb and your domain is mydomain.local,
internally you would be able to connect by
typing tsweb or tsweb.mydomain.local.

This would not work from the outside because
the name is not resolvable. For the outside you
need to use the public ip address or create a DNS
A record entry pointing to the public ip address.

Thanks.

-TP

Post by Nathan Thomas Sr
Yes, port 3389 is being fwd'd to the TS.
Thanks,
Nathan

[Nathan Thomas Sr]

I am accessing the site through the public ip/tsweb.
What is strange, is that in the 'server' name box, if I type the IP
address of the server instead of it's name, it gives me a different
error (rras is busy, etc).
Oddly, I think I may have narrowed it down.
It looks like if I create a vpn connection, connect, then access ts web
through the public site, it goes through.

Curiouser and curiouser...

Are you typing the public ip address or publicly resolvable fully
qualified domain name?
What happens if you simply click the connect button on the web page
instead of entering a name?
For example, if the server's internal name is tsweb and your domain is
mydomain.local, internally you would be able to connect by typing tsweb
or tsweb.mydomain.local.
This would not work from the outside because the name is not
resolvable. For the outside you need to use the public ip address or
create a DNS A record entry pointing to the public ip address.
Thanks.
-TP

Post by Nathan Thomas Sr
Yes, port 3389 is being fwd'd to the TS.
Thanks,
Nathan

[Nathan Thomas Sr]

Actually, I was able to get to the sign on screen by not putting
anything in the server name line, and clicking on 'connect'.
DNS issue..?

Are you typing the public ip address or publicly resolvable fully
qualified domain name?
What happens if you simply click the connect button on the web page
instead of entering a name?
For example, if the server's internal name is tsweb and your domain is
mydomain.local, internally you would be able to connect by typing tsweb
or tsweb.mydomain.local.
This would not work from the outside because the name is not
resolvable. For the outside you need to use the public ip address or
create a DNS A record entry pointing to the public ip address.
Thanks.
-TP

Post by Nathan Thomas Sr
Yes, port 3389 is being fwd'd to the TS.
Thanks,
Nathan

[TP]

Yes. The name needs to be resolvable via DNS.

For example, if you go to a random public computer
anywhere in the world, the name you are typing should be
be able to be resolved to an ip address. Like if you
type ping <servername> at a public computer it
should respond with the correct ip address. No VPN
or anything special is required.

-TP

Post by Nathan Thomas Sr
Actually, I was able to get to the sign on screen by not putting
anything in the server name line, and clicking on 'connect'.
DNS issue..?