asked on

Cannot initiate an .rdp session to DNS Name after Reboot (2K8 R2)

Just as the title says, I'm having a problem initiating a .rpd session after the target computer is rebooted.

Background:
- Target computers are 2k8 R2 servers.
- Host server is 2k8 R2

I have a 2k8 R2 level AD running on a small network. If I terminal in after a server is running then the .rpd session intiates just fine. If I reboot the server, I'm then forced to wait roughly 15-30 mins before the dns hostname becomes available again.

Using the ip address of the system does initiate a session.

Any ideas? I'm thinking dns and something like not registering upon boot... but I've never dealt with this area much.

Will Szymkowski

First thing would be to check the event logs on the server in question. Another thing i would check are all of the services to ensure that they are starting, especially the "netlogon" service.

Thanks

Will

Michael McCabe

ASKER

Thanks for the reply. I need to get back in front of a station to check, may be a little bit later.

Michael McCabe

ASKER

Just to be thorough I recreated the issue with cleared logs. Here is the sequence.

1.) Login to target server via .rdp session using hostname.

2.) Cleared logs on target machine.

3.) reboot target machine. (watching via ping when it's back up.)

(server successfully reboots)

4.) Attempt to login to target server via .rdp session using hostname.

First error: