Something up with XP and TCP/IP...

[Assimilator]

I have a small LAN at home (just a crossover cable). My own computer
is Firelance (192.168.10.20), my brother's computer is Bartonserver
(192.168.10.10). Both are running Windows XP Professional with Service
Pack 1. Workgroup is set to HOME for both PCs.

After installing some software, my machine BSODed whenever I
Hibernated it. So a week ago I ran System File Checker (sfc /scannow).
That fixed the BSOD problem, but now the networking is screwy.

Both computers can access each others' shared drives, but when I do:

"ping Bartonserver" or "ping 192.168.10.10"

from Firelance, I get the dreaded "Request timed out" message.
However, if I do

"ping Firelance" or "ping 192.168.10.20"

from Bartonserver, it works.

"ping localhost" and "ping 127.0.0.1" works on both machines.

On both machines, I've verified the network settings and uninstalled
all protocols except for TCP/IP. The hosts.sam files on both machines
contain the correct hostnames-to-IP mappings; neither is connected to
the Internet.

I've tried uninstalling the network cards in Device Manager, and
allowing the network to be re-installed - no fix.
I've tried allowing each network adapter to use a random IP address -
no fix.

I think it may be caused by SFC restoring system file(s) from the XP
install CD, rather than using the updates from SP1. Any suggestions?

 

[Chuck]

I have a small LAN at home (just a crossover cable). My own computer
is Firelance (192.168.10.20), my brother's computer is Bartonserver
(192.168.10.10). Both are running Windows XP Professional with Service
Pack 1. Workgroup is set to HOME for both PCs.

After installing some software, my machine BSODed whenever I
Hibernated it. So a week ago I ran System File Checker (sfc /scannow).
That fixed the BSOD problem, but now the networking is screwy.

Both computers can access each others' shared drives, but when I do:

"ping Bartonserver" or "ping 192.168.10.10"

from Firelance, I get the dreaded "Request timed out" message.
However, if I do

"ping Firelance" or "ping 192.168.10.20"

from Bartonserver, it works.

"ping localhost" and "ping 127.0.0.1" works on both machines.

On both machines, I've verified the network settings and uninstalled
all protocols except for TCP/IP. The hosts.sam files on both machines
contain the correct hostnames-to-IP mappings; neither is connected to
the Internet.

I've tried uninstalling the network cards in Device Manager, and
allowing the network to be re-installed - no fix.
I've tried allowing each network adapter to use a random IP address -
no fix.

I think it may be caused by SFC restoring system file(s) from the XP
install CD, rather than using the updates from SP1. Any suggestions?

Do you have any personal firewalls on either computer, or have you ever had in
the past?

Check for a corrupted LSP / Winsock subsystem.
http://support.microsoft.com/?id=318584
http://support.microsoft.com/?id=811259

Give LSP-Fix <http://www.cexx.org/lspfix.htm>, WinsockFix
<http://www.tacktech.com/display.cfm?ttid=257>, or WinsockXPFix
<http://www.spychecker.com/program/winsockxpfix.html> a shot.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.

 

[Steve Winograd [MVP]]

I have a small LAN at home (just a crossover cable). My own computer
is Firelance (192.168.10.20), my brother's computer is Bartonserver
(192.168.10.10). Both are running Windows XP Professional with Service
Pack 1. Workgroup is set to HOME for both PCs.

After installing some software, my machine BSODed whenever I
Hibernated it. So a week ago I ran System File Checker (sfc /scannow).
That fixed the BSOD problem, but now the networking is screwy.

Both computers can access each others' shared drives, but when I do:

"ping Bartonserver" or "ping 192.168.10.10"

from Firelance, I get the dreaded "Request timed out" message.
However, if I do

"ping Firelance" or "ping 192.168.10.20"

from Bartonserver, it works.

"ping localhost" and "ping 127.0.0.1" works on both machines.

On both machines, I've verified the network settings and uninstalled
all protocols except for TCP/IP. The hosts.sam files on both machines
contain the correct hostnames-to-IP mappings; neither is connected to
the Internet.

I've tried uninstalling the network cards in Device Manager, and
allowing the network to be re-installed - no fix.
I've tried allowing each network adapter to use a random IP address -
no fix.

I think it may be caused by SFC restoring system file(s) from the XP
install CD, rather than using the updates from SP1. Any suggestions?

Have you installed another network protocol on each computer? That
could explain why file sharing works but pinging from Firelance to
Bartonserver doesn't.

A hosts file isn't needed for a LAN to work. If you want to use one,
the correct file is c:\windows\system32\drivers\etc\hosts , which has
no ".sam" or other characters on the end.

A firewall program on Bartonserver could be blocking TCP/IP access
from Firelance: SP1's built-in Internet Connection Firewall, or a
third party program from ZoneLabs, Norton, McAfee, PC-cillin, etc.

If that doesn't help, try these:

1. Use the procedure shown here under "How to Recover from Winsock2
corruption":

How to determine and recover from Winsock2 corruption
http://support.microsoft.com/?id=811259

2. Download LSPFix on another computer, copy it to Bartonserver, and
run it. It's available from http://cexx.org/lspfix.htm .
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com