ICS File Sharing not working on Client

  • Thread starter Thread starter Tim C
  • Start date Start date
T

Tim C

Have set up a small home network, host Xp pro, client Xp home

All looks good, internet sharing works fine, host can see and use all
files on client.

Client can see shares on host, but cannot access them. when attempted
the following alert appears:

" \\servername\folder\ is not accessible. You might not have
permission to use this network resource. Contact the administrator of
this service to find out if you have access permissions.

Not enough server storage is available to process this command "

ICS is enabled, simple file sharing is enabled, IP configuration is
correct as per M$/PracticallyNetworked instructions, all protocols in
place, everything pings OK, and no logon/start up passwords required
for Xp Home or Pro.

I've tried just about everything on offer on the newsgroups and got
nowhere :(

What's gone wrong?

Regards

Tim
 
Unfortunately, I'm glad I'm not the only one! I'm trying
to get an XP-Home Wireless Machine to talk to an XP-Home
Desktop with similar results (the alert about not having
permission to use this network resource is very familiar).

Come on Microsoft - Give us an answer!
 
Well solved mine!

In desperation to try to get things working, I downloaded and installed the
extra networking pack for SP1. this provided an improved IP protocol and a
few other bits. What I didn't know was that there was a problem with the IP
stack causing the "Server" service to "not" work, even though it was
starting. Once I took a look in events this evening I was shocked to see the
pile of errors about this all reporting the same problem. The resolution
from M$ is to increase the stack size. Here are the instructions:

Details
Product: Windows Operating System
ID: 2011
Source: Srv
Version: 5.2
Symbolic Name: EVENT_SRV_IRP_STACK_SIZE
Message: The server's configuration parameter "irpstacksize" is too
small for the server to use a local device. Please increase the value of
this parameter.

Explanation
The server is configured with too many file system filter drivers (for
example, Quota and anti-virus) and/or too many devices, or the irpstacksize
parameter is set to less than the default of 15 stack frames. The
irpstacksize represents the number of kernel modules that can store
information in the input/output (I/O) Request Packet (IRP). The IRP is used
to track I/O requests in the kernel.


User Action
The irpstacksize parameter can be increased by changing the registry
value.

To change the registry value

1.. Using Regedit, open the following registry key:

HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters\IrpStackSize
2.. In the Value data box, type 15.
The default size is 15 stack frames. Each stack frame is 50 bytes. If
the value is less than 15, advanced users can safely set it back to 15. If
15 is too small, try increasing the number by increments of 5 until this
event is no longer logged. Changing this registry key requires a restart of
the Server service.



Version: 5.0
Symbolic Name: EVENT_SRV_IRP_STACK_SIZE
Message: The server's configuration parameter "irpstacksize" is too
small for the server to use a local device. Please increase the value of
this parameter.

Explanation
The server is configured with too many file system filter drivers (for
example, Quota and anti-virus) and/or too many devices, or the irpstacksize
parameter is set to less than the default of 15 stack frames. The
irpstacksize represents the number of kernel modules that can store
information in the input/output (I/O) Request Packet (IRP). The IRP is used
to track I/O requests in the kernel.


User Action
The irpstacksize parameter can be increased by changing the registry
value.

To change the registry value

1.. Using Regedit, open the following registry key:

HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters\IrpStackSize
2.. In the Value data box, type 15.
The default size is 15 stack frames. Each stack frame is 50 bytes. If
the value is less than 15, advanced users can safely set it back to 15. If
15 is too small, try increasing the number by increments of 5 until this
event is no longer logged. Changing this registry key requires a restart of
the Server service.
 
Back
Top