Re: XP Networking HElp
- From: Chuck <none@xxxxxxxxxxx>
- Date: 18 May 2005 14:49:01 -0500
On Tue, 17 May 2005 18:31:03 -0700, KennyK <KennyK@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
>"KennyK" wrote:
>
>> I was reading the posts relating to the use of a master browser as I am
>> having the same problem with one way communication. Here is the browstat and
>> nbtstat from the Delta_Flyer and Voyageur. How can I get rid of the error 53?
>> C:\>browstat status
>> Status for domain MSHOME on transport
>> \Device\NetBT_Tcpip_{6B30428B-D49A-44E5-86
>> 9C-C83014DBF871}
>> Browsing is active on domain.
>> Master browser name is: VOYAGEUR
>> Could not connect to registry, error = 53 Unable to determine build
>> of br
>> owser master: 53
>> Unable to determine server information for browser master: 5
>> 1 backup servers retrieved from master VOYAGEUR
>> \\VOYAGEUR
>> There are 2 servers in domain MSHOME on transport
>> \Device\NetBT_Tcpip_{6B304
>> 28B-D49A-44E5-869C-C83014DBF871}
>> There are 1 domains in domain MSHOME on transport
>> \Device\NetBT_Tcpip_{6B304
>> 28B-D49A-44E5-869C-C83014DBF871}
>>
>> C:\>nbtstat -n
>>
>> Local Area Connection 2:
>> Node IpAddress: [192.168.1.100] Scope Id: []
>>
>> NetBIOS Local Name Table
>>
>> Name Type Status
>> ---------------------------------------------
>> DELTA_FLYER <00> UNIQUE Registered
>> MSHOME <00> GROUP Registered
>> DELTA_FLYER <20> UNIQUE Registered
>> MSHOME <1E> GROUP Registered
>>
>> Here is the Browstat status and nbstat from Voyageur:
>> C:\>browstat status
>>
>>
>> Status for domain MSHOME on transport \Device\NetBT_Tcpip_{99C1369C-B
>> AA-7D6ECEB8B578}
>> Browsing is active on domain.
>> Master browser name is: VOYAGEUR
>> Master browser is running build 2600
>> 1 backup servers retrieved from master VOYAGEUR
>> \\VOYAGEUR
>> There are 2 servers in domain MSHOME on transport \Device\NetBT_T
>> 69C-B122-4396-94AA-7D6ECEB8B578}
>> There are 1 domains in domain MSHOME on transport \Device\NetBT_T
>> 69C-B122-4396-94AA-7D6ECEB8B578}
>>
>> C:\>nbtstat -n
>>
>> Local Area Connection:
>> Node IpAddress: [192.168.1.99] Scope Id: []
>>
>> NetBIOS Local Name Table
>>
>> Name Type Status
>> ---------------------------------------------
>> VOYAGEUR <00> UNIQUE Registered
>> VOYAGEUR <20> UNIQUE Registered
>> MSHOME <00> GROUP Registered
>> MSHOME <1E> GROUP Registered
>> MSHOME <1D> UNIQUE Registered
>> ..__MSBROWSE__.<01> GROUP Registered
>>
>> C:\>
>Got the answer in the post for "Subject: Re: Can't access other computer or
>printers". Thanks to Chuck for the anonymous bit in the registry.
Kenny,
It's surprising how often the restrictanonymous setting comes up as a solution.
Thanks for the feedback.
--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.
.
- References:
- XP Networking HElp
- From: KennyK
- RE: XP Networking HElp
- From: KennyK
- XP Networking HElp
- Prev by Date: Re: home lan puzzler
- Next by Date: Re: Reverting Wireless to Wired Network.
- Previous by thread: RE: XP Networking HElp
- Next by thread: XP Home and XP Pro
- Index(es):
Relevant Pages
|
