Re: BROWSTAT: ...Could not connect to registry, error = 53 (New question)

lurker wrote:
Chuck wrote:
On Fri, 23 Jun 2006 13:16:15 -0400, lurker <king-daddy@xxxxxxxxxxxxxx> wrote:

Chuck wrote:
On Fri, 23 Jun 2006 09:18:37 -0400, QUEENIE <clackey3@xxxxxxxxxxxxx~> wrote:

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

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)

--
cdiag stuff: http://rpchc.com/chuck/NetBT-disabled/

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>

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?

--
king-daddy
.

Relevant Pages

  • Re: BROWSTAT: ...Could not connect to registry, error = 53
    ... Unable to determine build of browser master: ... Now name resolution uses Server Message Blocks or SMBs. ... use the same SMB transport, or they will have no connection (causing, among ... NetBT setting, is not consistently effective. ...
    (microsoft.public.windowsxp.network_web)
  • Re: BROWSTAT: ...Could not connect to registry, error = 53
    ... I have found that I can resolve this message situation by mapping a drive share to the Master Browser machine. ... Now name resolution uses Server Message Blocks or SMBs. ... use the same SMB transport, or they will have no connection (causing, among ... NetBT setting, is not consistently effective. ...
    (microsoft.public.windowsxp.network_web)
  • Re: BROWSTAT: ...Could not connect to registry, error = 53 (New question)
    ... Unable to determine build of browser master: ... Now name resolution uses Server Message Blocks or SMBs. ... use the same SMB transport, or they will have no connection ... NetBT setting, is not consistently effective. ...
    (microsoft.public.windowsxp.network_web)
  • Re: BROWSTAT: ...Could not connect to registry, error = 53 (New question)
    ... Unable to determine build of browser master: ... use the same SMB transport, or they will have no connection ... NetBT setting, is not consistently effective. ... The network path was not found. ...
    (microsoft.public.windowsxp.network_web)
  • Re: BROWSTAT: ...Could not connect to registry, error = 53 (New question)
    ... I have found that I can resolve this message situation by mapping a drive share to the Master Browser machine. ... Now name resolution uses Server Message Blocks or SMBs. ... use the same SMB transport, or they will have no connection (causing, among ... NetBT setting, is not consistently effective. ...
    (microsoft.public.windowsxp.network_web)