Network (Share) Storage problem 2

[braddds]

Not sure if this is a w2k or xp problem...however I encountered an error while accessing a networked share on a xp pc from a w2k pc. The error said (sorry this is not the exact wording) "unable to view, insufficient network storage allocated to access drive". If I access the shares on w2k from xp I have no problem, also if a access a share on another w2k pc from this pc, again I have no problem (and "no" I didn't get a chance to see if the same error occurred from the second w2k pc when it accessed the xp pc). Has anyone else seen this before and does anyone know the solution!

Cheers

 

[braddds]

It seems I've stumped the panel on this one...well, no worries, it's not a critical or anything.

Cheers

 

[braddds]

Update:

The problem occurs from both w2k pc's trying to access the WinXP pc. I can see the shares on the XP pc but this takes 15 - 20 seconds for this to come up then when I click on a shares to see the contents the following error occurs:

"not enough server storage is available to process this command"

Cheers

 

[John Lewis]

Running Norton AV by any chance?

 

[bcastner]

http://support.microsoft.com/?scid=kb;en-us;177078

IrpStackSize errors are a varied lot. HP Printer drivers are known for this, and as mhkwood noted above several Anti-virus programs can cause Irp errors.

Please follow the advice in the linked article above and do not be overly ambitious in setting a new value. The recommendation is to add 3 to the existing value. Too high a value can lead to the same error.

 

[bcastner]

Tek-tip member blin2000 noted in a MS newsgroup some additional things to check:

1) Remove any unnecessary entries from this value in the registry,
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters\NullSessionPipes.
2) If the machine has a non-zero PagedPoolSize in the Registry, you need to re-set it by going to
HKEY_LOCALMACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\MemoryManagement and double-click on PagedPoolSize and set to 0.

Source:

http://www.chicagotech.net/

I hope it is clear that you apply these registry edits to the machine hosting the share, and not the machine that is showing the error message.

Best.

 

[braddds]

Ok here is the solution to my problem. It turns out to be the IrpStackSize, on the XP pc, it was set to 11 I reset it to 15 and all was right in the world!

Stars to bcastner for the solution!

...and yes mhkwood I am running Nortons AV which is appearently the culprit for placing this into the registry!

Thx All

Cheers