Network browse problem

[Clayton Sutton]

Hello everyone,

We are running a Win2k3 domain. Our forest has two domains. It would seem
that I can not browse the other domain. If I try it from my domain
controllers it works just fine. However, when I try it from my workstation
(XP Pro. sp2) I can not access it via "My Network Places". Anyone have any
idea what the problem is. It seems that none of our Admins can do it.


Clayton

 

[Paul Bergson]

Browsing is a wins issue. Does your client have access to the wins info
from the foreign domain? Both domains can use the same wins server but the
client needs to point to it. If they have seperate wins servers then you
will have to replicate wins between domains.

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Clayton Sutton]

We don't use WINS on our network.


Clayton

Browsing is a wins issue. Does your client have access to the wins info
from the foreign domain? Both domains can use the same wins server but
the client needs to point to it. If they have seperate wins servers then
you will have to replicate wins between domains.

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no
rights.

 

[Simas Kvilius]

Probably browsing is because other domain is on other subnet (broadcast
scope) and NetBIOS brodcasts aren't forwarded by router (NetBIOS naming are
vital for browsing it can be implenemted by client broadcasts or by wins
server).

 

[Michael Giorgio - MS MVP]

Assuming both domains are on the same tcp/ip subnet this
isn't a WINS issue. What error are the clients receiving when
attempting to browse?

 

[Paul Bergson]

Are you on more than one sub-net? I'm assuming so, if you are then you will
need wins to browse.

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Clayton Sutton]

Yes we are.


Clayton

Are you on more than one sub-net? I'm assuming so, if you are then you
will need wins to browse.

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no
rights.

 

[Paul Bergson]

You need wins or you can only browse the subnet your workstation resides on.

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Bill Grant]

Let's summarise what has been covered.

1. If they are all on the same IP subnet, it should just work. The master
browsers will find each other by broadcast and a merged browse list will be
built.

2. If they are separated by a router or WAN link, it will not work without
some way to resolve Netbios names between subnets. Broadcasts are blocked,
so you need WINS to allow the browse masters to find each other. The browser
service is NT legacy, so it relies on Netbios names, not DNS.

The standard tool to use to debug browser problems is browstat. This is
included in the support tools. The description of the browser service and
further links are in KB188001. There is a troubleshooter in KB188305 .

The most common problem with the browser service (apart from the lack of
WINS in routed networks) is a multihomed browse master. This includes remote
access servers, since they become multihomed as soon as a remote access
client connects. Symptoms of multihomed browsers is dicussed in KB191611 .
Problems with remote access servers is dicussed in KB292822 .