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?

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.

Chuck,

Thanks for the suggestions and link to the great web site!
Unfortunately nothing suggested on that site fixed my problem and I
tried everything listed including reinstalling the hardware and
resetting the winsock and tcp/ip systems.

Here is the info you requested... First for the good working machine
(diablo) on my local net:

OS: Windows XP, Version 2002, Service Pack 2 with updates about 2 weeks
old

ipconfig /all:

Windows IP Configuration

Host Name . . . . . . . . . . . . : diablo
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : oc.cox.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : oc.cox.net
Description . . . . . . . . . . . : Intel(R) PRO/100+
Management Adapter
Physical Address. . . . . . . . . : 00-D0-B7-BB-F7-BE
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Monday, December 05, 2005
11:53:58 PM
Lease Expires . . . . . . . . . . : Monday, December 12, 2005
11:53:58 PM

browstat status:

Status for domain MIES_NET on transport
\Device\NetBT_Tcpip_{6F65E529-273F-48CB-B8B1-A4847CC6CFF4}
Browsing is active on domain.
Master browser name is: DIABLO
Master browser is running build 2600
1 backup servers retrieved from master DIABLO
\\DIABLO
Unable to retrieve server list from DIABLO: 64

Secondly, for the bad non-working machine (munich) on my local net:

OS: Windows XP, Version 2002, Service Pack 2 with updates about 4 weeks
old

ipconfig /all:

Windows IP Configuration

Host Name . . . . . . . . . . . . : munich
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : oc.cox.net

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : oc.cox.net
Description . . . . . . . . . . . : Realtek RTL8139/810x Family
Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-13-D3-0C-26-92
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Wednesday, December 07,
2005 8:48:13 PM
Lease Expires . . . . . . . . . . : Wednesday, December 14,
2005 8:48:13 PM

browstat status:

Status for domain MIES_NET on transport
\Device\NetBT_Tcpip_{6F926788-8BCE-4149-B617-7F2C6EBFED2E}
Browsing is active on domain.
Master browser name is: DIABLO
Master browser is running build 2600
1 backup servers retrieved from master DIABLO
\\DIABLO
There are 2 servers in domain MIES_NET on transport
\Device\NetBT_Tcpip_{6F926788-8BCE-4149-B617-7F2C6EBFED2E}
There are 1 domains in domain MIES_NET on transport
\Device\NetBT_Tcpip_{6F926788-8BCE-4149-B617-7F2C6EBFED2E}

There are some obvious differences in the browstat output but I'm not
sure what they mean.

Thanks for the help!

On 7 Dec 2005 21:20:08 -0800, "Don" <don.mies@cox.net> wrote:

>Chuck,
>
>Thanks for the suggestions and link to the great web site!
>Unfortunately nothing suggested on that site fixed my problem and I
>tried everything listed including reinstalling the hardware and
>resetting the winsock and tcp/ip systems.
>
>Here is the info you requested...

<SNIP>

>There are some obvious differences in the browstat output but I'm not
>sure what they mean.

OK, Don. If you actually reinstalled the hardware, AND reset the software,
we're not left with too many options.

Your best bet is a misconfigured or overlooked personal firewall. What security
software do you have on the problem computer? List everything please.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/0...ther-help.html

Next, let's repeat all the diagnostics, and look for patterns. Take the
following code (everything inside the "#####"). (Please verify computer names
and ip addresses).

1. Open Notepad. Ensure that Format - Word Wrap is not checked. Highlight
then Copy the code (Ctrl-C), precisely as it is presented, and Paste (Ctrl-V)
into Notepad. Verify, and correct, names and addresses if necessary.
2. Save the Notepad file as "cdiag.cmd", as type "All Files", into the root
folder "C:\".
3. Run it by Start - Run - "c:\cdiag".
4. Wait patiently.
5. When Notepad opens up displaying c:\cdiag.txt, first check Format and
ensure that Word Wrap is NOT checked! Then, copy the entire contents (Ctrl-A
Ctrl-C) and paste (Ctrl-V) into your next post.

