I have two peplnk 210 routers used to connect two offices that need to share the same network and domain.
Peplnk IP: 192.168.1.1
Peplink IP 192.168.2.1
Office 1 has several servers, including a Windows 2012 R2 Active Directory Domain Controller (AD DC) as well as DNS on the same server (192.168.1.22). This is obviously on the 192.168.1.0 subnet.
No machines in Office 2 can join the domain though I can successfully ping the DC.
When attempting ping the DC from a Windows 7 workstation (192.168.2.137) in Office 2 I get a valid response:
Pinging 192.168.1.220 with 32 bytes of data:
Reply from 192.168.1.220: bytes=32 time=30ms TTL=126
Reply from 192.168.1.220: bytes=32 time=26ms TTL=126
Reply from 192.168.1.220: bytes=32 time=25ms TTL=126
Reply from 192.168.1.220: bytes=32 time=37ms TTL=126
Ping statistics for 192.168.1.220:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 37ms, Average = 29ms
However, when attempting to join the domain, I get an error that no DC is available:
The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain “mydomain.com”:
The error was: “DNS name does not exist.”
(error code 0x0000232B RCODE_NAME_ERROR)
All machines on the 192.168.1.0 subnet joined without incident. I know the issue is not on the AD DC Can anyone tell me what might be wrong with my routing?
I tried a trace route and it seems to get stuck somewhere, but does seem to reach the DC:
Tracing route to dc.mydomain.com [192.168.1.220]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms peplink-2 [192.168.2.1]
2 * * * Request timed out.
3 26 ms 24 ms 25 ms dc.mydomain.com [192.168.1.220]
Any help is appreciated.