TSC Explorer Window Error HELP!

  • Thread starter Thread starter C. Clark
  • Start date Start date
C

C. Clark

I posted this in W2000 Terminal Services forum as well,
with no response... (Maybe a different audience will
help?)
I have been having a problem when using any version of
Terminal Services Client (Remote Desktop Connection) and
Windows 2000. Whenever there is an explorer (Internet AND
Windows) window open, I get an error on the client
computer and the connetion closes. I then have to play
wackamole with the program to try and close the window
immediately after logging on again.
My host computer is running Windows XP Pro and the
problem only seems to occur when running TSC on NT based
machines (XP, 2000).
I have no problems opening an explorer window in TSC with
my HPC (CE 2000), but this is not always an option as I
am not always around a wireless network.
Any help would be greatly appreciated...
Thanks.
Chris
 
Have you observed whether there's some abnormality at the host end when the
explorer window is open--high CPU usage, for example?

You might be able to spot this with Task Manager, but doing it remotely will
be tricky, obviously--better to do it sitting at the host.
 
I can't do anything at the host end to monitor these
things, as my host comptuer is automatically sent to the
Switch Users screen whenever I log in remotely.

I have noticed that if I can get any other window to cover
up the explorer window (or get it minimized) that it
doesn't quit. Also the time it takes to cause the error
differs from time to time (almost like it takes the client
a little bit to "realize" that the explorer window is
open.)
This never lasts more than 1 second, but sometimes it does
last that long, other times it doesn't even get the screen
drawn before it quits.
 
Back
Top