My "gamer" -PC has lost its connection to the rest of my LAN, WDlive, laptop.
The laptop can not "see" my "gamer" -PC more. And yet. Do I open a cmd in my "gamer" -PC and writes PING PHOTO PC (called my laptop), then the corresponding fine, but in the Windows network can not be seen, and I can not connect or network drive to it. Oddly enough, I have always had a network drive on "gamer" looking for PHOTO-PC, and this old connection still works fine, even though I reboot both computers

As I see it, so can the PCs well find each other in a CMD, but not in Windows Explorer or Total Commander. Both PCs are members of the same workgroup. I have been through all the settings in "Network and Sharing Center" and they are 110% identical (there are not corrected in them, since that time it worked).
Is there perhaps a service not running? Or a policy that has been changed?

The laptop and WDlive can see each other, and the laptop can easily see the wife's PC when she is on (it can "gamer" -PC'en no longer).

If I create entries in reg.databasen, it connects the network drive just fine after a reboot. See picture for examples of drive Y and Z. Both networking places are available as network drives, and in a CMD prompt with "PING PHOTO-PC" for example.

It is only in Windows Explorer that it can not find the names and / or network sites. Therefore, I believe that it is a service or a policy that has gone wrong.

As seen in the picture, then there is only one PC in the Network, but my network drive is connected to two other "servers" using the homemade key displayed in regedit.

Where am I looking for this annoying error?

Sorry for the language, English is not my first language Click image for larger version