New 2012 Server not visible to rest of network in "Network Neighborhood"

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?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Hypercat (Deb)Commented:
Try this: Go to the properties of the NIC on the 2012 server (not the Hyper-V host but the virtual machines) and make sure that, on the WINS tab, the checkbox for "Enable NETBios over TCP/IP" is checked.
Eric_PriceAuthor Commented:
Already done. Didn't help.
Hypercat (Deb)Commented:
I've seen it take a very long time for browse lists to come up in Windows 2008/2012 networks, mostly on workstations though, not servers. And to be perfectly honest I've never quite figured out what's causing it, but it's usually not a huge deal because mostly the client machines are using mapped drives rather than the computer browsing window.  

If you open the computer browsing window and type in a client name (i.e., \\clientname or \\clientname\shared resource) on the address line, does it come up?

Have you tried setting one of your virtual servers as a master browser?
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Eric_PriceAuthor Commented:
I agree. This one has been left in the "correct" way (according to all the internet blog posts) overnight, and still no dice.

Yes, everything on the network works fine except for the browsing. This particular company likes to browse... Other than that, I agree, its rarely an issue in my networks in the past.

I have not set one as a master browser. TBH I don't know off the top of my head to do that any more or if its even relevant. I'll google that later.

I still kinda think its related to the fact that the host isn't a part of the domain. If no one else comes up with anything, Ill try that. Just didn't want to start shotgunning any more than I already had.
Hypercat (Deb)Commented:
I haven't worked with Hyper-V hosts, mostly with VMWare, so I can't comment about the non-domain membership issue.  However, if the virtual machine is a member of the domain, I wouldn't think that it would necessarily be affected by the fact that the host isn't a member.  Is the host set up to use the DNS servers on the domain even though it's not a domain member?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Eric_PriceAuthor Commented:
setting the host to use a domain DNS server didnt affect the outcome.

Neither did joining it to the domain.
having the host as a workgroup member isn't an issue so you're fine on that.

have you checked the firewall on the host though, as this can affect the VMs.

do you have an other VMs on the host or just the two Servers? it would be interesting to know if other machines on the host can be seen or not as this would help identify if the hyper-v host/config was the issue or not.

can the servers see each other in network neighbourhood?
Eric_PriceAuthor Commented:
the two guest servers on the host can see each other, but neither can see the other servers and PCs, and vice versa.

The firewall on the host is currently off while I troubleshoot

There are no other VMs on the host.
Eric_PriceAuthor Commented:
well, ultimately I moved the cable to a different port on the switch and the problem magically went away. *sigh* I hate magic as an answer. There is no earthly reason this should have corrected the issue. It wasnt a VLAN issue (though we never got around to talking about that here). I honestly have no idea why this now suddenly works.

Anyway, Im awarding points based on participation here. Thanks all.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.