Do this from all computers, please, with all computers powered up and online.

##### Start CDiag Assembled Code

@echo off
set FullTarget1=munich 192.168.0.100
set FullTarget2=diablo 192.168.0.101
set FullTarget3=
set FullTarget4=
set FullTargets=%FullTarget1% %FullTarget2% %FullTarget3% %FullTarget4%
set FullTargets=%FullTargets% 127.0.0.1
set PingTargets=www.yahoo.com 66.94.230.32 192.168.0.1
Set Version=V1.33
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Enumerate Shares >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net share >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Adhoc Browser View >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net view >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Full Targets %FullTargets% >>c:\cdiag.txt
for %%a in (%FullTargets%) do (
@echo. >>c:\cdiag.txt
@echo Target %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "%computername% ping %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "%computername% net view %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net view %%a >>c:\cdiag.txt
)
@echo. >>c:\cdiag.txt
@echo Ping Targets %PingTargets% >>c:\cdiag.txt
for %%a in (%PingTargets%) do (
@echo. >>c:\cdiag.txt
@echo Target %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "%computername% ping %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping %%a >>c:\cdiag.txt
)
@echo. >>c:\cdiag.txt
@echo End diagnosis for %computername% >>c:\cdiag.txt
notepad c:\cdiag.txt
:EOF

##### End CDiag Assembled Code

--
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.

Chuck,

I'll have to run your script tonight when I get home. The problem
machines are at home and unfortunately I am at work right now and can't
access those machines.

As far as security software goes, the only thing I'm running is Norton
AntiVirus 9.0 and AdAware 6.0. Early on in this process I tried
uninstalling both of them and that did not effect the problem. I can
try that again if you'd like me to. Both software packages are running
on both the good and bad machines. BTW, except for a bunch of
installed software on the bad machine, both machines are set up
identically with the same version of the OS, etc.

Don

Chuck,

Here is the output from your "cdiag" script...

######## From the good machine (diablo) ###########

CDiagnosis V1.33
Start diagnosis for DIABLO

Enumerate Shares


Share name Resource Remark

-------------------------------------------------------------------------------
C$ C:\ Default share

ADMIN$ C:\WINNT Remote Admin

IPC$ Remote IPC

C C:\
SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS.WINNT\DOCUMENTS

The command completed successfully.


Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\DIABLO Old System

\\MUNICH HP_System

The command completed successfully.


Full Targets munich 192.168.0.100 diablo 192.168.0.101 127.0.0.1

Target munich

"DIABLO ping munich"



Pinging munich [192.168.0.100] with 32 bytes of data:



Reply from 192.168.0.100: bytes=32 time<1ms TTL=128

Reply from 192.168.0.100: bytes=32 time<1ms TTL=128

Reply from 192.168.0.100: bytes=32 time<1ms TTL=128

Reply from 192.168.0.100: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.0.100:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"DIABLO net view munich"


Target 192.168.0.100

"DIABLO ping 192.168.0.100"



Pinging 192.168.0.100 with 32 bytes of data:



Reply from 192.168.0.100: bytes=32 time<1ms TTL=128

Reply from 192.168.0.100: bytes=32 time<1ms TTL=128

Reply from 192.168.0.100: bytes=32 time<1ms TTL=128

Reply from 192.168.0.100: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.0.100:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"DIABLO net view 192.168.0.100"


Target diablo

"DIABLO ping diablo"



Pinging diablo [192.168.0.101] with 32 bytes of data:



Reply from 192.168.0.101: bytes=32 time<1ms TTL=128

Reply from 192.168.0.101: bytes=32 time<1ms TTL=128

Reply from 192.168.0.101: bytes=32 time<1ms TTL=128

Reply from 192.168.0.101: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.0.101:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"DIABLO net view diablo"

Shared resources at diablo

Old System

Share name Type Used as Comment

-------------------------------------------------------------------------------
C Disk
SharedDocs Disk
The command completed successfully.


Target 192.168.0.101

"DIABLO ping 192.168.0.101"



