XP wired network connectivity...

[Wapiti]

I know this has been brought up in several NGs and forums before - and I
think there is some type of config issue in some XP installations causing
it - as some I have noticed go unresolved.

First, I'm not new to networking, software or computing hardware. I have
installed many networks - so having this baffle me like this is frustrating.

I have three XP machines, networked in a peer-to-peer configuration. DHCP
is handled via the dsl modem/router.

There is one XP machine that will not connect to the network properly.

Scenario: There are three computers, all XP. ComputerA, B and C.
ComputerC is the one giving problems. All are configured with the same
workgroup. All have matching username/passwords. I have swapped cable
lines between them with the same results.

ComputerA (10.0.0.14)
-----------------------------------------------------
Has NIS firewall, configured to allow the LAN
XP firewall is disabled.
Can ping A (localhost)
Can ping B
Cannot ping C
Can ping outside web address (ie ping www.att.net)
Can connect to the internet.
"View WG Computers" lists all computers on the network (B and C)
Can map drive to B
Cannot map drive to C
Can connect to the internet.

ComputerB
-----------------------------------------------------
Has XP firewall disabled
Can ping A
Can ping B (localhost)
Cannot ping C
Can ping outside web address (ie ping www.att.net)
Can connect to the internet.
"View WG Computers" lists all computers on the network
Can map drive to A
Cannot map drive to C

ComputerC
-----------------------------------------------------
Has -NO- firewall, XP fw is disabled
Can ping A
Can ping B
Can ping C (localhost)
Can ping outside web address (ie ping www.att.net)
Cannot connect to the internet (browser pagenotfound)
"View WG Computers" gives permission error.
Can map drive to A (using ip address only - not servername)
Can map drive to B (using ip address only - not servername)

Part of my job is to test and work on troubled computers - I connect many
different computers per day to this network without a problem. This new
computer however has not been able to connect (Dell Dmn 2400).

Can anyone else shed light on this problem? I'm at a loss.

Thanks,

Mike

 

[Lance]

I'm new to networking, so I hesitate to give advice to a pro.

Your computer C acts like my wired desktop at home used to (except I
could connect to the 'net and it could view itself, but no one else, in
My Network Places).

My fix is to uninstall Cisco VPN, uninstall the Zonelabs firewall
components Cisco VPN installs. Then go through manual uninstall steps
for Cisco and Zonelabs, reset the tcp/ip stack, reinstall Cisco VPN. I
have the links for these instructions at home (I'm at work now).

Look for vsdatant.sys or vsutil.dll in the system32 folder. These are
the Zonelab components that seem to give me trouble.

Others had some success with updating their NIC drivers.

Good luck,

Lance
*****

Wapiti said the following on 8/20/2004 12:54 PM:

 

[Wapiti]

I have no installation of VPN, nor ZoneAlarm.

I'm new to networking, so I hesitate to give advice to a pro.

Your computer C acts like my wired desktop at home used to (except I
could connect to the 'net and it could view itself, but no one else, in
My Network Places).

My fix is to uninstall Cisco VPN, uninstall the Zonelabs firewall
components Cisco VPN installs. Then go through manual uninstall steps
for Cisco and Zonelabs, reset the tcp/ip stack, reinstall Cisco VPN. I
have the links for these instructions at home (I'm at work now).

Look for vsdatant.sys or vsutil.dll in the system32 folder. These are
the Zonelab components that seem to give me trouble.

Others had some success with updating their NIC drivers.

Good luck,

Lance
*****

Wapiti said the following on 8/20/2004 12:54 PM: