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...
Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services
http://mypcassistant.blogspot.com/
Problem still persists.
"Hank Arnold" wrote:
> .
>
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
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/