Lost Connectivity to Server 2012 Share

We recently installed a Windows 2012 Server.  We have 5 Windows 7 Pro workstations.  On two of the 5 workstations, we randomly lose connectivity to mapped drives on the server.  If working in an application, we will frequently not be able to do a save to the server.  We have to close the app and reconnect to the share, sometimes just by double-clicking on the drive letter.

it is a Dell PowerEdge server with Broadcom NIC.  Three of the workstations never lose connectivity.  Cabling has been tested.  Putting a different server on the same connection does not create a problem.  We have updated the driver on the NIC, replaced NICs on the affected workstations.

Short of reinstalling the OS, is there anything else we can try?  it's a very small network and we are temporarily using a Windows 7 Pro workstation as a temporary server.  No connectivity issues with this.
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.

Bill BachPresident and Btrieve GuruCommented:
Have you already tried disabling the disconnect timeout? You can use the fix it tool found here: https://support.microsoft.com/en-us/kb/297684
You can also disable the timeout manually with a registry change.

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
jspazianoctoAuthor Commented:
Was not aware of a disconnect timeout.  Will check this out right away.
Bill BachPresident and Btrieve GuruCommented:
The disconnect timeout is designed to release server-side resources when a share is not in use.  However, in some situations, the drive gets disconnected, but does not get reconnected fast enough for the application, resulting in delayed write failures and other strange problems.  I've found that running a batch file -- one that does a directory of the drive letter, sleeps for one minute, and loops -- can keep the connection alive, but this can add other needless overhead, too.  You may wish to try this as a test.
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.