Ken Moore
December 1st, 2002, 23:23 PM
My client has 3 machines. C and B both run Win98 and were happily networked
together using a crossover UTP cable. He wanted the third machine (A)
brought into the equation so I got him a network switch and some normal UTP
cables. Machine C runs Windows XP.
C and B plugged in and worked OK. Add A to the equation and the connection
is bad. It's not that it doesn't work at all but that the connection is
poor, eg. when I ping C or B from A I get maybe 40% OK and fast (<1ms) but
the other 60% getting no response even with a 10 second wait! Needless to
say trying to use Windows explorer to look at the network is a waste of
time. It takes for ever to let me know that it can't get at the network and
this is the case from any machine. C and B seem able to ping A (and each
other) OK.
The machines seem to be announcing their presence OK on the network in that
I when I do 'ping <machine name>' it finds the correct IP address.
I have set the system to have fixed IP addresses (192.168.0.1, 2 or 3) just
so I know where I am (and they all have the same subnet mask of
255.255.255.0!)
I have checked all the following (and more)
* The XP firewall is turned off.
* NetBIOS is enabled over TCP/IP on all machines
* No extraneous protocols are lying around (eg. NetBEUI)
If nothing was working at all I'd feel I could track it down but it seems to
be almost working and I can't help feeling that there's some flag set
somewhere that is causing a problem.
I've changed cables and ports but to no avail.
The silly thing is that at one time machine A was connected to B with a
crossover cable but since then the XP system has been rebuilt in some way.
together using a crossover UTP cable. He wanted the third machine (A)
brought into the equation so I got him a network switch and some normal UTP
cables. Machine C runs Windows XP.
C and B plugged in and worked OK. Add A to the equation and the connection
is bad. It's not that it doesn't work at all but that the connection is
poor, eg. when I ping C or B from A I get maybe 40% OK and fast (<1ms) but
the other 60% getting no response even with a 10 second wait! Needless to
say trying to use Windows explorer to look at the network is a waste of
time. It takes for ever to let me know that it can't get at the network and
this is the case from any machine. C and B seem able to ping A (and each
other) OK.
The machines seem to be announcing their presence OK on the network in that
I when I do 'ping <machine name>' it finds the correct IP address.
I have set the system to have fixed IP addresses (192.168.0.1, 2 or 3) just
so I know where I am (and they all have the same subnet mask of
255.255.255.0!)
I have checked all the following (and more)
* The XP firewall is turned off.
* NetBIOS is enabled over TCP/IP on all machines
* No extraneous protocols are lying around (eg. NetBEUI)
If nothing was working at all I'd feel I could track it down but it seems to
be almost working and I can't help feeling that there's some flag set
somewhere that is causing a problem.
I've changed cables and ports but to no avail.
The silly thing is that at one time machine A was connected to B with a
crossover cable but since then the XP system has been rebuilt in some way.
