Here is the output of BROWSTAT STATUS:
Status for domain GRIMARD on transport
\Device\NetBT_Tcpip_{FF3CB40B-D4BB-429A-A88F-7E47F978AE97}
Browsing is active on domain.
Master browser name is: FICHIERS2
Master browser is running build 3790
3 backup servers retrieved from master FICHIERS2
\\FICHIERS2
\\DC1
\\TERMSERV
There are 99 servers in domain GRIMARD on transport
\Device\NetBT_Tcpip_{FF3CB40B-D4BB-429A-A88F-7E47F978AE97}
There are 4 domains in domain GRIMARD on transport
\Device\NetBT_Tcpip_{FF3CB40B-D4BB-429A-A88F-7E47F978AE97}
What does it mean ?
Thanks.
"Robert L. (MS-MVP)" <(E-Mail Removed)> wrote:
> Do a simple test. Use browstat.exe to check the master browser.
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> "ThePro" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> We use AD-integrated DNS with dynamic updates from the client computers,
>> so it must be what makes browsing works.
>>
>> ThePro
>>
>> "Bill Grant" <not.available@online> wrote:
>>> If computer browsing works across the WAN I suspect you are somehow
>>> allowing broadcasts across the WAN or have a complex LMHOSTS setup. Name
>>> resolution can of course work without WINS if you are using DNS.
>>>
>>> The reason that browsing usually fails in a WAN is that it was
>>> originally designed to work on a single segment using broadcasts. It was
>>> later modified to work across multiple segments but WINS was required to
>>> allow the browse masters to communicate across routers.
>>>
>>> The computer browser service is essentially unchanged since NT4 and
>>> the old KB articles still apply. See KB 150800, 188001 and 188305 .
>>>
>>> "ThePro" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>> Hi,
>>>>
>>>> I find this article misleading because it implies that you need WINS to
>>>> have NetBIOS name resolution.
>>>>
>>>> Our network is made of multiple TCP/IP subnets linked by site-to-site
>>>> VPN. Cross-subnet computer browsing, Exchange and others NetBIOS naming
>>>> resolution-dependant services DO work and there is absolutely NO WINS
>>>> servers.
>>>>
>>>> I can't tell you exactly how it works, but it works ;-)
>>>>
>>>> All our computers are XP and the servers are a mix of 2003/2008.
>>>>
>>>> ThePro
>>>>
>>>> "Robert L. (MS-MVP)" <(E-Mail Removed)> wrote:
>>>>> Do you have WINS server? If not, installing WINS may help. Or check
>>>>> this search result.
>>>>> Does Windows 2000/2003 domain needs WINS
>>>>> Does Windows 2000/2003 domain needs WINS. Q1: Is there a
>>>>> definitive list of the services and operations that will no longer
>>>>> work in Windows 2003 Server if ...
>>>>> www.howtonetworking.com/server/wins1.htm
>>>>>
>>>>>
>>>>> --
>>>>> Bob Lin, MS-MVP, MCSE & CNE
>>>>> Networking, Internet, Routing, VPN Troubleshooting on
>>>>> http://www.ChicagoTech.net
>>>>> How to Setup Windows, Network, VPN & Remote Access on
>>>>> http://www.HowToNetworking.com
>>>>> "Todd" <(E-Mail Removed)> wrote in message
>>>>> news:C5DE29B3-1B0D-497B-9C41-(E-Mail Removed)...
>>>>>>I have a unique situation here and hope I can get it resolved soon as
>>>>>>it
>>>>>> involves backing up an exchange server.
>>>>>>
>>>>>> I appear to have a one way browsing issue between two windows 2003
>>>>>> domains.
>>>>>> I can see the domain I need to back up from the one domain controller
>>>>>> which
>>>>>> is in Colo A, it is a single server domain controller that runs BE12
>>>>>> and CPS,
>>>>>> it can see all the drives and files etc on the Exchange server that
>>>>>> is in
>>>>>> Colo B. However, the Exchange server and domain controller in Colo B
>>>>>> cannot
>>>>>> see the domain of the server in Colo A. I was able to get a trust
>>>>>> relationship between the two domains, but still have other issues I
>>>>>> believe
>>>>>> are related to not being able to see the domain from Colo B to Colo
>>>>>> A. I am
>>>>>> able to verify trusts from each DC, but unable to manage the opposing
>>>>>> DC from
>>>>>> each server. BE CPS cant connect to the services on the DC in Colo A,
>>>>>> but the
>>>>>> DC in Colo A was able to push install to the Exchange server. What
>>>>>> can I do
>>>>>> to resolve this? I believe currently the connection between the two
>>>>>> colos is
>>>>>> via a GRE tunnel over the internet until we get the DS3 brought up
>>>>>> between
>>>>>> them.
>>>>>
>>>>
>>>>
>>
>>
>