Pinging 192.168.0.101 with 32 bytes of data:



Reply from 192.168.0.101: bytes=32 time<1ms TTL=128

Reply from 192.168.0.101: bytes=32 time<1ms TTL=128

Reply from 192.168.0.101: bytes=32 time<1ms TTL=128

Reply from 192.168.0.101: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.0.101:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"DIABLO net view 192.168.0.101"

Shared resources at 192.168.0.101

Old System

Share name Type Used as Comment

-------------------------------------------------------------------------------
C Disk
SharedDocs Disk
The command completed successfully.


Target 127.0.0.1

"DIABLO ping 127.0.0.1"



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"DIABLO net view 127.0.0.1"

Shared resources at 127.0.0.1

Old System

Share name Type Used as Comment

-------------------------------------------------------------------------------
C Disk
SharedDocs Disk
The command completed successfully.


Ping Targets www.yahoo.com 66.94.230.32 192.168.0.1

Target www.yahoo.com

"DIABLO ping www.yahoo.com"



Pinging www.yahoo.akadns.net [66.94.230.37] with 32 bytes of data:



Reply from 66.94.230.37: bytes=32 time=39ms TTL=52

Reply from 66.94.230.37: bytes=32 time=26ms TTL=52

Reply from 66.94.230.37: bytes=32 time=26ms TTL=52

Reply from 66.94.230.37: bytes=32 time=35ms TTL=52



Ping statistics for 66.94.230.37:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 26ms, Maximum = 39ms, Average = 31ms


Target 66.94.230.32

"DIABLO ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=32ms TTL=52

Reply from 66.94.230.32: bytes=32 time=26ms TTL=52

Reply from 66.94.230.32: bytes=32 time=28ms TTL=52

Reply from 66.94.230.32: bytes=32 time=28ms TTL=52



Ping statistics for 66.94.230.32:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 26ms, Maximum = 32ms, Average = 28ms


Target 192.168.0.1

"DIABLO ping 192.168.0.1"



Pinging 192.168.0.1 with 32 bytes of data:



Reply from 192.168.0.1: bytes=32 time<1ms TTL=127

Reply from 192.168.0.1: bytes=32 time<1ms TTL=127

Reply from 192.168.0.1: bytes=32 time<1ms TTL=127

Reply from 192.168.0.1: bytes=32 time<1ms TTL=127



Ping statistics for 192.168.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


End diagnosis for DIABLO

###############################################

NOTE: During this run, the following messages appeared in the command
window:

System error 5 has occurred.

Access is denied.

System error 5 has occurred.

Access is denied.

######## From the bad machine (munich) ###########

CDiagnosis V1.33
Start diagnosis for MUNICH

Enumerate Shares


Share name Resource Remark

-------------------------------------------------------------------------------
C$ C:\ Default share

print$ C:\WINDOWS\system32\spool\drivers
Printer Drivers

H$ H:\ Default share

ADMIN$ C:\WINDOWS Remote Admin

IPC$ Remote IPC

My Pictures C:\Documents and Settings\don.MUNICH\My Documents\My
Pictures
Don's Photos

SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS.WINDOWS\DOCUMENTS

Printer USB001 Spooled Samsung ML-1740 Series

Printer3 Microsoft Document Ima Spooled Microsoft Office Document
Image Wr
The command completed successfully.


Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\DIABLO Old System

\\MUNICH HP_System

The command completed successfully.


Full Targets munich 192.168.0.100 diablo 192.168.0.101 127.0.0.1

Target munich

"MUNICH ping munich"



Pinging munich [192.168.0.100] with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.0.100:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


"MUNICH net view munich"

Shared resources at munich

HP_System

Share name Type Used as Comment

-------------------------------------------------------------------------------
My Pictures Disk Don's Photos
Printer Print Samsung ML-1740 Series
Printer3 Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.


Target 192.168.0.100

"MUNICH ping 192.168.0.100"



Pinging 192.168.0.100 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.0.100:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


"MUNICH net view 192.168.0.100"

Shared resources at 192.168.0.100

