I'm having a strange issue connecting to my Server 2016 using Remote Desktop. I have an existing connection that works through RDCMan, but whenever I try to access the server with Remote Desktop Connection or set it up as a new server in RDCMan, I get a 'cannot connect' error. I can still ping the server without any problems, but it doesn't even get to the point of asking for my credentials. Any advice on how to resolve this?
3 Answers
Check if the network adapter has switched to a different profile, like public or private, and ensure network discovery is enabled in your sharing settings. Sometimes these settings can cause connection issues without warning.
The adapter is set to 'Domain network' profile, and network discovery is turned on, so that should be fine.
I've faced a similar problem, but on Server 2025. The first attempt to connect would fail, but a second one would usually work. Just out of curiosity: do you have IPSec enabled, or have a PKI with CRL or OSCP lookups in place? Also, how do you handle authentication? Just passwords, or are you using smart cards?
No IPSec since I'm on the same LAN as the server, and I don't have a PKI setup either.
I'm not even getting to the credential part; it feels like Remote Access is disabled.
Have you checked your Windows Firewall settings? Sometimes it can block connections without any alerts or notices.
I've turned off Windows Firewall completely, and I even uninstalled BitDefender temporarily, but it didn't help.
Good point! I've run into a similar issue before, so it’s worth checking.