[Jon M]

hi all.
i have 3 systems on a home network.
one day things changed and I can't figure out why.
used to be that every computer saw every computer & the printer
all three computers connect to a linksys router via hardwire.
nowadays:
desktop computer sees basement and laptop
basement sees desktop & laptop
laptop sees only basement. cannot see desktop or printer.
desktop IP can be pinged from the laptop
all computer names, workgroup names are correct, etc.
help!
thanks in advance,

jm

[Chuck]

On Wed, 29 Jun 2005 16:07:01 -0700, "Jon M" <JonM@discussions.microsoft.com>
wrote:

>hi all.
>i have 3 systems on a home network.
>one day things changed and I can't figure out why.
>used to be that every computer saw every computer & the printer
>all three computers connect to a linksys router via hardwire.
>nowadays:
>desktop computer sees basement and laptop
>basement sees desktop & laptop
>laptop sees only basement. cannot see desktop or printer.
>desktop IP can be pinged from the laptop
>all computer names, workgroup names are correct, etc.
>help!
>thanks in advance,
>
>jm

Jon,

First check for a firewall problem on one or more computers.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Security>

Then check for a browser conflict. Use browstat, run from all 3 computers, to
diagnose browser conflicts.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Browser>

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not a problem - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

[Jon M]

Saw the infamouse error 53 when I ran browstat.
when i shut everytning down, my network places still shows everything there
even with only one system turned on....
have lost all network connectivity with my laptop though it still accesses
the internet through the router without difficuty.
it seems like to would be simpler to just remove the entire neytwork and
reinstall everything.
is that a big deal- seems like ti wouldn't be...
thanks in advance, appreciate any help you can give me...
"Chuck" wrote:

> On Wed, 29 Jun 2005 16:07:01 -0700, "Jon M" <JonM@discussions.microsoft.com>
> wrote:
>
> >hi all.
> >i have 3 systems on a home network.
> >one day things changed and I can't figure out why.
> >used to be that every computer saw every computer & the printer
> >all three computers connect to a linksys router via hardwire.
> >nowadays:
> >desktop computer sees basement and laptop
> >basement sees desktop & laptop
> >laptop sees only basement. cannot see desktop or printer.
> >desktop IP can be pinged from the laptop
> >all computer names, workgroup names are correct, etc.
> >help!
> >thanks in advance,
> >
> >jm
>
> Jon,
>
> First check for a firewall problem on one or more computers.
> <http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Security>
>
> Then check for a browser conflict. Use browstat, run from all 3 computers, to
> diagnose browser conflicts.
> <http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Browser>
>
> --
> Cheers,
> Chuck
> http://nitecruzr.blogspot.com/
> Paranoia is not a problem - it's a normal response from experience.
> My email is AT DOT
> actual address pchuck sonic net.
>

[Chuck]

On Thu, 30 Jun 2005 15:41:02 -0700, "Jon M" <JonM@discussions.microsoft.com>
wrote:

>"Chuck" wrote:
>
>> On Wed, 29 Jun 2005 16:07:01 -0700, "Jon M" <JonM@discussions.microsoft.com>
>> wrote:
>>
>> >hi all.
>> >i have 3 systems on a home network.
>> >one day things changed and I can't figure out why.
>> >used to be that every computer saw every computer & the printer
>> >all three computers connect to a linksys router via hardwire.
>> >nowadays:
>> >desktop computer sees basement and laptop
>> >basement sees desktop & laptop
>> >laptop sees only basement. cannot see desktop or printer.
>> >desktop IP can be pinged from the laptop
>> >all computer names, workgroup names are correct, etc.
>> >help!
>> >thanks in advance,
>> >
>> >jm
>>
>> Jon,
>>
>> First check for a firewall problem on one or more computers.
>> <http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Security>
>>
>> Then check for a browser conflict. Use browstat, run from all 3 computers, to
>> diagnose browser conflicts.
>> <http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Browser>

>Saw the infamouse error 53 when I ran browstat.
>when i shut everytning down, my network places still shows everything there
>even with only one system turned on....
>have lost all network connectivity with my laptop though it still accesses
>the internet through the router without difficuty.
>it seems like to would be simpler to just remove the entire neytwork and
>reinstall everything.
>is that a big deal- seems like ti wouldn't be...
>thanks in advance, appreciate any help you can give me...

Jon,

The infamouse error 53 means "name not found". This could be caused by a
physical problem, ie maybe the network cable is unplugged.

If not a physical problem, then I know of 4 scenarios:
# Corrupted LSP / Winsock.
# Firewall problem.
# Invalid node type.
# Excessive protocols.
<http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>

Re installing everything is a good solution, except:
# Since you don't know what the problem is, how do you know even which computer
needs to be re installed?
# Since you don't know what the problem is, how do you keep it from happening
again?

Why not try and diagnose the problem? Start with "ipconfig /all" and "browstat
status" from all 3 computers. Define "lost all network connectivity"
objectively. Read this article, and either diagnose it yourself, or post the 6
logs here.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not a problem - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

[Jon M]

Hi again, and thanks for the help. Was up all night working thought I'd
postthis before crashing in the hopes that you may hev time to look it over
by the time I get up:


Desktop ipconfig data:

Windows IP Configuration

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

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 CT Network
Connection #2
Physical Address. . . . . . . . . : 00-0E-A6-F0-74-4F
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 204.127.202.19
216.148.227.79
Lease Obtained. . . . . . . . . . : Friday, July 01, 2005 8:53:01 AM
Lease Expires . . . . . . . . . . : Saturday, July 02, 2005 8:53:01
AM


Desktop Browstat data:

Status for domain HOME on transport
\Device\NetBT_Tcpip_{FA839BF3-2549-4662-B6C2-EA0C1BD63D4E}
Browsing is active on domain.
Master browser name is: ? ???
Could not connect to registry, error = 53 Unable to determine build
of browser master: 53
Unable to determine server information for browser master: 123
1 backup servers retrieved from master ? ???
\\LAPTOP
Unable to retrieve server list from ? ??? : 2351


Laptop browstat data:

Status for domain HOME on transport
\Device\NetBT_Tcpip_{D92D026B-8772-443B-AC42-B5498E50DBD1}
Browsing is active on domain.
Master browser name is: ? ???
Could not connect to registry, error = 53 Unable to determine build
of browser master: 53
Unable to determine server information for browser master: 123
1 backup servers retrieved from master ? ???
\\LAPTOP
Unable to retrieve server list from ? ??? : 2351


Status for domain HOME on transport
\Device\NetBT_Tcpip_{42EA40F1-8E79-475F-A23D-E16EBD7CCF5F}
Browsing is NOT active on domain.
Master browser name is held by: ? ???
Could not connect to registry, error = 53 Unable to determine build
of browser master: 53
Unable to determine server information for browser master: 123


Laptop Ipconfig data:

Windows IP Configuration

Host Name . . . . . . . . . . . . : LAPTOP
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated
Controller
Physical Address. . . . . . . . . : 00-0F-1F-25-40-A8
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 204.127.202.19
216.148.227.79
Lease Obtained. . . . . . . . . . : Friday, July 01, 2005 4:24:17 AM
Lease Expires . . . . . . . . . . : Saturday, July 02, 2005 4:24:17
AM

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Dell Wireless WLAN 1350 WLAN
Mini-PCI Card
Physical Address. . . . . . . . . : 00-0B-7D-08-A5-86
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.102
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 204.127.202.19
216.148.227.79
Lease Obtained. . . . . . . . . . : Thursday, June 30, 2005 4:24:25
PM
Lease Expires . . . . . . . . . . : Friday, July 01, 2005 4:24:25 PM


Basement browstat data:

Status for domain HOME on transport
\Device\NetBT_Tcpip_{737C98B4-B322-4922-AAF1-47ABF573054A}
Browsing is active on domain.
Master browser name is: ? ???
Could not connect to registry, error = 53 Unable to determine build
of browser master: 53
Unable to determine server information for browser master: 123
1 backup servers retrieved from master ? ???
\\LAPTOP
Unable to retrieve server list from ? ??? : 2351

Basement Ipconfig data:


Windows IP Configuration

Host Name . . . . . . . . . . . . : Basement
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet
Adapter
Physical Address. . . . . . . . . : 00-11-D8-29-7C-2C
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.103
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 204.127.202.19
216.148.227.79
Lease Obtained. . . . . . . . . . : Friday, July 01, 2005 4:39:24 AM
Lease Expires . . . . . . . . . . : Saturday, July 02, 2005 4:39:24
AM


"Chuck" wrote:

> On Thu, 30 Jun 2005 15:41:02 -0700, "Jon M" <JonM@discussions.microsoft.com>
> wrote:
>
> >"Chuck" wrote:
> >
> >> On Wed, 29 Jun 2005 16:07:01 -0700, "Jon M" <JonM@discussions.microsoft.com>
> >> wrote:
> >>
> >> >hi all.
> >> >i have 3 systems on a home network.
> >> >one day things changed and I can't figure out why.
> >> >used to be that every computer saw every computer & the printer
> >> >all three computers connect to a linksys router via hardwire.
> >> >nowadays:
> >> >desktop computer sees basement and laptop
> >> >basement sees desktop & laptop
> >> >laptop sees only basement. cannot see desktop or printer.
> >> >desktop IP can be pinged from the laptop
> >> >all computer names, workgroup names are correct, etc.
> >> >help!
> >> >thanks in advance,
> >> >
> >> >jm
> >>
> >> Jon,
> >>
> >> First check for a firewall problem on one or more computers.
> >> <http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Security>
> >>
> >> Then check for a browser conflict. Use browstat, run from all 3 computers, to
> >> diagnose browser conflicts.
> >> <http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Browser>
>
> >Saw the infamouse error 53 when I ran browstat.
> >when i shut everytning down, my network places still shows everything there
> >even with only one system turned on....
> >have lost all network connectivity with my laptop though it still accesses
> >the internet through the router without difficuty.
> >it seems like to would be simpler to just remove the entire neytwork and
> >reinstall everything.
> >is that a big deal- seems like ti wouldn't be...
> >thanks in advance, appreciate any help you can give me...
>
> Jon,
>
> The infamouse error 53 means "name not found". This could be caused by a
> physical problem, ie maybe the network cable is unplugged.
>
> If not a physical problem, then I know of 4 scenarios:
> # Corrupted LSP / Winsock.
> # Firewall problem.
> # Invalid node type.
> # Excessive protocols.
> <http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
>
> Re installing everything is a good solution, except:
> # Since you don't know what the problem is, how do you know even which computer
> needs to be re installed?
> # Since you don't know what the problem is, how do you keep it from happening
> again?
>
> Why not try and diagnose the problem? Start with "ipconfig /all" and "browstat
> status" from all 3 computers. Define "lost all network connectivity"
> objectively. Read this article, and either diagnose it yourself, or post the 6
> logs here.
> <http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
>
> --
> Cheers,
> Chuck
> http://nitecruzr.blogspot.com/
> Paranoia is not a problem - it's a normal response from experience.
> My email is AT DOT
> actual address pchuck sonic net.
>

