Windows XP TCP Stack Corruption on Dell Preloaded Machines

[Eric Hill]

I have now seen this same problem on two different Dell machines. It
seems the Windows networking stack is somehow corrupting data as it
flows through the network layers. The symptoms include:

1) Spotty DHCP assignment. Sometimes the machine gets an IP, most of
the time it doesn't.

2) Ping works with a statically assigned IP address to the router and
out to the internet. The name however (pinging xxx with 64 bytes of
data) is garbled with high-word ascii characters.

3) Establishing a TCP socket fails, as well as all DNS-related
queries, i.e. UDP traffic.

I have tried removing and reinstalling network adapter drivers, moving
network cards into different slots, and tried three distinct network
cards. (One onboard 10/100, one NetGear wireless card, and one
Linksys 10/100 PCI card) Both machines were running Windows XP (one
Home, one Pro) with Service Pack 1. I tried installing SP2 on the
Windows XP Home machine. It installed fine, but the problem
persisted.

Since TCP/IP is integral to the OS, I cannot deinstall-reinstall it,
so I'm now at a wall. What can I do next? Level the machine back to
the OEM load? The odd thing is that this problem occurred on two Dell
machines with the OEM preload. Other than that, they have *nothing*
in common. (Different locations/networks/users/purposes etc) Could
this be a problem with the Dell OEM load, or a deeper issue with some
part of the Windows OS network stack?

Any help would be greatly appreciated.

Thanks,
Eric

 

[Malke]

I have now seen this same problem on two different Dell machines. It
seems the Windows networking stack is somehow corrupting data as it
flows through the network layers. The symptoms include:

1) Spotty DHCP assignment. Sometimes the machine gets an IP, most of
the time it doesn't.

2) Ping works with a statically assigned IP address to the router and
out to the internet. The name however (pinging xxx with 64 bytes of
data) is garbled with high-word ascii characters.

3) Establishing a TCP socket fails, as well as all DNS-related
queries, i.e. UDP traffic.

I have tried removing and reinstalling network adapter drivers, moving
network cards into different slots, and tried three distinct network
cards. (One onboard 10/100, one NetGear wireless card, and one
Linksys 10/100 PCI card) Both machines were running Windows XP (one
Home, one Pro) with Service Pack 1. I tried installing SP2 on the
Windows XP Home machine. It installed fine, but the problem
persisted.

Since TCP/IP is integral to the OS, I cannot deinstall-reinstall it,
so I'm now at a wall. What can I do next? Level the machine back to
the OEM load? The odd thing is that this problem occurred on two Dell
machines with the OEM preload. Other than that, they have *nothing*
in common. (Different locations/networks/users/purposes etc) Could
this be a problem with the Dell OEM load, or a deeper issue with some
part of the Windows OS network stack?

Try a different router. We've got 40 Dells in the school lab and I have
numerous clients with Dells and have never seen this issue. That isn't
meant to invalidate your experience; it's just that I would look to a
faulty router or switch first.

Malke

 

[Eric Hill]

Try a different router. We've got 40 Dells in the school lab and I have

numerous clients with Dells and have never seen this issue. That isn't
meant to invalidate your experience; it's just that I would look to a
faulty router or switch first.

Thanks for the follow-up.

I've tried both a plain Linksys soho router (connected to two
different ethernet ports) and a Cisco 1711 router with a Cisco 2950
ethernet switch, both with the same results.

Other machines are working fine through both of these routers. Sigh.

Eric

 

[Malke]

Thanks for the follow-up.

I've tried both a plain Linksys soho router (connected to two
different ethernet ports) and a Cisco 1711 router with a Cisco 2950
ethernet switch, both with the same results.

Other machines are working fine through both of these routers. Sigh.

Eric

Then I'm so sorry, but I don't know the answer. Cables? Spyware?
Viruses? It just seems unlikely that there is something wrong with the
operating system since the same operating system doesn't produce your
symptoms elsewhere. If the machines are under warranty and/or you are a
company with a corporate service contract with Dell, maybe you could
escalate the issue with their higher tier tech support. Or even try
Microsoft support. Yes, you have to pay for it, but my experience with
paid support (I called for help on a server once) was very good.

Good luck,

Malke

 

[Eric Hill]

Then I'm so sorry, but I don't know the answer. Cables? Spyware?

Viruses? It just seems unlikely that there is something wrong with the
operating system since the same operating system doesn't produce your
symptoms elsewhere. If the machines are under warranty and/or you are a
company with a corporate service contract with Dell, maybe you could
escalate the issue with their higher tier tech support. Or even try
Microsoft support. Yes, you have to pay for it, but my experience with
paid support (I called for help on a server once) was very good.

I went down the spyware and virus road. The machine wasn't virus
infected, but had some spyware stuff on it, though removing it had no
effect on the problem.

I've practically given up on tech support from Dell since they want to
re-load the machine from the recovery CD for any problems like this.
That is my last resort, I'd really rather find the root cause of the
problem .

If I was going to spend $295 on a tech support call to Microsoft, I'd
just buy another computer

Thanks!

Eric

 

[Niels]

I went down the spyware and virus road. The machine wasn't virus
infected, but had some spyware stuff on it, though removing it had no
effect on the problem.

I've practically given up on tech support from Dell since they want to
re-load the machine from the recovery CD for any problems like this.
That is my last resort, I'd really rather find the root cause of the
problem .

If I was going to spend $295 on a tech support call to Microsoft, I'd
just buy another computer

Thanks!

Eric

I admit it becomes guessing what the problem is cause I haven't got any
problem either.
However, can it be that both Dell's are from the same series with
bad/corrupt chip set or whatsoever ? Did you buy them at the same time ?

We recently replaced 52 cisco 3500 switches because of a bad field note
(FN44941). Maybe Dell has a bad series ??

Just a thing that slipped my mind..

Good luck, I am starting the weekend ;-)

Niels

 

[Mike Kern]

I've seen this same problem on a Dell and a Systemax machine. Finally
reinstalled the OS on the Dell and solved the problem. No luck yet on
the Systemax box, but would love to find a solution that doesn't
involve a reload...

-Mike Kern
(e-mail address removed)

 

[Andre Da Costa]

Right click on the Ethernet connection in My Network Place and choose
Repair.

Andre

 

[Bill]

Also:
at the comand prompt use 'netsh int ip reset c:\resetlog.txt' to
restore the IP default config..
also 'netsh ?' will give you lots of comand operators...
Bill

 

[Guest]

I have fixed this problem on a few Dell pc's. I have fixed it by following
http://support.microsoft.com/default.aspx?scid=kb;en-us;299357 and
reinstalling the TCP/IP Protocol from I386, Reboot.

Charles