Vista : unable to allocate from nonpaged pool = No network shares

Hi, ive had this problem for sometime now and havent been able to solve it, my Vista SP1 MC, holds a lot of my movies/music etc etc. So when we got a second media center (also vista), i just decided i would set up shares on the first one so that both could have the same movies.

This all works fine most of the time, however at some point 2 of the XP machines and the other Media Center will stop being able to access the machines "may not have rights, contact admin" is the message they get....My own vista computer can continue accessing all the shares without any hitches.

When i look into the VistaMC (sharing) event viewer i see hundreds of event ID 2017 "The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations." messages and in the eventdata i see \Device\Lanmanserver so this is obviously the problem with network shares being denied.

Ive tried doing all the various registry fixes from microsoft such as MaxMpxCt, MaxNonPagedMemoryUsage, MaxWorkItems, Size etc in the Lanman section, but nothing gives, whilst typing this message the vista MC is using 1.1GB out of 2GB of memory has over 300GB of spare harddrive and is giving me the errors, also i dont see any process's with massive amounts of memory/handles etc being used, so i cannot understand why the machine would be out of resources. Checking the current logins to the machine shares so 1 in use, so that the 10 user/file (cant remember) limit is not the problem either.

Does anybody know how to solve the issue?

After changing the NIC and going through a bunch of reg settings, i finally found the solution. It appears that Vista uses SMB2 for networking and its obviously buggy in certain circumstances. Disabling it and forcing SMB1 (pre vista networking) fixes the problem and finally all my machines are able to connect to the Vista shares even after days of use. The Bug in SMB2 reports the EVENTID 2017 into your eventlogs, complaining that there is not enough nonpaged pool memory left, however this is not the case as taskmanager shows there is easily enough and also that no process's on the host machine are leaking any nonpaged pool memory at any point.

So the fix is, either

Download the reg file here and run it on your Vista system. Restart your computer and fixed.

Or

Open regedit goto HKEY_LOCAL_MACHINE ->SYSTEM ->CurrentControlSet ->Services ->LanmanServer -> Parameters. Then click createkey and create a DWORD with the name SMB2. The value should automatically be set as 0, which is correct to turn it off. Restart computer and fixed.

To remove the fix and reenabled SMB2 simply remove the DWORD from the place above in the registry.

This problem has been driving me crazy for weeks - system log full of Event ID 2017 and constant dropouts on clients accessing video/music.

I've implemented the reg change on my Vista Media Center PC - all appears to be fixed!!

Thank you so much for posting this fix - I'd tried everything else also and this appears to have done the job.

Well here is to hoping! Migrated a client to a Vista based server (they got it without conferring with me. Always a good idea to exclude your I.T. guy from your server purchase decisions....)

Anywho, been having some problems that looked a whole heckuva lot like network connectivity but nothing but the server had been changed so I check the even logs. Well, looky there...event ID 2017 in big 'ol long strings.

I just changed it tonight and I am REALLY hoping that this solves the problem. I was going to screw together an XP based server and install it over the weekend. I will be more than happy to NOT have to do that.

I will try and remember to post back with the results. Per the law of human nature, if it works, I will probably space out. If not, I will be posting a bummed out reply.

HURRAAYYYY!!!!!!!!!!!!!!!

It appears to have worked. They worked all day Friday without a problem. It is just a teensy bit too soon to declare complete and total victory but I really do think this fix took. No more Event ID 2017

This is honestly important enough to be in an official MS knowledgebase. If I had not stumbled across this thread, I would be on site right now swapping in an XP based server and trying to rebuild the other one to XP (no doubt with substantial grief). This SMB2 bidness is essentially completely broken it is totally unacceptable for it to be this problematic without an official (and thus easy to access fix). I'm pretty disgusted on this one. I just can't get over thinking about the hours and hours of grief I would have been in for without this incredibly easy to implement fix.

Words cannot express enough thanks for posting this fix.

The fix worked for me, but i went through so many other settings, i cant really be sure that its 100% with just the reg setting. Anyway i hope it works out, i spent many hours trying to troubleshoot the problem and still dont know what actually causes it.

Originally Posted by Toytown

The fix worked for me, but i went through so many other settings, i cant really be sure that its 100% with just the reg setting. Anyway i hope it works out, i spent many hours trying to troubleshoot the problem and still dont know what actually causes it.

I think it is safe to say that it is the reg key. It has been several weeks now without a recurrence of the problem. It was happening multiple times a day before so I really do think it was reg change. Thanks again for your post. You saved me (and the company in question) a lot grief.

I would say something cranky about not using Vista, but with the deadline looming (and absolutely looking like it is for real) it is simply time to accept that there will be more Vista stuff to deal with, not less in the coming years.

Hi !

I have a Vista Business 32 SP1 as a file server.

All clients can access files but suddenly, within 24 or 48 hours, network stops working, nobody can access the server anymore, until I reboot it.

I have hundreds of event id 2017 in system log

So, when I saw this thread, I was almost sure that this would fix my problem, but it doesn't !

My client just called me ten minutes ago, the network freezed again !!

What can I do ??

Should I modify some reg keys mentioned here : http://support.microsoft.com/kb/937082 ?

Since I disabled SMB2 in Vista CLIENTS too, network doesn't "shut down" anymore, but it's now EXTREMELY slow...

I'm sad to say this, but I'm *%£ïng forced to format and install a XP instead !!

I hate to dredge up an old thread, but I just wanted to point out that this happens in the glorious Windows 7 as well.

I'm running 64-bit Windows 7 Ultimate as my HTPC and had this error.

If I hadn't previously stumbled upon this thread last time it happened (of course, running Vista), I wouldn't have known what to do.

This is a big deal, as SMB 2 was supposed to allow us to make use of these fat ol' GigE connections most of us are running.

SMB 2.0 - Copying Files Faster
http://www.tomshardware.com/reviews/...ED,1710-8.html

*Thread necromancy*
Be sure to check out this link for a permanent fix that's working for a lot of folks - with SMB 2.0 enabled: http://alan.lamielle.net/2009/09/03/...srv-error-2017

Originally Posted by Kachunkachunk

*Thread necromancy*
Be sure to check out this link for a permanent fix that's working for a lot of folks - with SMB 2.0 enabled: http://alan.lamielle.net/2009/09/03/...srv-error-2017

Thanks for this. I will be sure to try it out!

Now to remember which reg branch I changed to disabled SMB 2.0....