HP_System

Share name Type Used as Comment

-------------------------------------------------------------------------------
My Pictures Disk Don's Photos
Printer Print Samsung ML-1740 Series
Printer3 Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.


Target diablo

"MUNICH ping diablo"



Pinging diablo [192.168.0.101] with 32 bytes of data:



Reply from 192.168.0.101: bytes=32 time<1ms TTL=128

Reply from 192.168.0.101: bytes=32 time<1ms TTL=128

Reply from 192.168.0.101: bytes=32 time<1ms TTL=128

Reply from 192.168.0.101: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.0.101:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"MUNICH net view diablo"

Shared resources at diablo

Old System

Share name Type Used as Comment

-------------------------------------------------------------------------------
C Disk
SharedDocs Disk
The command completed successfully.


Target 192.168.0.101

"MUNICH ping 192.168.0.101"



Pinging 192.168.0.101 with 32 bytes of data:



Reply from 192.168.0.101: bytes=32 time<1ms TTL=128

Reply from 192.168.0.101: bytes=32 time<1ms TTL=128

Reply from 192.168.0.101: bytes=32 time<1ms TTL=128

Reply from 192.168.0.101: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.0.101:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"MUNICH net view 192.168.0.101"

Shared resources at 192.168.0.101

Old System

Share name Type Used as Comment

-------------------------------------------------------------------------------
C Disk
SharedDocs Disk
The command completed successfully.


Target 127.0.0.1

"MUNICH ping 127.0.0.1"



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"MUNICH net view 127.0.0.1"


Ping Targets www.yahoo.com 66.94.230.32 192.168.0.1

Target www.yahoo.com

"MUNICH ping www.yahoo.com"



Pinging www.yahoo.akadns.net [66.94.230.44] with 32 bytes of data:



Reply from 66.94.230.44: bytes=32 time=32ms TTL=52

Reply from 66.94.230.44: bytes=32 time=28ms TTL=52

Reply from 66.94.230.44: bytes=32 time=30ms TTL=52

Reply from 66.94.230.44: bytes=32 time=30ms TTL=52



Ping statistics for 66.94.230.44:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 28ms, Maximum = 32ms, Average = 30ms


Target 66.94.230.32

"MUNICH ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=44ms TTL=52

Reply from 66.94.230.32: bytes=32 time=28ms TTL=52

Reply from 66.94.230.32: bytes=32 time=28ms TTL=52

Reply from 66.94.230.32: bytes=32 time=30ms TTL=52



Ping statistics for 66.94.230.32:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 28ms, Maximum = 44ms, Average = 32ms


Target 192.168.0.1

"MUNICH ping 192.168.0.1"



Pinging 192.168.0.1 with 32 bytes of data:



Reply from 192.168.0.1: bytes=32 time<1ms TTL=127

Reply from 192.168.0.1: bytes=32 time<1ms TTL=127

Reply from 192.168.0.1: bytes=32 time<1ms TTL=127

Reply from 192.168.0.1: bytes=32 time<1ms TTL=127



Ping statistics for 192.168.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


End diagnosis for MUNICH

###############################################

NOTE: During this run, the following messages appeared in the command
window:

System error 53 has occurred.

The network path was not found.

Also note that the shares on munich list "printer3" which I don't have
on my system. I think that I've tried to remove this from my printer
list before but I don't remember if it actually went away or not. It
may be back because of something that I've done in the process of
trying to fix this problem.


Don

I have another piece of information that might be useful... On your
prior suggestion, I went to remove the AdAware and Norton AntiVirus
programs from the bad system and I ran into a problem. The AdAware
program uninstalled with no problems but I can't get the Symantec
(Norton) AntiVirus program to uninstall. When I try using the usual
"Add/Remove Programs" utility, it starts the process and after a while
I get a dialog box saying that there as a fatal error during the
installation (should probably be "uninstallation") and the program
aborts and quits. I tried it several times and I can't get it to
uninstall.

Is there a way to remove this stuff manually?


Don

