Having trouble seeing a new XP box in a workgroup

  • Thread starter Thread starter Icebiker
  • Start date Start date
I

Icebiker

Hi,

I've added a new XP Home box to my network. The problem is that the existing
computers don't see it and it doesn't see the other computers.

The workgroup is set up correctly, and I ran the networking wizard on all
the boxes. Sometimes, if I turn off all the firewalls, everything talks.

However, the next time the computers come out of standby, the new box is out
in the cold again.

I think the network hardware itself is OK. All boxes can talk to the net
through the router even when the MS network isn't working.

What am I missing here? Is there a service that's not getting started? I
would have thought the network wizard would have set things up correctly.

/icebiker
 
I've added a new XP Home box to my network. The problem is that the existing
computers don't see it and it doesn't see the other computers.

The workgroup is set up correctly, and I ran the networking wizard on all
the boxes. Sometimes, if I turn off all the firewalls, everything talks.

However, the next time the computers come out of standby, the new box is out
in the cold again.

I think the network hardware itself is OK. All boxes can talk to the net
through the router even when the MS network isn't working.

What am I missing here? Is there a service that's not getting started? I
would have thought the network wizard would have set things up correctly.
Click to expand...

/icebiker,

please have a look at http://www.michna.com/kb/WxNetwork.htm.

Hans-Georg
 
Hi Hans-Georg

Your faq suggested that I try uninstalling the IPX protocol. In fact, the
new computer did not have the protocol, but all the others did (for lan
games). I installed IPX on the new box and everything seems to work. I guess
Client for MS Networks decided to use that protocol.

Is there a way to see what protocol Client for MS Networks is binding to? I
know how to find that out in Win98, but I can't figure out where that
information is in XP. It could have saved me a lot of grief if that was
visible.

Thanks for the help, I was really stuck.

icebiker
 
Your faq suggested that I try uninstalling the IPX protocol. In fact, the
new computer did not have the protocol, but all the others did (for lan
games). I installed IPX on the new box and everything seems to work. I guess
Client for MS Networks decided to use that protocol.

Is there a way to see what protocol Client for MS Networks is binding to? I
know how to find that out in Win98, but I can't figure out where that
information is in XP. It could have saved me a lot of grief if that was
visible.
Click to expand...

icebiker,

from http://www.michna.com/kb/WxNetwork#Transport_protocols :

"... If you need IPX for local network game playing, remove all
bindings to that protocol (use the Advanced command in control
panel, Network). But check your games first. Many also offer
gaming over IP, for example using the UDP protocol, in which
case only TCP/IP is needed."

I should have been more precise as to where the bindings can be
changed and have already tried to improve the text. Please have
another look if you like.

Or try this. Right-click on My Network Places, click on
Properties, click on the Advanced command, then Advanced
settings, then use the tab Network adapters and bindings. Remove
the check marks from the IPX protocol.

Actually you could also use IPX for Windows networking and
remove the checkbox from the TCP/IP protocol instead, but since
everybody else uses TCP/IP, it is better to stick to that, in
case you want to attach a guest's or friend's computer to your
network and copy some files.

Hans-Georg
 
You should probably say right-click on My Network Places in Explorer. There
is also a My Network Places item in the "See Also" section of the Network
and Internet Connections control panel that is not right clickable.

XP usability baffles me. Sometimes you right click on an object to change
it's properties, sometimes you use menus, and sometimes theres a button on
the left explorer bar.

I doubt I'll ever be able to get rid of IPX, it seems that there is always
going to be a game that needs it.

I agree about using TCPIP for MS networks. However, for a while I did use
IPX for my Windows network based on recommendations from Steve Gibson
(www.grc.com). I believe is reasoning was that it separated internet TCP/IP
traffic from local LAN traffic. I'm behind a router now, so I'm feeling
pretty safe.

By the way, your faq asks for e-mail if the tips helped. You might want to
update that.

Thanks for all your time.

/icebiker
 
You should probably say right-click on My Network Places in Explorer. There
is also a My Network Places item in the "See Also" section of the Network
and Internet Connections control panel that is not right clickable.
Click to expand...

Icebiker,

done. Thanks!
XP usability baffles me. Sometimes you right click on an object to change
it's properties, sometimes you use menus, and sometimes theres a button on
the left explorer bar.

I doubt I'll ever be able to get rid of IPX, it seems that there is always
going to be a game that needs it.

I agree about using TCPIP for MS networks. However, for a while I did use
IPX for my Windows network based on recommendations from Steve Gibson
(www.grc.com). I believe is reasoning was that it separated internet TCP/IP
traffic from local LAN traffic. I'm behind a router now, so I'm feeling
pretty safe.
Click to expand...

I've written a bit about that, in
http://www.michna.com/kb/WxCable.htm. I would remove all
bindings from IPX, so only the games use it. Have that here too
on the kids' computers.

Of course Windows networking can be run over IPX just as well.
Then I would remove the bindings from TCP/IP. This is one way
out of the problem when the cable ISP gives you fixed IP
addresses that are not in one subnet reserved for you. I prefer
to use TCP/IP for Windows networking though, for a couple of
reasons. One is that nearly everybody does it, so it is a more
thoroughly tested environment. Another is that I occasionally
establish a link across the Internet, which precludes IPX. Yet
another is that some computers here don't even have or need IPX,
but they all need TCP/IP.

Hans-Georg
 
Back
Top