Link to home
Start Free TrialLog in
Avatar of netminder69
netminder69Flag for United States of America

asked on

0x8007046A Not Enough Server Storage when accessing Shared Docs

When I try to add a file to the Shared Docs folder of my XP Home PC via my workgroup, I get the following error:

"0X8007046A; Not Enought Server Storage to Process Your Request."  When I go into the Event Viewer, I get the message about the IRPStackSize not being large enough for it.

I followed the instructions and increased the IRP Stack to 0xC (it was already set to 0xB) and still no joy.  I cannot connect to it from my Vista Ultimate box or from my XP pro laptop.  I used to be able to connect to it.  If I try to open the folder remotely, I get an error message saying it was unable to do so and gives the same error message.  (Not enough server storage)

i can connect to the PC and I get a list of shared printers and the Shared Docs folder.

The PC has a Pentium 4 CPU and 2 GB of RAM.  There's well over 10 GB of space on the HDD.  I tried making a new shared folder and couldn't connect to that either.  The laptop is able to print to the shared printer if that is relevant to anything.
Avatar of JoWickerman
JoWickerman
Flag of South Africa image

Hi netminder69,

Is the Computer Browser service running on both machines?
Avatar of netminder69

ASKER

Yes, it is running on all PCs.  Also, I forgot to mention I can connect from the XP Home box (the one with the problem) to the other PCs Shared folders.  I just can go from the other PCs to the XP Home PCs Shared Docs folder.
Ok. You do have file and print sharing enabled on the XP Home's NIC, right?
Yes, it is enabled on all PCs
Ok, I found this:

If you have win xp home edition, this is the only way to get over the problem as the local settings & sedurity policy are not available in Administration Tools.
As far as I know, user rights policies applies to WinXP Home as well, you just don't have a builtin GUI tool to see/change them.

You should be able to set/remove those privileges with the Windows 2003 resource kit command line tool ntrights.exe.

Ntrights.exe is in the free Win2k3 resource kit:

Windows Server 2003 Resource Kit Tools
http://go.microsoft.com/fwlink/?LinkId=4544
or
http://www.microsoft.com/downloads/d...displaylang=en
The kit will install on WinXP or later.

After installation, click on: Start, All Programs, Windows Resource Kit Tools, Command Shell

Then enter the following commands. (Attention: they are case sensitive.)

net user guest /active:yes
ntrights +r SeNetworkLogonRight -u Guest
ntrights -r SeDenyNetworkLogonRight -u Guest

The first command enables network access for Guest, the two subsequent ones change two different policies to allow network access for Guest.

Let me know if this helps.
Unfortunately no.  I still get the same error message.
What happend when you connect to the XPHome PC in the following way:

Start -> Run

\\xphomepc_name\share\

\\xphomepc_ipaddress\share\

Same errors?
Yes.  I got the same error trying to connect directly through the address bar.  Typing in just \\xphomepc gets me to the top level where I can see the shared folders and printers.  I can't then get into any of the folders, even if I create a new shared folder.

Curious if it might be a HDD problem, I created a shared folder on the second drive, but had the same results.
This is out and out a XP HOME freakin permissions issue...

Try to create a standard user with a password on the XP Home PC and see if you can access it then?
ASKER CERTIFIED SOLUTION
Avatar of Yancey Landrum
Yancey Landrum
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I thought the IRPStackSize could only max out at 0xC.
I increased it to 1c (28) and it worked.  I thought I had read somewhere that it maxed at c, but I guess not.  :)
Thanks for the heads up that it maxes at 50!
Cool! Glad it worked for you.

Also, you might want to consider setting security on guest back to default unless you have a good reason for leaving it open.
This thread solution worked for me with Vista Ultimate 64 and XP Pro. Thank you!
Avatar of Waffle008
Waffle008

Holy mother of crap this had me hung up for a good hour. Value of 21 did a trick here for Dell Vostro.

http://support.microsoft.com/kb/177078