File Sharing breaks while "in use"

L

lurker

Consider a home network with two PCs connected to a linksys router.
1) Windows XP Home and
2) Windows 2000 PRO

Both have been updated with all critical updates.

All has been well for several months. On Windows XP I use Quicken and
FrontPage 2000 with their data files on Windows 2000 File Shares.

Several (many?) weeks ago, I would go to bed with all working, and the
next morning, the Windows XP machine could no longer use (or create new)
shares.

After many frustrating weeks, I have observed the network connection
fails at any time of day, even if in use. There are no entries in
either system's Event Viewer.

Ping between the two machines works in both directions.
Net use from Windows 2000 to Windows XP works fine. It does not work
for XP => 2000. Net use produces error message
System Error 53. Network not found.

Rebooting the Windows 2000 machine fixes the problem.

I am looking for suggestions on what tools, procedures to use to
troubleshoot the problem.

King-daddy
 
C

Chuck

Consider a home network with two PCs connected to a linksys router.
1) Windows XP Home and
2) Windows 2000 PRO

Both have been updated with all critical updates.

All has been well for several months. On Windows XP I use Quicken and
FrontPage 2000 with their data files on Windows 2000 File Shares.

Several (many?) weeks ago, I would go to bed with all working, and the
next morning, the Windows XP machine could no longer use (or create new)
shares.

After many frustrating weeks, I have observed the network connection
fails at any time of day, even if in use. There are no entries in
either system's Event Viewer.

Ping between the two machines works in both directions.
Net use from Windows 2000 to Windows XP works fine. It does not work
for XP => 2000. Net use produces error message
System Error 53. Network not found.

Rebooting the Windows 2000 machine fixes the problem.

I am looking for suggestions on what tools, procedures to use to
troubleshoot the problem.

King-daddy

The next time you observe the problem, look at "browstat status", "ipconfig
/all", "net config server", and "net config workstation", from each computer.
Read this article, and linked articles, and follow instructions precisely
(download browstat!):
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

Look at each computer, and the power setting on the network adapter.
<http://nitecruzr.blogspot.com/2005/06/does-your-computer-lose-network.html>
http://nitecruzr.blogspot.com/2005/06/does-your-computer-lose-network.html
 
L

lurcer

Chuck said:
The next time you observe the problem, look at "browstat status", "ipconfig
/all", "net config server", and "net config workstation", from each computer.
Read this article, and linked articles, and follow instructions precisely
(download browstat!):
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

Look at each computer, and the power setting on the network adapter.
<http://nitecruzr.blogspot.com/2005/06/does-your-computer-lose-network.html>
http://nitecruzr.blogspot.com/2005/06/does-your-computer-lose-network.html
Don't be confused by two different user names. my regular earthlink.net
mirror is down now and I am a different name on that one.

I am enjoying learning so much useful information from your very fine
references. Well done!

Neither computer adapter has a power setting.

I no longer am using DHCP (simplifies debug)

I have been through two failures since starting this thread, but have
not saved the data that I observed. I am doing that now.

My current debug posture is that the problem is NOT a Computer Browser
issue. I lament that I cannot find any logs or event viewer that have
an exception posted. PING in both directions never breaks.

I have seen two things cause the error code 53 (after the failure has
occurred.

1) "Network not found" meaning the XP system no longer can find the
Windows 2000 system it was just talking to.

2) Can't remote access the registry (by BROWSTAT)

LSP is not corrupted.

I will post more as I collect the data.

king-daddy
 
C

Chuck

Don't be confused by two different user names. my regular earthlink.net
mirror is down now and I am a different name on that one.

I am enjoying learning so much useful information from your very fine
references. Well done!

Neither computer adapter has a power setting.

I no longer am using DHCP (simplifies debug)

I have been through two failures since starting this thread, but have
not saved the data that I observed. I am doing that now.

My current debug posture is that the problem is NOT a Computer Browser
issue. I lament that I cannot find any logs or event viewer that have
an exception posted. PING in both directions never breaks.

I have seen two things cause the error code 53 (after the failure has
occurred.

1) "Network not found" meaning the XP system no longer can find the
Windows 2000 system it was just talking to.

2) Can't remote access the registry (by BROWSTAT)

LSP is not corrupted.

I will post more as I collect the data.

king-daddy

Thanks for the note about the user name bit. I now presume that you are
"lurker", "lurcer", and "clackey". And you always sign, internally, as
"king-daddy"?

I don't think that the original problem is browser related. That won't prevent
the browser diagnostics from helping us though. But you'll need to run all
diagnostics on each computer, for it to be truly useful.

The "Can't remote access the registry" bit is normal for XP Home.
<http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html#Error53>
http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html#Error53

This type of investigation is typical detective work - a lot of duplicated
effort, and combing thru clues. But since you don't know what the problem is,
you don't know which clues are essential, so gather all of them please.
 
L

lurker

Chuck said:
Thanks for the note about the user name bit. I now presume that you are
"lurker", "lurcer", and "clackey". And you always sign, internally, as
"king-daddy"?

I don't think that the original problem is browser related. That won't prevent
the browser diagnostics from helping us though. But you'll need to run all
diagnostics on each computer, for it to be truly useful.

The "Can't remote access the registry" bit is normal for XP Home.
<http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html#Error53>
http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html#Error53

This type of investigation is typical detective work - a lot of duplicated
effort, and combing thru clues. But since you don't know what the problem is,
you don't know which clues are essential, so gather all of them please.

DHCP not used. Fixed IP is used
Firewall is shut down on the Windows 2000 machine (Kerio)
Firewall on Windows XP HOME is "Windows Live OneCare"

Windows 2000 MASTER BROWSER named QUEENIE
==========================================
Before failure
==========================================
D:\Shared>IPCONFIG /ALL

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : QUEENIE
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
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-50-2C-A7-BF-59

DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.52
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 207.69.188.186
207.69.188.187
207.69.188.185

D:\Shared>BROWSTAT STATUS


Status for domain KINGDOM on transport
\Device\NetBT_Tcpip_{75FDA3F6-AB58-4C26-BF1D-82F8380759B0}
Browsing is active on domain.
Master browser name is: QUEENIE
Master browser is running build 2195
1 backup servers retrieved from master QUEENIE
\\QUEENIE
There are 2 servers in domain KINGDOM on transport
\Device\NetBT_Tcpip_{75FDA3F6-AB58-4C26-BF1D-82F8380759B0}
There are 1 domains in domain KINGDOM on transport
\Device\NetBT_Tcpip_{75FDA3F6-AB58-4C26-BF1D-82F8380759B0}

==========================================
==========================================
WINDOWS XP HOME named KING-DADDY
==========================================
==========================================
J:\shared>IPCONFIG /ALL

Windows IP Configuration

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

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NETGEAR FA310TX Fast
Ethernet Adapter (NGRPCI)
Physical Address. . . . . . . . . : 00-A0-CC-54-8B-A3
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.51
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 207.69.188.185
207.69.188.187

J:\shared>BROWSTAT STATUS


Status for domain KINGDOM on transport
\Device\NetBT_Tcpip_{EA051C55-D2F3-4A2F-B263-BB3332A5FAF3}
Browsing is active on domain.
Master browser name is: QUEENIE
Master browser is running build 2195
1 backup servers retrieved from master QUEENIE
\\QUEENIE
There are 2 servers in domain KINGDOM on transport
\Device\NetBT_Tcpip_{EA051C55-D2F3-4A2F-B263-BB3332A5FAF3}
There are 1 domains in domain KINGDOM on transport
\Device\NetBT_Tcpip_{EA051C55-D2F3-4A2F-B263-BB3332A5FAF3}
 
L

lurker

Chuck said:
Thanks for the note about the user name bit. I now presume that you are
"lurker", "lurcer", and "clackey". And you always sign, internally, as
"king-daddy"?

I don't think that the original problem is browser related. That won't prevent
the browser diagnostics from helping us though. But you'll need to run all
diagnostics on each computer, for it to be truly useful.

The "Can't remote access the registry" bit is normal for XP Home.
<http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html#Error53>
http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html#Error53

This type of investigation is typical detective work - a lot of duplicated
effort, and combing thru clues. But since you don't know what the problem is,
you don't know which clues are essential, so gather all of them please.

Except for machine KING-DADDY getting RC 53 "Network Not Found" in
response to this command:
NET VIEW 192.168.1.52 /CACHE

Here is the browser status:
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : QUEENIE
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
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-50-2C-A7-BF-59
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.52
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 207.69.188.186
207.69.188.187
207.69.188.185


Status for domain KINGDOM on transport
\Device\NetBT_Tcpip_{75FDA3F6-AB58-4C26-BF1D-82F8380759B0}
Browsing is active on domain.
Master browser name is: QUEENIE
Master browser is running build 2195
1 backup servers retrieved from master QUEENIE
\\QUEENIE
Unable to retrieve server list from QUEENIE: 53

king-daddy
 
C

Chuck

DHCP not used. Fixed IP is used
Firewall is shut down on the Windows 2000 machine (Kerio)
Firewall on Windows XP HOME is "Windows Live OneCare"

<SNIP>

Well, no problems at all are apparent there.
# Both computers on same physical subnet, 192.168.1.0/24.
# Both computers using compatible name resolution (Node types Broadcast and
Unknown are fine).
# Both computers in same domain / workgroup Kingdom, with same master browser
Queenie.

Now, since Queenie is the master browser, you'll not see an "error = 53" in
browstat when accessing the registry. If you're seeing an "error = 53" when the
problem occurs, then King-Daddy is probably electing itself the master browser.

Is NetBT explicitly Enabled on both computers?
<http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html>
http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html

Let's try and enumerate the symptoms methodically.

Take the following code (everything INSIDE the "#####" lines). Please DO NOT
include ANY portion of the "#####" lines. (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 both computers, please, with both computers powered up and online.
Do this both when there is no problem (as a baseline), then later repeat when
there is a problem. Post logs as soon as any are available.

##### Start CDiag Assembled Code

@echo off
set FullTarget1=KING-DADDY 192.168.1.51
set FullTarget2=QUEENIE 192.168.1.52
set FullTarget3=
set FullTarget4=
set FullTargets=%FullTarget1% %FullTarget2% %FullTarget3% %FullTarget4%
set FullTargets=%FullTargets% 127.0.0.1
set PingTargets=www.yahoo.com 66.94.230.32 192.168.1.1
Set Version=V1.40
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% >>c:\cdiag.txt
@echo Full Targets %FullTargets% >>c:\cdiag.txt
@echo Ping Targets %PingTargets% >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Over All Analysis >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Enumerate Shares >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net share >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Adhoc Browser View >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net view >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Full Targets Analysis %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 Analysis %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
 
L

lurker

Chuck said:
<SNIP>

Well, no problems at all are apparent there.
# Both computers on same physical subnet, 192.168.1.0/24.
# Both computers using compatible name resolution (Node types Broadcast and
Unknown are fine).
# Both computers in same domain / workgroup Kingdom, with same master browser
Queenie.

Now, since Queenie is the master browser, you'll not see an "error = 53" in
browstat when accessing the registry. If you're seeing an "error = 53" when the
problem occurs, then King-Daddy is probably electing itself the master browser.

Is NetBT explicitly Enabled on both computers?
<http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html>
http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html

Let's try and enumerate the symptoms methodically.

