XP Pro to XP Home network crossover

I have purchased a new computer, it has XP Home, FAT32 filesystem.  I want to network this new computer with my main computer (server) which runs WinXP Pro.  The ICF works as I am typeing this message on the new computer (client).  The problem is the file shareing.  I get the message:

“\\<computer name> 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.

The XP Pro is on NTFS file system, where the client XP Home is Fat32.  The computers are connected via crossover cable, (I Know I will be buying a router in the very near future), for now I need to get the file shareing to work with the existing crossover cable.

The ICF has been disabled on both computers, they both are in workgroup MSHOME, Simple fileshareing disabled on server.  On server the folder to share has been enabled for shareing and permissions given for username blakelock, the client has been set up with a blakelock acount and same password to match the acount on the server.

I dont understand how this can be hapening.  I need a solution for this.
jetsonsblueAsked:
Who is Participating?
 
rindiConnect With a Mentor Commented:
Use tcp/ip, not ipx protocol. IPX was a protocol used for early netware systems, and isn't used anymore today. Routers and gateway devices probably don't support this protocol, and if they do, you have to configure this option in the device configuration tool.
0
 
woof-dogCommented:
Make sure no other firewqall is running.

Are you trying to mount (map) the C: drive?  If so don't forget you use \\I.P address\c$ or $c (can't remember), or instead of c$ or $c put in whatever you are using as a share name.

Ok if you already doing that try sharing a folder not a drive.  Example setup a sharing and a folder on computer A say folder 'test' then mount it from Computer B, example \\I.P address\test
0
 
jetsonsblueAuthor Commented:
Not wanting to share entire drive, I have set several folders includeing My Documents for shareing.  These shares apear in network places, however when I try to access them, I have the error.

What do you mean by trying to mount it?
0
Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

 
rindiCommented:
XP with SP2 has an automatically enabled firewall. Either disable this or configure it so that your networking functions are open (exceptions tab of the firewall, file an print sharing as exception, tcp ports 139, 445 and udp ports 137, 138 must be allowed). You will find the windows firewall under control panel. If you have a further firewall installed, you must first decide on which one you want to use. Some antivirus products also have some firewall functions, I believe mcaffee has such a product, symantec has different such products (internet security) etc. Then disable the firewall you aren't going to use and add the above settings to the one you are going to use.
You will also have to to add the user "blakelock" to those which are allowed access to your shares (check the "shares" properties).
0
 
Steve McCarthy, MCSE, MCSA, MCP x8, Network+, i-Net+, A+, CIWA, CCNA, FDLE FCIC, HIPAA Security OfficerIT Consultant, Network Engineer, Windows Network Administrator, VMware AdministratorCommented:
When putting peer to peer sharing in place with XP Pro and XP Home, I have found out that the administrative share c$ does not always work.  You have to have all the basics in place like the same subnet and same workgroup first as well as file and print sharing turned on.  If you have SP2, the firewall must also have file and print sharing enabled.  What I have done to get around this is to share the drive with a different drive letter.  So, since c$ didn't work, I shared it a C or CDrive.  It has worked every time.
0
 
jetsonsblueAuthor Commented:
How do I go abouts changeing the share name from c$ to C
0
 
rindiCommented:
Just right click the directory you want shared, select "sharing and security", then the "sharing" tab. Now select "share this folder", enter a share name, don't make the name too long and don't use special characters or spaces. If it is the complete drive you want to share, you'll have a sharename already (Drive$), then just click the button "new share"...
0
 
jetsonsblueAuthor Commented:
Ive gone into the firewall config, and turned it off, I then went to the exceptions tab and unchecked everything.  For the folder in which I want to share, on shareing and security, I have added for the permisions, blakelock.  There is no other firewalls, installed.

I tryed to find where I can rename the $c but cannot seem to find it.
0
 
rindiCommented:
You don't need to rename it, just create a new share. If I were you I wouldn't share at drive level, I believe it is better to share at directory level, it is safer and you can't wreck as much (If it is a system drive, it would be possible to delete important system files).

Also, in the firewall config you should only uncheck those exceptions you don't want. If you want your PC to be able to share folders and printer, the file and printer sharing exception must be checked.
0
 
jetsonsblueAuthor Commented:
the reason for wanting to rewname the c$ share was reguarding samccarthy's post.

I just rechecked the file and prionter shareing, but the problem still exists.  So now firewall is turned off and in exceptions file and printer shareing is checked.

I have now set 3 folderas foer share, and in shareing and security, ive addewd the user blakelock and given full access.  The problemn still exists.

Just to clerify

Comp A - WinXP PRO Sp1 - ntfs
Comp B - WinXP Home Sp2 - fat32

Same workgroup, ipx protocol,  
0
 
Steve McCarthy, MCSE, MCSA, MCP x8, Network+, i-Net+, A+, CIWA, CCNA, FDLE FCIC, HIPAA Security OfficerIT Consultant, Network Engineer, Windows Network Administrator, VMware AdministratorCommented:
You don't need to rename it, just create a new share and call it what you want.  Sorry if I wasn't clearer there.  As I said, it fixed all of my problems.  Also, you just need to use TCP/IP, not IPX.
0
 
jetsonsblueAuthor Commented:
ok it was a two part roblem, first I changed back to tpc/ip as sugested, and second, I had to add authenticated users and administrators group along with blackelock to the share permisions for each folder, and this finaly solved the problem.

Since TCP/IP was paert of my problem, and rindi mentioned it first, i think it is only fair to acept rindi's answer, Let me know if we can agree on this, and I will acept the answer/answers when I hear back.
0
 
jetsonsblueAuthor Commented:
I forgot to mention that before the problem was solved i  did create a new share on C drive named C , rebooted, and it did not work.  The actual solution was above, let me know if you think I should split points or assign only to rindi.
0
 
Steve McCarthy, MCSE, MCSA, MCP x8, Network+, i-Net+, A+, CIWA, CCNA, FDLE FCIC, HIPAA Security OfficerIT Consultant, Network Engineer, Windows Network Administrator, VMware AdministratorCommented:
Whatever got you to the answer.  If the thread pulled out the problem by questions and answers, then split the points.  If you feel rindi alone answered you post, then give it to him.
0
 
rindiCommented:
thanx.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.