asked on

Terminal Services login problem

I have a user in our Omaha location that is dependent on logging in to our Terminal Services server to use our database software. Up until about two days ago, she was able to login just fine. Suddenly, she tells me, she got booted off and after trying to connect again, she is unable to. Each time she tries to connect she receives this error:

Terminal Services Client disconnected - Could not connect - Server may be too busy or full.

The server is definitely not too busy or full. No one else from her location is having any problems connecting to Terminal Services at all. I had her try to login with her information from another workstation and that worked successfully, so it's not tied to her login account. I also had someone else try to login with different information from her workstation and they were unable to. This, of course, leads me to believe it is tied directly to her machine. I've had her check out the settings for Terminal Services on her machine and nothing has changed. I also had her look through the event viewer and we could find nothing related to the issue.

Any ideas? Do I need to reset her computer account on the server? I've rebooted both our main server and our terminal services server. I've checked every setting I can think of to check. I don't get it. I don't know a lot about terminal services, but I've tried everything I can come up with. Help a geek out!

pcbrat

I had this same problem. Try this link it fixed it for me.

http://support.microsoft.com/default.aspx?scid=kb;en-us;260746

Good luck and keep us posted!

DAwne :)

Vladimyr

ASKER

Thanks pcbrat. I looked over that page and I can assure you that the IP address it is trying to connect to is the proper IP address. It isn't attempting to resolve the server IP from a name. It has the IP address directly input into the settings for the connection.

Still going nuts! ;)

ASKER CERTIFIED SOLUTION

MSGeek

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

pcbrat

Yea do what the Geekman said. Go fo rthe reinstall of the client first. Then the others, if nothing works keep us posted we will help out.

Dawne

MSGeek

It could be Geekwoman? :) or are you stereotyping?

Adam Leinss

Sounds like a licensing issue. Have the user delete the key "MSLicensing" in the registry and then if she can connect from that computer.

pcbrat

Oh my you are right shame on me. How sexist of me! So is it man or woman? Who is the face behind the name?

Dawne

Vladimyr

ASKER

Thanks to MSGeek. After uninstalling and reinstalling the TS client things went fine. This was something I thought about doing, but since the workstation in question is in Omaha and I'm in Kansas City, it was barely an option. The users at that location and all very computer illiterate and it's very hard to do anything without being there, especially uninstalling and reinstalling software. They are so afraid to do everything!

Thanks everyone for your help. All of your suggestions are going into my book for future reference.

Vladimyr

ASKER

Your help is greatly appreciated!!

MSGeek

Glad I could help, what would life be without the unknown and EE?

pcbrat

You are welcome glad all worked out!

Dawne