File Sharing Problem Not enough server storage is available .....

[Guest]

I have a wireless network running between a Packard Bell Desk top and a Dell Inspiron Portable. I can get to onto the internet and share folders from the Dell onto the Packard Bell. The Dell however cannot share folders on the Packard bell.

The folders appear on the My Network Places but if I try and open them The message appears

\\SN011....\name is not accessible. You might not have permission to use the network resource . Contact the administrator of this server to find out if you have access permissions.

Not enough server storage is available to process this command.

I have adminstrator rights overall. I have tried help but cannot get to see any properties in the Administrative Tools, Computer Management, Shares on either the Dell or the Packard bell as proposed in the help message.

Whilst setting up the network I did get a spooler error on the Packard Bell which closed the spooler down. The network set up appeared to complete ok.

Can anybody help me?

 

[CTee]

I have the same problem using a wired connection.

It was working fine and now it doesn't.

Any help welcomed.

-----Original Message-----
I have a wireless network running between a Packard Bell

Desk top and a Dell Inspiron Portable. I can get to onto
the internet and share folders from the Dell onto the
Packard Bell. The Dell however cannot share folders on
the Packard bell.

The folders appear on the My Network Places but if I try

and open them The message appears

\\SN011....\name is not accessible. You might not have

permission to use the network resource . Contact the
administrator of this server to find out if you have
access permissions.

Not enough server storage is available to process this command.

I have adminstrator rights overall. I have tried help

but cannot get to see any properties in the
Administrative Tools, Computer Management, Shares on
either the Dell or the Packard bell as proposed in the
help message.

Whilst setting up the network I did get a spooler error

on the Packard Bell which closed the spooler down. The
network set up appeared to complete ok.

 

[Guest]

I am having the exact same error. I am trying to get my new Dell XPS to share files FROM my 8100 when I get this message. I can share files TO the 8100 with no problem. Please help!

----- Gerrard wrote: -----

I have a wireless network running between a Packard Bell Desk top and a Dell Inspiron Portable. I can get to onto the internet and share folders from the Dell onto the Packard Bell. The Dell however cannot share folders on the Packard bell.

The folders appear on the My Network Places but if I try and open them The message appears

\\SN011....\name is not accessible. You might not have permission to use the network resource . Contact the administrator of this server to find out if you have access permissions.

Not enough server storage is available to process this command.

I have adminstrator rights overall. I have tried help but cannot get to see any properties in the Administrative Tools, Computer Management, Shares on either the Dell or the Packard bell as proposed in the help message.

Whilst setting up the network I did get a spooler error on the Packard Bell which closed the spooler down. The network set up appeared to complete ok.

Can anybody help me?

 

[Unnamed]

I have a wireless network running between a Packard Bell Desk top and a

Dell Inspiron Portable. I can get to onto the internet and share folders
from the Dell onto the Packard Bell. The Dell however cannot share folders
on the Packard bell.

The folders appear on the My Network Places but if I try and open them The message appears

\\SN011....\name is not accessible. You might not have permission to use

the network resource . Contact the administrator of this server to find out
if you have access permissions.

Not enough server storage is available to process this command.

Your Irpstacksize is probably set at the default 11. Try increasing it to 22
as that is normally all you have to do - and reboot of course - to correct
the problem. You can find it in your registry under:

hkey_local_machine\system\CurrentControlSet\services\lanmanserver\parameters

.....or if it doesnt exist, create it and put the decimal value 22 in there
and reboot and try whatever you were trying all over again. Valid numbers
for this parameter are 11-50 decimal. The higher you go above 22, the more
chance of problems elsewhere.

 

[Hans-Georg Michna]

I have a wireless network running between a Packard Bell Desk top and a Dell Inspiron Portable. I can get to onto the internet and share folders from the Dell onto the Packard Bell. The Dell however cannot share folders on the Packard bell.

The folders appear on the My Network Places but if I try and open them The message appears

\\SN011....\name is not accessible. You might not have permission to use the network resource . Contact the administrator of this server to find out if you have access permissions.

Not enough server storage is available to process this command.

I have adminstrator rights overall. I have tried help but cannot get to see any properties in the Administrative Tools, Computer Management, Shares on either the Dell or the Packard bell as proposed in the help message.

Whilst setting up the network I did get a spooler error on the Packard Bell which closed the spooler down. The network set up appeared to complete ok.

Gerrard,

please have a look at
http://www.michna.com/kb/WxNotEnoughServerStorage.htm.

Hans-Georg

 

[CTee]

I have been having the same problem
Just resolved by visiting
http://www.michna.com/kb/WxNotEnoughServerStorage.htm
and following the instructions. You need to do this on
both (all) PCs to see each others folders.

CTee

-----Original Message-----
I have a wireless network running between a Packard Bell

Desk top and a Dell Inspiron Portable. I can get to onto
the internet and share folders from the Dell onto the
Packard Bell. The Dell however cannot share folders on
the Packard bell.

The folders appear on the My Network Places but if I try

and open them The message appears

\\SN011....\name is not accessible. You might not have

permission to use the network resource . Contact the
administrator of this server to find out if you have
access permissions.

Not enough server storage is available to process this command.

I have adminstrator rights overall. I have tried help

but cannot get to see any properties in the
Administrative Tools, Computer Management, Shares on
either the Dell or the Packard bell as proposed in the
help message.

Whilst setting up the network I did get a spooler error

on the Packard Bell which closed the spooler down. The
network set up appeared to complete ok.

 

[Unnamed]

I have been having the same problem
Just resolved by visiting
http://www.michna.com/kb/WxNotEnoughServerStorage.htm
and following the instructions. You need to do this on
both (all) PCs to see each others folders.

....which is what I posted before that URL was thrown in. IRPStacksize is
more often than not the culprit and one of the reasons for it can be
programs that are installed to do mirror or addendum backups.

 

[Guest]

Thank you people, it worked for me too. Is it possible that the application which set the value to 11 will not work correctly now it is set to 22?

I have not noticed any problems, so I guess not, I do run Go Back, Norton Antivirus all the time and Norton Ghost occasionally.

Thanks again

 

[Unnamed]

Thank you people, it worked for me too. Is it possible that the

application which set the value to 11 will not work correctly now it is set
to 22?

Nope. 22 works most of the time and is the ONLY thing you have to do in most
cases. However, there IS the 5% rule - that is "5% of machines are just
DIFFERENT!"

I have not noticed any problems, so I guess not, I do run Go Back, Norton

Antivirus all the time and Norton Ghost occasionally.

Thanks again

They aren't the only things that can affect it and to be honest if you have
XP you don't need Go Back anyway. Powerquest's desktop backup system where
you can have incremental backups as well as the base is the reason in some
cases. However, it is a dead easy fix the way I described and works for at
least 95% of machines. You also don't need to be a guru to make it work
again.