Home network connection problem

[KDS16]

We have two XP computers connected through a modem/router both by cable.  One has XP Pro and the other XP home.  At one time we could share files but the XP Pro has had its mother board and hard drive replaced.  Now, We can see each others computer with the intended folders showing in the "My Network Places" windows.  I [XP Pro] can try to "Map" the others folder or drive and the others computer information shows in the Map's "Browse for Folder" window, but when I try to pick a folder I get the following message:
 "The mapped networked drive could not be created because the following error has occurred.  --  Not enough server storage is available to process this command"

When I just click on the others folder in "My Network Places" I get the following error:
  "\\other-computer\folder on other computer is not accessible. You might not have permission to use this 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've looked to other fourms and got the following advice for XP Pro:
"Now you need to make sure that you have NetBIOS over TCP/IP enabled on all the PC's in the network. Open the Network Connections folder, right-click the local area network connection and click Properties, double click Internet Protocol (TCP/IP). Click Advanced button then on the WINS Tab, click the Enable NetBIOS Over TCP/IP button.

The next step is necessary on XP Pro to allow XP Home to connect to it. XP Home uses Simple File Sharing in which all authentication is done via the Guest account. For XP Pro to allow this you need to modify a Group Policy to allow blank passwords. Go to the Start Menu and click on Run. Type in gpedit.msc and click OK. Navigate to Computer Configuration / Windows Settings / Security Settings / Local Policies / Security Options. Now double click on Accounts: Limit local account use of blank passwords to console login only. Change this to Disabled and click OK. 

I did make these changes but nothing improved.

Keith

[couttsj]

1. XP Home does not support file sharing, so the XP Pro machine is the only one that can share files. The XP Home machine should be able to copy files to and from the XP Pro machine.

2. Use of passwords is strongly recommended. A fully updated XP Pro may not allow file sharing with a blank password.

3. Make sure that both computers belong to the same Work Group.

4. Make sure that the UserID/Password is set up the same in both computers. This will allow you to transfer files without having to re-enter the UserId & Password.

5. Make sure that both computers support NetBios over TCP. Alternately, you could install and enable NetBeui (includes NetBios), but NetBios over TCP is easier.

6. Delete all old mappings, because they will no longer be valid after reloading the operating system.

7. Make sure that there is at least one shared directory on the XP Pro machine.

J.A. Coutts

[RB2tfm]

 Sorry I am no help but #1 in the reply above is false.

I used to have a xp home, xp pro and a vista machine/s al networked and sharing folders, printer, etc.

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

[Black Viper]

1. XP Home does not support file sharing, so the XP Pro machine is the only one that can share files. The XP Home machine should be able to copy files to and from the XP Pro machine.

Not sure what you mean by this as I could copy files using "Simple" file sharing to and from a Home system. Thinking of a domain controller and or active directory?

[couttsj]

Not sure what you mean by this as I could copy files using "Simple" file sharing to and from a Home system. Thinking of a domain controller and or active directory?

It could have changed with SP updates, but the original XP Home would only share the "SharedDocs" directory, and could not be turned off. My XP (which I don't use very much) has only been updated to SP1, and it will not share files or directories that are not in the SharedDocs directory. The permissions on the "SharedDocs" directory were by default "Everyone", and that left it accessible to the Internet via NetBios. If you wanted to provide Read/Write access, that left you very vulnerable. Consequently, I changed the permissions on this directory to "Administrator", and accepted the fact that I could not share files. This machine used to sit on an open internet service, and had to be locked down very tightly.

I apologize if that is no longer the case.

J.A. Coutts

[couttsj]

It could have changed with SP updates, but the original XP Home would only share the "SharedDocs" directory, and could not be turned off. My XP (which I don't use very much) has only been updated to SP1, and it will not share files or directories that are not in the SharedDocs directory. The permissions on the "SharedDocs" directory were by default "Everyone", and that left it accessible to the Internet via NetBios. If you wanted to provide Read/Write access, that left you very vulnerable. Consequently, I changed the permissions on this directory to "Administrator", and accepted the fact that I could not share files. This machine used to sit on an open internet service, and had to be locked down very tightly.

I apologize if that is no longer the case.

J.A. Coutts

I am curious. Does XP Home SP3 share files that are not in the "SharedDocs" directory? I had to advise my customers not to use XP Home on a business network because of this limitation, so it would be good to know if this limitation no longer exists.

J.A. Coutts

[Black Viper]

I just looked at XP Home SP2 and no limitation on sharing exists. I just did c: on the Home system for testing purposes and accessed it from a Vista PC connected via the same workgroup. If said system is not in the same workgroup, it may not be shown as available. I do not have easy access to a default XP Home retail install, though, without digging through some old disks hiding somewhere in the junk room.
I was not aware that their was ever a problem, though, with XP Home. This is the first that I have heard of this.
On a business network, XP Home cannot connect to a domain controller for login purposes. This is so corporations could not get off "easy" with buying a bunch of Home editions vice XP Pro.