BROWSTAT: ...Could not connect to registry, error = 53

[QUEENIE]

I have a 3 WINDOWS machines home network connected together via a
Linksys router.

BROWSTAT STATUS

Result:
etc.
etc.
Could not connect to registry, error = 53
Unable to determine build of browser master: 53
etc..

I have found that I can resolve this message situation by mapping a
drive share to the Master Browser machine.

Anyone know of another way?

king-daddy

 

[Chuck]

I have a 3 WINDOWS machines home network connected together via a
Linksys router.

BROWSTAT STATUS

Result:
etc.
etc.
Could not connect to registry, error = 53
Unable to determine build of browser master: 53
etc..

I have found that I can resolve this message situation by mapping a
drive share to the Master Browser machine.

Anyone know of another way?

king-daddy

Hi Carl,

As I started to mention in your previous thread, an error 53 is "path not
found". Try "net helpmsg 53" sometime. This indicates a name resolution
problem.

On a small LAN like yours, you probably use NetBIOS name resolution (Broadcast,
Hybrid, or Mixed). Broadcast is best, unless you have a WINS server (which is
unusual).
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html

Now since you can manually map shares (by name or by address?), you don't have a
connectivity problem. Other reasons why you can't get name resolution would be:
# Personal firewall.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html
# LSP / Winsock corruption.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html
# SMB mismatch.

Now name resolution uses Server Message Blocks or SMBs. SMBs can use NetBT, or
they can be directly bound to TCP/IP. Both the client and the server have to
use the same SMB transport, or they will have no connection (causing, among
other things, an error 53).

This SMB transport issue, I think, is one reason why the TCP/IP Properties -
NetBT setting, is not consistently effective. If you Disable NetBT, or you at
least don't Enable it, your SMBs will be direct hosted (ie use TCP/IP). If
you're going to use direct hosting, though, both the client and the server have
to support that.
<http://support.microsoft.com/?id=204279>
http://support.microsoft.com/?id=204279

 

[lurker]

Hi Carl,

As I started to mention in your previous thread, an error 53 is "path not
found". Try "net helpmsg 53" sometime. This indicates a name resolution
problem.

On a small LAN like yours, you probably use NetBIOS name resolution (Broadcast,
Hybrid, or Mixed). Broadcast is best, unless you have a WINS server (which is
unusual).
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html

Now since you can manually map shares (by name or by address?), you don't have a
connectivity problem. Other reasons why you can't get name resolution would be:
# Personal firewall.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html
# LSP / Winsock corruption.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html
# SMB mismatch.

Now name resolution uses Server Message Blocks or SMBs. SMBs can use NetBT, or
they can be directly bound to TCP/IP. Both the client and the server have to
use the same SMB transport, or they will have no connection (causing, among
other things, an error 53).

This SMB transport issue, I think, is one reason why the TCP/IP Properties -
NetBT setting, is not consistently effective. If you Disable NetBT, or you at
least don't Enable it, your SMBs will be direct hosted (ie use TCP/IP). If
you're going to use direct hosting, though, both the client and the server have
to support that.
<http://support.microsoft.com/?id=204279>
http://support.microsoft.com/?id=204279

Thanks!
After reading
http://support.microsoft.com/?id=204279
It sounds like I do not need NetBT! That would be nice.

You stated, "If you're going to use direct hosting, though, both the
client and the server have to support that." which makes sense.

The terms "client and server" are unclear to me in the HOME environment
where I do not have a specific "server" except maybe in the sense of the
master browser. Can you elaborate on that?

I have turned off NetBT on KING-DADDY and QUEENIE and tried to establish
a file share.
net helpmsg 53 repeats what it already told me:
The network path was not found.

C:\>net config redirector
Computer name \\KING-DADD
====>> (WHY IS Computer name truncated??)
Full Computer name KING-DADDY
User name clackey

Workstation active on
NetbiosSmb (000000000000)

Software version Windows 200

Workstation domain KINGDOM
Workstation Domain DNS Name (null)
Logon domain KING-DADDY

COM Open Timeout (sec) 0
COM Send Count (byte) 16
COM Send Timeout (msec) 250
The command completed successfully.

QUEENIE (Win2K) Does not have a firewall.
PRINCE is powered down

NET USE * \\QUEENIE\downloads /user:userid pw
and
NET USE * \\192.168.1.52\downloads /user:userid pw

give error 53 network not found.

net view queenie (fails code 53)
net view 192.168.1.52 shows the shares

I put QUEENIE into HOSTS file and
now it works for NET VIEW QUEENIE

What am I missing?

1) How does DNS work with SMB?

2) Why is "net use" file share still failing? I can see the files using
already existing object in "My Net Work Places", but I can't browse
Microsoft Windows Network/Kingdom/ ? (using king-daddy)

 

[lurker]

Hi Carl,

As I started to mention in your previous thread, an error 53 is "path not
found". Try "net helpmsg 53" sometime. This indicates a name resolution
problem.

On a small LAN like yours, you probably use NetBIOS name resolution (Broadcast,
Hybrid, or Mixed). Broadcast is best, unless you have a WINS server (which is
unusual).
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html

Now since you can manually map shares (by name or by address?), you don't have a
connectivity problem. Other reasons why you can't get name resolution would be:
# Personal firewall.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html
# LSP / Winsock corruption.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html
# SMB mismatch.

Now name resolution uses Server Message Blocks or SMBs. SMBs can use NetBT, or
they can be directly bound to TCP/IP. Both the client and the server have to
use the same SMB transport, or they will have no connection (causing, among
other things, an error 53).

This SMB transport issue, I think, is one reason why the TCP/IP Properties -
NetBT setting, is not consistently effective. If you Disable NetBT, or you at
least don't Enable it, your SMBs will be direct hosted (ie use TCP/IP). If
you're going to use direct hosting, though, both the client and the server have
to support that.
<http://support.microsoft.com/?id=204279>
http://support.microsoft.com/?id=204279

Thanks!
After reading
http://support.microsoft.com/?id=204279
It sounds like I do not need NetBT! That would be nice.

You stated, "If you're going to use direct hosting, though, both the
client and the server have to support that." which makes sense.

The terms "client and server" are unclear to me in the HOME environment
where I do not have a specific "server" except maybe in the sense of the
master browser. Can you elaborate on that?

I have turned off NetBT on KING-DADDY and QUEENIE and tried to establish
a file share.
net helpmsg 53 repeats what it already told me:
The network path was not found.

C:\>net config redirector
Computer name \\KING-DADD
====>> (WHY IS Computer name truncated??)
Full Computer name KING-DADDY
User name clackey

Workstation active on
NetbiosSmb (000000000000)

Software version Windows 200

Workstation domain KINGDOM
Workstation Domain DNS Name (null)
Logon domain KING-DADDY

COM Open Timeout (sec) 0
COM Send Count (byte) 16
COM Send Timeout (msec) 250
The command completed successfully.

QUEENIE (Win2K) Does not have a firewall.
PRINCE is powered down

NET USE * \\QUEENIE\downloads /user:userid pw
and
NET USE * \\192.168.1.52\downloads /user:userid pw

give error 53 network not found.

net view queenie (fails code 53)
net view 192.168.1.52 shows the shares

I put QUEENIE into HOSTS file and
now it works for NET VIEW QUEENIE

What am I missing?

1) How does DNS work with SMB?

2) Why is "net use" file share still failing? I can see the files using
already existing object in "My Net Work Places", but I can't browse
Microsoft Windows Network/Kingdom/ ? (using king-daddy)

 

[Chuck]

Thanks!
After reading
http://support.microsoft.com/?id=204279
It sounds like I do not need NetBT! That would be nice.

You stated, "If you're going to use direct hosting, though, both the
client and the server have to support that." which makes sense.

The terms "client and server" are unclear to me in the HOME environment
where I do not have a specific "server" except maybe in the sense of the
master browser. Can you elaborate on that?

I have turned off NetBT on KING-DADDY and QUEENIE and tried to establish
a file share.
net helpmsg 53 repeats what it already told me:
The network path was not found.

C:\>net config redirector
Computer name \\KING-DADD
====>> (WHY IS Computer name truncated??)
Full Computer name KING-DADDY
User name clackey

Workstation active on
NetbiosSmb (000000000000)

Software version Windows 200

Workstation domain KINGDOM
Workstation Domain DNS Name (null)
Logon domain KING-DADDY

COM Open Timeout (sec) 0
COM Send Count (byte) 16
COM Send Timeout (msec) 250
The command completed successfully.

QUEENIE (Win2K) Does not have a firewall.
PRINCE is powered down

NET USE * \\QUEENIE\downloads /user:userid pw
and
NET USE * \\192.168.1.52\downloads /user:userid pw

give error 53 network not found.

net view queenie (fails code 53)
net view 192.168.1.52 shows the shares

I put QUEENIE into HOSTS file and
now it works for NET VIEW QUEENIE

What am I missing?

1) How does DNS work with SMB?

2) Why is "net use" file share still failing? I can see the files using
already existing object in "My Net Work Places", but I can't browse
Microsoft Windows Network/Kingdom/ ? (using king-daddy)

Carl,

A server is any computer providing shared data. Any Windows computer acts as a
server, even if it doesn't run a server OS, if it's running File & Printer
Sharing for Microsoft Windows.
<http://nitecruzr.blogspot.com/2005/05/simple-network-definition.html>
http://nitecruzr.blogspot.com/2005/05/simple-network-definition.html

If you're going to disable NetBT, you have to do it simultaneously on all
computers. All computer must support direct hosting of SMBs. All firewalls
have to pass microsoft-ds (port 445/tcp&udp). And you'll need either fixed IP
address assignment, or a DNS server on your LAN.

If turning NetBT off causes browser problems, then you have a firewall somewhere
blocking port 445.

How about you run "net config server" and "net config workstation" along with
CDiag, for all computers? I'll look at your current CDiag logs, but I think
"net config" and browstat should be useful.

 

[Chuck]

Thanks!
After reading
http://support.microsoft.com/?id=204279
It sounds like I do not need NetBT! That would be nice.

You stated, "If you're going to use direct hosting, though, both the
client and the server have to support that." which makes sense.

The terms "client and server" are unclear to me in the HOME environment
where I do not have a specific "server" except maybe in the sense of the
master browser. Can you elaborate on that?

I have turned off NetBT on KING-DADDY and QUEENIE and tried to establish
a file share.
net helpmsg 53 repeats what it already told me:
The network path was not found.

C:\>net config redirector
Computer name \\KING-DADD
====>> (WHY IS Computer name truncated??)
Full Computer name KING-DADDY
User name clackey

Workstation active on
NetbiosSmb (000000000000)

Software version Windows 200

Workstation domain KINGDOM
Workstation Domain DNS Name (null)
Logon domain KING-DADDY

COM Open Timeout (sec) 0
COM Send Count (byte) 16
COM Send Timeout (msec) 250
The command completed successfully.

QUEENIE (Win2K) Does not have a firewall.
PRINCE is powered down

NET USE * \\QUEENIE\downloads /user:userid pw
and
NET USE * \\192.168.1.52\downloads /user:userid pw

give error 53 network not found.

net view queenie (fails code 53)
net view 192.168.1.52 shows the shares

I put QUEENIE into HOSTS file and
now it works for NET VIEW QUEENIE

What am I missing?

1) How does DNS work with SMB?

2) Why is "net use" file share still failing? I can see the files using
already existing object in "My Net Work Places", but I can't browse
Microsoft Windows Network/Kingdom/ ? (using king-daddy)

Carl,

A server is any computer providing shared data. Any Windows computer acts as a
server, even if it doesn't run a server OS, if it's running File & Printer
Sharing for Microsoft Windows.
<http://nitecruzr.blogspot.com/2005/05/simple-network-definition.html>
http://nitecruzr.blogspot.com/2005/05/simple-network-definition.html

If you're going to disable NetBT, you have to do it simultaneously on all
computers. All computer must support direct hosting of SMBs. All firewalls
have to pass microsoft-ds (port 445/tcp&udp). And you'll need either fixed IP
address assignment, or a DNS server on your LAN.

If turning NetBT off causes browser problems, then you have a firewall somewhere
blocking port 445. OR you don't have name resolution working (and the error 53
will be back).

How about you run "net config server" and "net config workstation" along with
CDiag, for all computers? I'll look at your current CDiag logs, but I think
"net config" and browstat should be useful.

 

[lurker]

Carl,

A server is any computer providing shared data. Any Windows computer acts as a
server, even if it doesn't run a server OS, if it's running File & Printer
Sharing for Microsoft Windows.
<http://nitecruzr.blogspot.com/2005/05/simple-network-definition.html>
http://nitecruzr.blogspot.com/2005/05/simple-network-definition.html

If you're going to disable NetBT, you have to do it simultaneously on all
computers. All computer must support direct hosting of SMBs. All firewalls
have to pass microsoft-ds (port 445/tcp&udp). And you'll need either fixed IP
address assignment, or a DNS server on your LAN.

If turning NetBT off causes browser problems, then you have a firewall somewhere
blocking port 445.

How about you run "net config server" and "net config workstation" along with
CDiag, for all computers? I'll look at your current CDiag logs, but I think
"net config" and browstat should be useful.

Wow,
this article does not quote the contents when I "REPLY". I tried
several times.

Anyway..
....very impressive chuck!!
I stumbled around in Windows Live OneCare firewall, and added port 445
TCP/UDP both ways.

Now file sharing Works!

Hmmm... Microsoft engineers around the NetBIOS issues by bringing out
NetBT so we can perform file shares without using NetBIOS.

They even ship Windows XP HOME without NetBIOS.

Then they have this brainstorm to help with the Adware/Spyware
Virus/Worm problem, (which Internet Explorer and Active-X implemented
ease of spreading), and offered this very impressive "Windows Live
OneCare" program. I am very impressed... until now. By default it
kills file sharing using SMB simply because they did not default open
port 445.

Is that slick or what? <grin>

 

[lurker]

Wow,
this article does not quote the contents when I "REPLY". I tried
several times.

Anyway..
...very impressive chuck!!
I stumbled around in Windows Live OneCare firewall, and added port 445
TCP/UDP both ways.

Now file sharing Works!

Hmmm... Microsoft engineers around the NetBIOS issues by bringing out
NetBT so we can perform file shares without using NetBIOS.

They even ship Windows XP HOME without NetBIOS.

Then they have this brainstorm to help with the Adware/Spyware
Virus/Worm problem, (which Internet Explorer and Active-X implemented
ease of spreading), and offered this very impressive "Windows Live
OneCare" program. I am very impressed... until now. By default it
kills file sharing using SMB simply because they did not default open
port 445.

Is that slick or what? <grin>

Okay, so we don't need NetBT to do file sharing.
What do we give up?

The Browser, and Network Neighborhood (My Network Places)?

With the Browser and the world it supports, that convenience has quite a
substantial overhead. Right?

If a users skill set depends on a properly populated My Network Places,
etc. then all the trials and tribulations of NetBT systems configuration
go with the techie territory. Right?

 

[Chuck]

Okay, so we don't need NetBT to do file sharing.
What do we give up?

The Browser, and Network Neighborhood (My Network Places)?

With the Browser and the world it supports, that convenience has quite a
substantial overhead. Right?

If a users skill set depends on a properly populated My Network Places,
etc. then all the trials and tribulations of NetBT systems configuration
go with the techie territory. Right?

Carl,

Please don't confuse NetBIOS with NetBEUI. NetBIOS Over TCP is an application
interface, NetBEUI (installable yet not supported in Windows XP, not installable
in Vista) is a protocol. There are advantages and disadvantages to both.
<http://nitecruzr.blogspot.com/2005/07/windows-networking-and-alternate.html>
http://nitecruzr.blogspot.com/2005/07/windows-networking-and-alternate.html

Without NetBIOS Over TCP, we lose WINS and NetBIOS broadcast as a means of name
resolution.

So you tell me, since you are now testing direct hosting of SMB:
1) How do you have King-Daddy and Queenie talking to each other? Name
resolution, or fixed IP addresses with UNC mapped shares?
2) Is Network Neighbourhood empty now?

Don't blame Microsoft for Windows Firewall not allowing this by default. The
best principle in security is to be as restrictive as possible, anybody who
needs less restrictions has to know how to apply the changes.

Direct hosting of SMBs is generally found in large LANs, where DNS is used for
name resolution. Generally, that will have a domain controller, Active
Directory, and AD settings to open 445 uniformly. It's good to try this out,
but not a lot of SOHO folks will ever do that. But it's good to take a step
into the unknown sometimes.
<http://nitecruzr.blogspot.com/2006/06/solving-problems-lightweight-tutorial.html>
http://nitecruzr.blogspot.com/2006/06/solving-problems-lightweight-tutorial.html

So thanks for taking this step with me. Please post a couple more times, during
the week, and let us know that it's working (or not). I'm hoping to have this
documented over the weekend.

The techie territory is large, and getting larger every day.

 

[Chuck]

Wow,
this article does not quote the contents when I "REPLY". I tried
several times.

Anyway..
...very impressive chuck!!
I stumbled around in Windows Live OneCare firewall, and added port 445
TCP/UDP both ways.

Now file sharing Works!

Hmmm... Microsoft engineers around the NetBIOS issues by bringing out
NetBT so we can perform file shares without using NetBIOS.

They even ship Windows XP HOME without NetBIOS.

Then they have this brainstorm to help with the Adware/Spyware
Virus/Worm problem, (which Internet Explorer and Active-X implemented
ease of spreading), and offered this very impressive "Windows Live
OneCare" program. I am very impressed... until now. By default it
kills file sharing using SMB simply because they did not default open
port 445.

Is that slick or what? <grin>

Way to go, Carl! Patience and persistence pays off!!

But having gotten here, let's try and learn from the solution. Comments below.

 

[lurker]

Carl,

Please don't confuse NetBIOS with NetBEUI. NetBIOS Over TCP is an application
interface, NetBEUI (installable yet not supported in Windows XP, not installable
in Vista) is a protocol. There are advantages and disadvantages to both.
<http://nitecruzr.blogspot.com/2005/07/windows-networking-and-alternate.html>
http://nitecruzr.blogspot.com/2005/07/windows-networking-and-alternate.html

Without NetBIOS Over TCP, we lose WINS and NetBIOS broadcast as a means of name
resolution.

So you tell me, since you are now testing direct hosting of SMB:
1) How do you have King-Daddy and Queenie talking to each other? Name
resolution, or fixed IP addresses with UNC mapped shares?
2) Is Network Neighbourhood empty now?

Don't blame Microsoft for Windows Firewall not allowing this by default. The
best principle in security is to be as restrictive as possible, anybody who
needs less restrictions has to know how to apply the changes.

Direct hosting of SMBs is generally found in large LANs, where DNS is used for
name resolution. Generally, that will have a domain controller, Active
Directory, and AD settings to open 445 uniformly. It's good to try this out,
but not a lot of SOHO folks will ever do that. But it's good to take a step
into the unknown sometimes.
<http://nitecruzr.blogspot.com/2006/06/solving-problems-lightweight-tutorial.html>
http://nitecruzr.blogspot.com/2006/06/solving-problems-lightweight-tutorial.html

So thanks for taking this step with me. Please post a couple more times, during
the week, and let us know that it's working (or not). I'm hoping to have this
documented over the weekend.

The techie territory is large, and getting larger every day.

How is it working?
Fine... or sort of...

To get name resolution of my three machines (domains), I added each to
the each HOSTS file.

I get the perception that system initialization is moderately quicker
now (Browser has nothing to do?)

Network Neighborhood and My Network Places are empty. It doesn't take
long to populate a nothing!

I think I like it. However, I have a dialog going with Kerio right now,
so I will have to make my environment compatible with the problem I
opened. I'll make that another thread when I can make more sense of some
inconsistencies in testing environment setup. I definitely have
questions with the Browser negotiations and conclusions.

 

[Chuck]

How is it working?
Fine... or sort of...

To get name resolution of my three machines (domains), I added each to
the each HOSTS file.

I get the perception that system initialization is moderately quicker
now (Browser has nothing to do?)

Network Neighborhood and My Network Places are empty. It doesn't take
long to populate a nothing!

I think I like it. However, I have a dialog going with Kerio right now,
so I will have to make my environment compatible with the problem I
opened. I'll make that another thread when I can make more sense of some
inconsistencies in testing environment setup. I definitely have
questions with the Browser negotiations and conclusions.

Kewl, Carl. Keep at it, and ask lots of questions. I think we're both learning
here.

 

[Chuck]

How is it working?
Fine... or sort of...

To get name resolution of my three machines (domains), I added each to
the each HOSTS file.

I get the perception that system initialization is moderately quicker
now (Browser has nothing to do?)

Network Neighborhood and My Network Places are empty. It doesn't take
long to populate a nothing!

I think I like it. However, I have a dialog going with Kerio right now,
so I will have to make my environment compatible with the problem I
opened. I'll make that another thread when I can make more sense of some
inconsistencies in testing environment setup. I definitely have
questions with the Browser negotiations and conclusions.

