Performed that action, was again able to ping our troubled workstation from HyperV3 as well as VMCustomers. While I was removing the switch I saw the MAC address range under the switch, clicked on it to see if there was anything worthwhile in there and read the message about "Changing this setting does not affect network adapters that have already been configured." so I figured I'd delete my Virtual Switch, re-create it, and this time Remove the Network adapters from the Virtual Machines and re-add them instead of just pointing them to the new switch. So I did some reading online, didn’t really find anything, so I decided that I was going to try my removal of the Virtual Switch again and see if it worked. ![]() Back on HyperV3, I attempted to ping the users workstation again and appeared to be back to the drawing board, as I was getting the "Destination host unreachable." message again. Short time later, the user notified me that they couldnt access a different VM on HyperV3, and now they lost access to VMCustomers again. I let the user know they should be in business and went back to bringing my other VM's back online. I went to the troubled workstation and was happy that I could then ping VMCustomers. I went into the Virtual Switch Manager, removed my Virtual Switch and viola! I could then ping the troubled users workstation, happy what that change, I re-created the Virtual Switch, associated it to VMCustomers, got it online, tried to ping the workstation and was very happy to see it worked. So played around for a while trying to get the ARP cache to flush this entry to no avail, so I figured I'd get the VM's out of the mix and see if I could get HyperV3 to be able to see our troubled users workstation. So I checked VMCustomers, and hey, same thing! But what was odd was even clearing the arp cache and checking it almost immediately still shows this IP address with an Invalid type. Since DNS looked good I figured I'd look at the ARP cache, that’s when I noticed something, the troubled workstation's IP address was listed in the ARP table on HyperV3, but its physical address was 00-00-00-00-00-00 with Type "Invalid". I checked the DNS server, only single entries for VMCustomers and HyperV3, as well as the troubled workstation, and other workstations were able to use VMCustomers without issue. I tried flushing the arp cache and the dns cache on the workstation and the problem still remains, attempting the same on HyperV3 and VMCustomers appeared to have no effect. When a user experiencing problems attempts to ping VMCustomers, they're greeted with "Reply from (their IP): Destination host unreachable." If I try to ping the users machine from HyperV3, I get the same message, as well as from VMCustomers. HyperV3 has a VM called "VMCustomers", most users can connect to this VM via RDP, SQL Studio, and/or Ping it. I was out of the office last week but now that I've returned I've heard that some users have had difficulties connecting to some of the VM's on HyperV3. Got the VM's online, logged in, tried to ping a few critical servers on our network as well as the internet, and everything looked like we were in business. ![]() Then went into each VM on that server and pointed their network card to the new Virtual Switch. I then removed and re-created my Virutal Network Switch, associated it to my Team. The partictular server I'm having issues with (we'll call "HyperV3"), we recently installed an Intel Pro/1000PT Dual port NIC, and an Intel Pro/1000PT Quad Port NIC and Teamed all 6 Network adapters using "Virtual Machine Load Balancing" option when creating the NIC Team. I've heard of no issues with our other HyperV boxes, only this one. We've had 3 HyperV2 servers running in our enviroment without issues until we downed them to install more network cards and to team the cards together.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |