Unable To Browser Domain Across Router

[jamo]

Hello there

Here is my problem i have 3 domains, 2 domains in building (1) and another one in building (2). When i try browse the domain in building (2) from building (1) i am unable to see it, but if i do start, find, computer i am
able to find the PC's in building (2). Does anyone know a reason for this ?


Jamo

There are 2 pc in building (1) on the domain in building (2)could this be causing the problem ?

 

[ShackDaddy]

Are all three domains sharing a single WINS server? If not, special measures will have to be taken to allow a universal browsing environment. Let me know if you aren't using WINS and I will tell you how to go about setting up the non-WINS browsing environment using LMHOSTS files.

 

[jamo]

Cheers for replying shack daddy!!!

Did not know if all that building 1, 2 blah blah was gonna make sense, no all three domains do not share a single wins server, each domain has its own wins server. How tricky is it to setup a universal browsing environment ?!?

Cheers again James

 

[ghostrider3]

Are you using trust relationships for the domains?

 

[jamo]

Yep all the trust relationships are in order, each server has the other two domains

 

[ShackDaddy]

Solution 1: Well, the best and easiest thing you could do is have all three of your domains share the same WINS server. There is no compelling reason why they shouldn't have been set up that way in the first place, if you wanted to have all the networks visible to each other. Two of the domains could still use DHCP scope options to point their clients to a central WINS server if you like, otherwise we have to go with solution 2 of 3. I personally don't recommend going the alternate route of using WINS push-pull replication to consolidate all WINS information, but many average administrators have done (and still do) so successfully.

Solution 2: Open the WINS Manager on each WINS server and add entries for the domain controllers in the other domains. Here's how to do it. Go to Mappings -> Static Mappings. Choose Add Mappings, pick Domain Name in the radio buttons on the right, fill in one of the other domain names and enter each of that domain's domain controllers in the list of IP addresses. Click Add when you are finished. Do the same thing for the other domain. This should allow the browsing environment in each domain to expand its boundaries into the other domains. After a while you should see the names of the other domains showing up in Network Neighborhood. What's going on behind the scenes here is that all the domain master browsers are being introduced to each other, put into each other's personal address books, so to speak.

Solution 3. Involves adding entries to LMHOSTS files. This is the WINS-less solution, but I still occasionally use versions of it for various purposes even within a WINS environment. On each domain controller, you would edit the c:\winnt\system32\drivers\etc\lmhosts file (first removing the .sam extension) and add entries that look like the following. (When I use %name% type notations, I'm assuming you will substitute the proper information instead of the %xxxx%.)

10.10.2.5 %domann2PDCname% #PRE #DOM:%domain1%
10.10.3.5 %domain3PDCname% #PRE #DOM:%domain2%
10.10.3.6 %domain3BDCname% #PRE #DOM:%domain2%

Looking at the text in the LMHOSTS file should explain the syntax to you. Once you've edited the files and saved them, run 'nbtstat -R' on each server and then 'nbtstat -c' to view the newly cached information. This solution is the text-file based equivalent of solution 2.

 

[techieKid]

Hi,

I just installed WINS on my BDC.
However, I wasn't able to browse the domain from my network neighbourhood unless I install NetBEUI on my client machine.
I tried configuring my TCP/IP settings to specify my WINS server on my client machine without installing NetBEUI. This doesn't work.
MUST NetBEUI work with WINS in order to browse the domain?
Strange??

Thanks in advance!