an xp computer on an established win2000 wired network

  • Thread starter Thread starter Jim
  • Start date Start date
J

Jim

I've just installed XP on one of the computers in the
office and it cannot "see" any of the others on the
network. All are connected via a central hub in a simple
peer to peer config. All are working on the same
workgroup. What is it about XP that keeps it from just
showing up when all dives are shared?
 
I've just installed XP on one of the computers in the
office and it cannot "see" any of the others on the
network. All are connected via a central hub in a simple
peer to peer config. All are working on the same
workgroup. What is it about XP that keeps it from just
showing up when all dives are shared?
Click to expand...

The built-in firewall?
 
Jim:

With this problem the first thing to check in XP
is the built-in firewall. If you are behind a NAT router
you can safely turn this off for good, but at least turn it off temporarily to
diagnose your problem. (Under no circumstances expose your
system bare to a raw Internet connection -- even momentarily.)

Otherwise, you need to give forth a little more information as
there are a depressingly large number of ways things can
fail in network-land.

How do the systems get their IP settings (DHCP or fixed), and
what are they? Is the XP system able to access the Internet? Can
you "ping" any of the other computers. If you start...run...
"CMD" and type in "net view" do you see anything?
How about "net view \\remote-machine-name" -- can you see
the remote shares then?

Steve Duff, MCSE
Ergodic Systems, Inc.
 
I have the same symptoms as Jim.

To answer Steve's questions: I can ping in both directions XP Pro
<--->Win2K Pro
The XP firewall is disabled. The computer browser service is enable on
both.
The XP system can access the internet. The "net view" command displays
only the local machine on the XP system and doesn't display anything on the
Win2K Pro
machine.

Still Stymied after many days :-(
 
Back
Top