tcgood

the consultant we hired recommended this when he found out what was going on at the high level. You do lose all the benefits of smb 2 and 3. Let me know how long you go with out issues.

powershell you can | (pipe) Select-String -pattern "what you are looking for". Like above netstat | select-string -pattern ":389".

So those are listening ports, that is good. I have verified that the finals your server is listening on 445 which is SMB. Domain controller should be listening on 389. It might be but I have more issues besides the file server server. The occurrences I'm still happening I have a case open with Microsoft. We're doing some packet captures and memory dumps I will keep you posted.

So can everyone log into their Domain controllers and run netstat -an and look for 389 connections (more than one per device). Does it look like a lot of connections? When the File share server goes done (and run before it does as a comparison) run netstat -an | Select-String -pattern ":389" from powershell. Before connected after not connected? I am chasing this issue down for our environment. If you see what I am seeing we might be onto something.