Wow. That’s some fancy troubleshootin’, Tex…
In general, if you can see your PC under MEDIA SERVERS but *NOT* under Network Shares, then you can assume:
1- The network is functioning, at least partially.
2- There’s an issue with “Browser” services somewhere on your network.
Media Servers operate under the UPnP protocol, which uses a RELIABLE network transport (TCP/IP) for all functions. If you can see the Media Server, you can assume that your WD and your PC are able to connect to each other, but it doesn’t guarantee that it’s functioning “WELL.”
The SMB Browser Services all make use of NON-Reliable transports (UDP) which provides no guarantee that transmitted traffic will be received by the destination.
I once had an issue where I could play some files fine using Media Server, but NONE of my servers ever appeared in Network Shares for more than an hour. Then they showed up, and the movie played for a few minutes, then disappeared again. It turned out that my network switch was failing, and it was losing about 50% or more of the packets. TCP will work around that. UDP will not. Since Browser uses UDP, the servers never appeared in the list.
Depending on the Browser elected, it can take 20 minutes OR MORE for a device to show up in the server list.
The Windows Live Sign-in Assistant usually does not prevent a server from appearing in the WDTV’s List, it just prevents you from Logging In to that server (Invalid User-ID or Password! error).
So, I really don’t think you’ve found your root cause, but if it’s all working, I’d leave it alone!
In summary: You do NOT need IPv6. If you DO have IPv6, it will NOT interfere with the function of the WDTV. If you use ONLY IPv6 (in other words, you disable IPv4) that will certainly break.
Different VPN software behaves different ways. My corporate VPN software (Cisco) will break EVERYTHING that’s not on the corporate network. This is what happens if VPN software doesn’t allow “Split Tunnels.” Some VPN software also has its own Firewall to prevent certain network traffic from being allowed when the VPN is up.
So, I don’t really know if that had anything to do with your issue…