USB Hard Drive Share Failure
jonah
Got a USB drive (Iomega 120GB) connected to a new PC. Reformatted it
to remove all traces of previous shares so it is empty. Put a test
folder on it with some data.
Loads up OK and works fine but when I enable it for file sharing I can
see it on all the network PCs but not access it.
Same drive file shares fine on any other PC but not this one.
Error message is the standard "not accessible" which is not entirely
true cos I can access other shared folders on the PC- followed by
"Not enough server storage is available to process this command."
I am pretty experienced with networks, I have done all the usual
checks and fixes but nothing cures this. I can share other folders and
drives on the same PC no problem but not the USB drive.
I have read some very technical stuff about IRP Stacks which led me to
this
http://www.winguides.com/registry/display.php/756/
Tried changing the value in the registry but I am guessing at what it
should be and none of the range of allowed values has any effect, also
I am assuming its decimal as the paramaters are 1 to 12 but I also
read someone had fixed this by setting the value to 50? which is
outside the allowed range.
The only difference between this PC and the rest of the network is
this one has 2 x 80GB PATA & 1 x 80GB SATA drives attached. all the
rest only have 2 x HDDs on PATA. There are no other USB devices
attached at all
Can somebody give me a clue on what is going on and how to fix this?
TIA
Jonah
Malke
You are right that you need to change the IRPStackSize, but your
antivirus can also cause the problem. Here is information from MVP
Hans-Georg Michna about this error:
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
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User
Jonah
wrote:
>jonah wrote:
snip
>
>You are right that you need to change the IRPStackSize, but your
>antivirus can also cause the problem. Here is information from MVP
>Hans-Georg Michna about this error:
>
>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
Thanks Malke I was on the right track then. I will fix it tomorrow I
am too stressed out now with it.
I did put Norton 2006 on it when I installed the OS to have a look at
it, I then removed it and put NOD32 in and carried on with the set up.
Silly of me really I suppose.
Jonah