Network issues between Server 2008 and Windows 10

Anyone got a clue how to trace this down ?

​

Servers running:

Windows Server 2008

SBS 2011 (DC/AD)

​

Clients running:

Windows 7 x32 Pro in a domain.

Windows 10 X64 Pro in a domain.

​

​

Issue-Description:

We recently started migrating our Clients form Windows 7 to new Windows 10 machines. Windows 7 clients still remain unaffected; Windows 10 is haing issues . As per Windows 7 we map UNC paths (residing on the Windows Server 2008 to Drives via Script on Userlogon.

​

We have encountered the following Symptom(s) that seem to be connected:

- Business-Software that resides on a mapped drive (or UNC path) and gets started form there randomly (random interval's) crashes.

- Business-Software that resides on a local drive, but runs processing jobs that rely on grabbing files/PDF's on a mapped drive (or UNC path) randomly stop their jobs with error messages alluding to the fact that network shares / paths are not available.

- We never loose the mapped drives, they are and stay accessible. So this seems to be a very short Interruption.

- The best way to describe the issue is a slack joint (if this were, say a lamp).

​

What we have tried:

- Ran a new network cable to a test machine.

- installed a recent generation dummy switch (ours are OLD)

- turning off all IPv6 related settings on the network adapters.

- ran a 3 hour Iperf and "ping -t" between the Windows server 2008 and one affected machine, no issues, yet the symptoms still occurred on that specific machine.

​

I feel like this might have to something with the patch related network issues that we never were affected by during the last 10 month's of Windows Update Fiaskos.

​

Anyone know what this could be related to and/or how i might be able to trace this down ?