On 7 Dec 2005 10:23:00 -0800, "Don" <*email_address_deleted*> wrote:
>I'm running XP Pro with all the latest updates. I have 2 machines
>both running the same version of XP Pro on my local net. The 2
>machines are connected to the same D-Link router and the router is
>connected to a cable modem and on to my ISP.
>
>Something happened on one of the machines that suddently cut off
>access to the Internet for most of the applications. Applications
>like Firefox and Thunderbird will not talk to the net at all getting
>a "connection refused by server" message. Outlook can sometimes get
>out. IE is the only application that can get to the net pretty
>consistently but even that is not 100%. Some pages won't come up.
>
>The second machinge on the local net is stil working fine so I assume
>the router hardware and cable modem are still working correctly and
>the problem must be software on the bad machine.
>
>The obviously wrong symptom on the broken machine is that I cannot
>ping that machine's own IP address (either numerically or
>symbolically).
>The good computer can ping it's own IP address with no problems and
>has no trouble getting out to the Internet and this second machine can
>ping the computer that is having the trouble.
>
>I've tried adding entries for both local machinse into the hosts file
>but that had no effect of the problem.
>
>I've tried running with the XP firewall disabled and enabled with no
>change in the symptoms and currently have it disabled and the service
>is not even running. The firewall does not make any diffence to the
>good machine. That machine works with the firewall either disabled
>or enabled so the firewall is probably not the problem.
>
>I've tried resetting the tcp/ip stack using "netsh" with no effect.
>
>I've tried restoring the system to a previously know good working
>point using the system restore utility and it reported that there
>were no differences in the system files and did nothing,
>
>I've tried reinstalling XP and that did not fix the problem either.
>
>I've tried updating the driver on my NIC to the latest version and
>that did not fix the problem.
>
>I can ping the other computer on my home network and I can ping both
>127.0.0.1 and "localhost" on the problem machine with no problems.
>The "good" computer can ping all of the above and it can ping the "bad"
>computer. It can also ping it's own IP address just fine. Both
>machines can ping the router with no problems. The only ping that
>does not work is on the problem machine trying to ping itself.
>
>Running the XP network diagnostic on the "good" computer shows
>everything passing with no errors but running it on the bad computer
>shows everything passing except the ping of itself.
>
>In the process of trying to post information on the net from my good
>machine, I had to somehow get data from the bad machine to the good
>one. I can't use a floppy because the bad machine does not have a
>floppy drive.
>
>What I wound up doing was creating a shared folder on the "good"
>machine and mapping it on the "bad" machine and that worked. I am able
>to map network drives that exist on the "good" machine onto the "bad"
>one. The reverse does not work though. I cannot create a shared
>folder on the "bad" machine and map it on the "good" one. When I try
>to map a folder this way, the "good" machine sees the "bad" machine's
>name as part of my local network but it cannot see anything inside the
>machine.
>
>The IP is set up as DHCP from my local router. I've released and
>renewed the license several times using ipconfig and even forced it to
>use a different IP address by changing the settings in my router. None
>of that had any effect.
>
>The DNS server is passed through my router to the ISP and appears to
>work fine as the other computer on my home net has no problems
>accessing the net.
>
>The WINS settings are to enable LMHOSTS lookup and the NetBIOS is set
>to the "default" setting. No WINS servers are specified.
>
>I tried comparing the settings on the two machines. So far, I think
>I've gone through all the dialog boxes there are and have not found
>any differences in the setting on the two machines except one. In
>the Network Connections dialog box (Start/Settings/Network
>Connections),
>the good machine shows only one entry under "LAN or High-Speed
>Internet"
>which is the local area connection.
>
>The bad machine has 2 entries under that heading but one is for the
>firewire interface (that I'm not currently using). However, the bad
>machine also has a heading entitled "Internet Gateway" and there is
>one connection listed under that which reads "Internet Connection"
>with type "Internet Gateway", status "Connected", and name "Internet
>Connection". I've been told that this is an entry for the ICS service.
>
>Trying to bring up the properties window on this connection results in
>a dialog box that does not have any useful information in it. Right
>clicking on it and asking for it's status brings up a dialog box that
>indicates that the connection is good and working fine and there is
>constant send and receive traffic on the interface (not a large amount
>but the counters do constantly increment). There is a "disable" button
>on this form and pressing it causes the router to release it's IP
>address thereby disabling the connection to my ISP. Choosing the
>"enable" option causes the router to "renew" its IP address and
>everything works fine again.
>
>I've tried everything I can think of to get rid of this entry and
>cannot. I've even resorted to disabling the firewall/ICS service
>and confirmed that it is not running any more but the entry still
>exists. I've also tried manually editing the registry to disable
>the ICS service (per a posting on the net) and that did not work
>either.
>
>When I reboot the bad system and immediately log on and bring up
>the Network Connections dialog box, the Gateway entry is missing
>but after about 30-60 seconds, it suddently appears in the window
>again.
>
>Can anyone tell me if this Internet Gateway entry is what is
>causing my ping problems and if so, what can I do to fix it?
Don,
The "netsh" TCP/IP reset is just 1 of 6 possible fixes for an LSP / Winsock /
TCP/IP problem, and that's what it sounds like you started with. Fix the ping
issue first, then we can explore the share browsing and file sharing issues
which may have resulted.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/0...-layer-in.html
If no help yet, provide "browstat status" and "ipconfig /all" from each
computer, so we can diagnose the problem. Read this article, and linked
articles, and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.