Before today I had a handful of PCs and two existing 2008 R2 servers on a single subnet network. You could browse a list of PCs and the two servers from the "Network Neighborhood".
I added a new 2012 Hyper-V host (free version) and a 2012 Std guest. I joined this guest to the domain with a static IPv4 address (disabled IPv6 - same as existing servers) and added ADDS, DNS, DHCP, File, and Print roles.
All regular network functions appear fine (pings, network access via \\server\share method, dcdiag, DNS, DHCP functioning, etc) but I cant see the server from the other PCs and servers in "Network Neighborhood".
From the 2012 Std server I can see one client PC and itself in Network Neighborhood
From any other client or server I can see all the other servers and clients, but NOT the new 2012 Std server.
Turning the firewall off the host server and the guest server doesnt help.
Network Discovery is turned on (it wasnt initially)
Ive seen several articles about this situation in 2008 R2 that required turning on 4-5 services that are turned off by default (Computer Browser, SSDP Discovery, UPnP Device Host, Function Discovery Resource Publication, Function Discovery Provider host, Link Layer Topology Discoverer Mapper) and I followed those directions, but the issue remains.
Does anyone have any other thoughts on what the issue is here?
Edit: As a followup, if I run net view from either of the two old servers (or any client PCs for that matter) I get a list like
The lists are identical, but both Windows Server 2012 Standard editions running as guests on that 2012 Hyper-V host are missing, despite being on the same subnet and part of the domain.
Similarly, if I run net view from \\PROBLEM-SERVER I see only one entry in the list
From either side if I net view \\PROBLEM-SERVER or net view \\SERVER-01 I am presented with all the shares, etc that one would expect.
The one PC visible in both is an artifact I think. Its called tsclient, isnt an actual PC, and cant be pinged, addressed, or even stared at cross eyed. *shrug*
One thing different from what I normally do - The hyper-v host in this case is just in its own workgroup, and not joined to the domain (since the domain isnt even up when the host comes online once the old servers are retired) Perhaps this is part of the issue?