Remote desktop closes after 5 idle minutes since last update

[Ingot]

Greetings:

I have and XP Pro box, and I use XP standard on my laptop to make remote
desktop connections to it across my wireless network. Often, the laptop
sits next to me for extended periods while I do other things, I use it to
keep an eye on the main box.

Last night, after the last Windows Update came down, five minutes of idle
causes Remote Desktop to close.

I don't mean the connection drops. On the laptop the Remote Desktop
application simply closes. If I'm trying to keep an eye on something over a
period of hours, I'd have to completely restart Remote Destop, connect, and
log on again 12 times an hour.

I've looked for idle time-out settings, and can't find them.

Can anyone tell me if I'm missing a setting?

Failing that, is there a way to find out WHAT is closing Remote Desktop?

Chris

 

[Sooner Al [MVP]]

There are group policies that control idle user sessions.

http://support.microsoft.com/kb/294751/en-us

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...

 

[Ingot]

There are group policies that control idle user sessions.

http://support.microsoft.com/kb/294751/en-us

Ok, I've checked these. They're all unused.

It seems odd to me that the CLIENT is closing down Remote Desktop
completely, if the server was just diconnecting it, I'd get a disconnect
message on the client right?

I've turned off all screen savers, so it can't be that...

Is there any way to prod a Win XP Home Edition system into telling me what
is closing an application?

Chris

 

[Sooner Al [MVP]]

Possibly the event log may provide clues...

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...

 

[Ingot]

Possibly the event log may provide clues...

Oh my.

LOL, you don't have any way of knowing this of course, but I'm a Network
Administrator, and have been help desk, support, server admin, security
chief...

Event log is the FIRST place I go!



In any event, I THINK I got it, even if I don't fully understand it.

I noticed these two systems had different workgroup names, so I changed the
laptop one to match the serving system.

Now WHY this would cause RD to shut down? Why it would take five minutes of
inactivity to do so? WHY it would just have started since the last patch?

Haven't a clue. Maybe the authentication I typed in to access the main
system expired after a certain amount of time.

Who knows?

Anyway, it seems to be working now. Thanks for the help!

Chris