Unable to browse 2nd Domain

[Neily]

We have two domains (DOM1 and DOM2). All workstations are on DOM1 with 2 DCs and other servers. I can browse this domain fine from any workstation on server on that domain.

DOM2 contains our web servers and database servers and also has 2 DCs. From any server on DOM2 I can browse DOM1 and DOM2.

DOM2 uses two IP ranges 192.168.30.x and 192.168.50.x (both with SNM of 255.255.255.0) - 2nd DC of DOM1 has IP in 50.x range.

DOM1 uses IP range of 192.168.18.0 with SNM of 255.255.252.0

Until last week, when we replaced all DCs I was able to browse both domains from any computer in DOM1 but now I can't.

2nd DC in DOM1 (with 50.x IP) can browse both domains.

I've been googling (as I still will be) but everything I've tried doesn't work.

Any ideas??

Thanks

 

[markdmac]

How is DNS setup in each domain?

Can you ping machines via IP from each domain to the other?

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript

Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.

 

[Neily]

I can Ping all DCs and other servers form either domain.

Each site has DNS on each DC, and the workstations have a DNS entry for each domain.

Is that sufficient or do you have specifics?

 

[markdmac]

DNS Settings

Set all static NIC TCP/IP properties to only list internal DNS servers. In each domain, set the primary as a DNS server from that domain. Set the secondary as a DNS server from the second domain.

In DHCP set the DNS setting to internal DNS servers.

In DNS, configure ISP DNS on the forwarders tab.

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript

Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.

 

[Neily]

I have done all the above and still it does not allow me to browse the domain.

This is now urgent as we have new database servers that I cannot add to our backups because I cannot browse for them.

Any further ideas?

 

[Neily]

Ok, I'm still digging for an answer.

It turns out that any DOM1 server with an IP in the range of 192.168.50.x can browse both domains fine.

DOM1 can browse DOM1 but not DOM2. Domains are in seperate locations and are linked with a dedicated connection of 100Mbit. Servers mentioned above are in the other location.

DNS is configured as mentioned in here already.

I've tried giving DOM1 server in DOM1 location a 192.168.50.x IP, but that doesn't work.

I'm totally confused!! Using BROWSTAT I can't getmaster or getpdc. Get master returns Access Denied for both domains from any DC.

THANKS FOR ANY REPLIES (in advance!)

 

[pagy]

I don't suppose netbios over tcp/ip has been turned off on some network adapters has it????

Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[Neily]

yes its enabled both ends

 

[pagy]

Ok, it was a bit of a shot in the dark really.
Let me make sure I understand properly;
DOM1 = 192.168.18.0
From that network you cannot browse (I assume through things like network places) DOM2 which uses 192.168.30.x and 192.168.50.x.

But you can browse from DOM2 through to machines on DOM1

Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[Neily]

That is correct. You can browse machines in DOM2 via \\servername\sharename etc, and can ping all addresses over there.

I think its something to do with our master browser setup, but I ran out of time to completly check it. Got BROWSTAT working though!

 

[Neily]

Ok, little more info.

The DOM1 DC with 192.168.50.x that can browse DOM2 fine responds correctly when I run a BROWSTAT GETMASTER <transport> DOM2. When run with DOM1 it gives itself.

However, DOM1 DC with 192.168.18.x address responds with Unable to Get Master: Access Denied for DOM2 and with itself as Master for DOM1.

So any machine here can't "Get Master" and all say DC here is Master. But other DC says it is master.

I guess this isn't correct?! I'll keep digging, can anyone offer suggestions!

Oh, BTW a BROWSTAT VIEW <transport> DOM2 works from either DOM1 DC or DOM1 clients!