Strange networking problem...

[Mike]

I've got a desktop running XP Pro, SP3 & have a networking problem.
I am getting an IP address from my Linksys router, but cannot get on
Internet.
If I try to ping by name, I get 'host not found' & pinging by addess times
out.
I have tried Winsock fix & still no luck.
Nothing in hosts file, either.
Any other computer can connect just fine.
Any suggestions?

 

[Jack [MVP-Networking]]

Hi
Can you connect to the Router Menus, or and, other computers.
If you can not, it means that the computer is Not really connected to the
Router/Network.
Maybe this can Help, http://www.ezlan.net/debug.html
Jack (MS, MVP-Networking)

 

[John Wunderlich]

I've got a desktop running XP Pro, SP3 & have a networking
problem. I am getting an IP address from my Linksys router, but
cannot get on Internet.
If I try to ping by name, I get 'host not found' & pinging by
addess times out.
I have tried Winsock fix & still no luck.
Nothing in hosts file, either.
Any other computer can connect just fine.
Any suggestions?

I assume you can ping by IP address OK but by name doesn't work.
It sounds like your DNS settings aren't getting set automatically from
your router's DHCP server. Since other machines work OK, it's probably
not your DHCP server. Check the network configuration for your NIC and
make sure that you have the "Set DNS Automatically" box checked:

Control Panel -> Network Connections -> Right-click your connection->
Properties ->
In the window, scroll to the bottom and double-click on "TCP/IP"
Make sure the "Obtain DNS server address automatically" checkbox is
checked.

Verify DNS Server is being set correctly by bringing up a command
window (Start -> Run -> "cmd") and enter the command:

ipconfig /all

Verify your "DNS Servers" line is identical to your other machines.

HTH,
John

 

[Mike]

Yes, I am able to connect to router menus, run diagnostics from the
router, etc., but it gets even better.
Since I was running short on time, I took the computer home with me &
plugged into my network, basically the same Comcast, Linksys wireless
router.
The wired connection gets an IP address from my router, but still
can't get on internet or ping anything.
Even stranger, the wireless connection still thinks it's connected to
the wireless network at old location.
I can right click & show available networks & it doesn't show any of
the ones actually present, but shows ones from old location!
Maybe a repair install is in order?"

 

[Jack [MVP-Networking]]

Hi
If this process (which it seems that already did part of it) does not make
it working it might be that the solution is repair install.
http://www.ezlan.net/clean.html#refershnet
Jack (MS, MVP-Networking)

Yes, I am able to connect to router menus, run diagnostics from the
router, etc., but it gets even better.
Since I was running short on time, I took the computer home with me &
plugged into my network, basically the same Comcast, Linksys wireless
router.
The wired connection gets an IP address from my router, but still
can't get on internet or ping anything.
Even stranger, the wireless connection still thinks it's connected to
the wireless network at old location.
I can right click & show available networks & it doesn't show any of
the ones actually present, but shows ones from old location!
Maybe a repair install is in order?"

 

[Chuck [MVP]]

I've got a desktop running XP Pro, SP3 & have a networking problem.
I am getting an IP address from my Linksys router, but cannot get on
Internet.
If I try to ping by name, I get 'host not found' & pinging by addess times
out.
I have tried Winsock fix & still no luck.
Nothing in hosts file, either.
Any other computer can connect just fine.
Any suggestions?

Mike,

If LSP Winsock corruption is part of the problem, one pass with just Winsock Fix
may not be enough.

http://networking.nitecruzr.net/2005/05/problems-with-lsp-winsock-layer-in.html

 

[Mike]

Mike,

If LSP Winsock corruption is part of the problem, one pass with just Winsock Fix
may not be enough.

http://networking.nitecruzr.net/2005/05/problems-with-lsp-winsock-lay...

Really?
What could it do on any subsequent passes that it wouldn't fix on the
first?
I tried that, as well as LSP fix, but finally gave up & re-installed!

 

[Chuck [MVP]]

Really?
What could it do on any subsequent passes that it wouldn't fix on the
first?
I tried that, as well as LSP fix, but finally gave up & re-installed!

The chains in Winsock are complicated. Each of the different products - LSPFix
and the various flavours of WinsockFix, have different strengths and weaknesses,
and none of the choices will find all possible problems. Compound problems will
only be resolved by running each product repeatedly.

Rarely, but still it happens, we have had folks report "I ran LSPFix, and it
made changes, but I still can't share files - but I can ping now" or similar
statements. We've had them re run the process, and sometimes things are fixed.

LSP and Winsock are parts of the network stack. They are not the same parts of
the network stack, and they aren't all IP networking, though. Different
malware, and different anti-malware, products will muck up different parts of
LSP and / or Winsock. Sometimes, one problem will mask another problem - so you
have to fix problems in sequence.

And there's no non destructive diagnostic tool to analyse corruption. You run a
tool, it makes changes, the changes either fix something or they don't. Want to
get a look at your Winsock structure? Autoruns (SysInternals / Microsoft) and
(Programs - Accessories - System Tools - ) System Information will enumerate the
Winsock components on your computer.

But, if a reinstall is something that you can do, conveniently, that may be the
best solution - this time.