RDP to Win2K Servers fails after reboot

For about the past 6 months or so, I've noticed an odd occurrance.
If I reboot any of my Win2K servers for any reason (usually after the
monthly Windows Updates) after they restart I can't open an RDP session to
them. All of our servers are Win2K3 R2 - about 16 or so. About half are
also 64-bit.

We use RDP to remotely manage them.

A second reboot usually resolves the problem, but this is now a regular
occurrance. First, reboot for any reason and the server will not accept an
RDP session. Reboot again and you're fine.

There are no events in the event logs about any failed services or anything
pertaining to Remote Access or Terminal Services.

Is this a known issue for which there is a workaround?

TIA
Rick

Library Sysadmin wrote:
> For about the past 6 months or so, I've noticed an odd occurrance.
> If I reboot any of my Win2K servers for any reason (usually after the
> monthly Windows Updates) after they restart I can't open an RDP session to
> them. All of our servers are Win2K3 R2 - about 16 or so. About half are
> also 64-bit.
>
> We use RDP to remotely manage them.
>
> A second reboot usually resolves the problem, but this is now a regular
> occurrance. First, reboot for any reason and the server will not accept an
> RDP session. Reboot again and you're fine.
>
> There are no events in the event logs about any failed services or anything
> pertaining to Remote Access or Terminal Services.
>
> Is this a known issue for which there is a workaround?
>
> TIA
> Rick

I have about a dozen 2003 R2 servers running and I've never seen this. I
also do all my server management via RDP. There must be something going
on. Have you verified that all the "automatic" services are actually
started after the first reboot?

Are you allowing an automatic reboot after any updates? It does seem to
be a problem for some users...

http://techrepublic.com.com/5208-623...ontent;leftCol
--

Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services
http://mypcassistant.blogspot.com/

No. We don't allow the WSUS server to automatically reboot servers. For
servers, we only notify that updates are available.

Problem still persists.

"Hank Arnold" wrote:

> Library Sysadmin wrote:
> > For about the past 6 months or so, I've noticed an odd occurrance.
> > If I reboot any of my Win2K servers for any reason (usually after the
> > monthly Windows Updates) after they restart I can't open an RDP session to
> > them. All of our servers are Win2K3 R2 - about 16 or so. About half are
> > also 64-bit.
> >
> > We use RDP to remotely manage them.
> >
> > A second reboot usually resolves the problem, but this is now a regular
> > occurrance. First, reboot for any reason and the server will not accept an
> > RDP session. Reboot again and you're fine.
> >
> > There are no events in the event logs about any failed services or anything
> > pertaining to Remote Access or Terminal Services.
> >
> > Is this a known issue for which there is a workaround?
> >
> > TIA
> > Rick
>
> I have about a dozen 2003 R2 servers running and I've never seen this. I
> also do all my server management via RDP. There must be something going
> on. Have you verified that all the "automatic" services are actually
> started after the first reboot?
>
> Are you allowing an automatic reboot after any updates? It does seem to
> be a problem for some users...
>
> http://techrepublic.com.com/5208-623...ontent;leftCol
> --
>
> Regards,
> Hank Arnold
> Microsoft MVP
> Windows Server - Directory Services
> http://mypcassistant.blogspot.com/
> .
>

How long after the reboot do you wait. It can take some minutes after a local
login is possible before a RDP login can be done. I too have been using RDP and
never had an issue. The only things I can think of are a) too quick and the
services are not started. b) too many existing session in Admin mode (more than
2)


On Sun, 20 Dec 2009 09:42:01 -0800, Library Sysadmin
<> wrote:

>No. We don't allow the WSUS server to automatically reboot servers. For
>servers, we only notify that updates are available.
>
>Problem still persists.
>
>"Hank Arnold" wrote:
>
>> Library Sysadmin wrote:
>> > For about the past 6 months or so, I've noticed an odd occurrance.
>> > If I reboot any of my Win2K servers for any reason (usually after the
>> > monthly Windows Updates) after they restart I can't open an RDP session to
>> > them. All of our servers are Win2K3 R2 - about 16 or so. About half are
>> > also 64-bit.
>> >
>> > We use RDP to remotely manage them.
>> >
>> > A second reboot usually resolves the problem, but this is now a regular
>> > occurrance. First, reboot for any reason and the server will not accept an
>> > RDP session. Reboot again and you're fine.
>> >
>> > There are no events in the event logs about any failed services or anything
>> > pertaining to Remote Access or Terminal Services.
>> >
>> > Is this a known issue for which there is a workaround?
>> >
>> > TIA
>> > Rick
>>
>> I have about a dozen 2003 R2 servers running and I've never seen this. I
>> also do all my server management via RDP. There must be something going
>> on. Have you verified that all the "automatic" services are actually
>> started after the first reboot?
>>
>> Are you allowing an automatic reboot after any updates? It does seem to
>> be a problem for some users...
>>
>> http://techrepublic.com.com/5208-623...ontent;leftCol
>> --
>>
>> Regards,
>> Hank Arnold
>> Microsoft MVP
>> Windows Server - Directory Services
>> http://mypcassistant.blogspot.com/
>> .
>>
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.

That's been my experience, also. It can take a while, especially if the
server is slow or has a lot of stuff loading at boot time.

If you try to open too many "admin" sessions, you get a different message...

--

Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services
http://mypcassistant.blogspot.com/

DaveMills wrote:
> How long after the reboot do you wait. It can take some minutes after a local
> login is possible before a RDP login can be done. I too have been using RDP and
> never had an issue. The only things I can think of are a) too quick and the
> services are not started. b) too many existing session in Admin mode (more than
> 2)
>
>
> On Sun, 20 Dec 2009 09:42:01 -0800, Library Sysadmin
> <> wrote:
>
>> No. We don't allow the WSUS server to automatically reboot servers. For
>> servers, we only notify that updates are available.
>>
>> Problem still persists.
>>
>> "Hank Arnold" wrote:
>>
>>> Library Sysadmin wrote:
>>>> For about the past 6 months or so, I've noticed an odd occurrance.
>>>> If I reboot any of my Win2K servers for any reason (usually after the
>>>> monthly Windows Updates) after they restart I can't open an RDP session to
>>>> them. All of our servers are Win2K3 R2 - about 16 or so. About half are
>>>> also 64-bit.
>>>>
>>>> We use RDP to remotely manage them.
>>>>
>>>> A second reboot usually resolves the problem, but this is now a regular
>>>> occurrance. First, reboot for any reason and the server will not accept an
>>>> RDP session. Reboot again and you're fine.
>>>>
>>>> There are no events in the event logs about any failed services or anything
>>>> pertaining to Remote Access or Terminal Services.
>>>>
>>>> Is this a known issue for which there is a workaround?
>>>>
>>>> TIA
>>>> Rick
>>> I have about a dozen 2003 R2 servers running and I've never seen this. I
>>> also do all my server management via RDP. There must be something going
>>> on. Have you verified that all the "automatic" services are actually
>>> started after the first reboot?
>>>
>>> Are you allowing an automatic reboot after any updates? It does seem to
>>> be a problem for some users...
>>>
>>> http://techrepublic.com.com/5208-623...ontent;leftCol
>>> --
>>>
>>> Regards,
>>> Hank Arnold
>>> Microsoft MVP
>>> Windows Server - Directory Services
>>> http://mypcassistant.blogspot.com/
>>> .
>>>