Very slow saving times to H: drive and other shared areas!

[adhutton]

We had a similar issue to this last year.

 

I am assuming your PCs are Windows 7?

 

If so, it may be the Win 7 autotuning thing thats causing the issue. You can disable that quite easily.

 

We run this command in a PC startup script and it seemed to fix the problem:

 

netsh interface tcp set global autotuning=disabled

 

Might be worth a try?

 

Cheers - Andrew

[Koldov]

Just to keep you all in the loop I eventually found a fix to this I went on my file server and add a REG_DWORD entry named Smb2 with a value of 0 to HKLM\System\Current Control Set\Services\LanmanServer\Parameters then I rebooted the server and ta-dahhhh!a

 

I'd be interested as to where you found the 'fix' and what it actually fixes, as it would appear it isn't recommended... In fact it would appear that SMB2 is actually for improving things. Do you think there was a specific part of it that didn't work well within your network. I guess if it works don't knock it, but I like to know the why...

 

How to enable and disable SMBv1, SMBv2, and SMBv3 in Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012

 

Kol.

[DMcCoy]

Windows Server 2012?

 

See, this is why I asked if it was 2012.

 

I have had issues when testing 2012, with SMB v3 being a steaming turd and slow with office files. It managed to kill an mdb completely. I can't say I'm terribly impressed with 2012/R2

[abillybob]

@Koldov after doing some long hours researching into this I found an article online explaining how SMB2 and SMB3 can apparently cause havoc as it's very chatty and likes to redirect shares all over the place for no logical reason. These were sorted in Windows Updates apparently but I couldn't find the update anywhere! Anyway disabled it and it's worked ever since with not a single issue with anything... In fact it's been running like a dream. I was also in the expectation it's supposed to help but as you say... I'm not going to enable it again just because there's some apparent data out there which suggests it's good because after disabling it all I've found is everything works better and faster!