Cannot contact Domain Controller on another subnet


#1

I have two peplnk 210 routers used to connect two offices that need to share the same network and domain.

Office 1:
Peplnk IP: 192.168.1.1

Office 2:
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:
C:>ping 192.168.1.220

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:
C:>tracert 192.168.1.220

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]

Trace complete.

Any help is appreciated.

Thanks.


#2

Hi,

May I know what are the firmware version running on your Balance 210 routers?

There is known issue in earlier firmware that prevent some Windows services packets flow through SpeedFusion tunnel. Please try to load firmware 6.2.2 from here, which fixes that issue.

If problem persists, do open a support ticket hereto further diagnose the issue.

Thanks and regards.


#3

The current firmware is 5.4.9 build 1564.

I updated the firmware, but cannot activate it without a key. Really? I need a key to fix PepLink’s bugs?

I’ve registered the products and opened a support ticket. So far, this is abysmal support. I shouldn’t have to do anything to interact with a vendor to update buggy firmware. I’ve never had this with any other manufacturer.

So now, it’s another day, my colleagues still cannot do their work, and we’re losing money. Thanks, PepLink! Great Product!

Anyone else out there feeling cheated?


#4

The firmware key is provided at no cost and we will send it to you via the support ticket.


#5

OK, so I need to update this since I may have been a little harsh before. I still think self-service should allow me to easily get what I need to manage my devices. However, the support team that answered my ticket did so with very fast response, and got me back up and running. Thank you.


#6

Hi,

Glad to hear that. Anyway you may self-service to obtain the firmware license key in future. Please find here for more details.