• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 511
  • Last Modified:

One Windows domain, two IP Ranges. Possible?

Dear All,

We have a simple network (1 DC, 2 member servers, a database server (db1), an onsite failover (db2) and some 20 clients) on the range, linked to the internet via a Watchguard Firebox X Core.

For failover reasons, we are installing a database server (db3) with our files and SQL database in a datacenter. The IP range in the DC is .

In the DC, there's also a Watchguard Firebox and there's a VPN link between both.

My issue is that I want to include the db3 into my on-site domain.

How can I do that? I already made it a member while it was on the 192.168.245.x range and then changed the IP address to, but the db3 cannot reach the domain, even though there is IP connectivity (SMB/PING/...)

best regards,

  • 4
  • 3
1 Solution
DB3 will need to use the domain dns server. This will allow it to find the domain. Will DB3 become a DC? If so make sure to add a new site in AD.
nd2uManaging DirectorAuthor Commented:
It's set up to use the domain DNS server, but it's not necessary that it becomes a domain controller

(DC = DataCenter)
Use NSlookup to make sure that it is correctly resolving dns
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

nd2uManaging DirectorAuthor Commented:
NSLookup correctly connects to our DNS server, which is also the Domain Controller.

When I lookup the name of my Domain Controller (including the domain name), it correctly resolves to the IP address of the dom.contr.

If I only use the computer name, it does not resolve.
nd2uManaging DirectorAuthor Commented:
I took the DB3 out of the domain and tried to put it back in again.

Then I got the following message:

A domain controller for the domain XXXX could not be contacted.


DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain XXX.

The query was for the SRV record for

the following domain controllers were identified by the query:


Common causes of this error include:

- Host (A) records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses.

--> I can resolve the ipname of the domain controller... So this should not be the problem, right?

- Domain controllers registered in DNS are not connected to the network or are not running

--> it is running


nd2uManaging DirectorAuthor Commented:

problem solved.

I still had the DB3 on-site and connected it to a different port on my watchguard for test purposes.

Turned out that the firewall blocked access to the 389 port... Opened it and it's working fine.

Good fix
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now