Joing a domain 1

[allroy]

Hi, all!

I have a dilemna here, and I hope someone will be able to help.

We have just set up a W2K domain, and deployed it in our main building. Everything runs A-OK. However, we have a second location that we would like to join to this domain, to cut down on administration, and share our broadband connection.

Unfortunately, whenever we try to connect to the domain, we get an error that a DC cannot be found. This is really strange, as we can ping the DC, and are able to connect to the proxy running on the DC. We tried setting up a BDC at the location, but could not connect to the PDC.

Our main building has an IP range of 192.168.100.x, subnet 255.255.255.0. The other building is 192.168.102.x, subnet 255.255.255.0. There is a 56K pipe with routers at both ends connecting the buildings.

We would like to start using ISA to share the connection, with NAT, and administrate everything through AD, but this really puts a snarl on things.

Hope someone can help! Thanks!

 

[FilthPig]

Set up a Win2k DNS server at the second location, and have it host secondary zones replicated from the main site's DNS server(s). Marc Creviere

 

[allroy]

Thanks! I have the DNS server up and running, and replicating fine. However, it is failing on name resolution. Any suggestions?

 

[FilthPig]

Is the standard primary zone on the first server allowing dynamic updates? To check, Right-click on your server in the DNS console, select properties and it's on the General tab. Make sure Allow Dynamic Updates is set to yes.

Are you able to use nslookup to resolve the name at least? Marc Creviere

 

[allroy]

Everything is fine on this end. I had set everything up for dynamic updates.

I have the Reverse Lookup zone set up as 198.162.x, with domains for 100 and 102.

Nslookup shows that the server is working, but can't resolve the domain name.

 

[FilthPig]

So you have a DNS server in the second location, it's getting the zone information for your domain's forward lookup zone, but lookup requests to that zone are failing? Do you have the client machines pointing to this new DNS server? Marc Creviere

 

[C5Thunder]

Temporarily point your server at the second site to your primary dns and see if it works. You said you have proxy on the second DC, do you know if it is blocking access.

Also, check your reverse lookup zones, from your post it seems that you have the numbers reversed (or just a typo)

 

[allroy]

Thanks for all the suggestions.

It turned out that after we had hooked up our DSL here at the main building, the main DNS server on the DC was our ISP! DNS was working fine for this building, but that's why the other building couldn't resolve names.