0 pts.
 Terminal services client hangs on connection
Hello to everyone
I have a recurring problem with one of the Terminal services clients (MSTSC version 5.0 on OS Win2K SP4):
when I try to connect to any terminal server - a window appears, with plain black (ok, or blue) screen and cursor on it - and hangs forever, not responding to any events.
I found two suggestions in the Internet - first one about the profile color settings (everything`s OK with that),
and the second one about the MTU size ("black hole" routers).
But the problem appears even when i try to connect to a server in the same local network,
and surely - in ths case client and server can exchange average Ethernet 1500-bytes packages, so that is also not the case, I guess.
What is interesting - simply rebooting this client machine solves the problem. For a few days. Then it appears again - until the next reboot.
I`m pretty sure the problem is with the network, but i just can`t figure out _what_ it is, and what can I do instead of rebooting that poor machine...
Thanks.
ASKED: Jun 13, 2007  10:11 AM GMT
UPDATED: March 5, 2008  4:12:06 PM GMT
0 pts.

Answer Wiki:
Please check this link for more tips:
http://groups.google.com/group/microsoft.public.win2000.termserv.apps/browse_thread/thread/eaca71e307ca699e/6336202249b240b6%236336202249b240b6. If the link does not work, here is what was said as a tip: "I assume you have checked the event logs and are seeing nothing unusual. You
might want to try doing a couple of tests with Performance monitor. Do a logon session with Perfmon running to see if you can notice any particular culprits."


Key things initially are memory and CPU utilization. If neither of those hiccups, it will point towards a services or rights related issue during the
logon.
Last Wiki Answer Submitted:  Jun 14, 2007  1:11 AM (GMT)  by  shaktech   0 pts.
To see other answers submitted to the Answer Wiki View Answer History.
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _




 

does the user account you are using login fine from any other client? If so try reinstalling the MS terminal server client software on the culprit machine.

 6,835 pts.