ARCGuy
asked on
Cannot Map Drives on Home Network
dual boot Vista Ultimatex64 XPx64 Workstation w/ 320GB SATA II divided in half for each OS. 4GB RAM
Raid 5 4X320GB SATA II drives for 900GB storage.
XP system 1 250GB SATA II & 2GB RAM
Server 2003 r2 Enterprise DC 2GB RAM
Server 2003 Standard File and Print Server @GB RAM
Raid 5 4X320GB SATA II drives for 900GB storage.
XP system 1 250GB SATA II & 2GB RAM
Server 2003 r2 Enterprise DC 2GB RAM
Server 2003 Standard File and Print Server @GB RAM
Here is Microsoft article how to resolve the problem: http://support.microsoft.com/kb/225782
ASKER
I have already tried the solution described in the article.
This info was in the problem description.
This info was in the problem description.
ASKER
not enought server storage is available to process this command
is the error I receive. There are no options except OK.
is the error I receive. There are no options except OK.
So what value IRPStackSize is set to right now?
ASKER
I have tried values all the way up to 48 without sucess.
Currently it is at 18.
Currently it is at 18.
The article states that this error message may also occur after installing or uninstalling virus-scanning software. What is AV installed on your server, if any? Also, could you run (on the server) command "IPCONFIG /ALL" and post the output?
ASKER
I am Running Symantec Antivirus on all systems'
V10.1.7.7000 on the x64 Workstation
V10.1.5.5000 on the server 2003 Enterprise r2 Domain Controller
x64WS.txt
2003E-DC.txt
V10.1.7.7000 on the x64 Workstation
V10.1.5.5000 on the server 2003 Enterprise r2 Domain Controller
x64WS.txt
2003E-DC.txt
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I can now map drives except the RAID 5 volume on the XPx64 Workstation.
It still comes up w/ the "not enough sever storage to process this command" error.
Any ideas why this volume is still affected?
It still comes up w/ the "not enough sever storage to process this command" error.
Any ideas why this volume is still affected?
eb