Jump to content

Recommended Posts

Posted

Hello all,

 

I am running windows server 2012 as dc with 2 clients connected both running win7 pro.

 

This is a new setup (both server and clients) about 2 months old. First we used it to share word and excel files, which open really fast like you would expect but now that we've settled in the office we want to run applications and share larger files, this is when we noticed the problems.

 

Whenever i try to open a large file from the client (for example 100MB .exe file takes +- 10minutes to show an opening dialog) or an application from the client it takes forever to startup or to load.

 

 

The performance monitor indicates a maximum workload of 15% at all times.

 

I have tried all the following potential solutions i found, however none of them seem to do the trick.

 

- enable write cache = http://social.technet.microsoft.com/...m=winservergen

 

- change group policy = Langzame netwerkprestaties bij het openen van een bestand zich in een gedeelde map op een externe computer bevindt

 

- change group policy as = http://social.technet.microsoft.com/Forums/en-US/bcb4b580-50ef-4f10-bc9b-16db1bf24804/slow-network-file-execution-on-windows-server-2012?forum=winserverfiles

 

- changed network adapter offload values both server and client

 

- tried using another switch and cables

 

- disabled firewall & antivirus

 

- checked disk & memtested

 

- updated all drivers & windows updates to date

 

 

I'm really out of ideas and almost wanting to give up on this

 

Does anyone have any ideas?

 

 

 

Thanks in advance,

 

With kind regards

  • 2 weeks later...
Posted

I'm having major issues myself when Win 7 clients try to access files concurrently on Server 2012 R2 - Wireshark shows lots of SMB errors before the file eventually opens. Same files on a 2008 box open instantaneously. When I try accessing files from my Win 8 box, files open as quickly as they always have, Wireshark doesn't show nearly as many errors. Tried on physical Server 2012 box, as well as a VM with no anti-virus on it. Yet if a person opens files on their own and not concurrently, Windows 7 is pretty snappy, if not as fast as it was with 2008.

 

My conclusion is that Server 2012's SMB implementation is a bit screwy and isn't handling SMB2 clients very well, or at least Windows 7's SMB client.

Posted
I'm having major issues myself when Win 7 clients try to access files concurrently on Server 2012 R2 - Wireshark shows lots of SMB errors before the file eventually opens. Same files on a 2008 box open instantaneously. When I try accessing files from my Win 8 box, files open as quickly as they always have, Wireshark doesn't show nearly as many errors. Tried on physical Server 2012 box, as well as a VM with no anti-virus on it. Yet if a person opens files on their own and not concurrently, Windows 7 is pretty snappy, if not as fast as it was with 2008.

 

My conclusion is that Server 2012's SMB implementation is a bit screwy and isn't handling SMB2 clients very well, or at least Windows 7's SMB client.

 

Hey,

 

Thanks for the reply. I just tried to disable SMB1 on the server through the powershell and it seems to be running normal now. But i think the speed is not yet optimal.

Posted

There have been similar discussions on Edugeek already and the SMB does appear to be the source of the problem, but unfortunately it's tightly integrated with the OS and isn't something you can change.

 

2008 R2 and Windows 7 will work perfectly as they use the same SMB version, whereas issues do seem to creep in as 2012 and Windows 8 use a newer version.

 

In some cases, you can run 2008 R2 and 2012/2012 R2 in the same domain, with your file shares hosted on 2008 R2. It's a good compromise until Microsoft properly fix the issue.

Posted
The article was published 16th May 2014, so extremely recent. Hopefully users on here running 2012/2012 R2 can apply this fix and post some results if the problem's solved. This is one of the reasons why I haven't deployed any 2012 boxes as yet.
Posted
This again? We had a similar issue with poor copy performance between 2k/XP clients and 2008 server editions. Although the symptoms are the same, the root cause in this particular issue was something in TCP I think - something like having to disable heuristics.
Posted
I've been keeping an eye on this issue for a while now as I'm planning on deploying a couple of 2012 R2 file servers in the summer.

 

Seems that the issue is caused by 2012 digitally signing its SMB packets - have a look at this: How To Fix Windows Server Network Performance Problems -- Redmondmag.com

 

Hello,

 

Yes, I tried to disable digitally signing but it didn't solve this issue for me. I have better speed now that i have disabled SMB1 through powershell SMB cmdlet.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...