home networking (workgroup) for xp-home and win2k

[Guest]

Have read all the public postings, done and redone all the checks. simple 2
pc home network setup. xp-home system can see win2k system via windows
explorer as well as can ping it by name and ip. however, win2k system can not
see xp-home system. keep getting the ever popular "\\pc is not accessible.
the network path was not found." However, can sporadically can ping xp-home
system by name in the first couple minutes after rebooting win2k system.
After that, no more, but can still ping by ip, and both systems can access
internet with no issues...

yes, tcp/ip is setup as suggested
yes, same workgroup
yes, same "user" is logged onto both systems
yes, "user" has a real password that is the same on both systems

 

[Malke]

Have read all the public postings, done and redone all the checks.
simple 2 pc home network setup. xp-home system can see win2k system
via windows explorer as well as can ping it by name and ip. however,
win2k system can not see xp-home system. keep getting the ever popular
"\\pc is not accessible. the network path was not found." However, can
sporadically can ping xp-home system by name in the first couple
minutes after rebooting win2k system. After that, no more, but can
still ping by ip, and both systems can access internet with no
issues...

yes, tcp/ip is setup as suggested
yes, same workgroup
yes, same "user" is logged onto both systems
yes, "user" has a real password that is the same on both systems

That leaves the ever-popular "have you got a firewall" solution. Check
on both computers for a firewall and configure it to allow lan traffic.
If you have Service Pack 2 on your XP box, it automatically enables the
Windows Firewall. If you are not running a third-party firewall, go to
the Windows Firewall applet in Control Panel and enable File & Printer
Sharing on the Exceptions tab. If you are using a third-party firewall
(and have properly configured it to allow your lan traffic as Trusted),
then turn the Windows Firewall off. You don't want two firewalls
running, and a third-party program will be better than the WF.

Malke

 

[Guest]

too funny. right after I sent this posting last night, I realized that was
the one piece of info. I had left out. Thanks for suggesting this, but yes, I
have WF disabled, yes, I have a 3rd party FW, yes, my "trusted" domain is
setup correctly.

Does anyone know if there is something fundamental here that prevents
win2k-pro from being able to access an xp-home system via a workgroup?
Neither has ever been a member of a domain, so I don't believe I have any of
those issues.

Thanks again for the feedback, sorry for not posting that info up front.
FH

 

[Malke]

too funny. right after I sent this posting last night, I realized that
was the one piece of info. I had left out. Thanks for suggesting this,
but yes, I have WF disabled, yes, I have a 3rd party FW, yes, my
"trusted" domain is setup correctly.

Does anyone know if there is something fundamental here that prevents
win2k-pro from being able to access an xp-home system via a workgroup?
Neither has ever been a member of a domain, so I don't believe I have
any of those issues.

All 32-bit MS operating systems can successfully share files among
themselves in a Workgroup. I have a network with Win95, Win98, Win2k,
WinXP, Win2003 Server (and Linux). All machines interact happily. So
you've got something set up wrong.

Here is an excellent network troubleshooter by MVP Hans-Georg Michna. If
you take the time to go through its steps carefully, it will usually
pinpoint the trouble. After you've done so, post back with results if
you need more help.

http://www.michna.com/kb/wxnet.htm

Malke

 

[Guest]

Malke,

You rock!!! I went to your suggested website, and walked through the
questionairre. Had to do a bit of reading, but found my fix and had my home
network working in < hour.

Here's the website (for others reading this post):

http://www.michna.com/kb/wxnet.htm

My issue ended up being my 3rd party firewall (zone alarm). Per all the
posts, I had "turned off" my firewall for my local "trusted" zone, inside the
zone alarm gui. However, if you have only every setup the base "local
network" and have never "added" an allowed ip-range, the firewall somehow
blocks older windows systems' ability to network with XP systems. As with my
issue, before adding an ip-range, my xp system could see my 2k system, but
not visa-versa.

Thanks again!!!

FH

 

[Malke]

Malke,

You rock!!! I went to your suggested website, and walked through the
questionairre. Had to do a bit of reading, but found my fix and had my
home network working in < hour.

Here's the website (for others reading this post):

http://www.michna.com/kb/wxnet.htm

My issue ended up being my 3rd party firewall (zone alarm). Per all
the posts, I had "turned off" my firewall for my local "trusted" zone,
inside the zone alarm gui. However, if you have only every setup the
base "local network" and have never "added" an allowed ip-range, the
firewall somehow blocks older windows systems' ability to network with
XP systems. As with my issue, before adding an ip-range, my xp system
could see my 2k system, but not visa-versa.

Excellent! Actually, it is really Hans-Georg Michna who rocks since he
is the author of the troubleshooter. In any case, I'm very glad you got
things sorted. Thank you for taking the time to post the solution.

Malke