Not enought server storage

Hello, all.

I have gotten a lot of great info from all of you, Thanks a lot. So here is another problem to solve.

I have the standard PC/Laptop network, using a router. XP Pro on the pc, XP Home on the Laptop.

I have them connected, But when I try to Connect all the Drives I get a Message NOT ENOUGHT SERVER STORAGE IS AVAILABLE TO PROCESS THIS COMMAND. This appears on both computers.

A little help Please

 

This error (and it's been with us since NT3.1) is almost always an issue with the IRPStackSize value in the registry. A variety of causes but from 2K and on to XP, usually software either writing new values to the registry or requiring larger values and not making a suitable change.

Take a look at Antivirus Software May Cause Event ID 2011 and see if the fix shown in there helps.

 

No Luck

Thanks for the Info, But I ran up the value to max and NO Change. Any other options

 

More information needed at this point.
- how many drives/partitions in each PC?
- how many can you connect before it errors out?
- what router/switch are you using?
- any other major problems?
- check your event logs for the error. When you find it (and any others that seem related/relevant) please post them here in their entirety. Easiest to open the event, click on the icon below the up/down arrows which puts a text copy in your clipboard, and post the thing here.
- and any other tidbits you care to post.

Since there isn't much available information about XP and this particular error available, we may have to fumble around some but can either get it fixed or else give you enough information that you can pose the question to M$ tech support as a free case. Those folks are excellent at working on strange problems but do much better if you can give them details up front that make it obvious you have made a good effort to get things working.

 

more info

Ok Here is what I have: Main PC - No Partions, 3 HardDrives, 1 local, 2 external. I have 1 of the partions connected from the Laptop, but when I try to connect the other,that is when I get the message. The event log shows [The device, \Device\Ide\IdePort0, did not respond within the timeout period.]
As I stated earlier in this message, the Laptop is partioned into 2 drives. I have the main PC drive C mapped, but when I try to map to the other drives I get the message.

 

followup

I am using a Linksys Router.
NO other problems, YET

 

That helps. But please post the entire event log error. And since you should be getting errors on both PCs, post the findings from both.

If you do as suggested above to send the event log message to your clipboard, it won't be much effort to post the whole thing.

 

Followup

New Data: The Laptop ia working fine NOW. I retried to connect to all Drives and they connected. The PC is my only problem Child.

on a slightly different note. I read about installing NetBEUI on all machines. What is gained or lost by doing this???

 

On a small network, absolutely nothing lost by installing NetBEUI.

It is simply another networking protocol like TCP/IP is but much more limited and not able to ever get out to the internet. It also locates all the other machines on your network by shouting "who is out there" and listening for responses so it is a little noisy but with only a few machines, your network can deal with it and not really notice the extra.

The gain can be some added security if you set things up correctly. NetBEUI not only can't get to the internet, it also can't be seen from there. So if you set your PCs up to only use NetBEUI for printing and file sharing, you can be positive no one is peaking at you via the printer or file sharing feature.

If you want to go that route, install NetBEUI and it will connect to all PCs if they are in the same workgroup and have different names. It pays no attention to IP addresses - doesn't even see them in fact.

After that, change the network settings on all the PCs so that only NetBEUI is bound to file sharing and printer sharing. You will just remove TCP/IP from the bindings for those services. Specifics on doing it vary by NIC so can't tell you step-by-step.

You will find some very sharp folks on here who will only run this way and others of us who just use TCP/IP and aren't worried about this potential security hole. A router using NAT and a good firewall takes care of it pretty well IMO.