CANNOT CONNECT TO SECOND COMPUTER

[moveit]

I have set up a friends network but cannot get one of the computers to read the other. I get the following error message: Not enough server storage is available to process this command.

I have followed Microsoft's suggestion of increasing the IRPStackSize but no matter what size I increase it to I still get the same error message. Any help would be gratefully accepted.

 

[GrimR]

disable or uninstall all antivirus and firewalls.

 

[moveit]

Hi GrimR
I disabled both anti virus/firewalls on both computers but still got the same error message. My friend has XP Pro on one computer and Windows 2000 on the other. The XP computer can access 2000 computer drives C & D but 2000 computer cannot access XP drive C, only drive D.

 

[GrimR]

check that the admin username and password are the same

 

[moveit]

Admin username and password are the same throughout his home network. What I do not understand is why the Windows 2000 computer can read the drive D on the Xp computer but gets the error message when trying to map onto drive C.

 

[tlcscousin]

Drive C maybe not shared properly.With XP the c drive is usually listed with a $C: which will not allow sharing unless you can turn off simple file sharing and share using permissions. Sharing C drive is usually not recommended.

 

[moveit]

Drive C shows as C. Even the computer shows when mapping but just will not allow access to the C drive. The help on the XP computer does say it should be able to allow other computers to access it.

 

[tlcscousin]

Look at drive C and see if it shows as shared.
If the operating system is XP Pro then turn off simple file sharing and then share the drive.You might have to adjust permissions in order to allow access.

 

[moveit]

It is XP PRO. Simple file sharing was already turned off and as far as I can see the permissions allow access.

 

[tlcscousin]

http://windowsitpro.com/article/art...age-is-available-to-process-this-command.html

The above link suggests another fix to try.I will quote what they suggest.
"you may have a non-zero PagedPoolSize entry in the registry. Edit:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
Set PagedPoolSize to 0.
Reboot.
Another possible cause of this error is if you installed a Service Pack before installing any networking components. If this is the case, re-apply the Service Pack (and any hotfixes).

 

[moveit]

PagePoolSize was already set at 0. The OS came with SP4. All critical downloads have been installed.