Hyper-V guest machine cannot connect to anything other than the host and another hyper-v server on the same host. Cannot contact gateway

I have 2 hyper V guests on the same host. They are both configured the same in regards to the network cards and both have the same gateway and DNS servers. They are on the same domain, the one that is functioning properly is a domain controller. I have tried removing and reinstalling the NIC on the machine acting up but am not able to get any change in connectivity, I can only contact the host and its contents. I am using Server Standard 2012 R2 for both the host and guest OS's. Any ideas on what I should do other than do a full reload on machine acting up?
PIMSupportAsked:
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.

Cliff GaliherCommented:
Is the virtual NIC connected to the right virtual switch? The described behavior is indicative of an internal virtual switch instead of an external one.

The other low-hanging fruit possibility is a misconfigured subnet mask, which isn't unique to Hyper-V. Basic networking...to use a gateway, the server has to properly know what traffic is local and what traffic needs to be routed. An ipconfig would be helpful.
0
PIMSupportAuthor Commented:
There is only one switch configured, both hyper-v guests are on that switch and it is an external switch. I double checked the subnet mask and thank god that was not off or that would have been embarassing. ipconfig attached
0
PIMSupportAuthor Commented:
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Cliff GaliherCommented:
Next steps would be nslookup tests. Traceroute tests. Ping tests. See where things are choking up.
0
PIMSupportAuthor Commented:
Right, I ping tested earlier and  I can ping the host, I can ping the other hyper-v guest, but I cannot ping the gateway or anything outside of the NIC on the host.

Had not tried a tracert, that just comes back with a destination host unreachable.

nslookup is able to bring back results for anything I try because the other guest on the hyper-v host is a domain controller so it is pulling info from that DNS
0
Cliff GaliherCommented:
Is there another machine on the local network that does respond to ping from the host and the working VM *and* fails to respond to the dysfunctional VM? Both facets are important. After all, a software firewall can block pings, and then it wouldn't respond to working VMs either, so isolating the differences in behavior is important.
0
PIMSupportAuthor Commented:
Yep, I can ping another domain controller on the network from both the host and functional vm. The dysfunctional vm cannot ping it.
0
PIMSupportAuthor Commented:
BTW the firewall on all of these machines is off.
0
Cliff GaliherCommented:
Very strange. I don't have any easy suggestions I can make at this point.
0
PIMSupportAuthor Commented:
Also, as of right now, because of port space issues, there is only 1 NIC plugged in currently.

That being said, when we remove the virtual switch and create a new one it marries up with the first guest machine that connects to it and allows network access. The second machine that is cut on has these issues where it can't contact the default gateway and acts like it is part of the internal network only. I will be plugging in the second NIC tomorrow to see if that helps...do you think the fact these 2 guests and the host are on the same NIC is causing my issue?
0
David Johnson, CD, MVPOwnerCommented:
do you think the fact these 2 guests and the host are on the same NIC is causing my issue?  NO as I have multiple guests on the same nic, many guests use different vlans even.
Check your Virtual Switch settingCheck your Networking Setting -- don't use legacy adapter
0
Cliff GaliherCommented:
No, the way the virtual switch code works, the physical NIC becomes a layer 2 port. All layer 3 stuff happens at the VM level. The only time I've seen issues like you describe is when people have messed with the physical NIC settings after creating the switch (like trying to enable IPv4 again.)  But honestly, at that point, trying to troubleshoot in a forum becomes a fame of 20 questions and still has a very low success rate. I'd either build up a new VM, and if it works, migrate the data. Or call in a hyper-v specialist and pay them. It saves money in the long term.
0

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
PIMSupportAuthor Commented:
Come to find out the switch that this is plugged into has a port-security set at 3 so I am exceeding that maximum since there is a dummy switch between them funneling them into 1 port. Thanks for the suggestions and help guys. Handing out points for the good suggestions and walkthrough
0
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.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.