File sharing breaks while already in use

[POSITRON]

Original thread with same subject line was posted 05/30/2006 in this group.

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.

UPDATE:
Machines are FIXED IP Ethernet connected to linksys router at 192.168.1.1.

Netbios through TCP/IP is enabled.

All has been well for about two weeks this time. Power outage today due
to tropical storm caused me to have a fresh power up on all systems.

A short while later, my failure showed up again.

I have made diagnostic output available at
http://rpchc.com/chuck/
to resolve text formatting issue when pasted into newsgroup.

Observation this round:
Running chucks cdiag from a command prompt, I observed a message:
System Error 53. Network not found.

I traced it to a failing command:
"NET VIEW 127.0.0.1"

After rebooting QUEENIE, the NET VIEW command works okay. The omission
of the NET VIEW "127.0.0.1" results from the cdiag.txt (right before the
ping of YAHOO) is easy to overlook.

I think this might be the clue I have been looking for, but I don't know
what to do with it.

King-daddy

 

[lurker]

Sorry about the sender name confusion.
My first post to msnews. still has not showed itself.
I posted from an ISP mirror where I use a different name. This post is
reply by using msnews instead of the ISP mirror.

king-daddy

 

[lurker]

Original thread with same subject line was posted 05/30/2006 in this group.

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.

UPDATE:
Machines are FIXED IP Ethernet connected to linksys router at 192.168.1.1.

Netbios through TCP/IP is enabled.

All has been well for about two weeks this time. Power outage today due
to tropical storm caused me to have a fresh power up on all systems.

A short while later, my failure showed up again.

I have made diagnostic output available at
http://rpchc.com/chuck/
to resolve text formatting issue when pasted into newsgroup.

Observation this round:
Running chucks cdiag from a command prompt, I observed a message:
System Error 53. Network not found.

I traced it to a failing command:
"NET VIEW 127.0.0.1"

After rebooting QUEENIE, the NET VIEW command works okay. The omission
of the NET VIEW "127.0.0.1" results from the cdiag.txt (right before the
ping of YAHOO) is easy to overlook.

I think this might be the clue I have been looking for, but I don't know
what to do with it.

King-daddy

UPDATE::
I went to bed with it working. No activity on either machine all night.
At 0630 I find it failing again.
Only two machines powered up on the home network:

1) QUEENIE (Windows 2000); Master Browser.
C:\WINNT>net view 127.0.0.1
System error 53 has occurred.

The network path was not found.


C:\WINNT>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

C:\WINNT>net view localhost
System error 53 has occurred.

The network path was not found.

2) KING-DADDY (Windows XP Home):

C:\WINDOWS>net view \\queenie /cache
System error 51 has occurred.

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.

Ping works okay in both directions.

HOSTS file has
127.0.0.1 localhost

Ideas?

king-daddy

 

[lurker]

NOTE!
See the original CDIAG.TXT from June 03 failure.
http://rpchc.com/Library/

The "net view 127.0.0.1" response is missing. It is the same symptom
back then. My observation missed that symptom of no response.

king-daddy

 

[lurker]

UPDATE::
I went to bed with it working. No activity on either machine all night.
At 0630 I find it failing again.
Only two machines powered up on the home network:

1) QUEENIE (Windows 2000); Master Browser.
C:\WINNT>net view 127.0.0.1
System error 53 has occurred.

The network path was not found.


C:\WINNT>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

C:\WINNT>net view localhost
System error 53 has occurred.

The network path was not found.

2) KING-DADDY (Windows XP Home):

C:\WINDOWS>net view \\queenie /cache
System error 51 has occurred.

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.

Ping works okay in both directions.

HOSTS file has
127.0.0.1 localhost

Ideas?

king-daddy

I found another person with this symptom in this forum:
http://tinyurl.com/g8xct

I am NOT running Norton Anti Virus, so that suggestion is mute here.

I am disappointed there was no update after chuck asked that Autoruns be
executed.

Lurker

 

[Chuck]

I found another person with this symptom in this forum:
http://tinyurl.com/g8xct

I am NOT running Norton Anti Virus, so that suggestion is mute here.

I am disappointed there was no update after chuck asked that Autoruns be
executed.

Lurker

Carl,

The lack of Autoruns, in the other thread, is unfortunate; though I doubt that
it's presence would necessarily be relevant to your situation.

Both Queenie "net view 127.0.0.1" and "net view 192.168.1.52" is failing, though
"net view QUEENIE" is good. Both the "Error 53" (name not found) and the
failing "net view" by IP address, but not by name, indicate a name resolution
problem. But a name resolution error generally isn't chronic.

Is NetBT ENABLED on Queenie? Is LMHosts used on any computer?

Try and observe what is happening, during any failure, between when you can
access the server (Queenie? 192.168.1.52?) and when you can't.

And figure out what Prince is doing. When your "net view" shows Prince, and
that's when you're having problems, what do you think I'm thinking?

Adhoc Browser View

Server Name Remark

 

[lurker]

Carl,

The lack of Autoruns, in the other thread, is unfortunate; though I doubt that
it's presence would necessarily be relevant to your situation.

Both Queenie "net view 127.0.0.1" and "net view 192.168.1.52" is failing, though
"net view QUEENIE" is good. Both the "Error 53" (name not found) and the
failing "net view" by IP address, but not by name, indicate a name resolution
problem. But a name resolution error generally isn't chronic.

Is NetBT ENABLED on Queenie? Is LMHosts used on any computer?

Try and observe what is happening, during any failure, between when you can
access the server (Queenie? 192.168.1.52?) and when you can't.

And figure out what Prince is doing. When your "net view" shows Prince, and
that's when you're having problems, what do you think I'm thinking?

Adhoc Browser View

Server Name Remark
-------------------------------------------------------------------------------
\\KING-DADDY king-daddy 51
\\PRINCE
\\QUEENIE
The command completed successfully.

Chuck,
The old dated "WORKING" data was with PRINCE. I have not created new
working data with just KING-DADDY and QUEENIE. I will do that to
eliminate confusion. Sorry. It's not hard to update because the APACHE
server is running on KING-DADDY.

PRINCE is not in the picture now. I am totally testing without PRINCE
because the last three failures have been with PRINCE powered down. In
fact, when we had the power outage, PRINCE was already powered down.

LMHOSTS is enabled on QUEENIE, There is not a file for it. LMHOSTS.SAM
is the fully commented sample file.

LMHOSTS is enabled on KING-DADDY and has one line in it. The line is no
longer a valid domain (was the old queenie name)

I enable LMHOSTS back before I changed all machine names and workgroup
name. It was simply to see if it affected my problem. I forgot to undo
that after I determined it did not affect the problem.

QUEENIE has been "Enable NetBIOS over TCPIP" ever since fixed IP.
KING-DADDY also that way.

How does one develop a name resolution problem when the machine is not
being used by a user? Of course we have firewall activity, anti virus
activity, Windows Update activity and other behind the scenes processes.

I have already determined that the failure is not driven by timer driven
screen saver, Windows Defender and Anti Virus updates.

When problem originally showed up this year, I was running Norton Anti
Virus and Zone alarm. In March I changed to Grisoft AV and Kerio
personal firewall. That means the failure manifested itself with
different product in that arena.

 

[Chuck]

Chuck,
The old dated "WORKING" data was with PRINCE. I have not created new
working data with just KING-DADDY and QUEENIE. I will do that to
eliminate confusion. Sorry. It's not hard to update because the APACHE
server is running on KING-DADDY.

PRINCE is not in the picture now. I am totally testing without PRINCE
because the last three failures have been with PRINCE powered down. In
fact, when we had the power outage, PRINCE was already powered down.

LMHOSTS is enabled on QUEENIE, There is not a file for it. LMHOSTS.SAM
is the fully commented sample file.

LMHOSTS is enabled on KING-DADDY and has one line in it. The line is no
longer a valid domain (was the old queenie name)

I enable LMHOSTS back before I changed all machine names and workgroup
name. It was simply to see if it affected my problem. I forgot to undo
that after I determined it did not affect the problem.

QUEENIE has been "Enable NetBIOS over TCPIP" ever since fixed IP.
KING-DADDY also that way.

How does one develop a name resolution problem when the machine is not
being used by a user? Of course we have firewall activity, anti virus
activity, Windows Update activity and other behind the scenes processes.

I have already determined that the failure is not driven by timer driven
screen saver, Windows Defender and Anti Virus updates.

When problem originally showed up this year, I was running Norton Anti
Virus and Zone alarm. In March I changed to Grisoft AV and Kerio
personal firewall. That means the failure manifested itself with
different product in that arena.

Carl,

If your problem was a one-time thing, I'd say check your system changes. But
it's chronic.

So are you saying that Prince was not online when you ran CDiag last?
Adhoc Browser View

Server Name Remark
-------------------------------------------------------------------------------
\\KING-DADDY king-daddy 51
\\PRINCE
\\QUEENIE
The command completed successfully.

How does one develop a name resolution problem when the machine is not being
used by a user? What is name resolution? It's the ability of one computer to
find out the address of another. Any process, when accessing another computer,
has to have the name of the other computer resolved.

Looking back at the end of May (5/31 11:45 PST) I see your post with "ipconfig
/all" for both King-Daddy and Queenie. Queenie has node type = Broadcast;
King-Daddy also has Unknown; with no WINS server indicated, it is Broadcast.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html#Unknown>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html#Unknown

Broadcast name resolution uses NetBIOS broadcast packets, if NetBT is enabled
(either explicitly or implicitly). If broadcasting a request for the address
fails, and DNS is enabled for name resolution, a DNS server is queried; if not,
you get an Error 53.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html
<http://support.microsoft.com/Default.aspx?id=160177>
http://support.microsoft.com/Default.aspx?id=160177

Read this, as much as you can. Ask questions, and we will continue.

 

[lurker]

Carl,

If your problem was a one-time thing, I'd say check your system changes. But
it's chronic.

So are you saying that Prince was not online when you ran CDiag last?
Adhoc Browser View

Server Name Remark
-------------------------------------------------------------------------------
\\KING-DADDY king-daddy 51
\\PRINCE
\\QUEENIE
The command completed successfully.

How does one develop a name resolution problem when the machine is not being
used by a user? What is name resolution? It's the ability of one computer to
find out the address of another. Any process, when accessing another computer,
has to have the name of the other computer resolved.

Looking back at the end of May (5/31 11:45 PST) I see your post with "ipconfig
/all" for both King-Daddy and Queenie. Queenie has node type = Broadcast;
King-Daddy also has Unknown; with no WINS server indicated, it is Broadcast.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html#Unknown>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html#Unknown

Broadcast name resolution uses NetBIOS broadcast packets, if NetBT is enabled
(either explicitly or implicitly). If broadcasting a request for the address
fails, and DNS is enabled for name resolution, a DNS server is queried; if not,
you get an Error 53.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html
<http://support.microsoft.com/Default.aspx?id=160177>
http://support.microsoft.com/Default.aspx?id=160177

Read this, as much as you can. Ask questions, and we will continue.

NOTE: I have updated the cdiag data references to reflect only two
machines. The others are now in a different folder.

You provide great references! I have been there before, thanks to your
impressive web site.

Interesting tourist information:
I found a Microsoft item somewhere yesterday regarding the difference
between Windows XP home and Windows XP... regarding the BROWSER. It
said something to the effect of "Windows XP HOME is NEVER the browser
when on a network with Windows 2000. It will always be Windows 2000 that
is the Browser.

Another item said "...Unknown" node type operates as a "mixed" by default.

KING-DADDY has always and forever been "unknown", especially for all the
time that everything was working correctly for months and months and I
was DHCP for QUEENIE and PRINCE. KING-DADDY has always been fixed
because of running Apache.
Note: KING-DADDY (Windows XP Home) registry has no "Type" parameter.
QUEENIE (Windows 2000) does have a "Type" parameter=1 (b-type) Indeed,
the referenced http://support.microsoft.com/Default.aspx?id=160177
refers to Windows 2000 & NT.
I really think looking at KING-DADDY is a diversion. QUEENIE is what is
broken. QUEENIE can't NET VIEW 127.0.0.1 and the BROWSTAT cant retrieve
the server list when it breaks.

**Also, I found another forum with the identical problem using only two
systems, Windows XP Home and Windows 2000:

http://tinyurl.com/g87ek

Chuck was helping here, too (Thanks chuck!).

Exact same system configuration and failure with NET VIEW 127.0.0.1.

User never got back with the solution.

I don't understand how (on QUEENIE) "NET VIEW QUEENIE" works and "NET
VIEW 127.0.0.1 fails. Name resolution is the reversed lookup.

I also find it very confusing that I have to go to TCPIP properties /
Advanced / WINS tab to set "NetBIOS over TCPIP" but I do not have a WINS
server. I am a home network. No servers.

Regarding node types:
After Failure (Yep, I have it again)..
It makes perfect sense that KING-DADDY broadcast for name resolution
times out because the only other PC on the LAN is QUEENIE and QUEENIE
suddenly broke. QUEENIE Netbt can't even query it self using 127.0.0.1
to localhost. That's not funny. That's distressing.

I've chased many referenced registry keys and never found anything
incriminating on QUEENIE. (Do you believe in a ghost firewall? <grin>)

king-daddy

 

[Chuck]

NOTE: I have updated the cdiag data references to reflect only two
machines. The others are now in a different folder.

You provide great references! I have been there before, thanks to your
impressive web site.

Interesting tourist information:
I found a Microsoft item somewhere yesterday regarding the difference
between Windows XP home and Windows XP... regarding the BROWSER. It
said something to the effect of "Windows XP HOME is NEVER the browser
when on a network with Windows 2000. It will always be Windows 2000 that
is the Browser.

Another item said "...Unknown" node type operates as a "mixed" by default.

KING-DADDY has always and forever been "unknown", especially for all the
time that everything was working correctly for months and months and I
was DHCP for QUEENIE and PRINCE. KING-DADDY has always been fixed
because of running Apache.
Note: KING-DADDY (Windows XP Home) registry has no "Type" parameter.
QUEENIE (Windows 2000) does have a "Type" parameter=1 (b-type) Indeed,
the referenced http://support.microsoft.com/Default.aspx?id=160177
refers to Windows 2000 & NT.
I really think looking at KING-DADDY is a diversion. QUEENIE is what is
broken. QUEENIE can't NET VIEW 127.0.0.1 and the BROWSTAT cant retrieve
the server list when it breaks.

**Also, I found another forum with the identical problem using only two
systems, Windows XP Home and Windows 2000:

http://tinyurl.com/g87ek

Chuck was helping here, too (Thanks chuck!).

Exact same system configuration and failure with NET VIEW 127.0.0.1.

User never got back with the solution.

I don't understand how (on QUEENIE) "NET VIEW QUEENIE" works and "NET
VIEW 127.0.0.1 fails. Name resolution is the reversed lookup.

I also find it very confusing that I have to go to TCPIP properties /
Advanced / WINS tab to set "NetBIOS over TCPIP" but I do not have a WINS
server. I am a home network. No servers.

Regarding node types:
After Failure (Yep, I have it again)..
It makes perfect sense that KING-DADDY broadcast for name resolution
times out because the only other PC on the LAN is QUEENIE and QUEENIE
suddenly broke. QUEENIE Netbt can't even query it self using 127.0.0.1
to localhost. That's not funny. That's distressing.

I've chased many referenced registry keys and never found anything
incriminating on QUEENIE. (Do you believe in a ghost firewall? <grin>)

king-daddy

Carl,

You asked a lot of questions, not all using "?" though. From the end upwards:

The NetBIOS Over TCP affects name resolution. If you turn off NetBT, and setup
a DNS server for local name resolution, Windows XP will work just fine.
<http://support.microsoft.com/?id=204279>
http://support.microsoft.com/?id=204279

You can interpret the "Error = 53" by using "net view" in the combination that
CDiag does.
<http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cnbd_trb_ettg.asp>
http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cnbd_trb_ettg.asp

Regarding the browser, Carl, Windows XP Home and Pro are equal to Windows 2000.
Windows 95 / 98 / ME are subservient. See the browser white paper, and search
for "Master Browser Elections". There's a chart "Election Criterion" a dozen or
so lines after that heading. The interesting thing is that this chart is for
Windows NT (remember Windows XP is Windows NT V5.1), and Windows 95 / 98 / ME
does not always follow the chart.
<http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html>
http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html

If you're going to talk about articles that you've found, the URLs might be
useful. It wouldn't be the first time I've found Microsoft articles that
contradict each other.

When I'm researching a network problem, I always examine at least 2 computers -
and 3 if there are that many. Many tests, between computers A and B, if they
fail, you never know if the problem is with Computer A or Computer B. So I will
continue to ask that you include diagnostics from King-Daddy, and take all
diagnostics simultaneously.

What do you mean by "LMHOSTS is enabled on QUEENIE"? Is the selection "Enable
LMHOSTS lookup" checked, even with no content in LMHOSTS? Maybe the chart in
the browser white paper will be of interest to you. Find "Microsoft TCP/IP and
Name Resolution", and then "Computer Name and Host Name Resolution with NetBIOS
over TCP/IP".
<http://www.microsoft.com/library/me...ive/winntas/deploy/prodspecs/ntbrow01_big.gif>
http://www.microsoft.com/library/me...ive/winntas/deploy/prodspecs/ntbrow01_big.gif

Keep reading, Carl. And when you find an interesting document, note the URL.
Please.

 

[lurker~]

Carl,

You asked a lot of questions, not all using "?" though. From the end upwards:

The NetBIOS Over TCP affects name resolution. If you turn off NetBT, and setup
a DNS server for local name resolution, Windows XP will work just fine.
<http://support.microsoft.com/?id=204279>
http://support.microsoft.com/?id=204279

You can interpret the "Error = 53" by using "net view" in the combination that
CDiag does.
<http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cnbd_trb_ettg.asp>
http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cnbd_trb_ettg.asp

Regarding the browser, Carl, Windows XP Home and Pro are equal to Windows 2000.
Windows 95 / 98 / ME are subservient. See the browser white paper, and search
for "Master Browser Elections". There's a chart "Election Criterion" a dozen or
so lines after that heading. The interesting thing is that this chart is for
Windows NT (remember Windows XP is Windows NT V5.1), and Windows 95 / 98 / ME
does not always follow the chart.
<http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html>
http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html

If you're going to talk about articles that you've found, the URLs might be
useful. It wouldn't be the first time I've found Microsoft articles that
contradict each other.

When I'm researching a network problem, I always examine at least 2 computers -
and 3 if there are that many. Many tests, between computers A and B, if they
fail, you never know if the problem is with Computer A or Computer B. So I will
continue to ask that you include diagnostics from King-Daddy, and take all
diagnostics simultaneously.

What do you mean by "LMHOSTS is enabled on QUEENIE"? Is the selection "Enable
LMHOSTS lookup" checked, even with no content in LMHOSTS? Maybe the chart in
the browser white paper will be of interest to you. Find "Microsoft TCP/IP and
Name Resolution", and then "Computer Name and Host Name Resolution with NetBIOS
over TCP/IP".
<http://www.microsoft.com/library/me...ive/winntas/deploy/prodspecs/ntbrow01_big.gif>
http://www.microsoft.com/library/me...ive/winntas/deploy/prodspecs/ntbrow01_big.gif

Keep reading, Carl. And when you find an interesting document, note the URL.
Please.

Thanks for the prompt responses!!

I just posted new cdiag results for my last failure. I have
reorganized... using folders for organizing various events...
http://rpchc.com/chuck/20060616-1945-QUEENIE & KING-DADDY/

Your very useful link regarding interpreting error 53...
http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cnbd_trb_ettg.asp

is and has been well understood. The explanation assumes the cause is
permanent until resolved. Resolution in my case is to simply reboot the
Browser system "QUEENIE". The explanation does not accomodate a working
connection suddenly failing. The various netbt\parameters in the
registry are not changing at timeof failure. SO far I have not found
any useful suggestions what else to check.

QUEENIE TCPIP LMHOSTS box is checked, but no LNHOSTS file was ever
created on QUEENIE (I had one on KING-DADDY). I have now put the
LMHOSTS in the "etc" folder on QUEENIE.

When Queenie fails:
Prince can't connect as Windows 2000
Prince can't connect as Windows XP Home
King-daddy can't connect (XP)

I am focused on what caused NET VIEW 127.0.0.1 to suddenly stop working.

king-daddy

 

[lurker]

Carl,

You asked a lot of questions, not all using "?" though. From the end upwards:

The NetBIOS Over TCP affects name resolution. If you turn off NetBT, and setup
a DNS server for local name resolution, Windows XP will work just fine.
<http://support.microsoft.com/?id=204279>
http://support.microsoft.com/?id=204279

You can interpret the "Error = 53" by using "net view" in the combination that
CDiag does.
<http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cnbd_trb_ettg.asp>
http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cnbd_trb_ettg.asp

Regarding the browser, Carl, Windows XP Home and Pro are equal to Windows 2000.
Windows 95 / 98 / ME are subservient. See the browser white paper, and search
for "Master Browser Elections". There's a chart "Election Criterion" a dozen or
so lines after that heading. The interesting thing is that this chart is for
Windows NT (remember Windows XP is Windows NT V5.1), and Windows 95 / 98 / ME
does not always follow the chart.
<http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html>
http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html

If you're going to talk about articles that you've found, the URLs might be
useful. It wouldn't be the first time I've found Microsoft articles that
contradict each other.

When I'm researching a network problem, I always examine at least 2 computers -
and 3 if there are that many. Many tests, between computers A and B, if they
fail, you never know if the problem is with Computer A or Computer B. So I will
continue to ask that you include diagnostics from King-Daddy, and take all
diagnostics simultaneously.

What do you mean by "LMHOSTS is enabled on QUEENIE"? Is the selection "Enable
LMHOSTS lookup" checked, even with no content in LMHOSTS? Maybe the chart in
the browser white paper will be of interest to you. Find "Microsoft TCP/IP and
Name Resolution", and then "Computer Name and Host Name Resolution with NetBIOS
over TCP/IP".
<http://www.microsoft.com/library/me...ive/winntas/deploy/prodspecs/ntbrow01_big.gif>
http://www.microsoft.com/library/me...ive/winntas/deploy/prodspecs/ntbrow01_big.gif

Keep reading, Carl. And when you find an interesting document, note the URL.
Please.

Still reading... running out of material. Nothing addresses "working
(must be configured ok) then it breaks!"

I just now added LMHOSTS file to "etc" folder on QUEENIE.

MY data is now reorganized into folders respective of failure date-time.
See latest:
http://tinyurl.com/romm2
You can back up to previous directory if desired.
I have to find what causes a working link (including a mapped drive) to
suddenly break.

 

[lurker]

Carl,

You asked a lot of questions, not all using "?" though. From the end upwards:

The NetBIOS Over TCP affects name resolution. If you turn off NetBT, and setup
a DNS server for local name resolution, Windows XP will work just fine.
<http://support.microsoft.com/?id=204279>
http://support.microsoft.com/?id=204279

You can interpret the "Error = 53" by using "net view" in the combination that
CDiag does.
<http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cnbd_trb_ettg.asp>
http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cnbd_trb_ettg.asp

Regarding the browser, Carl, Windows XP Home and Pro are equal to Windows 2000.
Windows 95 / 98 / ME are subservient. See the browser white paper, and search
for "Master Browser Elections". There's a chart "Election Criterion" a dozen or
so lines after that heading. The interesting thing is that this chart is for
Windows NT (remember Windows XP is Windows NT V5.1), and Windows 95 / 98 / ME
does not always follow the chart.
<http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html>
http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html

If you're going to talk about articles that you've found, the URLs might be
useful. It wouldn't be the first time I've found Microsoft articles that
contradict each other.

When I'm researching a network problem, I always examine at least 2 computers -
and 3 if there are that many. Many tests, between computers A and B, if they
fail, you never know if the problem is with Computer A or Computer B. So I will
continue to ask that you include diagnostics from King-Daddy, and take all
diagnostics simultaneously.

What do you mean by "LMHOSTS is enabled on QUEENIE"? Is the selection "Enable
LMHOSTS lookup" checked, even with no content in LMHOSTS? Maybe the chart in
the browser white paper will be of interest to you. Find "Microsoft TCP/IP and
Name Resolution", and then "Computer Name and Host Name Resolution with NetBIOS
over TCP/IP".
<http://www.microsoft.com/library/me...ive/winntas/deploy/prodspecs/ntbrow01_big.gif>
http://www.microsoft.com/library/me...ive/winntas/deploy/prodspecs/ntbrow01_big.gif

Keep reading, Carl. And when you find an interesting document, note the URL.
Please.

Another failure this AM (June 17) between 0130 and 0200. I note several
observations without suggesting they are related (yet).

QUEENIE EVENT LOG:
http://tinyurl.com/hq2d7 "unable to allocate work item"

2 hours later, this event log item:

http://tinyurl.com/kthp6

END QUEENIE EVENT LOG:

QUEENIE FIRE WALL OBSERVATIONS:
comment: Kerio fire wall has all logging enabled. There is a lot of
data logged, but nothing in the failure time window. To give an idea of
the logs available, here is a screen shot of the logs directory:

http://tinyurl.com/zq7ug

I am closely scrutinizing firewall because at some point I think I may
have to run several days without it (just to prove/disprove firewall.)

 

[lurker~]

Keep reading, Carl. And when you find an interesting document, note the URL.
Please.

Interesting observation:
QUEENIE Event Log (System)
always has a similar item in the time frame window of each failure:
http://tinyurl.com/hq2d7
and after each reboot / failure...
the item always shows "Event ID" 2021

Why always 2021?
Process Explorer Task numbers are not that high; highest is in the 1600's.

What is this Event ID 2021?

king-daddy

 

[lurker~]

Interesting observation:
QUEENIE Event Log (System)
always has a similar item in the time frame window of each failure:
http://tinyurl.com/hq2d7
and after each reboot / failure...
the item always shows "Event ID" 2021

Why always 2021?
Process Explorer Task numbers are not that high; highest is in the 1600's.

What is this Event ID 2021?

king-daddy

I am beginning to think this logged event may be a result of the error,
not causing the error...

http://support.microsoft.com/default.aspx?scid=kb;en-us;q317249&sd=tech
is for servers. The tweek requires over 1.5 GB Memory... clearly not in
my ballpark.

Event ID 2021 suggests network flooding or overload. "...Server service
cannot keep up with the demand for network work items that are queued by
the network layer of the I/O stream."

I don't believe this applies to my situation of two home computers
sitting with no user driven activity.

king-daddy

 

[lurker]

Carl,

You asked a lot of questions, not all using "?" though. From the end upwards:

The NetBIOS Over TCP affects name resolution. If you turn off NetBT, and setup
a DNS server for local name resolution, Windows XP will work just fine.
<http://support.microsoft.com/?id=204279>
http://support.microsoft.com/?id=204279

