Microsoft Windows Network Browsing

I have set up one domain that have one Windows 2003 SP1 Domain controller.
This domain is on of many in the enterprise. There is one root domain and
several regional office domains. In one domain I have a problem browsing the
network. There is no problem in other domains, just with these one.
I can not see all computers in these domain only few of them. I was told
that the clients in this domain, have the same problem.

Domain computers have regular names, the descriptions of computers have a
lot of non regular characters, witch are display ok on local computer on DC
are displayed as square.
All client computers are Windows XP with SP2.
I set up GPO to disable Firewall.

Today I find that from root domain, I can not brows that problematic domain
, when I brows network , I get the following error. Domainxxx is not
accessible. The specified network name is no longer available. I restart
browser service on DC in problematic domain. With no help. The problem is
continuing from start.

Domain controller has three network addresses, but only one network card.
The only error that is related to browser service is :
Event Type: Warning
Event Source: MRxSmb
Event Category: None
Event ID: 3019
Date: 2005-07-20
Time: 11:26:52
User: N/A
Computer: DCxxx
Description:
The redirector failed to determine the connection type.


For witch is Microsoft says that I can safely ignore it.
I was told, but I could not check on remote clients if thay have netbios
enabled. I was told that thay have. Server does have enabled NetBIos. Server
does not run firewall. Locally all client and servers are connected on the
same switch. There is VPN connection to root domain.
All test in dcdiag and netdiag are successful. Domain is working order…
But I have to make all client visible in local domain.

Thank you for replay.

In a routed TCP/IP environment you will need some form
of NetBIOS name resolution in order for this to work. You
could lmhosts or an easier / dynamic form such as WINS.

"Mr.B" <(E-Mail Removed)> wrote in message news:
>I have set up one domain that have one Windows 2003 SP1 Domain controller.
> This domain is on of many in the enterprise. There is one root domain and
> several regional office domains. In one domain I have a problem browsing
> the
> network. There is no problem in other domains, just with these one.
> I can not see all computers in these domain only few of them. I was told
> that the clients in this domain, have the same problem.
>
> Domain computers have regular names, the descriptions of computers have a
> lot of non regular characters, witch are display ok on local computer on
> DC
> are displayed as square.
> All client computers are Windows XP with SP2.
> I set up GPO to disable Firewall.
>
> Today I find that from root domain, I can not brows that problematic
> domain
> , when I brows network , I get the following error. Domainxxx is not
> accessible. The specified network name is no longer available. I restart
> browser service on DC in problematic domain. With no help. The problem is
> continuing from start.
>
> Domain controller has three network addresses, but only one network card.
> The only error that is related to browser service is :
> Event Type: Warning
> Event Source: MRxSmb
> Event Category: None
> Event ID: 3019
> Date: 2005-07-20
> Time: 11:26:52
> User: N/A
> Computer: DCxxx
> Description:
> The redirector failed to determine the connection type.
>
>
> For witch is Microsoft says that I can safely ignore it.
> I was told, but I could not check on remote clients if thay have netbios
> enabled. I was told that thay have. Server does have enabled NetBIos.
> Server
> does not run firewall. Locally all client and servers are connected on the
> same switch. There is VPN connection to root domain.
> All test in dcdiag and netdiag are successful. Domain is working order.
> But I have to make all client visible in local domain.
>
> Thank you for replay.
>

I have set up WINS. And i set up replication with wins server in root domain.

"Michael Giorgio - MS MVP" wrote:

> In a routed TCP/IP environment you will need some form
> of NetBIOS name resolution in order for this to work. You
> could lmhosts or an easier / dynamic form such as WINS.
>
> "Mr.B" <(E-Mail Removed)> wrote in message news:
> >I have set up one domain that have one Windows 2003 SP1 Domain controller.
> > This domain is on of many in the enterprise. There is one root domain and
> > several regional office domains. In one domain I have a problem browsing
> > the
> > network. There is no problem in other domains, just with these one.
> > I can not see all computers in these domain only few of them. I was told
> > that the clients in this domain, have the same problem.
> >
> > Domain computers have regular names, the descriptions of computers have a
> > lot of non regular characters, witch are display ok on local computer on
> > DC
> > are displayed as square.
> > All client computers are Windows XP with SP2.
> > I set up GPO to disable Firewall.
> >
> > Today I find that from root domain, I can not brows that problematic
> > domain
> > , when I brows network , I get the following error. Domainxxx is not
> > accessible. The specified network name is no longer available. I restart
> > browser service on DC in problematic domain. With no help. The problem is
> > continuing from start.
> >
> > Domain controller has three network addresses, but only one network card.
> > The only error that is related to browser service is :
> > Event Type: Warning
> > Event Source: MRxSmb
> > Event Category: None
> > Event ID: 3019
> > Date: 2005-07-20
> > Time: 11:26:52
> > User: N/A
> > Computer: DCxxx
> > Description:
> > The redirector failed to determine the connection type.
> >
> >
> > For witch is Microsoft says that I can safely ignore it.
> > I was told, but I could not check on remote clients if thay have netbios
> > enabled. I was told that thay have. Server does have enabled NetBIos.
> > Server
> > does not run firewall. Locally all client and servers are connected on the
> > same switch. There is VPN connection to root domain.
> > All test in dcdiag and netdiag are successful. Domain is working order.
> > But I have to make all client visible in local domain.
> >
> > Thank you for replay.
> >
>
>
>

All clients on your LAN are pointing towards your local
WINS server and all remote WINS servers are configured
to push and pull with 1 single main WINS server in a hub
and spoke configuration? If so then attempt to map to a
share from your DMB (domain master browser) to each
remote DMB. The DMB in each domain is the PDC or
PDC emulator role holder.

"Mr.B" <(E-Mail Removed)> wrote in message news:
>I have set up WINS. And i set up replication with wins server in root
>domain.
>

Yes DC is WINS server in local domain and it replicate in both side is
push/pull configuration.
I would like at least fix, local browsing. Primary I do not need to see
computers by NetBIOS name from root domain.
SO i need to fix local browsing, remote browsing I can fix, because I need
only to have NetBIOS name for DC.

Thank you.


"Michael Giorgio - MS MVP" wrote:

> All clients on your LAN are pointing towards your local
> WINS server and all remote WINS servers are configured
> to push and pull with 1 single main WINS server in a hub
> and spoke configuration? If so then attempt to map to a
> share from your DMB (domain master browser) to each
> remote DMB. The DMB in each domain is the PDC or
> PDC emulator role holder.
>
> "Mr.B" <(E-Mail Removed)> wrote in message news:
> >I have set up WINS. And i set up replication with wins server in root
> >domain.
> >
>
>
>

Without proper name resolution e.g., NetBIOS name
resoltion, proper browsing cannot occur. Make sure
you do not have a multihomed (2 NICs) DC or
master browser acting as a router on your local LAN.
Also make sure your router(s) are not forwarding
broadcasts via some form of NetBIOS helper; this
causes machines to register with a remote SMB instead
of the local SMB. You could also check the system
log of the event viewer on your PDC to see if there
are any browse related errors. Finally you can use
the following application:

Description of NetBIOS Browsing Console (Browcon.exe)
http://support.microsoft.com/default...b;en-us;818092

"Mr.B" <(E-Mail Removed)> wrote in message news:...
> Yes DC is WINS server in local domain and it replicate in both side is
> push/pull configuration.
> I would like at least fix, local browsing. Primary I do not need to see
> computers by NetBIOS name from root domain.
> SO i need to fix local browsing, remote browsing I can fix, because I need
> only to have NetBIOS name for DC.
>

I have single network card. Domain is connected with VPN to central site.
Clients are registered with local WINS, on DC.
I will check utility.

Thank you.

"Michael Giorgio - MS MVP" wrote:

> Without proper name resolution e.g., NetBIOS name
> resoltion, proper browsing cannot occur. Make sure
> you do not have a multihomed (2 NICs) DC or
> master browser acting as a router on your local LAN.
> Also make sure your router(s) are not forwarding
> broadcasts via some form of NetBIOS helper; this
> causes machines to register with a remote SMB instead
> of the local SMB. You could also check the system
> log of the event viewer on your PDC to see if there
> are any browse related errors. Finally you can use
> the following application:
>
> Description of NetBIOS Browsing Console (Browcon.exe)
> http://support.microsoft.com/default...b;en-us;818092
>
> "Mr.B" <(E-Mail Removed)> wrote in message news:...
> > Yes DC is WINS server in local domain and it replicate in both side is
> > push/pull configuration.
> > I would like at least fix, local browsing. Primary I do not need to see
> > computers by NetBIOS name from root domain.
> > SO i need to fix local browsing, remote browsing I can fix, because I need
> > only to have NetBIOS name for DC.
> >
>
>
>

On 7/21/2005 13:45, Mr.B wrote:
> I have single network card. Domain is connected with VPN to central site.
> Clients are registered with local WINS, on DC.
> I will check utility.

Couple more things to check:

Is TCP port 42 being blocked by a router inbetween WINS servers?

Is the WAN link slower than 256Kb? In this case, you should configure
lmhosts files on the WINS servers so that they can replicate reliably.

~Jason

--

Well yes, but i would like to fix local bowsing first...

"Jason Gurtz" wrote:

> On 7/21/2005 13:45, Mr.B wrote:
> > I have single network card. Domain is connected with VPN to central site.
> > Clients are registered with local WINS, on DC.
> > I will check utility.
>
> Couple more things to check:
>
> Is TCP port 42 being blocked by a router inbetween WINS servers?
>
> Is the WAN link slower than 256Kb? In this case, you should configure
> lmhosts files on the WINS servers so that they can replicate reliably.
>
> ~Jason
>
> --
>