Take the following code (everything INSIDE the "#####" lines). Please DO NOT
include ANY portion of the "#####" lines. (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 both computers, please, with both computers powered up and online.
Do this both when there is no problem (as a baseline), then later repeat when
there is a problem. Post logs as soon as any are available.

##### Start CDiag Assembled Code

@echo off
set FullTarget1=KING-DADDY 192.168.1.51
set FullTarget2=QUEENIE 192.168.1.52
set FullTarget3=
set FullTarget4=
set FullTargets=%FullTarget1% %FullTarget2% %FullTarget3% %FullTarget4%
set FullTargets=%FullTargets% 127.0.0.1
set PingTargets=www.yahoo.com 66.94.230.32 192.168.1.1
Set Version=V1.40
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% >>c:\cdiag.txt
@echo Full Targets %FullTargets% >>c:\cdiag.txt
@echo Ping Targets %PingTargets% >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Over All Analysis >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Enumerate Shares >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net share >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Adhoc Browser View >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net view >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Full Targets Analysis %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 Analysis %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

CDiagnosis V1.40
Start diagnosis for KING-DADDY
Full Targets KING-DADDY 192.168.1.51 QUEENIE 192.168.1.52 127.0.0.1
Ping Targets www.yahoo.com 66.94.230.32 192.168.1.1

Over All Analysis

Enumerate Shares

Share name Resource Remark
-------------------------------------------------------------------------------
print$ C:\WINDOWS\system32\spool\drivers
Printer Drivers

IPC$ Remote IPC

debug J:\clackey\debug
downloads I:\downloads
SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS.WINDOWS\DOCUMENTS

TOOLS J:\TOOLS
clackey LPT1: Spooled Laser Printer

Color Printer
USB001 Spooled Canon S800

The command completed successfully.

Adhoc Browser View
Server Name Remark
-------------------------------------------------------------------------------
\\KING-DADDY king-daddy 51

\\QUEENIE

The command completed successfully.

Full Targets Analysis KING-DADDY 192.168.1.51 QUEENIE 192.168.1.52
127.0.0.1

Target KING-DADDY

"KING-DADDY ping KING-DADDY"

Pinging KING-DADDY [192.168.1.51] with 32 bytes of data:

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

Ping statistics for 192.168.1.51:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"KING-DADDY net view KING-DADDY"

Shared resources at KING-DADDY

king-daddy 51

Share name Type Used as Comment
-------------------------------------------------------------------------------
clackey Print Laser Printer
Color Printer Print Canon S800
debug Disk
downloads Disk
SharedDocs Disk
TOOLS Disk
The command completed successfully.

Target 192.168.1.51

"KING-DADDY ping 192.168.1.51"

Pinging 192.168.1.51 with 32 bytes of data:

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

Ping statistics for 192.168.1.51:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"KING-DADDY net view 192.168.1.51"
Shared resources at 192.168.1.51

king-daddy 51

Share name Type Used as Comment
-------------------------------------------------------------------------------
clackey Print Laser Printer
Color Printer Print Canon S800
debug Disk
downloads Disk
SharedDocs Disk
TOOLS Disk
The command completed successfully.

Target QUEENIE

"KING-DADDY ping QUEENIE"

Pinging QUEENIE [192.168.1.52] with 32 bytes of data:

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

Ping statistics for 192.168.1.52:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"KING-DADDY net view QUEENIE"

Shared resources at QUEENIE

Share name Type Used as Comment
-------------------------------------------------------------------------------
BrotherH Print Brother HL-1440 Dolphin
desktop Disk
downloads Disk
joint Disk X:
mine Disk Dolphind Drive D
PCService Disk
Shared Disk Z: shared files
TOOLS Disk W: Dolphin Tools folder
The command completed successfully.

Target 192.168.1.52
"KING-DADDY ping 192.168.1.52"

Pinging 192.168.1.52 with 32 bytes of data:

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

Ping statistics for 192.168.1.52:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"KING-DADDY net view 192.168.1.52"
Shared resources at 192.168.1.52

Share name Type Used as Comment
-------------------------------------------------------------------------------
BrotherH Print Brother HL-1440 Dolphin
desktop Disk
downloads Disk
joint Disk
mine Disk Dolphind Drive D
PCService Disk
Shared Disk shared files
TOOLS Disk Dolphin Tools folder
The command completed successfully.

Target 127.0.0.1
"KING-DADDY 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

"KING-DADDY net view 127.0.0.1"
Shared resources at 127.0.0.1
king-daddy 51

Share name Type Used as Comment

-------------------------------------------------------------------------------
clackey Print Laser Printer
Color Printer Print Canon S800
debug Disk
downloads Disk
SharedDocs Disk
TOOLS Disk
The command completed successfully.

Ping Targets Analysis www.yahoo.com 66.94.230.32 192.168.1.1
Target www.yahoo.com

"KING-DADDY ping www.yahoo.com"

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

Reply from 68.142.226.51: bytes=32 time=26ms TTL=50
Reply from 68.142.226.51: bytes=32 time=28ms TTL=50
Reply from 68.142.226.51: bytes=32 time=25ms TTL=50
Reply from 68.142.226.51: bytes=32 time=26ms TTL=50

Ping statistics for 68.142.226.51:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 28ms, Average = 26ms


Target 66.94.230.32

"KING-DADDY ping 66.94.230.32"

Pinging 66.94.230.32 with 32 bytes of data:

Reply from 66.94.230.32: bytes=32 time=106ms TTL=46
Reply from 66.94.230.32: bytes=32 time=109ms TTL=47
Reply from 66.94.230.32: bytes=32 time=105ms TTL=47
Reply from 66.94.230.32: bytes=32 time=106ms TTL=46

Ping statistics for 66.94.230.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 105ms, Maximum = 109ms, Average = 106ms

Target 192.168.1.1
"KING-DADDY 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 = 1ms, Average = 0ms

End diagnosis for KING-DADDY
======================================
CDiagnosis V1.40
Start diagnosis for QUEENIE
Full Targets KING-DADDY 192.168.1.51 QUEENIE 192.168.1.52 127.0.0.1
Ping Targets www.yahoo.com 66.94.230.32 192.168.1.1

Over All Analysis

Enumerate Shares


Share name Resource Remark


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

H$ H:\ Default share

IPC$ Remote IPC

D$ D:\ Default share

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

ADMIN$ C:\WINNT Remote Admin

E$ E:\ Default share

desktop D:\desktop
downloads E:\downloads
joint D:\QUICKEN\joint
mine D:\ Dolphind Drive D

PCService D:\QUICKEN\PCService
Shared D:\Shared shared files

TOOLS D:\TOOLS Dolphin Tools folder

BrotherH USB001 Spooled Brother HL-1440 Dolphin

The command completed successfully.

Adhoc Browser View

Server Name Remark
-------------------------------------------------------------------------------
\\KING-DADDY king-daddy 51

\\QUEENIE

The command completed successfully.

Full Targets Analysis KING-DADDY 192.168.1.51 QUEENIE 192.168.1.52
127.0.0.1

Target KING-DADDY

"QUEENIE ping KING-DADDY"

Pinging KING-DADDY [192.168.1.51] with 32 bytes of data:

Reply from 192.168.1.51: bytes=32 time<10ms TTL=128
Reply from 192.168.1.51: bytes=32 time<10ms TTL=128
Reply from 192.168.1.51: bytes=32 time<10ms TTL=128
Reply from 192.168.1.51: bytes=32 time<10ms TTL=128

Ping statistics for 192.168.1.51:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms


"QUEENIE net view KING-DADDY"

Shared resources at KING-DADDY

king-daddy 51

Share name Type Used as Comment


-------------------------------------------------------------------------------
clackey Print Laser Printer

Color Printer
Print Canon S800

debug Disk

downloads Disk

SharedDocs Disk

TOOLS Disk

The command completed successfull
Target 192.168.1.51

"QUEENIE ping 192.168.1.51"

Pinging 192.168.1.51 with 32 bytes of data:

Reply from 192.168.1.51: bytes=32 time<10ms TTL=128
Reply from 192.168.1.51: bytes=32 time<10ms TTL=128
Reply from 192.168.1.51: bytes=32 time<10ms TTL=128
Reply from 192.168.1.51: bytes=32 time<10ms TTL=128

Ping statistics for 192.168.1.51:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"QUEENIE net view 192.168.1.51"

Shared resources at 192.168.1.51

king-daddy 51

Share name Type Used as Comment
-------------------------------------------------------------------------------
clackey Print Laser Printer

Color Printer
Print Canon S800

debug Disk

downloads Disk

SharedDocs Disk

TOOLS Disk

The command completed successfully.

Target QUEENIE

"QUEENIE ping QUEENIE"


Pinging QUEENIE [192.168.1.52] with 32 bytes of data:

Reply from 192.168.1.52: bytes=32 time<10ms TTL=128
Reply from 192.168.1.52: bytes=32 time<10ms TTL=128
Reply from 192.168.1.52: bytes=32 time<10ms TTL=128
Reply from 192.168.1.52: bytes=32 time<10ms TTL=128

Ping statistics for 192.168.1.52:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"QUEENIE net view QUEENIE"

Shared resources at QUEENIE

Share name Type Used as Comment
-------------------------------------------------------------------------------
BrotherH Print Brother HL-1440 Dolphin

desktop Disk

downloads Disk

joint Disk

mine Disk Dolphind Drive D

PCService Disk

Shared Disk shared files

TOOLS Disk Dolphin Tools folder

The command completed successfully.

Target 192.168.1.52

"QUEENIE ping 192.168.1.52"

Pinging 192.168.1.52 with 32 bytes of data:

Reply from 192.168.1.52: bytes=32 time<10ms TTL=128
Reply from 192.168.1.52: bytes=32 time<10ms TTL=128
Reply from 192.168.1.52: bytes=32 time<10ms TTL=128
Reply from 192.168.1.52: bytes=32 time<10ms TTL=128

Ping statistics for 192.168.1.52:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"QUEENIE net view 192.168.1.52"

Shared resources at 192.168.1.52

Share name Type Used as Comment
-------------------------------------------------------------------------------
BrotherH Print Brother HL-1440 Dolphin

desktop Disk

downloads Disk

joint Disk

mine Disk Dolphind Drive D

PCService Disk

Shared Disk shared files

TOOLS Disk Dolphin Tools folder

The command completed successfully.

Target 127.0.0.1

"QUEENIE ping 127.0.0.1"

Pinging 127.0.0.1 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms 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

"QUEENIE net view 127.0.0.1"

Shared resources at 127.0.0.1

Share name Type Used as Comment
-------------------------------------------------------------------------------
BrotherH Print Brother HL-1440 Dolphin

desktop Disk

downloads Disk

joint Disk

mine Disk Dolphind Drive D

PCService Disk

Shared Disk shared files

TOOLS Disk Dolphin Tools folder

The command completed successfully.

Ping Targets Analysis www.yahoo.com 66.94.230.32 192.168.1.1

Target www.yahoo.com

"QUEENIE ping www.yahoo.com"

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

Reply from 68.142.226.39: bytes=32 time=22ms TTL=50
Reply from 68.142.226.39: bytes=32 time=21ms TTL=49
Reply from 68.142.226.39: bytes=32 time=30ms TTL=49
Reply from 68.142.226.39: bytes=32 time=21ms TTL=50

Ping statistics for 68.142.226.39:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 30ms, Average = 23ms

Target 66.94.230.32

"QUEENIE ping 66.94.230.32"

Pinging 66.94.230.32 with 32 bytes of data:

Reply from 66.94.230.32: bytes=32 time=107ms TTL=47
Reply from 66.94.230.32: bytes=32 time=105ms TTL=47
Reply from 66.94.230.32: bytes=32 time=106ms TTL=46
Reply from 66.94.230.32: bytes=32 time=124ms TTL=47

Ping statistics for 66.94.230.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 105ms, Maximum = 124ms, Average = 110ms

Target 192.168.1.1

"QUEENIE ping 192.168.1.1"

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time<10ms TTL=64
Reply from 192.168.1.1: bytes=32 time<10ms TTL=64
Reply from 192.168.1.1: bytes=32 time<10ms 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 = 2ms, Average = 0ms

End diagnosis for QUEENIE
 
L

lurker

Chuck said:
<SNIP>

Well, no problems at all are apparent there.
# Both computers on same physical subnet, 192.168.1.0/24.
# Both computers using compatible name resolution (Node types Broadcast and
Unknown are fine).
# Both computers in same domain / workgroup Kingdom, with same master browser
Queenie.

Now, since Queenie is the master browser, you'll not see an "error = 53" in
browstat when accessing the registry. If you're seeing an "error = 53" when the
problem occurs, then King-Daddy is probably electing itself the master browser.

Is NetBT explicitly Enabled on both computers?
<http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html>
http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html

Let's try and enumerate the symptoms methodically.

Take the following code (everything INSIDE the "#####" lines). Please DO NOT
include ANY portion of the "#####" lines. (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 both computers, please, with both computers powered up and online.
Do this both when there is no problem (as a baseline), then later repeat when
there is a problem. Post logs as soon as any are available.

##### Start CDiag Assembled Code
[clip]
WOW!
Into 2nd day without a failure!

I am unsure if I should be happy, or disappointed (from a techie point
of view.) It's as if the systems know "the big gun" is watching. You
know, "the kids behave when Daddy is watching."

The only thing I recall changing (right before the request to install
CDIAG was the significant work effort I put into cleaning up My Network
Places and Network Neighborhood:

I had a significant number of shares on both systems, both local and my
web sites. I cleaned them up so as to have the useful bare minimum (for
now) on each system. Then I entered the dialog about "how to remove the
objects from the network neighborhood / listing. By this time, I had
renamed my computers and the workgroup. Besides objects in the list
that no longer existed (Yes, I waited about an hour to see of the
Browser would clean them up), those unwanted objects displayed Computer:
Unknown. I sorted on "Computer" column.

....I used standard Windows protocol to mark the ones with Computer =
"Unknown" and deleted them.

It was after that cleanup when I received the note about CDIAG (Thanks
for that. There are useful examples in CDIAG that will be helpful to me
in other tasks!)

After collecting the Baseline data and posting same, I have not had a
failure. Actually, I am still hoping for one. I will post information
when it happens. If it is too untimely, I will put a notice in a new
thread with substantial information in it.
 
C

Chuck

Chuck said:
<SNIP>

Well, no problems at all are apparent there.
# Both computers on same physical subnet, 192.168.1.0/24.
# Both computers using compatible name resolution (Node types Broadcast and
Unknown are fine).
# Both computers in same domain / workgroup Kingdom, with same master browser
Queenie.

Now, since Queenie is the master browser, you'll not see an "error = 53" in
browstat when accessing the registry. If you're seeing an "error = 53" when the
problem occurs, then King-Daddy is probably electing itself the master browser.

Is NetBT explicitly Enabled on both computers?
<http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html>
http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html

Let's try and enumerate the symptoms methodically.

Take the following code (everything INSIDE the "#####" lines). Please DO NOT
include ANY portion of the "#####" lines. (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 both computers, please, with both computers powered up and online.
Do this both when there is no problem (as a baseline), then later repeat when
there is a problem. Post logs as soon as any are available.

##### Start CDiag Assembled Code
[clip]
WOW!
Into 2nd day without a failure!

I am unsure if I should be happy, or disappointed (from a techie point
of view.) It's as if the systems know "the big gun" is watching. You
know, "the kids behave when Daddy is watching."

The only thing I recall changing (right before the request to install
CDIAG was the significant work effort I put into cleaning up My Network
Places and Network Neighborhood:

I had a significant number of shares on both systems, both local and my
web sites. I cleaned them up so as to have the useful bare minimum (for
now) on each system. Then I entered the dialog about "how to remove the
objects from the network neighborhood / listing. By this time, I had
renamed my computers and the workgroup. Besides objects in the list
that no longer existed (Yes, I waited about an hour to see of the
Browser would clean them up), those unwanted objects displayed Computer:
Unknown. I sorted on "Computer" column.

...I used standard Windows protocol to mark the ones with Computer =
"Unknown" and deleted them.

It was after that cleanup when I received the note about CDIAG (Thanks
for that. There are useful examples in CDIAG that will be helpful to me
in other tasks!)

After collecting the Baseline data and posting same, I have not had a
failure. Actually, I am still hoping for one. I will post information
when it happens. If it is too untimely, I will put a notice in a new
thread with substantial information in it.

I was sort of wondering what was up with you, last night. Thanks for posting.

Don't you love computers? %-)

Just ping this thread every few days, let us know you're still there, and it
will stay active. I'll keep watching it.
 
L

lurker

lurker said:
Chuck said:
Chuck wrote:
On Wed, 31 May 2006 10:23:06 -0400, lurcer

Chuck wrote:
On Tue, 30 May 2006 13:09:29 GMT, lurker
<"[remove]king-daddy"@earthlink.net>
wrote:

Consider a home network with two PCs connected to a linksys router.
1) Windows XP Home and
2) Windows 2000 PRO

Both have been updated with all critical updates.

All has been well for several months. On Windows XP I use
Quicken and FrontPage 2000 with their data files on Windows 2000
File Shares.

Several (many?) weeks ago, I would go to bed with all working,
and the next morning, the Windows XP machine could no longer use
(or create new) shares.

After many frustrating weeks, I have observed the network
connection fails at any time of day, even if in use. There are
no entries in either system's Event Viewer.

Ping between the two machines works in both directions.
Net use from Windows 2000 to Windows XP works fine. It does not
work for XP => 2000. Net use produces error message
System Error 53. Network not found.

Rebooting the Windows 2000 machine fixes the problem.

I am looking for suggestions on what tools, procedures to use to
troubleshoot the problem.

King-daddy
The next time you observe the problem, look at "browstat status",
"ipconfig
/all", "net config server", and "net config workstation", from
each computer.
Read this article, and linked articles, and follow instructions
precisely
(download browstat!):
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>

http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp


Look at each computer, and the power setting on the network adapter.
<http://nitecruzr.blogspot.com/2005/06/does-your-computer-lose-network.html>

http://nitecruzr.blogspot.com/2005/06/does-your-computer-lose-network.html


Don't be confused by two different user names. my regular
earthlink.net mirror is down now and I am a different name on that
one.

I am enjoying learning so much useful information from your very
fine references. Well done!

Neither computer adapter has a power setting.

I no longer am using DHCP (simplifies debug)

I have been through two failures since starting this thread, but
have not saved the data that I observed. I am doing that now.

My current debug posture is that the problem is NOT a Computer
Browser issue. I lament that I cannot find any logs or event
viewer that have an exception posted. PING in both directions
never breaks.

I have seen two things cause the error code 53 (after the failure
has occurred.

1) "Network not found" meaning the XP system no longer can find the
Windows 2000 system it was just talking to.

2) Can't remote access the registry (by BROWSTAT)

