Frequent Disconnects from Clients to a Hyper-V 2012 R2 Server

Working with a new Dell PowerEdge R420 server running Server 2012 R2 Standard. The hardware is hosting a Hyper-V client also running Server 2012 R2 Standard which is sharing several SCSI controller VHDX drives. Frequently clients using MS Access 2013 running mdbx databases get disconnected with errors that connection to the database were lost. No network errors are logged on the client, host server or VM. Network adapter is Broadcom Gigabit Ethernet BCM5720, with the Virtual Switch using a dedicated physical NIC port. Virtual machine queue is disabled on the host NIC and within Hyper-V. Right now no other virtual machines are running on this machine due to instability. Worked with Dell ProSupport to no avail and all drivers/firmware are updated. Any help or insight would be greatly appreciated!
GISCOOBYDirector of Information TechnologyAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Jeffery HayesSystem Support Technician Commented:
Are you able to do the following?

From the host that clients are using pull a Netmon log?

Also not sure but this might help. 

Even though it's VMware and not Hyper V. Could be the Nic however. But are other systems in the environment the same and working fine?

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
Cliff GaliherCommented:
The current Broadcom drivers are broken (again.) And honestly I've quit trying to track what past versions are stable.  Buy a non-Broadcom NIC (I recommend Intel) and save yourself repetitive pain . Not just now, but down the road during driver update cycles
GISCOOBYDirector of Information TechnologyAuthor Commented:
Thanks for both of your help! Jeffery Hayes: pointed me in the right direction with the ESX site even though this is a Hyper-V environment and Cliff Galiher then confirmed the suspicions. I will add an Intel NIC. Thanks again.
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

From novice to tech pro — start learning today.