You can interpret the "Error = 53" by using "net view" in the combination that
CDiag does.
<http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cnbd_trb_ettg.asp>
http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cnbd_trb_ettg.asp

Regarding the browser, Carl, Windows XP Home and Pro are equal to Windows 2000.
Windows 95 / 98 / ME are subservient. See the browser white paper, and search
for "Master Browser Elections". There's a chart "Election Criterion" a dozen or
so lines after that heading. The interesting thing is that this chart is for
Windows NT (remember Windows XP is Windows NT V5.1), and Windows 95 / 98 / ME
does not always follow the chart.
<http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html>
http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html

If you're going to talk about articles that you've found, the URLs might be
useful. It wouldn't be the first time I've found Microsoft articles that
contradict each other.

When I'm researching a network problem, I always examine at least 2 computers -
and 3 if there are that many. Many tests, between computers A and B, if they
fail, you never know if the problem is with Computer A or Computer B. So I will
continue to ask that you include diagnostics from King-Daddy, and take all
diagnostics simultaneously.

What do you mean by "LMHOSTS is enabled on QUEENIE"? Is the selection "Enable
LMHOSTS lookup" checked, even with no content in LMHOSTS? Maybe the chart in
the browser white paper will be of interest to you. Find "Microsoft TCP/IP and
Name Resolution", and then "Computer Name and Host Name Resolution with NetBIOS
over TCP/IP".
<http://www.microsoft.com/library/me...ive/winntas/deploy/prodspecs/ntbrow01_big.gif>
http://www.microsoft.com/library/me...ive/winntas/deploy/prodspecs/ntbrow01_big.gif

Keep reading, Carl. And when you find an interesting document, note the URL.
Please.

Node Type = Unknown

Q. What causes this?
A. XP Home

XP Home is not discussed in that manner here, but here is a clue:
QUOTE:
4. To set the Node Type to Unknown (recommended), open the registry
editor and go to:
HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/Netbt/Parameters
and delete these values if they're present: NodeType and DhcpNodeType.
(You must reboot for changes to take effect).

FROM THIS PAGE:
http://www.techbuilder.org/recipes/59200376


And there is more:
http://support.microsoft.com/kb/310570

At the bottom:
APPLIES TO
• Microsoft Windows Server 2003, Standard Edition
• Microsoft Windows Server 2003, Enterprise Edition
• Microsoft Windows XP Professional Edition
• Microsoft Windows Small Business Server 2003 Premium Edition
• Microsoft Windows Small Business Server 2003 Standard Edition

I have noticed many KB articles are qualified this way. Not the
exclusion of XP HOME. I have not specifically located the reference
regarding differences in XP Home and XP PRO regarding networking.
UNQUOTE:

Useful "Differences" between XP Home and PRO sites seem to focus on
"FAQ" type questions, and not technical details how differences are
implemented. I have been running into registry details.

http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/z04d621675.mspx
Differences are noted in "networking" but not listed in detail. For
example, I would like to find again the explanation of why XP HOME has
"Node Type: Unknown". It made sense when I read it.

Also consider this link:

http://www.winsupersite.com/showcase/windowsxp_home_pro.asp

 

[Chuck]

Node Type = Unknown

Q. What causes this?
A. XP Home

XP Home is not discussed in that manner here, but here is a clue:
QUOTE:
4. To set the Node Type to Unknown (recommended), open the registry
editor and go to:
HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/Netbt/Parameters
and delete these values if they're present: NodeType and DhcpNodeType.
(You must reboot for changes to take effect).

FROM THIS PAGE:
http://www.techbuilder.org/recipes/59200376


And there is more:
http://support.microsoft.com/kb/310570

At the bottom:
APPLIES TO
• Microsoft Windows Server 2003, Standard Edition
• Microsoft Windows Server 2003, Enterprise Edition
• Microsoft Windows XP Professional Edition
• Microsoft Windows Small Business Server 2003 Premium Edition
• Microsoft Windows Small Business Server 2003 Standard Edition

I have noticed many KB articles are qualified this way. Not the
exclusion of XP HOME. I have not specifically located the reference
regarding differences in XP Home and XP PRO regarding networking.
UNQUOTE:

Useful "Differences" between XP Home and PRO sites seem to focus on
"FAQ" type questions, and not technical details how differences are
implemented. I have been running into registry details.

http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/z04d621675.mspx
Differences are noted in "networking" but not listed in detail. For
example, I would like to find again the explanation of why XP HOME has
"Node Type: Unknown". It made sense when I read it.

Also consider this link:

http://www.winsupersite.com/showcase/windowsxp_home_pro.asp

Interesting, Carl.

But Node Type = Unknown is simply a symptom. Or do you see a different value
leading to better name resolution, which leads to a more precise handle on your
problem?

And AFAIK, not only Windows XP Home is subject to not having that registry key.

<http://support.microsoft.com/kb/310570>
http://support.microsoft.com/kb/310570
CAUSE
This issue can occur if the EnableProxy key in the registry is set to an invalid
value.

I have an XP Pro system with that. It doesn't bother me anyway. Unknown is
treated as Broadcast if WINS is not configured, or Hybrid if WINS is configured.
<http://support.microsoft.com/?id=160177>
http://support.microsoft.com/?id=160177

But keep looking. I am meditating and writing today.

 

[lurker]

Carl,

You asked a lot of questions, not all using "?" though. From the end upwards:

The NetBIOS Over TCP affects name resolution. If you turn off NetBT, and setup
a DNS server for local name resolution, Windows XP will work just fine.
<http://support.microsoft.com/?id=204279>
http://support.microsoft.com/?id=204279

You can interpret the "Error = 53" by using "net view" in the combination that
CDiag does.
<http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cnbd_trb_ettg.asp>
http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cnbd_trb_ettg.asp

Regarding the browser, Carl, Windows XP Home and Pro are equal to Windows 2000.
Windows 95 / 98 / ME are subservient. See the browser white paper, and search
for "Master Browser Elections". There's a chart "Election Criterion" a dozen or
so lines after that heading. The interesting thing is that this chart is for
Windows NT (remember Windows XP is Windows NT V5.1), and Windows 95 / 98 / ME
does not always follow the chart.
<http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html>
http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html

If you're going to talk about articles that you've found, the URLs might be
useful. It wouldn't be the first time I've found Microsoft articles that
contradict each other.

When I'm researching a network problem, I always examine at least 2 computers -
and 3 if there are that many. Many tests, between computers A and B, if they
fail, you never know if the problem is with Computer A or Computer B. So I will
continue to ask that you include diagnostics from King-Daddy, and take all
diagnostics simultaneously.

What do you mean by "LMHOSTS is enabled on QUEENIE"? Is the selection "Enable
LMHOSTS lookup" checked, even with no content in LMHOSTS? Maybe the chart in
the browser white paper will be of interest to you. Find "Microsoft TCP/IP and
Name Resolution", and then "Computer Name and Host Name Resolution with NetBIOS
over TCP/IP".
<http://www.microsoft.com/library/me...ive/winntas/deploy/prodspecs/ntbrow01_big.gif>
http://www.microsoft.com/library/me...ive/winntas/deploy/prodspecs/ntbrow01_big.gif

Keep reading, Carl. And when you find an interesting document, note the URL.
Please.

I have been running now for 36 hours without a failure. I'm not
convinced yet, so will continue for a conclusive period.

I have opened a problem ticket for Kerio Personal Firewall. No more
failures since I uninstalled Kerio. Then I recall the several days of
"Hey, it worked while I was gone a while."... I can't be sure I had
Kerio running at that time. But when we finally had an incident to
force a power cycle, of course Kerio restarted. Then I had problems.

Chasing records, I find that I never experienced this problem with Zone
Alarm Pro which was uninstalled 12/28/2005. Within about three weeks, I
was aware I had a problem... maybe before that. I am fuzzy on that time
frame because of other health events at that time.

My "Casual Observer" opinion of what is happening... or so it looks:

QUEENIE Firewall sudden decides that all the QUEENIE file shares are not
of WORKGROUP "KINGDOM"... or some such silliness like that. The fact
that all networked machines, and QUEENIE itself cannot browse the shares
suggest they are "not there" because of the error 53 "network not
found". So what did the firewall do to lose the network connection to
self? Nothing in any of the Kerio logs showed any activity in the
failure time frame.

What bothers me is that the other two forum hits where they had the same
scenario as I do, Kerio was not identified as the fire wall.. it is an
unknown. Neither person posted a follow-up fix.

I have had Kerio on two other machines, but none of them were netbios
browsers. I think that has to be the difference. The MASTER BROWSER
does things that the other machines are not doing.

Are we having fun yet?

 

[lurker]

Carl,

You asked a lot of questions, not all using "?" though. From the end upwards:

The NetBIOS Over TCP affects name resolution. If you turn off NetBT, and setup
a DNS server for local name resolution, Windows XP will work just fine.
<http://support.microsoft.com/?id=204279>
http://support.microsoft.com/?id=204279

You can interpret the "Error = 53" by using "net view" in the combination that
CDiag does.
<http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cnbd_trb_ettg.asp>
http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cnbd_trb_ettg.asp

Regarding the browser, Carl, Windows XP Home and Pro are equal to Windows 2000.
Windows 95 / 98 / ME are subservient. See the browser white paper, and search
for "Master Browser Elections". There's a chart "Election Criterion" a dozen or
so lines after that heading. The interesting thing is that this chart is for
Windows NT (remember Windows XP is Windows NT V5.1), and Windows 95 / 98 / ME
does not always follow the chart.
<http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html>
http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html

If you're going to talk about articles that you've found, the URLs might be
useful. It wouldn't be the first time I've found Microsoft articles that
contradict each other.

When I'm researching a network problem, I always examine at least 2 computers -
and 3 if there are that many. Many tests, between computers A and B, if they
fail, you never know if the problem is with Computer A or Computer B. So I will
continue to ask that you include diagnostics from King-Daddy, and take all
diagnostics simultaneously.

What do you mean by "LMHOSTS is enabled on QUEENIE"? Is the selection "Enable
LMHOSTS lookup" checked, even with no content in LMHOSTS? Maybe the chart in
the browser white paper will be of interest to you. Find "Microsoft TCP/IP and
Name Resolution", and then "Computer Name and Host Name Resolution with NetBIOS
over TCP/IP".
<http://www.microsoft.com/library/me...ive/winntas/deploy/prodspecs/ntbrow01_big.gif>
http://www.microsoft.com/library/me...ive/winntas/deploy/prodspecs/ntbrow01_big.gif

Keep reading, Carl. And when you find an interesting document, note the URL.
Please.

Whew! I've been nearly full time for three days trying to create a
consistent set of procedures and documentation gathering to give to
Kerio so they can reproduce the problem.

I have tried with just two machines in the workgroup, and with three. I
switched the roles of QUEENIE and PRINCE That proved it is not a machine
sensitive problem. Both PRINCE and QUEENIE fail when either is the
Master Browser.

