Network Access to Shared Folders Stopped Working

[rosco]

Today I signed up for the Windows Live One Care beta.

I can no longer access shared folders on this machine from other machines on
my LAN. On the remote machine (W2K OS) it now says \\machine\SharedDocs not
accessible. Not enough server storage is available to process your command.

There is 20+ GB available on that disk. The sharing options haven't changed
on those folders. What do I need to do to get this to work again?

 

[Malke]

Today I signed up for the Windows Live One Care beta.

I can no longer access shared folders on this machine from other
machines on
my LAN. On the remote machine (W2K OS) it now says
\\machine\SharedDocs not
accessible. Not enough server storage is available to process your
command.

There is 20+ GB available on that disk. The sharing options haven't
changed
on those folders. What do I need to do to get this to work again?

I don't know why One Care would have changed this, but its antivirus
might be the culprit. Here's what that error message means (credit to
MVP Hans-Georg Michna):

This error indicates that you are falling foul of the IRPStackSize bug.
The problem is on the machine you are attempting to connect to, not the
machine where you see the error message. On the computer you are
attempting to connect to, check the event viewer for an event ID 2011.

Usual fix : You need to fix a parameter called IRPStackSize

On the computer you are attempting to connect to, Set the IRPStackSize
back to the default (15 ). Perform the following steps:

1. Start regedit.
2. Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters.
3. Double-click IRPStackSize (or if this registry setting doesn't
exist, create it with type DWORD and ensure the case is correct).
4. Change the base to decimal, set the value to 15, and click OK.
5. Reboot the computer.

Norton AV is usual suspect for breaking it. There's a KB article about
this, too:

Antivirus Software May Cause Event ID 2011 (Q177078)
http://support.microsoft.com/default.aspx?scid=kb;EN-US;177078

Malke

 

[rosco]

Thank you.

It did the trick. Had to create the registry entry, and set the value to
decimal 20. It still gave the error at a value of 15.

 

[Malke]

Thank you.

It did the trick. Had to create the registry entry, and set the value
to
decimal 20. It still gave the error at a value of 15.

Glad it worked. Thanks for updating the thread.

Malke