Error adding a computer to the domain

anshsky 5

Hi. We cannot add a computer from a remote office to the domain.lan domain. The remote machine has 192.168.8.2.

DC 192.168.1.1 is accessible from it via IP. The VPN is configured using two UDMs.

From remote machine 192.168.8.2:

PS C:\Windows\system32> tracert 192.168.1.1
Tracing route to 192.168.1.1
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  unifi [192.168.8.1]
  2    31 ms    31 ms    32 ms  192.168.9.8
  3    32 ms    31 ms    32 ms  192.168.1.1
Trace complete.

Starting portqry.exe -n 192.168.1.1 -e 53 -p UDP …
Querying target system called:
192.168.1.1
Attempting to resolve IP address to a name…
Failed to resolve IP address to name
querying…
UDP port 53 (domain service): LISTENING or FILTERED
Sending DNS query to UDP port 53…
UDP port 53 is LISTENING
portqry.exe -n 192.168.1.1 -e 53 -p UDP exits with return code 0x00000000.

PS C:\Windows\system32> test-netconnection 192.168.1.1 -port 53
ComputerName : 192.168.1.1
RemoteAddress : 192.168.1.1
RemotePort : 53
InterfaceAlias : 
EthernetSourceAddress : 192.168.8.2
TcpTestSucceeded : True

PING over IP works, but not through the host name or domain name domain.lan:

PS C:\Windows\system32>ping domain.lan
Ping request could not find host domain.lan. Please check the name and try again.
PS C:\Windows\system32> nslookup domain.lan
Server: UnKnown
Address: 192.168.1.1

*** UnKnown can't find domain.lan: Non-existent domain

Handian Sudianto 4,836 Reputation points

2023-09-11T08:20:03.2366667+00:00

Hello,

Can you screen shot of ipconfig /all to see your DNS server?

anshsky 5

Computers on the network 192.168.1.0/24-192.168.2.0/24 can be added to the domain.

PS C:\Windows\system32> ipconfig /all
Windows IP Configuration
   Host Name . . . . . . . . . . . . : servDC1
   Primary Dns Suffix  . . . . . . . : domain.lan
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : domain.lan
Ethernet adapter Ethernet:
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter
   Physical Address. . . . . . . . . : 00-15-5D-0A-58-41
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.1.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.10
   DNS Servers . . . . . . . . . . . : 192.168.1.1
                                       192.168.1.2
   NetBIOS over Tcpip. . . . . . . . : Enabled

Handian Sudianto 4,836 Reputation points

2023-09-12T00:23:41.6333333+00:00

HI..

That resulf of ipconfig /all for your DC right? can you post on PC which can't joined to the domain?
anshsky 5 Reputation points

2023-09-12T05:36:42.9133333+00:00
Yes, ipconfig on my DC.

Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\Windows\debug\dcdiag.txt. 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 "domain.lan": The error was: "DNS name does not exist." (error code 0x0000232B RCODE_NAME_ERROR) The query was for the SRV record for _ldap._tcp.dc._msdcs.domain.lan Common causes of this error include the following:

The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses: 192.168.1.1

One or more of the following zones do not include delegation to its child zone: domain.lan lan . (the root zone)

Add the FQDN of the DC to the hosts file on the remote PC 192.168.8.2:

C:\Windows\system32>C:\PortQryV2\portqry.exe -n 192.168.1.1 -e 53 -p udp Querying target system called: 192.168.1.1 Attempting to resolve IP address to a name... IP address resolved to domain querying... UDP port 53 (domain service): LISTENING or FILTERED Sending DNS query to UDP port 53... UDP port 53 is LISTENING

1 answer

anshsky 5 Reputation points

2023-09-12T11:22:21.5133333+00:00

https://community.ui.com/questions/Site-to-Site-IPSEC-VPN-VLAN-Traffic-over-VPN-DNS-Issue/edbf90c8-c655-48d0-b8e2-e83b736fd0b7

https://serverfault.com/questions/1064670/udm-pro-site-to-site-vpn-with-domain-issues
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Error adding a computer to the domain

1 answer

Your answer