I just had a weird experience with my new ASUS RT-AX88U router (which I’m using as a wireless access point, or WAP). I won’t bore you with the details (read about it in my recent blog post for Windows Enterprise Desktop, if you like) but I will say I had to reset all of my wireless network connections to get my 802.11n wireless adapters working again. Immediately after that, I tried to remote into one of those machines and got the old, familiar “can’t connect” message shown in the following screencap. “Egad!” thought I to myself, “I bet the network profile got reset from Private to Public.” Alas, I was right. And returning the status from Public to Private did the trick. Once I made that change, I was able to RDP into the target system without further difficulty.
I am all too familiar with this error message and its typical causes.
Luckily for me, the usual suspect was guilty!
[Click image for full-sized view.]
Making the Status Change That Fixes the Problem
The repair comes from clicking Settings → Network & Internet → Change connection properties in the Network Profile. I saw that the Public radio button was checked, so I checked the Private radio button instead, like this:
After I made that change, I was able to RDP to the target machine without further difficulty. If you ever find yourself in a similar boat after a network reset (or adding a new wirless network, which is essentially what resulted from my actions), the same change may do the trick for you, too. Give it a try!
Author: Ed Tittel
Ed Tittel is a 30-plus-year computer industry veteran. He’s a Princeton and multiple University of Texas graduate who’s worked in IT since 1981 when he started his first programming job. Over the past three decades he’s also worked as a manager, technical evangelist, consultant, trainer, and an expert witness. See his professional bio for all the details.