Windows Server 2016 Intermittently Slow

%3CLINGO-SUB%20id%3D%22lingo-sub-1895421%22%20slang%3D%22en-US%22%3EWindows%20Server%202016%20Intermittently%20Slow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1895421%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ESo%20I%20have%20two%20Windows%20Server%202016%20(1607)%20they%20are%20RDS%20servers%20they%20do%20run%20SQL%20but%20the%20CPU%20is%20not%20massively%20high%20on%20them.%26nbsp%3B%20The%20both%20run%20on%20ESXi%206.5.%26nbsp%3B%20Latest%20hardware%20and%20tools%20applied.%26nbsp%3B%20Both%20servers%20run%20the%20same%20AV%20the%20same%20FW%20rules%2C%20etc.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThey%20connect%20to%20a%20file%20server%20which%20is%20running%20Windows%20Server%202019%20(1809).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20some%20reason%20only%20one%20of%20the%20RDS%20servers%20will%20be%20a%20pain.%26nbsp%3B%20The%20other%20one%20will%20run%20fine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20for%20example%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E01%20-%20Fine%3C%2FP%3E%3CP%3E02%20-%20Painfully%20slow%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELogging%20on%20to%2001%20takes%20around%205%20seconds.%26nbsp%3B%20Logging%20on%20to%2002%20takes%20around%203%20minutes%20-%20stuck%20on%20either%20applying%20the%20printer%20GPO%20or%20the%20drive%20mapping%20GPO.%26nbsp%3B%20When%20logged%20in%20people%20will%20get%20a%20blue%20wheel%20when%20accessing%20file%20shares%20or%20such%20like.%26nbsp%3B%20The%20file%20shares%20will%20just%20hang%20when%20browsing%20but%20then%20return%20fine.%26nbsp%3B%20On%20the%20other%20server%20it's%20fine.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EI've%20checked%20and%20they're%20both%20running%20SMBv3%20to%20all%20connections%20that%20I%20can%20see.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20completely%20ran%20out%20of%20ideas%20on%20what%20could%20be%20causing%20this.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EAnyone%20have%20any%20ideas%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1895421%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Eslow%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESMB%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
New Contributor

Hi


So I have two Windows Server 2016 (1607) they are RDS servers they do run SQL but the CPU is not massively high on them.  The both run on ESXi 6.5.  Latest hardware and tools applied.  Both servers run the same AV the same FW rules, etc.

 

They connect to a file server which is running Windows Server 2019 (1809).

 

For some reason only one of the RDS servers will be a pain.  The other one will run fine.

 

So for example:

 

01 - Fine

02 - Painfully slow

 

Logging on to 01 takes around 5 seconds.  Logging on to 02 takes around 3 minutes - stuck on either applying the printer GPO or the drive mapping GPO.  When logged in people will get a blue wheel when accessing file shares or such like.  The file shares will just hang when browsing but then return fine.  On the other server it's fine.


I've checked and they're both running SMBv3 to all connections that I can see.

 

I have completely ran out of ideas on what could be causing this.


Anyone have any ideas?

 

Thanks!

4 Replies
Highlighted

These sort of things usually stem from incorrect or problematic DNS settings / setup. I'd check the domain controller and problem members have the static ip address of DC listed for DNS and no others such as router or public DNS

 

 

 

Highlighted

@Dave Patrick 

 

First thing I checked:

 

01 --> Primary is DC01 --> Secondary is DC02

02 --> Primary is DC01 --> Secondary is DC02

 

DC01 is a DNS server with two forwarders to Google

DC02 is same as above

Highlighted

I'd check the problem members settings. Also check the domain health is 100%

 

 

Highlighted
No errors in DCDIAG - I'll rejoin them to the domain though just as a quick check.