Re: Remote desktop hangs on second invocation

From: Brendan Perez (anon_at_anon.com)
Date: 06/03/04


Date: Wed, 2 Jun 2004 20:43:38 -0700

I have the same problem. It doesn't always happen, but has discouraged me
from using fast user switching unless I have to or have nothing going on my
main signon.

Sometimes it happens after I log out of the second session. The welcome
screen doesn't return and the monitor goes into power saving mode. Other
times it gets to the welcome screen but if I try to log into the first
session or another profile, it happens then. I don't remember if it happens
when I switch between my first sessiona and the second without logging off.

My monitor makes a clicking noise whenever the screen goes blank or switches
modes, and it's at this mode change/blank where the screen either comes back
or goes into power saving mode. I wonder if there is a problem with
terminal services and DirectX.

I also noticed that this problem happened a lot more often whenever NAV 2004
went to scan the floppy disk on log out. I would see the floppy light come
on for the scan and then the screen would shut off. Disabling the scan
floppy on exit seemed to somewhat improve my chances of getting back to the
welcome screen and into the first session.

If I go to my laptop and try to connect to my computer, I do get a
connection, but can't connect to the first session or the one I just logged
out of. I get a message about not being able to reconnect to that session.
I can, however, successfully log into another profile. I can reboot the
computer from here and can log out the disconnected sessions. I still can't
connect to them and the screen doesn't come back. If I logout of this
remote connection, I usually can't get back to it.
I still wonder if this is some sort of issue with the "console" session.

This doesn't seem to be confined to my current hardware configuration. I've
had three different motherboards, the first one with onboard AGP and later a
PCI video card, as well as an AGP card on my second, and two different AGP
cards on my current.

I run the Folding@Home command line client as a service under a different
profile and I know that the application recieves and will terminate upon
receiving logoff messages. It's possible that the application is receiving
these messages when the second profile logs off, but I don't know if this
has any bearing.

When I finish with my video coding, I'm going to disable the Folding@Home
service and try to do lots of switching and loggging off and will get back
to the newsgroup with anything new. If this keeps happening, I may ghost my
current configuration and restore my intial install image-XP, drivers, and
updates.

"meetoo" <anonymous@discussions.microsoft.com> wrote in message
news:B7A62872-8192-48F7-99A5-ECBBD03CED58@microsoft.com...
>
> I hope someone answers your question, as I've had a similar problem.
When I log onto the office computer (uses XP Pro 2002) using Remote Desktop
from home (uses XP Home), I can connect without problems. After I
disconnect, I can reconnect with no problem.
>
> The problem is even after I've disconnected from the office computer, the
people in the office can't log onto the computer and have to do a hard
reboot. Or rather, they can log on using the user name and password, but
all they get is a black screen like you mention.
>
> I thought it might be caused by the Gotomypc software that was also on the
computer, since that was what caused my Remote Desktop connection problems
in the past (having Gotomyc software active in the background caused my
Remote Desktop connection to run at an insanely slow pace). But I've since
uninstalled gotomypc and the black screen problem persists, even though the
Remote Desktop connection runs at a normal pace.
>
>
> ----- Remotely confused wrote: -----
>
> I have been using remote desktop for a year or so with no problems
but recently (past 3 months) I have been having problems. The first time I
use remote desktop it works great. But the second time I use it (without
intervening restart) I get the wallpaper and signon prompt. When I hit enter
after entering userid & PW the screen never goes any further and back on the
actual PC the screen is black and the only way to recover is Power off/on.
This occurs regardless of where I try to remote from. In all cases both OS's
have XP pro. It occurs regardless of the way I end the first desktop
session.This is very irritating and I really do not want to rebuild this
machine.



Relevant Pages

  • Re: Windows 2008 Remote desktop instances
    ... When I disabled it than I could connect to the second session. ... Meinolf Weber wrote: ... parallel remote desktop connection plus one console connection. ...
    (microsoft.public.windows.server.general)
  • RE: Cannot Save file to desktop !!
    ... To make the local drives available in the session follow the steps given ... In the Remote Desktop Connection window, ... 2.Mapping local drives is not available on computers running Windows 2000 ...
    (microsoft.public.windows.terminal_services)
  • Re: AutoLogon Question
    ... a reboot command on the RDP session termination (or just ... >> never blanked out on the remote. ... >> After I use remote Desktop Connection to access the machine and do some ... We do this over the network using the remote desktop ...
    (microsoft.public.windowsxp.embedded)
  • Re: Cant see local network printer from Remote Desktop session over VPN
    ... Kurt wrote: ... Within the remote session, I can ping the network address of the local printer, and can even connect to its administrative "web" page, but I can't print to it. ... If I understand you correctly, you're using remote desktop to connect to a terminal server at the other end, but you're trying to print directly from the terminal server to the network printer at your end. ...
    (microsoft.public.win2000.networking)
  • Re: Cant see local network printer from Remote Desktop session over VPN
    ... Within the remote session, I can ping the network address of the local printer, and can even connect to its administrative "web" page, but I can't print to it. ... If I understand you correctly, you're using remote desktop to connect to a terminal server at the other end, but you're trying to print directly from the terminal server to the network printer at your end. ...
    (microsoft.public.win2000.networking)