XP home cannot talk to XP Pro

[Guest]

This can turn hair gray quickly

2 computers in a LAN
Laptop with XP home
Desktop with XP Pro

I can see the other computer and its shares

Problem: It asks for a login/password

I tried the secpol.msc and setting classic model -- along with same account/pass on both boxes but no luck.

My ideal solution is to have the thing just share without having to mess with creating/modifying accounts or messing with secpol.msc

Help is appreciated!!

 

[David Dickinson]

Um... which one is "the other computer". It makes a difference.

 

[Chuck]

This can turn hair gray quickly

2 computers in a LAN
Laptop with XP home
Desktop with XP Pro

I can see the other computer and its shares

Problem: It asks for a login/password

I tried the secpol.msc and setting classic model -- along with same account/pass on both boxes but no luck.

My ideal solution is to have the thing just share without having to mess with creating/modifying accounts or messing with secpol.msc

Help is appreciated!!

With a mixed LAN (XP Home and Pro), you need to enable Simple File Sharing
(Control Panel - Folder Options - View - Advanced settings) on the XP Pro
computer. SFS is the only choice with XP Home.

You then have to enable the Guest account on both computers (Start - Run -
"lusrmgr.msc"). SFS uses the Guest account, only, for network sharing.

Do either computer have a software firewall (ICF or third party)? If so, you
need to configure them for file sharing, by opening ports TCP 139, 445 and UDP
137, 138, 445, and / or by identifying the other computers as present in the
Local (Trusted) zone. Firewall configurations are a very common cause of
(network) browser, and file sharing, problems.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[Guest]

After 11 hours of banging my head...

The problem was due to NORTON ANTIVIRUS changing a registry setting improperly.
Sorry I do not have the Microsoft Knowledgebase article number --
I changed the one registry setting then reboot -and IT WORKS

 

[Chuck]

After 11 hours of banging my head...

The problem was due to NORTON ANTIVIRUS changing a registry setting improperly.
Sorry I do not have the Microsoft Knowledgebase article number --
I changed the one registry setting then reboot -and IT WORKS

Thanks for updating us. If you get the KB number, you might help some folks in
the future by posting it. That's how these forums work.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[Guest]

The solution to this proble is here:

NORTON ANTIVIRUS CAUSED THE PROBLEM
http://support.microsoft.com/default.aspx?scid=kb;en-us;177078