Carl,

When you opened port 445, how did you do that? Did you specify it by number, or
did you enable the File and Printer Sharing exception?

 

[lurker]

Carl,

When you opened port 445, how did you do that? Did you specify it by number, or
did you enable the File and Printer Sharing exception?

...., in Firewall Tab /
Advanced settings /
Ports and Protocalls / "Not use NetBT"

http://rpchc.com/kingdom/WindowsLiveOneCare-445.htm

 

[Chuck]

..., in Firewall Tab /
Advanced settings /
Ports and Protocalls / "Not use NetBT"

http://rpchc.com/kingdom/WindowsLiveOneCare-445.htm

OK, there's 2 useful settings.
# Not use NetBT.
# Printe and file sharing local network (sic)

I am presuming that you didn't photoshop the pics?

So what was checked from the start? When you were doing all the diagnosing?
What we have here is a 2 selection process to enable file and printer sharing,
with NetBT (137 - 139) and / or SMB direct (445). Crude and confusing - typical
M$ first attempt.

Normal Windows Firewall has one selection:
# File and Printer Sharing exception

I would prefer that you get file sharing using NetBT working first - that's the
supported solution, and gives the most functionality. Please clear the first
("Not use NetBT"), and check the second ("Printe and file sharing local
network"). Wait an hour or so, and see what you see.

It's your network though.

 

[lurker]

OK, there's 2 useful settings.
# Not use NetBT.
# Printe and file sharing local network (sic)

I am presuming that you didn't photoshop the pics?

So what was checked from the start? When you were doing all the diagnosing?
What we have here is a 2 selection process to enable file and printer sharing,
with NetBT (137 - 139) and / or SMB direct (445). Crude and confusing - typical
M$ first attempt.

Normal Windows Firewall has one selection:
# File and Printer Sharing exception

I would prefer that you get file sharing using NetBT working first - that's the
supported solution, and gives the most functionality. Please clear the first
("Not use NetBT"), and check the second ("Printe and file sharing local
network"). Wait an hour or so, and see what you see.

It's your network though.

I am unclear what you are looking for regarding "photoshop the pics."
Of course the pics on the web site are there, saved from a photo editor,
and can be saved by anyone. I can get you anything else you want quite
quickly.

Windows Live OneCare firewall... It's just a firewall. With the
referenced image
http://rpchc.com/kingdom/images/WLOC_settings_ports.gif
you see both "printe and file sharing..." and "Not use NetBT" actually
checked. I don't know what Microsoft's intention is, but that screen is
from KING-DADDY (Since Windows Live OneCare is not for Windows 2000). I
have switched back to NetBT and "My Network Places" function works on
both systems. QUEENIE is Master Browser and running Kerio.

Apparently Live OneCare firewall currently is allowing both methods to
work, in both directions, with my current settings as captured. Net Use
drive mapping also is working.

As for Waiting an hour, Everything was working good in about 10 minutes
after enabling NetBT on all machines. Changing the Live OneCare
firewall had not been done yet.

For consistency of Documentation and experience I have now unchecked the
box.

 

[Chuck]

I am unclear what you are looking for regarding "photoshop the pics."
Of course the pics on the web site are there, saved from a photo editor,
and can be saved by anyone. I can get you anything else you want quite
quickly.

Windows Live OneCare firewall... It's just a firewall. With the
referenced image
http://rpchc.com/kingdom/images/WLOC_settings_ports.gif
you see both "printe and file sharing..." and "Not use NetBT" actually
checked. I don't know what Microsoft's intention is, but that screen is
from KING-DADDY (Since Windows Live OneCare is not for Windows 2000). I
have switched back to NetBT and "My Network Places" function works on
both systems. QUEENIE is Master Browser and running Kerio.

Apparently Live OneCare firewall currently is allowing both methods to
work, in both directions, with my current settings as captured. Net Use
drive mapping also is working.

As for Waiting an hour, Everything was working good in about 10 minutes
after enabling NetBT on all machines. Changing the Live OneCare
firewall had not been done yet.

For consistency of Documentation and experience I have now unchecked the
box.

So you're saying that the Windows OneCare (aka "Wanker") settings, having been
corrected, allow file sharing to work using NetBT?

You did see the winkie face next to the photoshop question? Sorry. I just
couldn't believe that Microsoft would release Wanker with such a stupid spelling
(to say nothing of the phrasing). It's been called "File and Printer Sharing"
for so long, how did they come up with "Printe and file sharing local network"??
Maybe the "Wanker" homonym is appropriate after all.

As to the one hour, it sometimes takes as much as 52 minutes (or maybe 48
minutes) for master browser elections to take place. So now you have a stable
master browser, everything running NetBT, and everything working? Which means
the problem was OneCare settings?

 

[lurker]

So you're saying that the Windows OneCare (aka "Wanker") settings, having been
corrected, allow file sharing to work using NetBT?

You did see the winkie face next to the photoshop question? Sorry. I just
couldn't believe that Microsoft would release Wanker with such a stupid spelling
(to say nothing of the phrasing). It's been called "File and Printer Sharing"
for so long, how did they come up with "Printe and file sharing local network"??
Maybe the "Wanker" homonym is appropriate after all.

As to the one hour, it sometimes takes as much as 52 minutes (or maybe 48
minutes) for master browser elections to take place. So now you have a stable
master browser, everything running NetBT, and everything working? Which means
the problem was OneCare settings?

On KING-DADDY )XP HOME), Marking WINS/"Disable NetBIOS over TCP/IP"
neutered "My Network Places", but File Sharing did not function until I
fixed the KING-DADDY firewall ("Live OneCare").

