Discussion Locked

Terminal Server Error

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello,
We are having a weird problem with our Terminal Server. From one Windows 2000 workstation I can get in from the internet to our server with no problem whatsoever. The computer is a Dell. I have installed the latest service packs on the server so that is not an issue. I recently got a hotfix from the microsoft website that I installed for terminal services. That did not solve the problem. We have a client that is using a Windows 2000 OS and he cannot connect. He gets an error message of
VBScript: Error in Connection to Terminal Server. It doesn't display anything else. We have looked at the licensing on the server and that does not seem to be an issue. In our office we have two identical brand new IBM laptops that have the same configuration and one of them can connect and the other cannot connect. They both have the same Terminal Services Client installed from the SAME disks. What could possibly be the problem here. I have looked at a couple of Q Knowledge Base Articles on Microsoft's website and have not come up with anything except for a test I can do in telnet to see if port 3389 is accepting connections. I found that it accepts a connection if I type in telnet and then www.ourwebsiteaddress.com, but if Itry and type in the server name it does not accept the connection to the server.
Someone please help us on this issue as our clients have not been able to connect to our server in a few days.

Thanks,

Eddie

9 replies

by flan

is this s win2k term serv or nt term serv?

win2k has 2 different client setups, one for 2k one for nt.

and are you in the same network?

by qhcomputingny

This server is a Windows 2000 server. It is on the same network. We just tried to change the network identification from a domain to a workgroup and the laptop that could not get in before, can now get in. We still don't understand what the problem is because the other laptop with the same configuration was able to connect to it before the domain to workgroup change was made. Hope this helps.
The problem may be fixed, but we would much rather have that server in our domain rather than in its own workgroup. It should be able to work in our domain for all computers.

by stillatit

Based on your experience with telnet, it sounds like part of the difference may be in name resolution. Try using the IP address of the server, and see if everyone can get in. If so, check whether some stations have hosts or lmhosts files with an incorrect entry for your server.

While you may not think that licensing has anything to do with it, check the license database anyway. You may find that your server has run out of TS CALS.

Note that if your server was upgraded from a workstation, there may still be a limit of 10 simultaneous connections from a leftover registry entry. I do not remember the key offhand, but a search of Techrepublic questions using the term "simultaneous" should find it.

Good luck.

by sativocomputerservices

Your problem is definitely with name resolution. I would make sure that the box on the DNS tab in your TCP/IP properties is checked to enable DNS for Windows resolution. If this is not checked, you will never be able to connect over the internet.Also check for hosts files taht may conflict with the DNS information; however, I am confident this will solve your problem.

This discussion is closed to new replies.