Crossover cable connection failure

[Bill Willett]

We are using Netline USB ethernet cards with a crossover
cable to connect to pc's at home. This connection worked
up until yesterday when we scratched the hard drive on one
pc. The reinstall of Windows 2000 was required by the
infestation of BLASTER and poor performance following the
clean up. Now, the pc with the new install cannot access
the other pc but the unaffected pc can access the other.
We have verified that the WINS settings in TCP/IP are
correct and are matching in both pc's. The driver is
installed and showing as correct on non-connecting pc.
Service pack has been installed and the patch for BLASTER
has been installed and Symantec's BLASTER cleaner has been
run and the pc shows as clean from BLASTER. Any ideas on
where to go from here would be most appreciated. Thanks.

 

[bill willett]

Forgot to add - we are using Windows 2k Pro - the network
identifier has been tried both as a business network and
as being used at home - we tried using both the default
WORKGROUP name as the workgroup and with HOME designated
as the workgroup - the results have been the same.

 

[bill willett]

Can PING from the non-connecting pc to the working pc

 

[David Bolt]

First, I don't understand why you had to re-install as a result of msblast,
installing the patch and then running the McAfee cleaner worked fine for me.
Second, I have found that ensuring both machines are on the same workgroup
name AND both are on static IP addresses, eg 192.168.0.1 and 192.168.0.2,
AND the mask is the same, eg 255.255.255.0, often clears this up in the
short term.
I am not sure that W2k provides a DNS server, can anyone enlighten me,
unless it is the server version.
HTH
Dave