Problem sharing external drive

[Guest]

Just connected an Iomega 120GB USB 2.0 external drive to computer A. Computer
B is networked with A and can share files on computer A's internal hard
drive. B can see the new Iomega drive in Explorer, but can't access it.
Message says drive is not accessible, might not have permission. Also says
"Not enough server storage is available to process this command." I've
increased the IRPStackSize considerably with no success. Also have tried
classical and simple file sharing. Any other ideas would be appreciated.

 

[JR K Yoshikawa]

Check microsoft KB Document below for error message "Not enough server storage is available to process this command."

Antivirus software may cause Event ID 2011
( After you install Norton AntiVirus for Windows or IBM AntiVirus 3.01N (Build 301.590),
you receive the following error messages:
Not enough server storage is available to process this command.)

http://support.microsoft.com/default.aspx?scid=kb;EN-US;177078


also can you post more detail info?
(are both PC are windows XP? is that pro or home edition?
did you check Iomega's properties share tab?
did you check permission?
etc. )

 

[Ron Lowe]

Just connected an Iomega 120GB USB 2.0 external drive to computer A.
Computer
B is networked with A and can share files on computer A's internal hard
drive. B can see the new Iomega drive in Explorer, but can't access it.
Message says drive is not accessible, might not have permission. Also says
"Not enough server storage is available to process this command." I've
increased the IRPStackSize considerably with no success. Also have tried
classical and simple file sharing. Any other ideas would be appreciated.

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 the registry editor (e.g., regedit.exe).
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 of
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

 

[Guest]

Thanks for the replies, but still no luck. I had already found the article
and have taken the IRPStackSize all the way up to 30 with no success. Both
computers run XP Pro, I think all permissions and sharing options have been
set correctly. Other shared folders on a different drive can be accessed
from comp B with no problem. Any other suggestions would be welcome.

 

[Ron Lowe]

Thanks for the replies, but still no luck. I had already found the article
and have taken the IRPStackSize all the way up to 30 with no success. Both
computers run XP Pro, I think all permissions and sharing options have
been
set correctly. Other shared folders on a different drive can be accessed
from comp B with no problem. Any other suggestions would be welcome.

Have you looked in the event viewer on the
machine you are attempting to connect to?

Are there instances of error 2011?
Are there any other errors ?

If there are, then it appears the IRPStackSize is still wrong.
The only time I've seen this happen is has been caused by one of these:

1) Applying the IRPStackSize adjustment on the wrong machine ( it needs to
be on the machine you are connecting to );
or
2) Applying it in the wrong place in the registry ( check it's in the
\parameters key );
or
3) A typo error in then name IRPStackSize. ( eg incorrect capitailisation )

Double-check, especially (2).

 

[Guest]

Got it working.... Thanks for sticking with me... I must have been asleep
last night when reading your posts and was working on comp B rather than A...
Dumb, but it was really late... An IRPStackSize of 15 on comp A did the
trick... Again, thanks.