Can't Remote Desktop into domain controller

[toffee_paul]

Hi all,

Had a problem for a couple of weeks where I can't remote into our Server 2012 R2 DC. I can remote into any other device on the network bar this including the Hyper-V host on which the DC is virtualised on.

It just stays stuck on "Initiating remote connection" for about 15 seconds then throws up the "can't connect to the remote computer"

Here's what I've tried altready.

 

1. Checked all required services are running - they are
   
2. Checked pinging DC works - it does
   
3. Rebooted DC - still happens
   
4. EDIT: Also tried remoting in from other desktops to the DC, all the same, I can remote to everything apart from this DC.
   

Any ideas? I'm thinking a dodgy Windows Update but can't see anyone else with the same issue.

Edited May 24, 2018 by toffee_paul

[SHimmer45]

An update hasnt turn on or made changed to your firewall settings on the DC or made changes to what version of RDP client can connect to the DC

can you connect out other machines on from the DC?

[ollyyllo]

Is "Allow remote desktop to this computer" enabled? are you in the user group of allowed users?

[toffee_paul]

An update hasnt turn on or made changed to your firewall settings on the DC or made changes to what version of RDP client can connect to the DC

can you connect out other machines on from the DC?

 

There's update KB 4103718 which changes what happens if unpatched clients connect to patched servers etc but all clients and services are completely up-to-date and I've gone through all the MS bumf on it and checked the settings are all correct.

No changes to firewall either.

 

- - - Updated - - -

 

Is "Allow remote desktop to this computer" enabled? are you in the user group of allowed users?

This setting is enabled and only group that has access is the Administrators group of which I am a member.

[strawberry]

can you connect via Ip/hostname?

[Jawloms]

Is the firewall on or off? If it's on, turn it off and see if it then works. If it does, turn it back on and figure out what exceptions you need.

[toffee_paul]

Is the firewall on or off? If it's on, turn it off and see if it then works. If it does, turn it back on and figure out what exceptions you need.

 

Just tried this, no different

 

- - - Updated - - -

 

can you connect via Ip/hostname?

 

No luck, same thing happens.

[Davit2005]

Sorry to state the obvious first but Is remote Desktop allowed/Configured on the DC in Remote Settings?

 

Any firewalls or switch ACL's in the way?

 

Is this the same DC you were having an issue browsing to the Internet on back in April?

Edited May 24, 2018 by Davit2005

[ollyyllo]

Can you connect to the DC via Hyper-v Manager?

[toffee_paul]

Sorry to state the obvious first but Is remote Desktop allowed/Configured on the DC in Remote Settings?

Yes this is configured fine.

Any firewalls or switch ACL's in the way?

No checked all these.

Is this the same DC you were having an issue browsing to the Internet on back in April?

It is, although I found that Malwarebytes was responsible for causing that issue and rectified it by uninstalling.

 

Remote desktop to from every other device is working normally but can't connect to the DC from any device.

 

- - - Updated - - -

 

Can you connect to the DC via Hyper-v Manager?

Yes this is the only way in to the DC at the moment and that's how I've been logging on to the server.

[evatheale]

This worked when we had a similar issue:

 

Login via the Hyper-V Console

Start > Right Click Computer > Properties > Remote Settings > Check for the "Enable Windows Firewall exceptions warning". And make sure RDP is enabled.

 

Then to add exception go to

 

Start > Control Panel > Windows Firewall > Advanced Settings (Right hand side) > Inbound Rules > Right click > New > Predefined Rule > Remote Desktop Services > Tick the only option > Next and Finish

[toffee_paul]

Right it's fixed. For some reason under the Network and Sharing Centre it was the showing the DC as being a Public network and not Domain. After restarting the Network Location Awareness service it automatically picked up the Domain network and remoting into the DC works fine again.

 

Not sure why this happened so will need to read up on this a little. Hope this helps if anyone has the same problem.