Remote Desktop can t connect to the Remote computer Server 2012 R2

Do you receive any error messages when you attempt to remote to it?

Do the event logs show anything?

1

I would just start uninstalling all the updates you recently applied until it starts working again.

Why isn't this a VM?

1

Are you trying to connect with IP, or DNS name? If DNS name, does it resolve to the proper IP address?

And, I know you said you checked them all [the suggestions in that link...], but did you try to reboot the server after you checked them all?

0

CoryHamma wrote:

Is the time working properly? For example, is the machine you're connecting from, as well as this server, set to synchronize with a NTP server? I've fixed issues before that occurred when time drift left one of the PCs too far off from each other.

I checked the time. It was OK. But good one. That one has caught me with some other things.

0

Anything in group policy overriding? Also, I know it's silly, but did you check you are in the Remote Desktop users group?

0

The only error message was:

Nothing in the event log. I could even remote registry, remote computer management - everything seemed to be working.

Tried IP & DNS name.

I fixed it but I don't understand why this fixed it. But I'm not going to question why. It's working again.

I went into the Remote tab of computer properties - turned off allow RDC and then turned it back on. That's it. It's working now. Don't know why I didn't try that before. I've been messing around with this for a week or so on and off when I had time.

CRAZY!! Ugh!

1

I had something similar with a Server 2012 box in recent memory, I just can't remember what fixed it ultimately. I'm happy at least it wasn't too much more than just re-enabling boxes :-]

1

Same exact thing happened to me.

I found that somehow, the current network got switched to Public Network instead of Private Network. RDP is automatically set to deny connections when it's set to a Public Network. I switched my network type to Private and it fixed everything.

EDIT: You can test this by going into the Windows Firewall settings > Inbound > Remote Desktop - User Mode [TCP-In] > Advanced Tab > Check the Public box, then try and RDP into the server.

Edited Aug 24, 2016 at 19:52 UTC

2

TravisIT wrote:

Same exact thing happened to me.

I found that somehow, the current network got switched to Public Network instead of Private Network. RDP is automatically set to deny connections when it's set to a Public Network. I switched my network type to Private and it fixed everything.

EDIT: You can test this by going into the Windows Firewall settings > Inbound > Remote Desktop - User Mode [TCP-In] > Advanced Tab > Check the Public box, then try and RDP into the server.

I checked that. I've had so many issues with Win7, 8, 10 doing screwy things like that I sort of expected it. But it was good. I still can't believe turning RD off and back on again fixed it. Windoze!

1

I know this sounds crazy, but I've been having my 12servers changing from the "domain" network to a work or public network [when you hover over the network icon down by the time]. The only way I could force this to recognize that the IP was part of my domain network was to toggle off or on IPv6. I only use IPv4, but I couldn't figure out any other way. Your firewall settings are probably preventing RDP on non-domain networks.

2

I've had lots of goofiness with IPv6 turned on - on Server 2012 & sometimes on Win10 boxes too. I don't understand why if you don't have it turned on anywhere else - switches, etc. No "one" else should be seeing it in a switched environment if the switches aren't passing the traffic...

Regardless I turn it off on everything that has the option. i hope I'm retired by the time I need IPv6 on the inside of the firewall.

2

It's not as crazy as you might think, cause it hit the source of my issue right on the nose! We had a power fluctuation, which caused the server to reboot hard [despite an APC3000RS Smart UPS in place - checking that out now]. The hard reset must have resulted in a fault on the network adapter as it was not showing a connection to the domain/private network. I was able to ping the server's IP address just fine, shared directories were accessible but could not connect via remote desktop.

I disabled and re-enabled the adapter on the server, and it came back up connected to our domain. After that, remote desktop sessions worked as normal.

Thanks katewistowicz!

2

A GUI way of making this change:

Hit Winkey R to open Run prompt and type gpedit.mscNavigate to: Computer Configuration/Windows Settings/Security Setting /Network List Manager Policies.Choose your Network name in the right panel.
Note: To show networks not currently connected, right-click Network List Manager Policies in the left pane and choose Show All Networks.

Go to Network Location tab and change the Location type from Public to Private.

Close Local Policy Editor.

0

Thanks Mark Cockburn.

Disabled and Enabled the network device and all is well again. One additional note. In my case, the adapter not being connected to the domain meant that the adapter reverted to using the default Firewall profile of "Guest or Public Network" instead of "Domain Networks". RDP connections are not allowed in the Public Network profile. Once I disabled and reenabled the adapter, the adapter saw the domain and the Firewall profile automatically flipped back to "Domain".

Thanks

DMac

0

Great suggestion! For months I was unable to Remote into one Server 2012r2, and followed your advice to look at Windows Firewall, Advanced Settings, and then enable the Remote Desktop rules for User Mode [TCP-in], User Mode [UDP-in] and Shadow [TCP-in]. NOW I can Remote into it! Thanks lots!

0

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.