XP Home will not network at all

  • Thread starter Thread starter Larry Sonderling
  • Start date Start date
L

Larry Sonderling

A friend of mine asked me to try and resolve the networking problems on a
Dell laptop running XP Home. The machine cannot connect to a network at
all. TCP/IP is set up to use DNS on a LAN. My own machines work fine on
this network. Status show packets going out but none coming in. XP
Firewall is turned off. I know the networking hardware is good because it
works fine under other operating systems. TCP/IP is good because I can ping
the localhost.

BTW, this is my first time working with XP; my own computers run Windows
2000 Professional, but it seems that they shouldn't be too far apart in
setting up the networking.

I feel that I have missed something obvious here but I can't figure out
what!

Any help, hints or pointers will be much appreciated.

Thanks,

Larry
 
What OS's does the rest of the LAN consist of (in your friends case). Can
you also ping the other PC's on the LAN? Can the other PC's ping the Dell?
 
Outgoing Traffic does not mean, that packets are actually
leaving your NIC - they could go to nirwana. Check the
cable...
Then check your TCP/IP settings with "ipconfig /all" from
within a MS-Dos Box.
Do you have a valid IP-address out of your Network-ID?
then you should be able to ping an IP on your LAN.
If everything fails, you can allways try to reinstall the
NIC driver.

Bernie
 
Anonymous said:
What OS's does the rest of the LAN consist of (in your friends case). Can
you also ping the other PC's on the LAN? Can the other PC's ping the Dell?
Click to expand...

The other machines all run Windows 2000. This laptop cannot ping other PCs
nor can other PCs ping it. The laptop also cannot connect to the Internet.
Since this is the case, it also cannot talk to the local DHCP server to get
an ip address.

Output from ipconfig /all is:

Windows IP Configuration

Host Name . . . . . . . . . . . . : FoLAR03
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : IBM 10/100 EtherJet CardBus
Adapter
Physical Address. . . . . . . . . : 00-06-29-92-03-7D
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.59.125
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
 
bernie said:
Outgoing Traffic does not mean, that packets are actually
leaving your NIC - they could go to nirwana. Check the
cable...
Then check your TCP/IP settings with "ipconfig /all" from
within a MS-Dos Box.
Do you have a valid IP-address out of your Network-ID?
then you should be able to ping an IP on your LAN.
If everything fails, you can allways try to reinstall the
NIC driver.
Click to expand...

Right, I see no activity on the hub lights to indicate that packets are, in
fact, being sent out. However, cable is good. If I boot the same laptop
with Linux then everything works correctly (no OS wars, please ;] ). Under
XP Home the laptop doesn't talk or listen to anybody.

I know I'm not a networking guru, but I can't see what I'm missing here.

Larry
 
I have found the answer in another thread which mentioned a similar problem.
it is related to corruption of registry entries for TCP/IP and WinSock. The
fix is a program called WinsockXPFix.exe available at
http://members.shaw.ca/techcd/WinsockXPFix.exe

It goes beyond the results of running "netsh int ip reset resetlog.txt" and
makes other corrections to the registry, LMHOSTS and other networking files.

This really did the trick.

Thanks to all who responded!

Larry
 
Back
Top