VBScript error using TSWeb "Error Connecting to Terminal Server:"
When we use TS Web to connect to our servers over the internet we get a VBScript message:
"Error connecting to Terminal Server: <<name of server>>"
This only happens when I try to access the server over the internet. When I access the server over the LAN, it works perfect. Currently the server is exposed directly to the internet and is not behind a firewall.
I have searched the MS Knowledge Base with no success. I have also confirmed this to be a problem with a client over the internet to his server. It works just fine on his LAN.
"Error connecting to Terminal Server: <<name of server>>"
This only happens when I try to access the server over the internet. When I access the server over the LAN, it works perfect. Currently the server is exposed directly to the internet and is not behind a firewall.
I have searched the MS Knowledge Base with no success. I have also confirmed this to be a problem with a client over the internet to his server. It works just fine on his LAN.
I recently had this problem as well, in my situation, the Terminal Server License service sould not start. To allow the server to start run "dcpromo" and promote your TS to a domain controller, then the TS license service will start and allow external connections to connect.
Be careful as this will delete all local accounts, and you also need to change the default security policy to allow local logins, under Domain Users->properties of your domain object->group policy tab->policy->computer settings->local settings->logon locally
add your users to this section
-Jason.
Be careful as this will delete all local accounts, and you also need to change the default security policy to allow local logins, under Domain Users->properties of your domain object->group policy tab->policy->computer settings->local settings->logon locally
add your users to this section
-Jason.
Our situation seems very similar, clients on our LAN could access it fine as well.
Good luck.
-Jason
Good luck.
-Jason
That's a rather weird solution! I don't know (haven't had to check into it) but would be rather suprised if you had to have an application server promoted to a DC to allow access. It might work, but it can't be the best solution can it?
Hello all,
I am Computer101, a moderator from Experts-Exchange. This question has been open a long time. What I am going to do is allow feedback from the questioner and experts or hope that the questioner comes back to close this question. If it is not resolved, I will delete or accept an answer based on the info I have been given, Experts, feel free to offer input. I will monitor these questions for a period of 5-7 days and come back and evaluate.
Thank you
Computer101
Community Support Moderator
I am Computer101, a moderator from Experts-Exchange. This question has been open a long time. What I am going to do is allow feedback from the questioner and experts or hope that the questioner comes back to close this question. If it is not resolved, I will delete or accept an answer based on the info I have been given, Experts, feel free to offer input. I will monitor these questions for a period of 5-7 days and come back and evaluate.
Thank you
Computer101
Community Support Moderator
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You haven't stated the licencing type that you're using for the TS server - this may be important.
Have you had a look in the eventlogs &/or the Terminal Services application event log? What entries are relevant to this (if any)?