Windows server 2012 r2 standard remote desktop not working free download
It is a physical server. Couple of weeks ago rebooted it after patches and I haven’t been able to get into it since — well of course except thru local terminal. Who does that anymore??? I would suspect patches this month’s patches BTW but my other server is hunky dory. Califorensics is an IT service provider. I would just start uninstalling all the updates you recently applied until it starts working again.
And, I know you said you checked them all the suggestions in that link Anything in group policy overriding? Also, I know it’s silly, but did you check you are in the Remote Desktop users group? Nothing in the event log. I could even remote registry, remote computer management – everything seemed to be working.
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. I had something similar with a Server 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 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. 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. 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.
It’s not as crazy as you might think, cause it hit the source of my issue right on the nose! 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. 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”. Great suggestion! NOW I can Remote into it! Thanks lots! To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks.
I’ve Googled and come up with nothing. Popular Topics in Windows Server. Spiceworks Help Desk. The help desk software for IT. Track users’ IT needs, easily, and with only the features you need. Learn More ». CoryHamma This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. 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. Do you receive any error messages when you attempt to remote to it? Do the event logs show anything? Tim-H This person is a verified professional. Why isn’t this a VM?
Thai Pepper. Dan This person is a verified professional. CoryHamma wrote: Is the time working properly? I checked the time. It was OK. But good one. That one has caught me with some other things. The only error message was: Nothing in the event log. TravisIT This person is a verified professional. Same exact thing happened to me. Edited Aug 24, at UTC. TravisIT wrote: Same exact thing happened to me. 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. Thanks katewistowicz! Choose your Network name in the right panel. Close Local Policy Editor. Thanks Mark Cockburn. Thanks DMac. This topic has been locked by an administrator and is no longer open for commenting. Read these next
How to enable Remote Desktop (RDP) on Windows server | SSD VPS Servers | VPSie.Step by Step Windows R2 Remote Desktop Services – Part 1 | msfreaks
ThinManager Tech Notes Windows R2 and Remote Desktop Services – 16 At this point, we need to now look at some of the other settings. In the Server Manager, with Remote Desktop Services > Collections > QuickSessionCollection selected, press on the Task drop down shown in the image below, and then select “Edit Properties”. In this video demonstration we will see how to enable remote desktop feature (RDP) in Windows Server R2, as well as we will see how to connect Windows S. Aug 13, · 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 .