On 8 Dec 2005 20:12:47 -0800, "Don" <*email_address_deleted*> wrote:

>I have another piece of information that might be useful... On your
>prior suggestion, I went to remove the AdAware and Norton AntiVirus
>programs from the bad system and I ran into a problem. The AdAware
>program uninstalled with no problems but I can't get the Symantec
>(Norton) AntiVirus program to uninstall. When I try using the usual
>"Add/Remove Programs" utility, it starts the process and after a while
>I get a dialog box saying that there as a fatal error during the
>installation (should probably be "uninstallation") and the program
>aborts and quits. I tried it several times and I can't get it to
>uninstall.
>
>Is there a way to remove this stuff manually?
>
>
>Don

Aha! So it is another Symantec mess!!

Norton Antivirus has caused problems like this before - Google this forum if you
want details. There are tools on the Symantec website which you have to use,
manually, along with an ever changing list of manual procedures (registry
edits). And you can generally only get them from specifying the version of S$
product that you're running, and maybe you will even have to wait for specific
instructions from a S$ tech.

S$ normal response, to ANY problem with NAV, is to un install and re install
(restarting system 3 or 4 times). When there's a problem with an un install
(about 50% of the time), they'll give you a manual checklist of registry edits.

The last time I went thru this was either 3 or 4 years ago. I switched to
flatten and pave (fdisk, format, and install new OS) (and then install new S$
product) after that. Last year, I stopped reinstalling S$ completely (picked an
alternate AV), and I haven't looked back since. Two months ago, I flattened and
paved my last computer with NAV on it. I am now S$ free, and happier for it.

You MIGHT find a reparative process on S$ Support. If you don't, I suspect that
a flatten and pave is your best option. Just find a better antivirus after that
- and that's the easiest part of this whole process.

--
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.

Chuck,

I spent quite a while following the detailed instructions on the
Symantec site for manually removing NAV which included many registry
edits as well as removing things from the disk. The system appears to
be clean now and there is no trace of any of the Symantec processes or
programs running and there is nothing in any of the menus.

However... The system behaves the same as before. I still can't ping
my own IP address and the only Internet application that works at all
is IE and that's not 100%.

I still have the same problem.

What now?


Don

On 10 Dec 2005 18:18:10 -0800, "Don" <don.mies@cox.net> wrote:

>Chuck,
>
>I spent quite a while following the detailed instructions on the
>Symantec site for manually removing NAV which included many registry
>edits as well as removing things from the disk. The system appears to
>be clean now and there is no trace of any of the Symantec processes or
>programs running and there is nothing in any of the menus.
>
>However... The system behaves the same as before. I still can't ping
>my own IP address and the only Internet application that works at all
>is IE and that's not 100%.
>
>I still have the same problem.
>
>What now?
>
>
>Don

Don,

Well, we're getting into uncharted territory now. We've explored the obvious
possibilities, so now let's look for new, unobvious ones. We'll start with
Autoruns, which is a simple analytic.
<http://nitecruzr.blogspot.com/2005/05/essential-tools-for-desktop-and.html#Autoruns>
http://nitecruzr.blogspot.com/2005/0....html#Autoruns
# Start a new message, and reply to this post. Don't Send just yet.
# Make a new folder, say "C:\Utility" is what I use.
# Download Autoruns, unzip all components and copy to C:\Utility.
# Open C:\Utility from Windows Explorer, find "autoruns.exe" and double click on
it.
# When Autoruns starts, check under User and ensure that the name of the user
which you are running under, when you are having your problems, is checked.
# Let Autoruns finish scanning.
# Do File - Save As, and save the scan as file type Autoruns Data (txt),
whatever name you wish. Remember where the file gets saved.
# Start Notepad from Accessories, and Open the file you just saved.
# With this big text file open in front of you, place the cursor in the middle
of it all, to position it.
# Hit Ctrl-A (to Select All), then Ctrl-C (to Copy).
# Come back to your new post here, and Paste into your message.
# Now Send your message.

I'll take a look at the Autoruns file, and see what clues we can see.

--
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.