On the other hand, when I restored function of NetBT by marking
WINS/"Enable NetBIOS over TCP/IP", I did NOT have to change anything in
the firewall configuration... but (later) just to return all settings
back to the way it was before the SMB discussion herein, I unchecked the
firewall configuration setting "Printe and file sharing local network"

In other words, if you had not asked the question, I would have left the
firewall settings alone.

 

[lurker]

So you're saying that the Windows OneCare (aka "Wanker") settings, having been
corrected, allow file sharing to work using NetBT?

You did see the winkie face next to the photoshop question? Sorry. I just
couldn't believe that Microsoft would release Wanker with such a stupid spelling
(to say nothing of the phrasing). It's been called "File and Printer Sharing"
for so long, how did they come up with "Printe and file sharing local network"??
Maybe the "Wanker" homonym is appropriate after all.

As to the one hour, it sometimes takes as much as 52 minutes (or maybe 48
minutes) for master browser elections to take place. So now you have a stable
master browser, everything running NetBT, and everything working? Which means
the problem was OneCare settings?

On KING-DADDY )XP HOME), Marking WINS/"Disable NetBIOS over TCP/IP"
neutered "My Network Places", but File Sharing did not function until I
fixed the KING-DADDY firewall ("Live OneCare").

On the other hand, when I restored function of NetBT by marking
WINS/"Enable NetBIOS over TCP/IP", I did NOT have to change anything in
the firewall configuration... but (later) just to return all settings
back to the way it was before the SMB discussion herein, I unchecked the
firewall configuration setting "Printe and file sharing local network"

In other words, if you had not asked the question, I would have left the
firewall settings alone.

 

[lurker]

So you're saying that the Windows OneCare (aka "Wanker") settings, having been
corrected, allow file sharing to work using NetBT?

You did see the winkie face next to the photoshop question? Sorry. I just
couldn't believe that Microsoft would release Wanker with such a stupid spelling
(to say nothing of the phrasing). It's been called "File and Printer Sharing"
for so long, how did they come up with "Printe and file sharing local network"??
Maybe the "Wanker" homonym is appropriate after all.

As to the one hour, it sometimes takes as much as 52 minutes (or maybe 48
minutes) for master browser elections to take place. So now you have a stable
master browser, everything running NetBT, and everything working? Which means
the problem was OneCare settings?

On KING-DADDY )XP HOME), Marking WINS/"Disable NetBIOS over TCP/IP"
neutered "My Network Places", but File Sharing did not function until I
fixed the KING-DADDY firewall ("Live OneCare").

On the other hand, when I restored function of NetBT by marking
WINS/"Enable NetBIOS over TCP/IP", I did NOT have to change anything in
the firewall configuration... but (later) just to return all settings
back to the way it was before the SMB discussion herein, I unchecked the
firewall configuration setting "Printe and file sharing local network"

In other words, if you had not asked the question, I would have left the
firewall settings alone.