Remote login

[D.Currie]

I use remote desktop extensively...on multiple computers, different
locations. It used to be that I could reboot a remote computer (for example,
after doing a Windows update that required it) and after the reboot
completed, I could log back into the remote computer. Now, I can't log in
remotely unless I've first logged in to the specific machine locally.
Needless to say, this is just a bit annoying.

Any ideas?

 

[Rick \Nutcase\ Rogers]

Hi,

You are not alone. I've no ideas for you yet, as this has been an issue for
a number of people. Myself included. What I do currently is set any machine
that I use for remote desktop to autologon on system reboot, with a 1 minute
"non-use" timeout back to the logon screen. I am currently still trying to
isolate what caused this change in behavior (my theory is a Windows Update
sometime in the past 12 months, but there are a number of them), as this
does not occur in a new unupdated installation.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[D.Currie]

Hmmm.

I just reformatted one of my computers, set it up with dual boot, updated
everything, and I can log in remotely just fine after booting. Maybe it
fixed itself with the latest updates. I'll have to try the other computers
as well and see if any of the others are working again.

I don't reboot all that often, but if I'm doing the kind of maintenance that
requires a couple of reboots, it can be annoying to have to go to the
computers to log in.

Here's a related oddity; maybe you've heard of this one. With one of my
computers, once I've connected remotely, if I connect locally, I get a blue
screen. I can connect remotely through any computer without a hitch; it's
the local connection that crashes. But if I connect locally after booting,
there's no problem at all.

I know it would help to have the error message, but it's been months since
I've done this, and it when it happened it wasn't that much of an issue. I
never use that computer locally and I'm not inclined to create a blue screen
error just to test it.

D.C.

Hi,

You are not alone. I've no ideas for you yet, as this has been an issue for
a number of people. Myself included. What I do currently is set any machine
that I use for remote desktop to autologon on system reboot, with a 1 minute
"non-use" timeout back to the logon screen. I am currently still trying to
isolate what caused this change in behavior (my theory is a Windows Update
sometime in the past 12 months, but there are a number of them), as this
does not occur in a new unupdated installation.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[Rick \Nutcase\ Rogers]

Nope, haven't seen that - and I do that all the time (connect through both
the LAN and via the 'net). The stop error message might help (if you feel so
inclined to to recreate the conditions where it happens), but offhand I
would suspect something in the nic drivers.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

Hmmm.

I just reformatted one of my computers, set it up with dual boot, updated
everything, and I can log in remotely just fine after booting. Maybe it
fixed itself with the latest updates. I'll have to try the other computers
as well and see if any of the others are working again.

I don't reboot all that often, but if I'm doing the kind of maintenance that
requires a couple of reboots, it can be annoying to have to go to the
computers to log in.

Here's a related oddity; maybe you've heard of this one. With one of my
computers, once I've connected remotely, if I connect locally, I get a blue
screen. I can connect remotely through any computer without a hitch; it's
the local connection that crashes. But if I connect locally after booting,
there's no problem at all.

I know it would help to have the error message, but it's been months since
I've done this, and it when it happened it wasn't that much of an issue. I
never use that computer locally and I'm not inclined to create a blue screen
error just to test it.

D.C.