LSP is not corrupted.

I will post more as I collect the data.

king-daddy
Thanks for the note about the user name bit. I now presume that you
are
"lurker", "lurcer", and "clackey". And you always sign, internally, as
"king-daddy"?

I don't think that the original problem is browser related. That
won't prevent
the browser diagnostics from helping us though. But you'll need to
run all
diagnostics on each computer, for it to be truly useful.

The "Can't remote access the registry" bit is normal for XP Home.
<http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html#Error53>

http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html#Error53


This type of investigation is typical detective work - a lot of
duplicated
effort, and combing thru clues. But since you don't know what the
problem is,
you don't know which clues are essential, so gather all of them please.

DHCP not used. Fixed IP is used
Firewall is shut down on the Windows 2000 machine (Kerio)
Firewall on Windows XP HOME is "Windows Live OneCare"

<SNIP>

Well, no problems at all are apparent there.
# Both computers on same physical subnet, 192.168.1.0/24.
# Both computers using compatible name resolution (Node types
Broadcast and
Unknown are fine).
# Both computers in same domain / workgroup Kingdom, with same master
browser
Queenie.

Now, since Queenie is the master browser, you'll not see an "error =
53" in
browstat when accessing the registry. If you're seeing an "error =
53" when the
problem occurs, then King-Daddy is probably electing itself the master
browser.

Is NetBT explicitly Enabled on both computers?
<http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html>
http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html

Let's try and enumerate the symptoms methodically.

