asked on Lost Access to Mapped Network Drive after setup of NIC Teaming
We have a host server running Hyper-V with 2 VM's on it running. One is Server 2008 the other is SErver 2012 R2. Originally they were just sharing a Virtual NIC. We added an additional 4 Port NIC and set them up as a team, Switch Independent and Hyper-V Port. Shut down the VM's, changed the NICs to the new Teamed NIC, and booted the VMs back up. They were able to get online fine, but now our mapped drives to the file server VM are not connecting. And our other server which runs our CRM is up, but our clients on our PC are unable to connect to the Database. What are we missing? Is there something cached pointing to the old NIC MAC???
Thanks for the help.
Thanks for the help.
NetworkingHyper-VWindows Server 2012
Last Comment
invisimax
ASKER
Thanks for the response aleghart, we had switched back to the other virtual nic for now. I will try that when we switch to test again.
Thanks
Thanks
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
I was able to resolve the issue by disabling the Virtual Machine Queues on the physical NIC under the configure options.
IIRC, Cisco devices default to 4 hours before timeout. You need to clear it ASAP. Or, reboot a dumb switch...but that has greater consequences than just clearing arp cache.