Nothing is ever in the Windows Event logs.
Nothing is ever in the Kerio debug log, error log, or any other logs.

See my network here:
http://raleighncpchousecalls.com/kingdom/

See my most recent (incomplete)document set here:
http://rpchc.com/chuck/PRINCE-MasterBrowser-Kerio-21-jun-2006/

I have proved:
1)The problems does not exist with Zone Alarm Personal or "no firewall"
on the Master Browser. (Does that mean I have a Kerio configuration
problem?)

2)It fails only when Windows 2000 is the Master Browser

3)KING-DADDY sees the failure up to 2 minutes before the Master Browser
displays the failure in BROWSTAT STATUS. It makes me ask myself, "Did
KING-DADDY break something, or is the browser machine's BROWSTAT results
displayed from its cache."

4) Rebooting the Master Browser machine clears the problem for a while.

Because of item 3, I tried killing and rebooting KING-DADDY while PRINCE
was Master and still not reflecting the error.
1) PRINCE continued without posting the error!
2) When KING-DADDY restarted... it eventually took over as Master
Browser!$#@ and I have not yet been able to break the habit.

Just when I thought I was done, the rules changed, or so it seems.

For months, all has been behaving like this descriptor:
Windows 9x/Me/XP Home clients are not true members of a domain for
reasons outlined in this chapter. The protocol for support of Windows
9x/Me style network (domain) log-ons is completely different from
NT4/Windows 200x type domain logons and has been officially supported
for some time. These clients use the old LanMan Network Logon facilities
that are supported in Samba since approximately the Samba-1.9.15 series.
See http://tinyurl.com/epj9e

This article does not mention XP-HOME.
http://support.microsoft.com/kb/188001

I can't seem to find a "bible" to describe what to consistently expect.
My current conclusions is to refrain from using Kerio on Windows 2000
PRO when Win2K is the Master Browser and there is a Windows XP Home
system in the workgroup. Somehow I am uneasy with that perspective.

(Why I need a Windows 2000 machine in the workgroup is another
discussion. ('Thank you' Microsoft)).

Meanwhile... I'm not done yet.

 

[lurker]

Carl,

You asked a lot of questions, not all using "?" though. From the end upwards:

The NetBIOS Over TCP affects name resolution. If you turn off NetBT, and setup
a DNS server for local name resolution, Windows XP will work just fine.
<http://support.microsoft.com/?id=204279>
http://support.microsoft.com/?id=204279

You can interpret the "Error = 53" by using "net view" in the combination that
CDiag does.
<http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cnbd_trb_ettg.asp>
http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cnbd_trb_ettg.asp

Regarding the browser, Carl, Windows XP Home and Pro are equal to Windows 2000.
Windows 95 / 98 / ME are subservient. See the browser white paper, and search
for "Master Browser Elections". There's a chart "Election Criterion" a dozen or
so lines after that heading. The interesting thing is that this chart is for
Windows NT (remember Windows XP is Windows NT V5.1), and Windows 95 / 98 / ME
does not always follow the chart.
<http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html>
http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html

If you're going to talk about articles that you've found, the URLs might be
useful. It wouldn't be the first time I've found Microsoft articles that
contradict each other.

When I'm researching a network problem, I always examine at least 2 computers -
and 3 if there are that many. Many tests, between computers A and B, if they
fail, you never know if the problem is with Computer A or Computer B. So I will
continue to ask that you include diagnostics from King-Daddy, and take all
diagnostics simultaneously.

What do you mean by "LMHOSTS is enabled on QUEENIE"? Is the selection "Enable
LMHOSTS lookup" checked, even with no content in LMHOSTS? Maybe the chart in
the browser white paper will be of interest to you. Find "Microsoft TCP/IP and
Name Resolution", and then "Computer Name and Host Name Resolution with NetBIOS
over TCP/IP".
<http://www.microsoft.com/library/me...ive/winntas/deploy/prodspecs/ntbrow01_big.gif>
http://www.microsoft.com/library/me...ive/winntas/deploy/prodspecs/ntbrow01_big.gif

Keep reading, Carl. And when you find an interesting document, note the URL.
Please.

Chuck, are you still watching?

This is getting interesting again.
Right after rebooting the Master Browser (PRINCE this time)
Firewall comes up. I have verified that, with or without the firewall,
you need that mapped drive, and it needs to be active. Otherwise you
get the Error 53 on Registry fetch from other workgroup machines.

This message is interesting in another way. Reboot starts the firewall.
I know I need to wait for the completion of one or more of the 12
minute browser process cycles before BROWSTAT results get consistent.

I can't seem to get rid of this message:
"Unable to retrieve server list from PRINCE: 64" until I shut down the
Kerio Firewall. (I will do some testing with Zone Alarm tomorrow).

I have also noticed that often, after 2 or three of the 12 minute
browser process cycles, that message may go away, anyway. I would love
to know what that is all about.

I also notice, without a Firewall, if I break the mapped drive link, a
few seconds later, BROWSTAT (From remote workgroup (KING-DADDY) still
gives all good results. ...but wait a minute or two, and the message:
"Unable to retrieve server list from PRINCE: 64"
message returns. I expected that. What surprises me is the:
"Master browser is running build 2195."
is present instead of the error 53 for the registry fetch.

Without the mapped drive, how can he fetch the registry data for browser
build without the link? But can't get the server list? Maybe the build
list is considered not so dynamic, but the server list is dynamic?