Take the following code (everything INSIDE the "#####" lines). Please
DO NOT
include ANY portion of the "#####" lines. (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 both computers, please, with both computers powered up
and online.
Do this both when there is no problem (as a baseline), then later
repeat when
there is a problem. Post logs as soon as any are available.

##### Start CDiag Assembled Code

@echo off
set FullTarget1=KING-DADDY 192.168.1.51
set FullTarget2=QUEENIE 192.168.1.52
set FullTarget3=
set FullTarget4=
set FullTargets=%FullTarget1% %FullTarget2% %FullTarget3% %FullTarget4%
set FullTargets=%FullTargets% 127.0.0.1
set PingTargets=www.yahoo.com 66.94.230.32 192.168.1.1
Set Version=V1.40
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% >>c:\cdiag.txt
@echo Full Targets %FullTargets% >>c:\cdiag.txt
@echo Ping Targets %PingTargets% >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Over All Analysis >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Enumerate Shares >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net share >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Adhoc Browser View >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net view >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Full Targets Analysis %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 Analysis %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

CDiagnosis V1.40
Start diagnosis for KING-DADDY
Full Targets KING-DADDY 192.168.1.51 QUEENIE 192.168.1.52 127.0.0.1
Ping Targets www.yahoo.com 66.94.230.32 192.168.1.1

Over All Analysis

Enumerate Shares

Share name Resource Remark
-------------------------------------------------------------------------------

print$ C:\WINDOWS\system32\spool\drivers
Printer Drivers
IPC$ Remote IPC
debug J:\clackey\debug
downloads I:\downloads
SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS.WINDOWS\DOCUMENTS

TOOLS J:\TOOLS
clackey LPT1: Spooled Laser Printer
Color Printer
USB001 Spooled Canon S800
The command completed successfully.

Adhoc Browser View
Server Name Remark
-------------------------------------------------------------------------------

\\KING-DADDY king-daddy 51
\\QUEENIE
The command completed successfully.

Full Targets Analysis KING-DADDY 192.168.1.51 QUEENIE 192.168.1.52
127.0.0.1

Target KING-DADDY

"KING-DADDY ping KING-DADDY"

Pinging KING-DADDY [192.168.1.51] with 32 bytes of data:

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

Ping statistics for 192.168.1.51:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"KING-DADDY net view KING-DADDY"

Shared resources at KING-DADDY

king-daddy 51

Share name Type Used as Comment
-------------------------------------------------------------------------------

clackey Print Laser Printer
Color Printer Print Canon S800
debug Disk
downloads Disk
SharedDocs Disk
TOOLS Disk
The command completed successfully.

Target 192.168.1.51

"KING-DADDY ping 192.168.1.51"

Pinging 192.168.1.51 with 32 bytes of data:

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

Ping statistics for 192.168.1.51:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"KING-DADDY net view 192.168.1.51"
Shared resources at 192.168.1.51

king-daddy 51

Share name Type Used as Comment
-------------------------------------------------------------------------------

clackey Print Laser Printer
Color Printer Print Canon S800
debug Disk
downloads Disk
SharedDocs Disk
TOOLS Disk
The command completed successfully.

Target QUEENIE

"KING-DADDY ping QUEENIE"

Pinging QUEENIE [192.168.1.52] with 32 bytes of data:

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

Ping statistics for 192.168.1.52:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"KING-DADDY net view QUEENIE"

Shared resources at QUEENIE

Share name Type Used as Comment
-------------------------------------------------------------------------------

BrotherH Print Brother HL-1440 Dolphin
desktop Disk
downloads Disk
joint Disk X:
mine Disk Dolphind Drive D
PCService Disk
Shared Disk Z: shared files
TOOLS Disk W: Dolphin Tools folder
The command completed successfully.

Target 192.168.1.52
"KING-DADDY ping 192.168.1.52"

Pinging 192.168.1.52 with 32 bytes of data:

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

Ping statistics for 192.168.1.52:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"KING-DADDY net view 192.168.1.52"
Shared resources at 192.168.1.52

Share name Type Used as Comment
-------------------------------------------------------------------------------

BrotherH Print Brother HL-1440 Dolphin
desktop Disk
downloads Disk
joint Disk
mine Disk Dolphind Drive D
PCService Disk
Shared Disk shared files
TOOLS Disk Dolphin Tools folder
The command completed successfully.

Target 127.0.0.1
"KING-DADDY 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

"KING-DADDY net view 127.0.0.1"
Shared resources at 127.0.0.1
king-daddy 51

Share name Type Used as Comment

-------------------------------------------------------------------------------

clackey Print Laser Printer
Color Printer Print Canon S800
debug Disk
downloads Disk
SharedDocs Disk
TOOLS Disk
The command completed successfully.

Ping Targets Analysis www.yahoo.com 66.94.230.32 192.168.1.1
Target www.yahoo.com

"KING-DADDY ping www.yahoo.com"

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

Reply from 68.142.226.51: bytes=32 time=26ms TTL=50
Reply from 68.142.226.51: bytes=32 time=28ms TTL=50
Reply from 68.142.226.51: bytes=32 time=25ms TTL=50
Reply from 68.142.226.51: bytes=32 time=26ms TTL=50

Ping statistics for 68.142.226.51:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 28ms, Average = 26ms


Target 66.94.230.32

"KING-DADDY ping 66.94.230.32"

Pinging 66.94.230.32 with 32 bytes of data:

Reply from 66.94.230.32: bytes=32 time=106ms TTL=46
Reply from 66.94.230.32: bytes=32 time=109ms TTL=47
Reply from 66.94.230.32: bytes=32 time=105ms TTL=47
Reply from 66.94.230.32: bytes=32 time=106ms TTL=46

Ping statistics for 66.94.230.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 105ms, Maximum = 109ms, Average = 106ms

Target 192.168.1.1
"KING-DADDY 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 = 1ms, Average = 0ms

End diagnosis for KING-DADDY
======================================
CDiagnosis V1.40
Start diagnosis for QUEENIE
Full Targets KING-DADDY 192.168.1.51 QUEENIE 192.168.1.52 127.0.0.1
Ping Targets www.yahoo.com 66.94.230.32 192.168.1.1

Over All Analysis

Enumerate Shares


Share name Resource Remark


-------------------------------------------------------------------------------

C$ C:\ Default share
H$ H:\ Default share
IPC$ Remote IPC
D$ D:\ Default share
print$ C:\WINNT\system32\spool\drivers Printer Drivers
ADMIN$ C:\WINNT Remote Admin
E$ E:\ Default share
desktop D:\desktop
downloads E:\downloads
joint D:\QUICKEN\joint
mine D:\ Dolphind Drive D
PCService D:\QUICKEN\PCService
Shared D:\Shared shared files
TOOLS D:\TOOLS Dolphin Tools folder
BrotherH USB001 Spooled Brother HL-1440 Dolphin
The command completed successfully.

Adhoc Browser View

Server Name Remark
-------------------------------------------------------------------------------

\\KING-DADDY king-daddy 51
\\QUEENIE
The command completed successfully.

Full Targets Analysis KING-DADDY 192.168.1.51 QUEENIE 192.168.1.52
127.0.0.1

Target KING-DADDY

"QUEENIE ping KING-DADDY"

Pinging KING-DADDY [192.168.1.51] with 32 bytes of data:

Reply from 192.168.1.51: bytes=32 time<10ms TTL=128
Reply from 192.168.1.51: bytes=32 time<10ms TTL=128
Reply from 192.168.1.51: bytes=32 time<10ms TTL=128
Reply from 192.168.1.51: bytes=32 time<10ms TTL=128

Ping statistics for 192.168.1.51:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms


"QUEENIE net view KING-DADDY"

Shared resources at KING-DADDY

king-daddy 51

Share name Type Used as Comment


-------------------------------------------------------------------------------

clackey Print Laser Printer
Color Printer
Print Canon S800
debug Disk
downloads Disk
SharedDocs Disk
TOOLS Disk
The command completed successfull
Target 192.168.1.51

"QUEENIE ping 192.168.1.51"

Pinging 192.168.1.51 with 32 bytes of data:

Reply from 192.168.1.51: bytes=32 time<10ms TTL=128
Reply from 192.168.1.51: bytes=32 time<10ms TTL=128
Reply from 192.168.1.51: bytes=32 time<10ms TTL=128
Reply from 192.168.1.51: bytes=32 time<10ms TTL=128

Ping statistics for 192.168.1.51:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"QUEENIE net view 192.168.1.51"

Shared resources at 192.168.1.51

king-daddy 51

Share name Type Used as Comment
-------------------------------------------------------------------------------

clackey Print Laser Printer
Color Printer
Print Canon S800
debug Disk
downloads Disk
SharedDocs Disk
TOOLS Disk
The command completed successfully.

Target QUEENIE

"QUEENIE ping QUEENIE"


Pinging QUEENIE [192.168.1.52] with 32 bytes of data:

Reply from 192.168.1.52: bytes=32 time<10ms TTL=128
Reply from 192.168.1.52: bytes=32 time<10ms TTL=128
Reply from 192.168.1.52: bytes=32 time<10ms TTL=128
Reply from 192.168.1.52: bytes=32 time<10ms TTL=128

Ping statistics for 192.168.1.52:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"QUEENIE net view QUEENIE"

Shared resources at QUEENIE

Share name Type Used as Comment
-------------------------------------------------------------------------------

BrotherH Print Brother HL-1440 Dolphin
desktop Disk
downloads Disk
joint Disk
mine Disk Dolphind Drive D
PCService Disk
Shared Disk shared files
TOOLS Disk Dolphin Tools folder
The command completed successfully.

Target 192.168.1.52

"QUEENIE ping 192.168.1.52"

Pinging 192.168.1.52 with 32 bytes of data:

Reply from 192.168.1.52: bytes=32 time<10ms TTL=128
Reply from 192.168.1.52: bytes=32 time<10ms TTL=128
Reply from 192.168.1.52: bytes=32 time<10ms TTL=128
Reply from 192.168.1.52: bytes=32 time<10ms TTL=128

Ping statistics for 192.168.1.52:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"QUEENIE net view 192.168.1.52"

Shared resources at 192.168.1.52

Share name Type Used as Comment
-------------------------------------------------------------------------------

BrotherH Print Brother HL-1440 Dolphin
desktop Disk
downloads Disk
joint Disk
mine Disk Dolphind Drive D
PCService Disk
Shared Disk shared files
TOOLS Disk Dolphin Tools folder
The command completed successfully.

Target 127.0.0.1

"QUEENIE ping 127.0.0.1"

Pinging 127.0.0.1 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms 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

"QUEENIE net view 127.0.0.1"

Shared resources at 127.0.0.1

Share name Type Used as Comment
-------------------------------------------------------------------------------

BrotherH Print Brother HL-1440 Dolphin
desktop Disk
downloads Disk
joint Disk
mine Disk Dolphind Drive D
PCService Disk
Shared Disk shared files
TOOLS Disk Dolphin Tools folder
The command completed successfully.

Ping Targets Analysis www.yahoo.com 66.94.230.32 192.168.1.1

Target www.yahoo.com

"QUEENIE ping www.yahoo.com"

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

Reply from 68.142.226.39: bytes=32 time=22ms TTL=50
Reply from 68.142.226.39: bytes=32 time=21ms TTL=49
Reply from 68.142.226.39: bytes=32 time=30ms TTL=49
Reply from 68.142.226.39: bytes=32 time=21ms TTL=50

Ping statistics for 68.142.226.39:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 30ms, Average = 23ms

Target 66.94.230.32

"QUEENIE ping 66.94.230.32"

Pinging 66.94.230.32 with 32 bytes of data:

Reply from 66.94.230.32: bytes=32 time=107ms TTL=47
Reply from 66.94.230.32: bytes=32 time=105ms TTL=47
Reply from 66.94.230.32: bytes=32 time=106ms TTL=46
Reply from 66.94.230.32: bytes=32 time=124ms TTL=47

Ping statistics for 66.94.230.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 105ms, Maximum = 124ms, Average = 110ms

Target 192.168.1.1

"QUEENIE ping 192.168.1.1"

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time<10ms TTL=64
Reply from 192.168.1.1: bytes=32 time<10ms TTL=64
Reply from 192.168.1.1: bytes=32 time<10ms 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 = 2ms, Average = 0ms

End diagnosis for QUEENIE
================================+
KING-DADDY CDAIG FAILED, RESULTS|
================================+

================================+
QUEENIE CDAIG FAILED, RESULTS |
================================+
To eliminate the formating text problem,
see the result here:
http://rpchc.com/Library/

king-daddy
 
C

Chuck

================================+
KING-DADDY CDAIG FAILED, RESULTS|
================================+

================================+
QUEENIE CDAIG FAILED, RESULTS |
================================+
To eliminate the formating text problem,
see the result here:
http://rpchc.com/Library/

Carl,

Is NetBT Explicitly ENABLED on all computers?
<http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html>
http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html

What is Prince?
Server Name Remark
-------------------------------------------------------------------------------
\\KING-DADDY king-daddy 51
\\PRINCE PRINCE192.168.1.50
\\QUEENIE

Note again how the browser causes problems:
<http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html>
http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html
 
L

lurker

Chuck said:
Carl,

Is NetBT Explicitly ENABLED on all computers?
<http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html>
http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html

What is Prince?
Server Name Remark
-------------------------------------------------------------------------------
\\KING-DADDY king-daddy 51
\\PRINCE PRINCE192.168.1.50
\\QUEENIE

Note again how the browser causes problems:
<http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html>
http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html

PRINCE is a Dual Boot machine
1> Windows XP
2> Windows 2000
...that is usually not powered up. It is used as a "stable environment"
when I am working on customer PC's infected with adware / spyware /worms
and viruses. Often, I pull the customers hard drive and install it as
an additional drive in PRINCE; and scan it.

In PRINCE / Windows XP SP2 I found the Netbios setting to be "Default",
which states if Static IP use NetBios over TCP/IP. KING-DADDDY and
QUEENIE are specific NetBios over TCP/IP.

king-daddy
 
C

Chuck

PRINCE is a Dual Boot machine
1> Windows XP
2> Windows 2000
..that is usually not powered up. It is used as a "stable environment"
when I am working on customer PC's infected with adware / spyware /worms
and viruses. Often, I pull the customers hard drive and install it as
an additional drive in PRINCE; and scan it.

In PRINCE / Windows XP SP2 I found the Netbios setting to be "Default",
which states if Static IP use NetBios over TCP/IP. KING-DADDDY and
QUEENIE are specific NetBios over TCP/IP.

Well, look at Net View from King-Daddy, and then from Queenie. And this was
when you were seeing your failure. I don't think that this was a coincidence.

Did you per chance run "browstat status" from all 3 computers? Please do that
the next time Prince is up.
 
L

lurker

Chuck said:
Well, look at Net View from King-Daddy, and then from Queenie. And this was
when you were seeing your failure. I don't think that this was a coincidence.

Did you per chance run "browstat status" from all 3 computers? Please do that
the next time Prince is up.
FROM KING-DADDY:
C:\>browstat status


Status for domain KINGDOM on transport
\Device\NetBT_Tcpip_{EA051C55-D2F3-4A2F-B263-BB3332A5FAF3}
Browsing is active on domain.
Master browser name is: QUEENIE
Could not connect to registry, error = 53 Unable to determine
build of browser master: 53
Unable to determine server information for browser master: 51
1 backup servers retrieved from master QUEENIE
\\QUEENIE
Unable to retrieve server list from QUEENIE: 51

FROM QUEENIE:
Status for domain KINGDOM on transport
\Device\NetBT_Tcpip_{75FDA3F6-AB58-4C26-BF1D-82F8380759B0}
Browsing is active on domain.
Master browser name is: QUEENIE
Master browser is running build 2195
1 backup servers retrieved from master QUEENIE
\\QUEENIE
Unable to retrieve server list from QUEENIE: 53

FROM PRINCE:
C:\WINDOWS\SYSTEM32>browstat status


Status for domain KINGDOM on transport
\Device\NetBT_Tcpip_{A4A5DC32-3818-42EF-A496-24A58ED1416F}
Browsing is active on domain.
Master browser name is: QUEENIE
Could not connect to registry, error = 53 Unable to determine
build of browser master: 53
Unable to determine server information for browser master: 51
1 backup servers retrieved from master QUEENIE
\\QUEENIE
Unable to retrieve server list from QUEENIE: 51

king-daddy
 
L

lurker

Chuck said:
Well, look at Net View from King-Daddy, and then from Queenie. And this was
when you were seeing your failure. I don't think that this was a coincidence.

Did you per chance run "browstat status" from all 3 computers? Please do that
the next time Prince is up.

Chick, Have you received my previous response regarding PRINCE and
BROWSTAT results.

I have not rebooted QUEENIE. I am trying to preserve the failure until
I hear from you.

king-daddy
 
C

Chuck

Chick, Have you received my previous response regarding PRINCE and
BROWSTAT results.

I have not rebooted QUEENIE. I am trying to preserve the failure until
I hear from you.

king-daddy

Carl,

OK, so Queenie is the Windows 2000 computer? That's the master browser.

Here's an error 51:
Windows cannot find the network path. Verify that the network path is correct
and the destination computer is not busy or turned off. If Windows still cannot
find the network path, contact your network administrator.

And an error 53:
The network path was not found.

The error 53 is very common.
<http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html

The error 51 I have not seen before. Searching http://search.microsoft.com for
"cannot find the network path", I get a couple of interesting articles:
<http://support.microsoft.com/kb/896427>
http://support.microsoft.com/kb/896427
<http://support.microsoft.com/kb/831651>
http://support.microsoft.com/kb/831651

So if rebooting Queenie fixes the problem, let's try that next. Then run CDiag
again, on all 3 computers, after you make the following update in the content:
set FullTarget3=Prince 192.168.1.50

We need to figure out how Prince fits into this. Where do you see "if Static IP
use NetBios over TCP/IP"?
 
L

lurker

Chuck said:
Carl,

OK, so Queenie is the Windows 2000 computer? That's the master browser.

Here's an error 51:
Windows cannot find the network path. Verify that the network path is correct
and the destination computer is not busy or turned off. If Windows still cannot
find the network path, contact your network administrator.

And an error 53:
The network path was not found.

The error 53 is very common.
<http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html

The error 51 I have not seen before. Searching http://search.microsoft.com for
"cannot find the network path", I get a couple of interesting articles:
<http://support.microsoft.com/kb/896427>
http://support.microsoft.com/kb/896427
<http://support.microsoft.com/kb/831651>
http://support.microsoft.com/kb/831651

So if rebooting Queenie fixes the problem, let's try that next. Then run CDiag
again, on all 3 computers, after you make the following update in the content:
set FullTarget3=Prince 192.168.1.50

We need to figure out how Prince fits into this. Where do you see "if Static IP
use NetBios over TCP/IP"?

Yes QUEENIE is Windows 2000.

If_static IP... see
http://rpchc.com/Library/if_static.jpg

As I recall, failures with PRINCE online, most of the time it was booted
Windows 2000. This last failure is the first time I have had PRINCE
online booted into Windows XP and it failed.

Until now, I have believed I had many failures without PRINCE being
powered up. PRINCE is usually not powered on. I will have to re-verify
that impression.

(PRINCE is a 2 year old DELL Dimension 2400)

I will gather the rest of the information much later tonight.

king-daddy
 
C

Chuck

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top