[Chuck]

On Fri, 1 Jul 2005 06:15:02 -0700, "Jon M" <JonM@discussions.microsoft.com>
wrote:

>Hi again, and thanks for the help. Was up all night working thought I'd
>postthis before crashing in the hopes that you may hev time to look it over
>by the time I get up:

<SNIP>

Jon,

Let's see where we are.
# Node Types Hybrid and Unknown, no problem there.
# No gratuitous protocols.

I can't find any references to either a "123" or "2351" error in Microsoft
documentation. I did a Google search, though, and got several hits. This set
of errors has come up in the past, in problems resolved in this group. They've
unfortunately been trial-and-error resolutions based upon my other 2 listed
possible causes for the "error = 53", namely:
# Corrupted LSP / Winsock.
# Firewall problem.

I looked at the search hits. One guy reported having an "internet filter
service" running, and his problem was resolved by removing that. Two others had
gratuitous protocols, one IPV6, and the other NetBEUI.

Why no "browstat status" for Laptop?

What's different in your situation is that you have a symmetrical problem, ie
each computer showing these symptoms. In a way, this is good. You can work on
just ONE computer at a time, check "browstat status" on EACH computer after each
change, and look for a difference in results (possibly showing from either
computer).
<http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>

What personal firewalls and antivirus products do you have?
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>

Look for corrupted LSP / Winsock. Run each of the 5 fixes, one at a time, on
ONE of your computers, and check for results using "browstat status" run on EACH
computer.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
# LSP-Fix.
# WinsockFix
# WinsockXPFix
# Do you have SP2, or pre-SP2? Do the appropriate Windows native fix.
# Reset TCP/IP.

Once you get results from updating ONE computer, try the same fix on a second
computer, and observe the results.

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not a problem - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

[Jon M]

help.
tried all of these fixes and still nothing.
hired someone local to come over and fix this and she said it was the router
which i believe is incorrect.
ready to take lives.
willing to pay for competent help.
could it be the router?


"Chuck" wrote:

> On Fri, 1 Jul 2005 06:15:02 -0700, "Jon M" <JonM@discussions.microsoft.com>
> wrote:
>
> >Hi again, and thanks for the help. Was up all night working thought I'd
> >postthis before crashing in the hopes that you may hev time to look it over
> >by the time I get up:
>
> <SNIP>
>
> Jon,
>
> Let's see where we are.
> # Node Types Hybrid and Unknown, no problem there.
> # No gratuitous protocols.
>
> I can't find any references to either a "123" or "2351" error in Microsoft
> documentation. I did a Google search, though, and got several hits. This set
> of errors has come up in the past, in problems resolved in this group. They've
> unfortunately been trial-and-error resolutions based upon my other 2 listed
> possible causes for the "error = 53", namely:
> # Corrupted LSP / Winsock.
> # Firewall problem.
>
> I looked at the search hits. One guy reported having an "internet filter
> service" running, and his problem was resolved by removing that. Two others had
> gratuitous protocols, one IPV6, and the other NetBEUI.
>
> Why no "browstat status" for Laptop?
>
> What's different in your situation is that you have a symmetrical problem, ie
> each computer showing these symptoms. In a way, this is good. You can work on
> just ONE computer at a time, check "browstat status" on EACH computer after each
> change, and look for a difference in results (possibly showing from either
> computer).
> <http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
>
> What personal firewalls and antivirus products do you have?
> <http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
>
> Look for corrupted LSP / Winsock. Run each of the 5 fixes, one at a time, on
> ONE of your computers, and check for results using "browstat status" run on EACH
> computer.
> <http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
> # LSP-Fix.
> # WinsockFix
> # WinsockXPFix
> # Do you have SP2, or pre-SP2? Do the appropriate Windows native fix.
> # Reset TCP/IP.
>
> Once you get results from updating ONE computer, try the same fix on a second
> computer, and observe the results.
>
> --
> Cheers,
> Chuck
> http://nitecruzr.blogspot.com/
> Paranoia is not a problem - it's a normal response from experience.
> My email is AT DOT
> actual address pchuck sonic net.
>

[Chuck]

On Sun, 3 Jul 2005 13:17:01 -0700, "Jon M" <JonM@discussions.microsoft.com>
wrote:

>"Chuck" wrote:
>
>> On Fri, 1 Jul 2005 06:15:02 -0700, "Jon M" <JonM@discussions.microsoft.com>
>> wrote:
>>
>> >Hi again, and thanks for the help. Was up all night working thought I'd
>> >postthis before crashing in the hopes that you may hev time to look it over
>> >by the time I get up:
>>
>> <SNIP>
>>
>> Jon,
>>
>> Let's see where we are.
>> # Node Types Hybrid and Unknown, no problem there.
>> # No gratuitous protocols.
>>
>> I can't find any references to either a "123" or "2351" error in Microsoft
>> documentation. I did a Google search, though, and got several hits. This set
>> of errors has come up in the past, in problems resolved in this group. They've
>> unfortunately been trial-and-error resolutions based upon my other 2 listed
>> possible causes for the "error = 53", namely:
>> # Corrupted LSP / Winsock.
>> # Firewall problem.
>>
>> I looked at the search hits. One guy reported having an "internet filter
>> service" running, and his problem was resolved by removing that. Two others had
>> gratuitous protocols, one IPV6, and the other NetBEUI.
>>
>> Why no "browstat status" for Laptop?
>>
>> What's different in your situation is that you have a symmetrical problem, ie
>> each computer showing these symptoms. In a way, this is good. You can work on
>> just ONE computer at a time, check "browstat status" on EACH computer after each
>> change, and look for a difference in results (possibly showing from either
>> computer).
>> <http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
>>
>> What personal firewalls and antivirus products do you have?
>> <http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
>>
>> Look for corrupted LSP / Winsock. Run each of the 5 fixes, one at a time, on
>> ONE of your computers, and check for results using "browstat status" run on EACH
>> computer.
>> <http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
>> # LSP-Fix.
>> # WinsockFix
>> # WinsockXPFix
>> # Do you have SP2, or pre-SP2? Do the appropriate Windows native fix.
>> # Reset TCP/IP.
>>
>> Once you get results from updating ONE computer, try the same fix on a second
>> computer, and observe the results.

>help.
>tried all of these fixes and still nothing.
>hired someone local to come over and fix this and she said it was the router
>which i believe is incorrect.
>ready to take lives.
>willing to pay for competent help.
>could it be the router?

Jon,

