[SOLVED] Unable to remote desktop LAN computers after router upgrade

The Fix:

Make your Windows 10 device discoverable (which will convert the network from Public to Private.)

If you were using the computer when the new connection was detected and connected to, Windows 10 should have prompted you when it detected the new network asking if you wanted to make it discoverable.  If you missed that prompt or answered "No" when it asked, you will need to reconfigure that setting.

Steps to fix:

On the machine you want to control, do the following...

• Hit your "Start" button and type "ethernet"
  
  
• Click on "Change Ethernet settings"
• On the Ethernet settings view, click the name of the network you need to configure.
  (In my case, it was "Network 11")
  
• Toggle the "Make this PC discoverable" switch to "On"
  
• Try connecting via Remote Desktop to said machine with another device on your network

Why it Happened:

After upgrading my router tonight, all of my Windows 10 devices detected a new network and automatically decided they would be "Public" and defaulted the device to be undiscoverable.

The problem for me was, one of my devices is a server that has no keyboard or monitor hooked up to it.  I needed to remote in to make sure some services were up and running again.  I had to track down a monitor, DisplayPort-to-HDMI cable and keyboard to be able to access the machine and get it configured so I can remote again.

While frustrating, this is actually a useful feature of Windows 10 to assume that any new network if potentially dangerous and default it to Public.

I hope this helps save someone a few hours of frustration thinking your new router is defective!

Windows XP Computer Can't Be Seen Properly on Network

I installed Windows XP Pro fresh on a new machine I built at home. I'd done this several times in the past and was able to successfully see all those machines on the network with no problem.

This one was different, however. I could do everything I wanted from this particular machine to the others in my network (pushing/pulling files to other shares on other machines), but I couldn't get the others to talk to this one.

The only difference with this computer's install was that it was done from the Windows XP SP3 CD. My prior installs were done on earlier XP versions.

It seems the SP3 CD will firewall your connection by default and NOT count "File and Printer Sharing" as an exception.

To resolve it, you need to get that Exception enabled (recommended) or disable your Windows Firewall for the connection (not recommended).

To enable the exception in Windows Firewall (assuming Windows Firewall is enabled on the connection):

1. Open Network Connections (Start >> Settings >> Control Panel >> Network Connections; or use your favorite quicker means...)
2. Right-click the offending connection >> Properties >> "Advanced" tab
   
3. Click the "Settings" button for Windows Firewall >> "Exceptions" tab
   
4. Check the "File and Printer Sharing" checkbox
5. Click OK on the Windows Firewall dialog.
6. Click OK on the Connection Properties dialog.
   

Screenshot
in the non-working state
(click to see full-size)

You should now be able to ping the computer by name and access its file shares, etc. on your network.