Well, almost anything COULD be the router, but the symmetrical nature of the
problem makes it unlikely, at least it doesn't look like failed router ports.
All 3 computers appear to be getting DHCP{ settings from the router, so I can't
see positive evidence of obvious hardware failure there.

You could find out, if you want to try another router, but let's see if we can
pinpoint the problem a bit more.

We've tried the most obvious possibilities. Go through the troubleshooting
checklist if you wish.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html>

Next, 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=gateway 192.168.1.100
set FullTarget2=LAPTOP 192.168.1.101
set FullTarget3=Basement 192.168.1.103
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.1.1
Set Version=V1.32
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% >>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 sonic net.

[Jon M]

thanks so much for your help.
i noticed yesterday that I've lost the ability to log into my hospital's
secured VPN (i'm an ER physician and do work daily from my home) from the
desktop (had worked okay a few days ago) but still can from the laptop. argh.
anyway, appreciate your help & patience. will owe you hugely for any input
you can give me.
thanks again.
ouput follows:

CDiagnosis V1.32
Start diagnosis for GATEWAY

Adhoc Browser View


Full Targets gateway 192.168.1.101 LAPTOP 192.168.1.104 Basement
192.168.1.100 127.0.0.1

Target gateway

"GATEWAY ping gateway"



Pinging gateway [::1] with 32 bytes of data:



Reply from ::1: time<1ms

Reply from ::1: time<1ms

Reply from ::1: time<1ms

Reply from ::1: time<1ms



Ping statistics for ::1:

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

Approximate round trip times in milli-seconds:

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


"GATEWAY net view gateway"

Shared resources at gateway

Study

Share name Type Used as Comment


-------------------------------------------------------------------------------
C Disk

Chelsea Disk

hppsc900 Print hp psc 900 series

My Documents Disk

Printer Print Print to this device to send a photo quality
fax.
Printer11 Print Adobe PDF

Printer2 Print Print to this device to send a fax.

Printer5 Print PaperPort Color Image

Printer6 Print PaperPort Black & White Image

Printer8 Print Microsoft Office Document Image Writer

Printer9 Print hp psc 900 series fax

SharedDocs Disk

The command completed successfully.


Target 192.168.1.101

"GATEWAY ping 192.168.1.101"



Pinging 192.168.1.101 with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.1.101:

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

Approximate round trip times in milli-seconds:

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


"GATEWAY net view 192.168.1.101"


Target LAPTOP

"GATEWAY ping LAPTOP"



Pinging LAPTOP [192.168.1.103] with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.103:

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


"GATEWAY net view LAPTOP"


Target 192.168.1.104

"GATEWAY ping 192.168.1.104"



Pinging 192.168.1.104 with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.1.104:

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

Approximate round trip times in milli-seconds:

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


"GATEWAY net view 192.168.1.104"


Target Basement

"GATEWAY ping Basement"



Pinging Basement [192.168.1.100] with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.1.100:

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

Approximate round trip times in milli-seconds:

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


"GATEWAY net view Basement"

Shared resources at Basement

Kid's Computer

Share name Type Used as Comment

-------------------------------------------------------------------------------
My Documents Disk
PRESARIO (C) Disk
Printer Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.


Target 192.168.1.100

"GATEWAY ping 192.168.1.100"



Pinging 192.168.1.100 with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.1.100:

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

Approximate round trip times in milli-seconds:

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


"GATEWAY net view 192.168.1.100"

Shared resources at 192.168.1.100

Kid's Computer

Share name Type Used as Comment

-------------------------------------------------------------------------------
My Documents Disk
PRESARIO (C) Disk
Printer Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.


Target 127.0.0.1

"GATEWAY 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


"GATEWAY net view 127.0.0.1"

Shared resources at 127.0.0.1

Study

Share name Type Used as Comment


-------------------------------------------------------------------------------
C Disk

Chelsea Disk

hppsc900 Print hp psc 900 series

My Documents Disk

Printer Print Print to this device to send a photo quality
fax.
Printer11 Print Adobe PDF

Printer2 Print Print to this device to send a fax.

Printer5 Print PaperPort Color Image

Printer6 Print PaperPort Black & White Image

Printer8 Print Microsoft Office Document Image Writer

Printer9 Print hp psc 900 series fax

SharedDocs Disk

The command completed successfully.


Ping Targets www.yahoo.com 66.94.230.32 192.168.1.1

Target www.yahoo.com

"GATEWAY ping www.yahoo.com"



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



Reply from 216.109.118.78: bytes=32 time=28ms TTL=46

Reply from 216.109.118.78: bytes=32 time=24ms TTL=46

Reply from 216.109.118.78: bytes=32 time=22ms TTL=46

Reply from 216.109.118.78: bytes=32 time=23ms TTL=46



Ping statistics for 216.109.118.78:

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

Approximate round trip times in milli-seconds:

Minimum = 22ms, Maximum = 28ms, Average = 24ms


Target 66.94.230.32

"GATEWAY ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=86ms TTL=43

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

Reply from 66.94.230.32: bytes=32 time=89ms TTL=43

Reply from 66.94.230.32: bytes=32 time=85ms TTL=43



Ping statistics for 66.94.230.32:

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

Approximate round trip times in milli-seconds:

Minimum = 85ms, Maximum = 89ms, Average = 86ms


Target 192.168.1.1

"GATEWAY ping 192.168.1.1"



Pinging 192.168.1.1 with 32 bytes of data:



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Ping statistics for 192.168.1.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 GATEWAY



CDiagnosis V1.32
Start diagnosis for LAPTOP

Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\BASEMENT Kid's Computer

The command completed successfully.


Full Targets gateway 192.168.1.101 LAPTOP 192.168.1.104 Basement
192.168.1.100 127.0.0.1

Target gateway

"LAPTOP ping gateway"

Pinging gateway [192.168.1.101] with 32 bytes of data:Reply from
192.168.1.101: bytes=32 time<1ms TTL=128Reply from 192.168.1.101: bytes=32
time<1ms TTL=128Reply from 192.168.1.101: bytes=32 time<1ms TTL=128Reply from
192.168.1.101: bytes=32 time<1ms TTL=128Ping statistics for 192.168.1.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip
times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"LAPTOP net view gateway"


Target 192.168.1.101

"LAPTOP ping 192.168.1.101"

Pinging 192.168.1.101 with 32 bytes of data:Reply from 192.168.1.101:
bytes=32 time<1ms TTL=128Reply from 192.168.1.101: bytes=32 time<1ms
TTL=128Reply from 192.168.1.101: bytes=32 time<1ms TTL=128Reply from
192.168.1.101: bytes=32 time<1ms TTL=128Ping statistics for 192.168.1.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip
times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"LAPTOP net view 192.168.1.101"


Target LAPTOP

"LAPTOP ping LAPTOP"

Pinging LAPTOP [192.168.1.104] with 32 bytes of data:Reply from
192.168.1.104: bytes=32 time<1ms TTL=128Reply from 192.168.1.104: bytes=32
time<1ms TTL=128Reply from 192.168.1.104: bytes=32 time<1ms TTL=128Reply from
192.168.1.104: bytes=32 time<1ms TTL=128Ping statistics for 192.168.1.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip
times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"LAPTOP net view LAPTOP"

Shared resources at LAPTOP

EP-MBA 2006

Share name Type Used as Comment

-------------------------------------------------------------------------------
C Disk
Desktop Disk
My Documents Disk
Printer Print Microsoft Office Document Image Writer
Printer2 Print SMART Notebook Print Capture
Printer3 Print HP LaserJet 4050 Series PCL6
Printer6 Print HP LaserJet 4250 PCL 6
Printer8 Print Adobe PDF
SharedDocs Disk
The command completed successfully.


Target 192.168.1.104

"LAPTOP ping 192.168.1.104"

Pinging 192.168.1.104 with 32 bytes of data:Reply from 192.168.1.104:
bytes=32 time<1ms TTL=128Reply from 192.168.1.104: bytes=32 time<1ms
TTL=128Reply from 192.168.1.104: bytes=32 time<1ms TTL=128Reply from
192.168.1.104: bytes=32 time<1ms TTL=128Ping statistics for 192.168.1.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip
times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"LAPTOP net view 192.168.1.104"


Target Basement

"LAPTOP ping Basement"

Pinging Basement [192.168.1.100] with 32 bytes of data:Reply from
192.168.1.100: bytes=32 time<1ms TTL=128Reply from 192.168.1.100: bytes=32
time<1ms TTL=128Reply from 192.168.1.100: bytes=32 time<1ms TTL=128Reply from
192.168.1.100: bytes=32 time<1ms TTL=128Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip
times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"LAPTOP net view Basement"

Shared resources at Basement

Kid's Computer

Share name Type Used as Comment

-------------------------------------------------------------------------------
My Documents Disk
PRESARIO (C) Disk
Printer Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.


Target 192.168.1.100

"LAPTOP ping 192.168.1.100"

Pinging 192.168.1.100 with 32 bytes of data:Reply from 192.168.1.100:
bytes=32 time<1ms TTL=128Reply from 192.168.1.100: bytes=32 time<1ms
TTL=128Reply from 192.168.1.100: bytes=32 time<1ms TTL=128Reply from
192.168.1.100: bytes=32 time<1ms TTL=128Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip
times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"LAPTOP net view 192.168.1.100"

Shared resources at 192.168.1.100

Kid's Computer

Share name Type Used as Comment

-------------------------------------------------------------------------------
My Documents Disk
PRESARIO (C) Disk
Printer Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.


Target 127.0.0.1

"LAPTOP 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=128Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Reply from
127.0.0.1: bytes=32 time<1ms TTL=128Reply from 127.0.0.1: bytes=32 time<1ms
TTL=128Ping 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
"LAPTOP net view 127.0.0.1"

Shared resources at 127.0.0.1

EP-MBA 2006

Share name Type Used as Comment

-------------------------------------------------------------------------------
C Disk
Desktop Disk
My Documents Disk
Printer Print Microsoft Office Document Image Writer
Printer2 Print SMART Notebook Print Capture
Printer3 Print HP LaserJet 4050 Series PCL6
Printer6 Print HP LaserJet 4250 PCL 6
Printer8 Print Adobe PDF
SharedDocs Disk
The command completed successfully.


Ping Targets www.yahoo.com 66.94.230.32 192.168.1.1

Target www.yahoo.com

"LAPTOP ping www.yahoo.com"

Pinging www.yahoo.akadns.net [216.109.118.68] with 32 bytes of data:Reply
from 216.109.118.68: bytes=32 time=23ms TTL=45Reply from 216.109.118.68:
bytes=32 time=23ms TTL=45Reply from 216.109.118.68: bytes=32 time=23ms
TTL=45Reply from 216.109.118.68: bytes=32 time=24ms TTL=45Ping statistics for
216.109.118.68: Packets: Sent = 4, Received = 4, Lost = 0 (0%
loss),Approximate round trip times in milli-seconds: Minimum = 23ms,
Maximum = 24ms, Average = 23ms
Target 66.94.230.32

"LAPTOP ping 66.94.230.32"

Pinging 66.94.230.32 with 32 bytes of data:Reply from 66.94.230.32: bytes=32
time=86ms TTL=44Reply from 66.94.230.32: bytes=32 time=85ms TTL=43Reply from
66.94.230.32: bytes=32 time=84ms TTL=44Reply from 66.94.230.32: bytes=32
time=85ms TTL=44Ping statistics for 66.94.230.32: Packets: Sent = 4,
Received = 4, Lost = 0 (0% loss),Approximate round trip times in
milli-seconds: Minimum = 84ms, Maximum = 86ms, Average = 85ms
Target 192.168.1.1

"LAPTOP ping 192.168.1.1"

Pinging 192.168.1.1 with 32 bytes of data:Reply from 192.168.1.1: bytes=32
time=3ms TTL=64Reply from 192.168.1.1: bytes=32 time<1ms TTL=64Reply from
192.168.1.1: bytes=32 time<1ms TTL=64Reply from 192.168.1.1: bytes=32
time<1ms TTL=64Ping statistics for 192.168.1.1: Packets: Sent = 4,
Received = 4, Lost = 0 (0% loss),Approximate round trip times in
milli-seconds: Minimum = 0ms, Maximum = 3ms, Average = 0ms
End diagnosis for LAPTOP


CDiagnosis V1.32
Start diagnosis for BASEMENT

Adhoc Browser View


Full Targets gateway 192.168.1.101 LAPTOP 192.168.1.104 Basement
192.168.1.100 127.0.0.1

Target gateway

"BASEMENT ping gateway"

Pinging gateway [192.168.1.101] with 32 bytes of data:Reply from
192.168.1.101: bytes=32 time<1ms TTL=128Reply from 192.168.1.101: bytes=32
time<1ms TTL=128Reply from 192.168.1.101: bytes=32 time<1ms TTL=128Reply from
192.168.1.101: bytes=32 time<1ms TTL=128Ping statistics for 192.168.1.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip
times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"BASEMENT net view gateway"


Target 192.168.1.101

"BASEMENT ping 192.168.1.101"

Pinging 192.168.1.101 with 32 bytes of data:Reply from 192.168.1.101:
bytes=32 time<1ms TTL=128Reply from 192.168.1.101: bytes=32 time<1ms
TTL=128Reply from 192.168.1.101: bytes=32 time<1ms TTL=128Reply from
192.168.1.101: bytes=32 time<1ms TTL=128Ping statistics for 192.168.1.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip
times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"BASEMENT net view 192.168.1.101"


Target LAPTOP

"BASEMENT ping LAPTOP"

Pinging LAPTOP [192.168.1.103] with 32 bytes of data:Request timed
out.Request timed out.Request timed out.Request timed out.Ping statistics for
192.168.1.103: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
"BASEMENT net view LAPTOP"


Target 192.168.1.104

"BASEMENT ping 192.168.1.104"

Pinging 192.168.1.104 with 32 bytes of data:Reply from 192.168.1.104:
bytes=32 time<1ms TTL=128Reply from 192.168.1.104: bytes=32 time<1ms
TTL=128Reply from 192.168.1.104: bytes=32 time<1ms TTL=128Reply from
192.168.1.104: bytes=32 time<1ms TTL=128Ping statistics for 192.168.1.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip
times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"BASEMENT net view 192.168.1.104"


Target Basement

"BASEMENT ping Basement"

Pinging Basement [192.168.1.100] with 32 bytes of data:Reply from
192.168.1.100: bytes=32 time<1ms TTL=128Reply from 192.168.1.100: bytes=32
time<1ms TTL=128Reply from 192.168.1.100: bytes=32 time<1ms TTL=128Reply from
192.168.1.100: bytes=32 time<1ms TTL=128Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip
times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"BASEMENT net view Basement"

Shared resources at Basement

Kid's Computer

Share name Type Used as Comment

-------------------------------------------------------------------------------
My Documents Disk
PRESARIO (C) Disk
Printer Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.


Target 192.168.1.100

"BASEMENT ping 192.168.1.100"

Pinging 192.168.1.100 with 32 bytes of data:Reply from 192.168.1.100:
bytes=32 time<1ms TTL=128Reply from 192.168.1.100: bytes=32 time<1ms
TTL=128Reply from 192.168.1.100: bytes=32 time<1ms TTL=128Reply from
192.168.1.100: bytes=32 time<1ms TTL=128Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip
times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"BASEMENT net view 192.168.1.100"

Shared resources at 192.168.1.100

Kid's Computer

Share name Type Used as Comment

-------------------------------------------------------------------------------
My Documents Disk
PRESARIO (C) Disk
Printer Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.


Target 127.0.0.1

"BASEMENT 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=128Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Reply from
127.0.0.1: bytes=32 time<1ms TTL=128Reply from 127.0.0.1: bytes=32 time<1ms
TTL=128Ping 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
"BASEMENT net view 127.0.0.1"

Shared resources at 127.0.0.1

Kid's Computer

Share name Type Used as Comment

-------------------------------------------------------------------------------
My Documents Disk
PRESARIO (C) Disk
Printer Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.


Ping Targets www.yahoo.com 66.94.230.32 192.168.1.1

Target www.yahoo.com

"BASEMENT ping www.yahoo.com"

Pinging www.yahoo.akadns.net [216.109.117.106] with 32 bytes of data:Reply
from 216.109.117.106: bytes=32 time=22ms TTL=46Reply from 216.109.117.106:
bytes=32 time=23ms TTL=46Reply from 216.109.117.106: bytes=32 time=28ms
TTL=46Reply from 216.109.117.106: bytes=32 time=22ms TTL=46Ping statistics
for 216.109.117.106: Packets: Sent = 4, Received = 4, Lost = 0 (0%
loss),Approximate round trip times in milli-seconds: Minimum = 22ms,
Maximum = 28ms, Average = 23ms
Target 66.94.230.32

"BASEMENT ping 66.94.230.32"

Pinging 66.94.230.32 with 32 bytes of data:Reply from 66.94.230.32: bytes=32
time=86ms TTL=44Reply from 66.94.230.32: bytes=32 time=85ms TTL=44Reply from
66.94.230.32: bytes=32 time=84ms TTL=43Reply from 66.94.230.32: bytes=32
time=86ms TTL=44Ping statistics for 66.94.230.32: Packets: Sent = 4,
Received = 4, Lost = 0 (0% loss),Approximate round trip times in
milli-seconds: Minimum = 84ms, Maximum = 86ms, Average = 85ms
Target 192.168.1.1

"BASEMENT ping 192.168.1.1"

Pinging 192.168.1.1 with 32 bytes of data:Reply from 192.168.1.1: bytes=32
time<1ms TTL=64Reply from 192.168.1.1: bytes=32 time<1ms TTL=64Reply from
192.168.1.1: bytes=32 time<1ms TTL=64Reply from 192.168.1.1: bytes=32
time<1ms TTL=64Ping statistics for 192.168.1.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 BASEMENT


"Chuck" wrote:

> On Sun, 3 Jul 2005 13:17:01 -0700, "Jon M" <JonM@discussions.microsoft.com>
> wrote:
>
> >"Chuck" wrote:
> >
> >> On Fri, 1 Jul 2005 06:15:02 -0700, "Jon M" <JonM@discussions.microsoft.com>
> >> wrote:
> >>
> >> >Hi again, and thanks for the help. Was up all night working thought I'd
> >> >postthis before crashing in the hopes that you may hev time to look it over
> >> >by the time I get up:
> >>
> >> <SNIP>
> >>
> >> Jon,
> >>
> >> Let's see where we are.
> >> # Node Types Hybrid and Unknown, no problem there.
> >> # No gratuitous protocols.
> >>
> >> I can't find any references to either a "123" or "2351" error in Microsoft
> >> documentation. I did a Google search, though, and got several hits. This set
> >> of errors has come up in the past, in problems resolved in this group. They've
> >> unfortunately been trial-and-error resolutions based upon my other 2 listed
> >> possible causes for the "error = 53", namely:
> >> # Corrupted LSP / Winsock.
> >> # Firewall problem.
> >>
> >> I looked at the search hits. One guy reported having an "internet filter
> >> service" running, and his problem was resolved by removing that. Two others had
> >> gratuitous protocols, one IPV6, and the other NetBEUI.
> >>
> >> Why no "browstat status" for Laptop?
> >>
> >> What's different in your situation is that you have a symmetrical problem, ie
> >> each computer showing these symptoms. In a way, this is good. You can work on
> >> just ONE computer at a time, check "browstat status" on EACH computer after each
> >> change, and look for a difference in results (possibly showing from either
> >> computer).
> >> <http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
> >>
> >> What personal firewalls and antivirus products do you have?
> >> <http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
> >>
> >> Look for corrupted LSP / Winsock. Run each of the 5 fixes, one at a time, on
> >> ONE of your computers, and check for results using "browstat status" run on EACH
> >> computer.
> >> <http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
> >> # LSP-Fix.
> >> # WinsockFix
> >> # WinsockXPFix
> >> # Do you have SP2, or pre-SP2? Do the appropriate Windows native fix.
> >> # Reset TCP/IP.
> >>
> >> Once you get results from updating ONE computer, try the same fix on a second
> >> computer, and observe the results.
>
> >help.
> >tried all of these fixes and still nothing.
> >hired someone local to come over and fix this and she said it was the router
> >which i believe is incorrect.
> >ready to take lives.
> >willing to pay for competent help.
> >could it be the router?

[Chuck]

On Sun, 3 Jul 2005 17:17:01 -0700, "Jon M" <JonM@discussions.microsoft.com>
wrote:

>"Chuck" wrote:
>
>> On Sun, 3 Jul 2005 13:17:01 -0700, "Jon M" <JonM@discussions.microsoft.com>
>> wrote:
>>
>> >"Chuck" wrote:
>> >
>> >> On Fri, 1 Jul 2005 06:15:02 -0700, "Jon M" <JonM@discussions.microsoft.com>
>> >> wrote:
>> >>
>> >> >Hi again, and thanks for the help. Was up all night working thought I'd
>> >> >postthis before crashing in the hopes that you may hev time to look it over
>> >> >by the time I get up:
>> >>
>> >> <SNIP>
>> >>
>> >> Jon,
>> >>
>> >> Let's see where we are.
>> >> # Node Types Hybrid and Unknown, no problem there.
>> >> # No gratuitous protocols.
>> >>
>> >> I can't find any references to either a "123" or "2351" error in Microsoft
>> >> documentation. I did a Google search, though, and got several hits. This set
>> >> of errors has come up in the past, in problems resolved in this group. They've
>> >> unfortunately been trial-and-error resolutions based upon my other 2 listed
>> >> possible causes for the "error = 53", namely:
>> >> # Corrupted LSP / Winsock.
>> >> # Firewall problem.
>> >>
>> >> I looked at the search hits. One guy reported having an "internet filter
>> >> service" running, and his problem was resolved by removing that. Two others had
>> >> gratuitous protocols, one IPV6, and the other NetBEUI.
>> >>
>> >> Why no "browstat status" for Laptop?
>> >>
>> >> What's different in your situation is that you have a symmetrical problem, ie
>> >> each computer showing these symptoms. In a way, this is good. You can work on
>> >> just ONE computer at a time, check "browstat status" on EACH computer after each
>> >> change, and look for a difference in results (possibly showing from either
>> >> computer).
>> >> <http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
>> >>
>> >> What personal firewalls and antivirus products do you have?
>> >> <http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
>> >>
>> >> Look for corrupted LSP / Winsock. Run each of the 5 fixes, one at a time, on
>> >> ONE of your computers, and check for results using "browstat status" run on EACH
>> >> computer.
>> >> <http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
>> >> # LSP-Fix.
>> >> # WinsockFix
>> >> # WinsockXPFix
>> >> # Do you have SP2, or pre-SP2? Do the appropriate Windows native fix.
>> >> # Reset TCP/IP.
>> >>
>> >> Once you get results from updating ONE computer, try the same fix on a second
>> >> computer, and observe the results.
>>
>> >help.
>> >tried all of these fixes and still nothing.
>> >hired someone local to come over and fix this and she said it was the router
>> >which i believe is incorrect.
>> >ready to take lives.
>> >willing to pay for competent help.
>> >could it be the router?

>thanks so much for your help.
>i noticed yesterday that I've lost the ability to log into my hospital's
>secured VPN (i'm an ER physician and do work daily from my home) from the
>desktop (had worked okay a few days ago) but still can from the laptop. argh.
>anyway, appreciate your help & patience. will owe you hugely for any input
>you can give me.
>thanks again.
>ouput follows:

<SNIP>

Jon,

Well, you have at least 2 problems to work on.

Firstly, look at Gateway:

"GATEWAY ping gateway"
Pinging gateway [::1] with 32 bytes of data:
Reply from ::1: time<1ms

"GATEWAY ping LAPTOP"
Pinging LAPTOP [192.168.1.103] with 32 bytes of data:

That almost has to be LSP / Winsock corruption.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>

Or look at the Hosts and LMHosts files on Gateway (in
"C:\WINDOWS\system32\drivers\etc") for odd entries.

Second, look at Laptop. Neither Gateway nor Basement can get anything from "Net
View", either against its name or IP address. Is Laptop using Guest
authentication? If so, check the restrictanonymous setting.
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Guest>
Next, check Laptop for a firewall problem.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>

Also, what's with the IP address for laptop? The original IPConfig showed it at
....101. You changed it in CDiag to ...104.

Let's see if any of those suggestions makes any improvement.

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

[Jon M]

how do i look at the Hosts and LMHosts files on Gateway (in
> "C:\WINDOWS\system32\drivers\etc") for odd entries?
have seen that before but didn't know what it meant.
will try the other stuff and get back with you.
thanks again-



"Chuck" wrote:

> On Sun, 3 Jul 2005 17:17:01 -0700, "Jon M" <JonM@discussions.microsoft.com>
> wrote:
>
> >"Chuck" wrote:
> >
> >> On Sun, 3 Jul 2005 13:17:01 -0700, "Jon M" <JonM@discussions.microsoft.com>
> >> wrote:
> >>
> >> >"Chuck" wrote:
> >> >
> >> >> On Fri, 1 Jul 2005 06:15:02 -0700, "Jon M" <JonM@discussions.microsoft.com>
> >> >> wrote:
> >> >>
> >> >> >Hi again, and thanks for the help. Was up all night working thought I'd
> >> >> >postthis before crashing in the hopes that you may hev time to look it over
> >> >> >by the time I get up:
> >> >>
> >> >> <SNIP>
> >> >>
> >> >> Jon,
> >> >>
> >> >> Let's see where we are.
> >> >> # Node Types Hybrid and Unknown, no problem there.
> >> >> # No gratuitous protocols.
> >> >>
> >> >> I can't find any references to either a "123" or "2351" error in Microsoft
> >> >> documentation. I did a Google search, though, and got several hits. This set
> >> >> of errors has come up in the past, in problems resolved in this group. They've
> >> >> unfortunately been trial-and-error resolutions based upon my other 2 listed
> >> >> possible causes for the "error = 53", namely:
> >> >> # Corrupted LSP / Winsock.
> >> >> # Firewall problem.
> >> >>
> >> >> I looked at the search hits. One guy reported having an "internet filter
> >> >> service" running, and his problem was resolved by removing that. Two others had
> >> >> gratuitous protocols, one IPV6, and the other NetBEUI.
> >> >>
> >> >> Why no "browstat status" for Laptop?
> >> >>
> >> >> What's different in your situation is that you have a symmetrical problem, ie
> >> >> each computer showing these symptoms. In a way, this is good. You can work on
> >> >> just ONE computer at a time, check "browstat status" on EACH computer after each
> >> >> change, and look for a difference in results (possibly showing from either
> >> >> computer).
> >> >> <http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
> >> >>
> >> >> What personal firewalls and antivirus products do you have?
> >> >> <http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
> >> >>
> >> >> Look for corrupted LSP / Winsock. Run each of the 5 fixes, one at a time, on
> >> >> ONE of your computers, and check for results using "browstat status" run on EACH
> >> >> computer.
> >> >> <http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
> >> >> # LSP-Fix.
> >> >> # WinsockFix
> >> >> # WinsockXPFix
> >> >> # Do you have SP2, or pre-SP2? Do the appropriate Windows native fix.
> >> >> # Reset TCP/IP.
> >> >>
> >> >> Once you get results from updating ONE computer, try the same fix on a second
> >> >> computer, and observe the results.
> >>
> >> >help.
> >> >tried all of these fixes and still nothing.
> >> >hired someone local to come over and fix this and she said it was the router
> >> >which i believe is incorrect.
> >> >ready to take lives.
> >> >willing to pay for competent help.
> >> >could it be the router?
>
> >thanks so much for your help.
> >i noticed yesterday that I've lost the ability to log into my hospital's
> >secured VPN (i'm an ER physician and do work daily from my home) from the
> >desktop (had worked okay a few days ago) but still can from the laptop. argh.
> >anyway, appreciate your help & patience. will owe you hugely for any input
> >you can give me.
> >thanks again.
> >ouput follows:
>
> <SNIP>
>
> Jon,
>
> Well, you have at least 2 problems to work on.
>
> Firstly, look at Gateway:
>
> "GATEWAY ping gateway"
> Pinging gateway [::1] with 32 bytes of data:
> Reply from ::1: time<1ms
>
> "GATEWAY ping LAPTOP"
> Pinging LAPTOP [192.168.1.103] with 32 bytes of data:
>
> That almost has to be LSP / Winsock corruption.
> <http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
>
> Or look at the Hosts and LMHosts files on Gateway (in
> "C:\WINDOWS\system32\drivers\etc") for odd entries.
>
> Second, look at Laptop. Neither Gateway nor Basement can get anything from "Net
> View", either against its name or IP address. Is Laptop using Guest
> authentication? If so, check the restrictanonymous setting.
> <http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Guest>
> Next, check Laptop for a firewall problem.
> <http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
>
> Also, what's with the IP address for laptop? The original IPConfig showed it at
> ....101. You changed it in CDiag to ...104.
>
> Let's see if any of those suggestions makes any improvement.
>
> --
> 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 sonic net.
>

[Chuck]

On Mon, 4 Jul 2005 00:45:01 -0700, "Jon M" <JonM@discussions.microsoft.com>
wrote:

>"Chuck" wrote:
>
>> On Sun, 3 Jul 2005 17:17:01 -0700, "Jon M" <JonM@discussions.microsoft.com>
>> wrote:
>>
>> >"Chuck" wrote:
>> >
>> >> On Sun, 3 Jul 2005 13:17:01 -0700, "Jon M" <JonM@discussions.microsoft.com>
>> >> wrote:
>> >>
>> >> >"Chuck" wrote:
>> >> >
>> >> >> On Fri, 1 Jul 2005 06:15:02 -0700, "Jon M" <JonM@discussions.microsoft.com>
>> >> >> wrote:
>> >> >>
>> >> >> >Hi again, and thanks for the help. Was up all night working thought I'd
>> >> >> >postthis before crashing in the hopes that you may hev time to look it over
>> >> >> >by the time I get up:
>> >> >>
>> >> >> <SNIP>
>> >> >>
>> >> >> Jon,
>> >> >>
>> >> >> Let's see where we are.
>> >> >> # Node Types Hybrid and Unknown, no problem there.
>> >> >> # No gratuitous protocols.
>> >> >>
>> >> >> I can't find any references to either a "123" or "2351" error in Microsoft
>> >> >> documentation. I did a Google search, though, and got several hits. This set
>> >> >> of errors has come up in the past, in problems resolved in this group. They've
>> >> >> unfortunately been trial-and-error resolutions based upon my other 2 listed
>> >> >> possible causes for the "error = 53", namely:
>> >> >> # Corrupted LSP / Winsock.
>> >> >> # Firewall problem.
>> >> >>
>> >> >> I looked at the search hits. One guy reported having an "internet filter
>> >> >> service" running, and his problem was resolved by removing that. Two others had
>> >> >> gratuitous protocols, one IPV6, and the other NetBEUI.
>> >> >>
>> >> >> Why no "browstat status" for Laptop?
>> >> >>
>> >> >> What's different in your situation is that you have a symmetrical problem, ie
>> >> >> each computer showing these symptoms. In a way, this is good. You can work on
>> >> >> just ONE computer at a time, check "browstat status" on EACH computer after each
>> >> >> change, and look for a difference in results (possibly showing from either
>> >> >> computer).
>> >> >> <http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
>> >> >>
>> >> >> What personal firewalls and antivirus products do you have?
>> >> >> <http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
>> >> >>
>> >> >> Look for corrupted LSP / Winsock. Run each of the 5 fixes, one at a time, on
>> >> >> ONE of your computers, and check for results using "browstat status" run on EACH
>> >> >> computer.
>> >> >> <http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
>> >> >> # LSP-Fix.
>> >> >> # WinsockFix
>> >> >> # WinsockXPFix
>> >> >> # Do you have SP2, or pre-SP2? Do the appropriate Windows native fix.
>> >> >> # Reset TCP/IP.
>> >> >>
>> >> >> Once you get results from updating ONE computer, try the same fix on a second
>> >> >> computer, and observe the results.
>> >>
>> >> >help.
>> >> >tried all of these fixes and still nothing.
>> >> >hired someone local to come over and fix this and she said it was the router
>> >> >which i believe is incorrect.
>> >> >ready to take lives.
>> >> >willing to pay for competent help.
>> >> >could it be the router?
>>
>> >thanks so much for your help.
>> >i noticed yesterday that I've lost the ability to log into my hospital's
>> >secured VPN (i'm an ER physician and do work daily from my home) from the
>> >desktop (had worked okay a few days ago) but still can from the laptop. argh.
>> >anyway, appreciate your help & patience. will owe you hugely for any input
>> >you can give me.
>> >thanks again.
>> >ouput follows:
>>
>> <SNIP>
>>
>> Jon,
>>
>> Well, you have at least 2 problems to work on.
>>
>> Firstly, look at Gateway:
>>
>> "GATEWAY ping gateway"
>> Pinging gateway [::1] with 32 bytes of data:
>> Reply from ::1: time<1ms
>>
>> "GATEWAY ping LAPTOP"
>> Pinging LAPTOP [192.168.1.103] with 32 bytes of data:
>>
>> That almost has to be LSP / Winsock corruption.
>> <http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
>>
>> Or look at the Hosts and LMHosts files on Gateway (in
>> "C:\WINDOWS\system32\drivers\etc") for odd entries.
>>
>> Second, look at Laptop. Neither Gateway nor Basement can get anything from "Net
>> View", either against its name or IP address. Is Laptop using Guest
>> authentication? If so, check the restrictanonymous setting.
>> <http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Guest>
>> Next, check Laptop for a firewall problem.
>> <http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
>>
>> Also, what's with the IP address for laptop? The original IPConfig showed it at
>> ....101. You changed it in CDiag to ...104.
>>
>> Let's see if any of those suggestions makes any improvement.

>how do i look at the Hosts and LMHosts files on Gateway (in
>> "C:\WINDOWS\system32\drivers\etc") for odd entries?
>have seen that before but didn't know what it meant.
>will try the other stuff and get back with you.
>thanks again-

Jon,

Hosts and LMHosts are local, fixed name resolution caches on your computer,
invented before the concept of DNS. Their contents may cause the computer to
ignore use of dynamic name resolution like DNS, name broadcast, and / or WINS.

Laptop should have an IP address of 192.168.1.104 (per your change), but if
there was, for instance, an entry:
"192.168.1.103 Laptop" (less the "")
in either Hosts or LMHosts on Gateway, that would cause the discrepancy in the
way it appears to be addressing Laptop.

Gateway appearing to resolve its own IP address to "::1", on the other hand, is
either a corruption problem, or a remnant of IPV6. Yet I saw no sign of IPV6 in
the IPConfig for Gateway. If there was an entry:
"::1 Gateway" (less the "")
in either Hosts or LMHosts on Gateway, that would also cause this address
resolution anomaly.

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

[Chuck]

On Mon, 4 Jul 2005 00:45:01 -0700, "Jon M" <JonM@discussions.microsoft.com>
wrote:

>"Chuck" wrote:
>
>> On Sun, 3 Jul 2005 17:17:01 -0700, "Jon M" <JonM@discussions.microsoft.com>
>> wrote:
>>
>> >"Chuck" wrote:
>> >
>> >> On Sun, 3 Jul 2005 13:17:01 -0700, "Jon M" <JonM@discussions.microsoft.com>
>> >> wrote:
>> >>
>> >> >"Chuck" wrote:
>> >> >
>> >> >> On Fri, 1 Jul 2005 06:15:02 -0700, "Jon M" <JonM@discussions.microsoft.com>
>> >> >> wrote:
>> >> >>
>> >> >> >Hi again, and thanks for the help. Was up all night working thought I'd
>> >> >> >postthis before crashing in the hopes that you may hev time to look it over
>> >> >> >by the time I get up:
>> >> >>
>> >> >> <SNIP>
>> >> >>
>> >> >> Jon,
>> >> >>
>> >> >> Let's see where we are.
>> >> >> # Node Types Hybrid and Unknown, no problem there.
>> >> >> # No gratuitous protocols.
>> >> >>
>> >> >> I can't find any references to either a "123" or "2351" error in Microsoft
>> >> >> documentation. I did a Google search, though, and got several hits. This set
>> >> >> of errors has come up in the past, in problems resolved in this group. They've
>> >> >> unfortunately been trial-and-error resolutions based upon my other 2 listed
>> >> >> possible causes for the "error = 53", namely:
>> >> >> # Corrupted LSP / Winsock.
>> >> >> # Firewall problem.
>> >> >>
>> >> >> I looked at the search hits. One guy reported having an "internet filter
>> >> >> service" running, and his problem was resolved by removing that. Two others had
>> >> >> gratuitous protocols, one IPV6, and the other NetBEUI.
>> >> >>
>> >> >> Why no "browstat status" for Laptop?
>> >> >>
>> >> >> What's different in your situation is that you have a symmetrical problem, ie
>> >> >> each computer showing these symptoms. In a way, this is good. You can work on
>> >> >> just ONE computer at a time, check "browstat status" on EACH computer after each
>> >> >> change, and look for a difference in results (possibly showing from either
>> >> >> computer).
>> >> >> <http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
>> >> >>
>> >> >> What personal firewalls and antivirus products do you have?
>> >> >> <http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
>> >> >>
>> >> >> Look for corrupted LSP / Winsock. Run each of the 5 fixes, one at a time, on
>> >> >> ONE of your computers, and check for results using "browstat status" run on EACH
>> >> >> computer.
>> >> >> <http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
>> >> >> # LSP-Fix.
>> >> >> # WinsockFix
>> >> >> # WinsockXPFix
>> >> >> # Do you have SP2, or pre-SP2? Do the appropriate Windows native fix.
>> >> >> # Reset TCP/IP.
>> >> >>
>> >> >> Once you get results from updating ONE computer, try the same fix on a second
>> >> >> computer, and observe the results.
>> >>
>> >> >help.
>> >> >tried all of these fixes and still nothing.
>> >> >hired someone local to come over and fix this and she said it was the router
>> >> >which i believe is incorrect.
>> >> >ready to take lives.
>> >> >willing to pay for competent help.
>> >> >could it be the router?
>>
>> >thanks so much for your help.
>> >i noticed yesterday that I've lost the ability to log into my hospital's
>> >secured VPN (i'm an ER physician and do work daily from my home) from the
>> >desktop (had worked okay a few days ago) but still can from the laptop. argh.
>> >anyway, appreciate your help & patience. will owe you hugely for any input
>> >you can give me.
>> >thanks again.
>> >ouput follows:
>>
>> <SNIP>
>>
>> Jon,
>>
>> Well, you have at least 2 problems to work on.
>>
>> Firstly, look at Gateway:
>>
>> "GATEWAY ping gateway"
>> Pinging gateway [::1] with 32 bytes of data:
>> Reply from ::1: time<1ms
>>
>> "GATEWAY ping LAPTOP"
>> Pinging LAPTOP [192.168.1.103] with 32 bytes of data:
>>
>> That almost has to be LSP / Winsock corruption.
>> <http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
>>
>> Or look at the Hosts and LMHosts files on Gateway (in
>> "C:\WINDOWS\system32\drivers\etc") for odd entries.
>>
>> Second, look at Laptop. Neither Gateway nor Basement can get anything from "Net
>> View", either against its name or IP address. Is Laptop using Guest
>> authentication? If so, check the restrictanonymous setting.
>> <http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Guest>
>> Next, check Laptop for a firewall problem.
>> <http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
>>
>> Also, what's with the IP address for laptop? The original IPConfig showed it at
>> ....101. You changed it in CDiag to ...104.
>>
>> Let's see if any of those suggestions makes any improvement.

>how do i look at the Hosts and LMHosts files on Gateway (in
>> "C:\WINDOWS\system32\drivers\etc") for odd entries?
>have seen that before but didn't know what it meant.
>will try the other stuff and get back with you.
>thanks again-

Jon,

Hosts and LMHosts are local, fixed name resolution caches on your computer,
invented before the concept of DNS. Their contents may cause the computer to
ignore use of dynamic name resolution like DNS, name broadcast, and / or WINS.
<http://nitecruzr.blogspot.com/2005/07/local-name-and-address-resolution-on.html>

Laptop should have an IP address of 192.168.1.104 (per your change), but if
there was, for instance, an entry:
"192.168.1.103 Laptop" (less the "")
in either Hosts or LMHosts on Gateway, that would cause the discrepancy in the
way it appears to be addressing Laptop.

Gateway appearing to resolve its own IP address to "::1", on the other hand, is
either a corruption problem, or a remnant of IPV6. Yet I saw no sign of IPV6 in
the IPConfig for Gateway. If there was an entry:
"::1 Gateway" (less the "")
in either Hosts or LMHosts on Gateway, that would also cause this address
resolution anomaly.

You can open either file using Notepad.

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

[Jon M]

well.
this is interesting.
ran the tcp/ip reset.
also switched the ethernet cable to a difgferent socket on the router for
the laptop as it was showing intermittently connecting & disconnecting on the
connectoid in the system tray on the laptop.
now:

laptop sees basement
desktop sees basement.
desktop & laptop don't see each other.
desktop still cannot access hospital vpn over the internet (using smartpass)
though the laptop can.
alkmost like something on the desktop is blocking the smartpass vpn access &
the network/laptop connection.
strange, huh?
maybe it's the router, but that doesn't seem to make sense either.
happy 4th...

files-
hosts:
# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

127.0.0.1 localhost

lmhosts:
# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample LMHOSTS file used by the Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to computernames
# (NetBIOS) names. Each entry should be kept on an individual line.
# The IP address should be placed in the first column followed by the
# corresponding computername. The address and the computername
# should be separated by at least one space or tab. The "#" character
# is generally used to denote the start of a comment (see the exceptions
# below).
#
# This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
# files and offers the following extensions:
#
# #PRE
# #DOM:<domain>
# #INCLUDE <filename>
# #BEGIN_ALTERNATE
# #END_ALTERNATE
# \0xnn (non-printing character support)
#
# Following any entry in the file with the characters "#PRE" will cause
# the entry to be preloaded into the name cache. By default, entries are
# not preloaded, but are parsed only after dynamic name resolution fails.
#
# Following an entry with the "#DOM:<domain>" tag will associate the
# entry with the domain specified by <domain>. This affects how the
# browser and logon services behave in TCP/IP environments. To preload
# the host name associated with #DOM entry, it is necessary to also add a
# #PRE to the line. The <domain> is always preloaded although it will not
# be shown when the name cache is viewed.
#
# Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)
# software to seek the specified <filename> and parse it as if it were
# local. <filename> is generally a UNC-based name, allowing a
# centralized lmhosts file to be maintained on a server.
# It is ALWAYS necessary to provide a mapping for the IP address of the
# server prior to the #INCLUDE. This mapping must use the #PRE directive.
# In addtion the share "public" in the example below must be in the
# LanManServer list of "NullSessionShares" in order for client machines to
# be able to read the lmhosts file successfully. This key is under
#
\machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares
# in the registry. Simply add "public" to the list found there.
#
# The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
# statements to be grouped together. Any single successful include
# will cause the group to succeed.
#
# Finally, non-printing characters can be embedded in mappings by
# first surrounding the NetBIOS name in quotations, then using the
# \0xnn notation to specify a hex value for a non-printing character.
#
# The following example illustrates all of these extensions:
#
# 102.54.94.97 rhino #PRE #DOM:networking #net group's DC
# 102.54.94.102 "appname \0x14" #special app server
# 102.54.94.123 popular #PRE #source server
# 102.54.94.117 localsrv #PRE #needed for the include
#
# #BEGIN_ALTERNATE
# #INCLUDE \\localsrv\public\lmhosts
# #INCLUDE \\rhino\public\lmhosts
# #END_ALTERNATE
#
# In the above example, the "appname" server contains a special
# character in its name, the "popular" and "localsrv" server names are
# preloaded, and the "rhino" server name is specified so it can be used
# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
# system is unavailable.
#
# Note that the whole file is parsed including comments on each lookup,
# so keeping the number of comments to a minimum will improve performance.
# Therefore it is not advisable to simply add lmhosts file entries onto the
# end of this file.







"Chuck" wrote:

> On Mon, 4 Jul 2005 00:45:01 -0700, "Jon M" <JonM@discussions.microsoft.com>
> wrote:
>
> >"Chuck" wrote:
> >
> >> On Sun, 3 Jul 2005 17:17:01 -0700, "Jon M" <JonM@discussions.microsoft.com>
> >> wrote:
> >>
> >> >"Chuck" wrote:
> >> >
> >> >> On Sun, 3 Jul 2005 13:17:01 -0700, "Jon M" <JonM@discussions.microsoft.com>
> >> >> wrote:
> >> >>
> >> >> >"Chuck" wrote:
> >> >> >
> >> >> >> On Fri, 1 Jul 2005 06:15:02 -0700, "Jon M" <JonM@discussions.microsoft.com>
> >> >> >> wrote:
> >> >> >>
> >> >> >> >Hi again, and thanks for the help. Was up all night working thought I'd
> >> >> >> >postthis before crashing in the hopes that you may hev time to look it over
> >> >> >> >by the time I get up:
> >> >> >>
> >> >> >> <SNIP>
> >> >> >>
> >> >> >> Jon,
> >> >> >>
> >> >> >> Let's see where we are.
> >> >> >> # Node Types Hybrid and Unknown, no problem there.
> >> >> >> # No gratuitous protocols.
> >> >> >>
> >> >> >> I can't find any references to either a "123" or "2351" error in Microsoft
> >> >> >> documentation. I did a Google search, though, and got several hits. This set
> >> >> >> of errors has come up in the past, in problems resolved in this group. They've
> >> >> >> unfortunately been trial-and-error resolutions based upon my other 2 listed
> >> >> >> possible causes for the "error = 53", namely:
> >> >> >> # Corrupted LSP / Winsock.
> >> >> >> # Firewall problem.
> >> >> >>
> >> >> >> I looked at the search hits. One guy reported having an "internet filter
> >> >> >> service" running, and his problem was resolved by removing that. Two others had
> >> >> >> gratuitous protocols, one IPV6, and the other NetBEUI.
> >> >> >>
> >> >> >> Why no "browstat status" for Laptop?
> >> >> >>
> >> >> >> What's different in your situation is that you have a symmetrical problem, ie
> >> >> >> each computer showing these symptoms. In a way, this is good. You can work on
> >> >> >> just ONE computer at a time, check "browstat status" on EACH computer after each
> >> >> >> change, and look for a difference in results (possibly showing from either
> >> >> >> computer).
> >> >> >> <http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
> >> >> >>
> >> >> >> What personal firewalls and antivirus products do you have?
> >> >> >> <http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
> >> >> >>
> >> >> >> Look for corrupted LSP / Winsock. Run each of the 5 fixes, one at a time, on
> >> >> >> ONE of your computers, and check for results using "browstat status" run on EACH
> >> >> >> computer.
> >> >> >> <http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
> >> >> >> # LSP-Fix.
> >> >> >> # WinsockFix
> >> >> >> # WinsockXPFix
> >> >> >> # Do you have SP2, or pre-SP2? Do the appropriate Windows native fix.
> >> >> >> # Reset TCP/IP.
> >> >> >>
> >> >> >> Once you get results from updating ONE computer, try the same fix on a second
> >> >> >> computer, and observe the results.
> >> >>
> >> >> >help.
> >> >> >tried all of these fixes and still nothing.
> >> >> >hired someone local to come over and fix this and she said it was the router
> >> >> >which i believe is incorrect.
> >> >> >ready to take lives.
> >> >> >willing to pay for competent help.
> >> >> >could it be the router?
> >>
> >> >thanks so much for your help.
> >> >i noticed yesterday that I've lost the ability to log into my hospital's
> >> >secured VPN (i'm an ER physician and do work daily from my home) from the
> >> >desktop (had worked okay a few days ago) but still can from the laptop. argh.
> >> >anyway, appreciate your help & patience. will owe you hugely for any input
> >> >you can give me.
> >> >thanks again.
> >> >ouput follows:
> >>
> >> <SNIP>
> >>
> >> Jon,
> >>
> >> Well, you have at least 2 problems to work on.
> >>
> >> Firstly, look at Gateway:
> >>
> >> "GATEWAY ping gateway"
> >> Pinging gateway [::1] with 32 bytes of data:
> >> Reply from ::1: time<1ms
> >>
> >> "GATEWAY ping LAPTOP"
> >> Pinging LAPTOP [192.168.1.103] with 32 bytes of data:
> >>
> >> That almost has to be LSP / Winsock corruption.
> >> <http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
> >>
> >> Or look at the Hosts and LMHosts files on Gateway (in
> >> "C:\WINDOWS\system32\drivers\etc") for odd entries.
> >>
> >> Second, look at Laptop. Neither Gateway nor Basement can get anything from "Net
> >> View", either against its name or IP address. Is Laptop using Guest
> >> authentication? If so, check the restrictanonymous setting.
> >> <http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Guest>
> >> Next, check Laptop for a firewall problem.
> >> <http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
> >>
> >> Also, what's with the IP address for laptop? The original IPConfig showed it at
> >> ....101. You changed it in CDiag to ...104.
> >>
> >> Let's see if any of those suggestions makes any improvement.
>
> >how do i look at the Hosts and LMHosts files on Gateway (in
> >> "C:\WINDOWS\system32\drivers\etc") for odd entries?
> >have seen that before but didn't know what it meant.
> >will try the other stuff and get back with you.
> >thanks again-
>
> Jon,
>
> Hosts and LMHosts are local, fixed name resolution caches on your computer,
> invented before the concept of DNS. Their contents may cause the computer to
> ignore use of dynamic name resolution like DNS, name broadcast, and / or WINS.
> <http://nitecruzr.blogspot.com/2005/07/local-name-and-address-resolution-on.html>
>
> Laptop should have an IP address of 192.168.1.104 (per your change), but if
> there was, for instance, an entry:
> "192.168.1.103 Laptop" (less the "")
> in either Hosts or LMHosts on Gateway, that would cause the discrepancy in the
> way it appears to be addressing Laptop.
>
> Gateway appearing to resolve its own IP address to "::1", on the other hand, is
> either a corruption problem, or a remnant of IPV6. Yet I saw no sign of IPV6 in
> the IPConfig for Gateway. If there was an entry:
> "::1 Gateway" (less the "")
> in either Hosts or LMHosts on Gateway, that would also cause this address
> resolution anomaly.
>
> You can open either file using Notepad.
>
> --
> 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 sonic net.
>

[Chuck]

On Mon, 4 Jul 2005 12:46:01 -0700, "Jon M" <JonM@discussions.microsoft.com>
wrote:

>"Chuck" wrote:
>
>> On Mon, 4 Jul 2005 00:45:01 -0700, "Jon M" <JonM@discussions.microsoft.com>
>> wrote:
>>
>> >"Chuck" wrote:
>> >
>> >> On Sun, 3 Jul 2005 17:17:01 -0700, "Jon M" <JonM@discussions.microsoft.com>
>> >> wrote:
>> >>
>> >> >"Chuck" wrote:
>> >> >
>> >> >> On Sun, 3 Jul 2005 13:17:01 -0700, "Jon M" <JonM@discussions.microsoft.com>
>> >> >> wrote:
>> >> >>
>> >> >> >"Chuck" wrote:
>> >> >> >
>> >> >> >> On Fri, 1 Jul 2005 06:15:02 -0700, "Jon M" <JonM@discussions.microsoft.com>
>> >> >> >> wrote:
>> >> >> >>
>> >> >> >> >Hi again, and thanks for the help. Was up all night working thought I'd
>> >> >> >> >postthis before crashing in the hopes that you may hev time to look it over
>> >> >> >> >by the time I get up:
>> >> >> >>
>> >> >> >> <SNIP>
>> >> >> >>
>> >> >> >> Jon,
>> >> >> >>
>> >> >> >> Let's see where we are.
>> >> >> >> # Node Types Hybrid and Unknown, no problem there.
>> >> >> >> # No gratuitous protocols.
>> >> >> >>
>> >> >> >> I can't find any references to either a "123" or "2351" error in Microsoft
>> >> >> >> documentation. I did a Google search, though, and got several hits. This set
>> >> >> >> of errors has come up in the past, in problems resolved in this group. They've
>> >> >> >> unfortunately been trial-and-error resolutions based upon my other 2 listed
>> >> >> >> possible causes for the "error = 53", namely:
>> >> >> >> # Corrupted LSP / Winsock.
>> >> >> >> # Firewall problem.
>> >> >> >>
>> >> >> >> I looked at the search hits. One guy reported having an "internet filter
>> >> >> >> service" running, and his problem was resolved by removing that. Two others had
>> >> >> >> gratuitous protocols, one IPV6, and the other NetBEUI.
>> >> >> >>
>> >> >> >> Why no "browstat status" for Laptop?
>> >> >> >>
>> >> >> >> What's different in your situation is that you have a symmetrical problem, ie
>> >> >> >> each computer showing these symptoms. In a way, this is good. You can work on
>> >> >> >> just ONE computer at a time, check "browstat status" on EACH computer after each
>> >> >> >> change, and look for a difference in results (possibly showing from either
>> >> >> >> computer).
>> >> >> >> <http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
>> >> >> >>
>> >> >> >> What personal firewalls and antivirus products do you have?
>> >> >> >> <http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
>> >> >> >>
>> >> >> >> Look for corrupted LSP / Winsock. Run each of the 5 fixes, one at a time, on
>> >> >> >> ONE of your computers, and check for results using "browstat status" run on EACH
>> >> >> >> computer.
>> >> >> >> <http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
>> >> >> >> # LSP-Fix.
>> >> >> >> # WinsockFix
>> >> >> >> # WinsockXPFix
>> >> >> >> # Do you have SP2, or pre-SP2? Do the appropriate Windows native fix.
>> >> >> >> # Reset TCP/IP.
>> >> >> >>
>> >> >> >> Once you get results from updating ONE computer, try the same fix on a second
>> >> >> >> computer, and observe the results.
>> >> >>
>> >> >> >help.
>> >> >> >tried all of these fixes and still nothing.
>> >> >> >hired someone local to come over and fix this and she said it was the router
>> >> >> >which i believe is incorrect.
>> >> >> >ready to take lives.
>> >> >> >willing to pay for competent help.
>> >> >> >could it be the router?
>> >>
>> >> >thanks so much for your help.
>> >> >i noticed yesterday that I've lost the ability to log into my hospital's
>> >> >secured VPN (i'm an ER physician and do work daily from my home) from the
>> >> >desktop (had worked okay a few days ago) but still can from the laptop. argh.
>> >> >anyway, appreciate your help & patience. will owe you hugely for any input
>> >> >you can give me.
>> >> >thanks again.
>> >> >ouput follows:
>> >>
>> >> <SNIP>
>> >>
>> >> Jon,
>> >>
>> >> Well, you have at least 2 problems to work on.
>> >>
>> >> Firstly, look at Gateway:
>> >>
>> >> "GATEWAY ping gateway"
>> >> Pinging gateway [::1] with 32 bytes of data:
>> >> Reply from ::1: time<1ms
>> >>
>> >> "GATEWAY ping LAPTOP"
>> >> Pinging LAPTOP [192.168.1.103] with 32 bytes of data:
>> >>
>> >> That almost has to be LSP / Winsock corruption.
>> >> <http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
>> >>
>> >> Or look at the Hosts and LMHosts files on Gateway (in
>> >> "C:\WINDOWS\system32\drivers\etc") for odd entries.
>> >>
>> >> Second, look at Laptop. Neither Gateway nor Basement can get anything from "Net
>> >> View", either against its name or IP address. Is Laptop using Guest
>> >> authentication? If so, check the restrictanonymous setting.
>> >> <http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Guest>
>> >> Next, check Laptop for a firewall problem.
>> >> <http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
>> >>
>> >> Also, what's with the IP address for laptop? The original IPConfig showed it at
>> >> ....101. You changed it in CDiag to ...104.
>> >>
>> >> Let's see if any of those suggestions makes any improvement.
>>
>> >how do i look at the Hosts and LMHosts files on Gateway (in
>> >> "C:\WINDOWS\system32\drivers\etc") for odd entries?
>> >have seen that before but didn't know what it meant.
>> >will try the other stuff and get back with you.
>> >thanks again-
>>
>> Jon,
>>
>> Hosts and LMHosts are local, fixed name resolution caches on your computer,
>> invented before the concept of DNS. Their contents may cause the computer to
>> ignore use of dynamic name resolution like DNS, name broadcast, and / or WINS.
>> <http://nitecruzr.blogspot.com/2005/07/local-name-and-address-resolution-on.html>
>>
>> Laptop should have an IP address of 192.168.1.104 (per your change), but if
>> there was, for instance, an entry:
>> "192.168.1.103 Laptop" (less the "")
>> in either Hosts or LMHosts on Gateway, that would cause the discrepancy in the
>> way it appears to be addressing Laptop.
>>
>> Gateway appearing to resolve its own IP address to "::1", on the other hand, is
>> either a corruption problem, or a remnant of IPV6. Yet I saw no sign of IPV6 in
>> the IPConfig for Gateway. If there was an entry:
>> "::1 Gateway" (less the "")
>> in either Hosts or LMHosts on Gateway, that would also cause this address
>> resolution anomaly.
>>
>> You can open either file using Notepad.

>well.
>this is interesting.
>ran the tcp/ip reset.
>also switched the ethernet cable to a difgferent socket on the router for
>the laptop as it was showing intermittently connecting & disconnecting on the
>connectoid in the system tray on the laptop.
>now:
>
>laptop sees basement
>desktop sees basement.
>desktop & laptop don't see each other.
>desktop still cannot access hospital vpn over the internet (using smartpass)
>though the laptop can.
>alkmost like something on the desktop is blocking the smartpass vpn access &
>the network/laptop connection.
>strange, huh?
>maybe it's the router, but that doesn't seem to make sense either.
>happy 4th...
>
>files-
>hosts:
># Copyright (c) 1993-1999 Microsoft Corp.
>#
># This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
>#
># This file contains the mappings of IP addresses to host names. Each
># entry should be kept on an individual line. The IP address should
># be placed in the first column followed by the corresponding host name.
># The IP address and the host name should be separated by at least one
># space.
>#
># Additionally, comments (such as these) may be inserted on individual
># lines or following the machine name denoted by a '#' symbol.
>#
># For example:
>#
># 102.54.94.97 rhino.acme.com # source server
># 38.25.63.10 x.acme.com # x client host
>
>127.0.0.1 localhost
>
>lmhosts:
># Copyright (c) 1993-1999 Microsoft Corp.
>#
># This is a sample LMHOSTS file used by the Microsoft TCP/IP for Windows.
>#
># This file contains the mappings of IP addresses to computernames
># (NetBIOS) names. Each entry should be kept on an individual line.
># The IP address should be placed in the first column followed by the
># corresponding computername. The address and the computername
># should be separated by at least one space or tab. The "#" character
># is generally used to denote the start of a comment (see the exceptions
># below).
>#
># This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
># files and offers the following extensions:
>#
># #PRE
># #DOM:<domain>
># #INCLUDE <filename>
># #BEGIN_ALTERNATE
># #END_ALTERNATE
># \0xnn (non-printing character support)
>#
># Following any entry in the file with the characters "#PRE" will cause
># the entry to be preloaded into the name cache. By default, entries are
># not preloaded, but are parsed only after dynamic name resolution fails.
>#
># Following an entry with the "#DOM:<domain>" tag will associate the
># entry with the domain specified by <domain>. This affects how the
># browser and logon services behave in TCP/IP environments. To preload
># the host name associated with #DOM entry, it is necessary to also add a
># #PRE to the line. The <domain> is always preloaded although it will not
># be shown when the name cache is viewed.
>#
># Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)
># software to seek the specified <filename> and parse it as if it were
># local. <filename> is generally a UNC-based name, allowing a
># centralized lmhosts file to be maintained on a server.
># It is ALWAYS necessary to provide a mapping for the IP address of the
># server prior to the #INCLUDE. This mapping must use the #PRE directive.
># In addtion the share "public" in the example below must be in the
># LanManServer list of "NullSessionShares" in order for client machines to
># be able to read the lmhosts file successfully. This key is under
>#
>\machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares
># in the registry. Simply add "public" to the list found there.
>#
># The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
># statements to be grouped together. Any single successful include
># will cause the group to succeed.
>#
># Finally, non-printing characters can be embedded in mappings by
># first surrounding the NetBIOS name in quotations, then using the
># \0xnn notation to specify a hex value for a non-printing character.
>#
># The following example illustrates all of these extensions:
>#
># 102.54.94.97 rhino #PRE #DOM:networking #net group's DC
># 102.54.94.102 "appname \0x14" #special app server
># 102.54.94.123 popular #PRE #source server
># 102.54.94.117 localsrv #PRE #needed for the include
>#
># #BEGIN_ALTERNATE
># #INCLUDE \\localsrv\public\lmhosts
># #INCLUDE \\rhino\public\lmhosts
># #END_ALTERNATE
>#
># In the above example, the "appname" server contains a special
># character in its name, the "popular" and "localsrv" server names are
># preloaded, and the "rhino" server name is specified so it can be used
># to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
># system is unavailable.
>#
># Note that the whole file is parsed including comments on each lookup,
># so keeping the number of comments to a minimum will improve performance.
># Therefore it is not advisable to simply add lmhosts file entries onto the
># end of this file.

Jon,

Well those two files (Hosts / LMHosts) look empty. Did you verify the registry
setting is correct (I added to the article a bit since the first posting)?
<http://nitecruzr.blogspot.com/2005/07/local-name-and-address-resolution-on.html>

Regarding the VPN / Firewall issue, that's come up here before. Steve Winograd,
if my memory serves me, provided some guidance about that issue. Do a search on
"steve vpn firewall" from the "Search this group" button here:
<http://groups-beta.google.com/group/microsoft.public.windowsxp.network_web/>

I wish you had done the TCP/IP reset (on which computer?) OR switched router
ports, but not both. Now, you need to rerun CDiag on all 3 computers, but
please update the IP addresses from "ipconfig" on each computer first. CDiag
will give us an idea what's improved, and should indicate what remains to be
done.

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