Error joining to target domain - Error code 1355
Error 1355 when joining a computer to Active Directory usually means:
“The specified domain either does not exist or could not be contacted.”
In practical terms, the machine cannot properly find or talk to a domain controller for the target domain.
Common causes are:
- DNS is wrong
- client is not using the AD DNS server
- wrong suffix/search order
- stale DNS records
- No network connectivity to the DC
- routing/VPN issue
- firewall blocking required ports
- The domain name was entered incorrectly
- typo
- using the wrong FQDN/NetBIOS name
- The DC cannot be located via DNS SRV records
_ldap._tcp.dc._msdcs.domain.comissues
- Time skew / trust-related connectivity issues
- less common for 1355, but still possible in some environments
- Joining across VPN before line-of-sight to the DC exists
Resolution
Sign in to the device
Sign in to the affected device with a local administrator account, such as the Fallback Admin account, and open an elevated Command Prompt or PowerShell window.
Check that the device can find a domain controller
- Look up the domain controller SRV record for the target domain:
nslookup -type=SRV _ldap._tcp.dc._msdcs.<target domain FQDN>
The result should list one or more domain controller host names. If it does not, point the device at DNS servers that can resolve the target domain, or add a conditional forwarder for it.
- Ask the domain controller locator directly:
nltest /dsgetdc:<target domain FQDN>
A working result returns a domain controller name and address.
- Check the DNS client. Run
ipconfig /allto confirm which DNS servers the device is using, then clear the cache and resolve a domain controller by name:ipconfig /all
ipconfig /flushdns
Resolve-DnsName <DC host name> - Test the ports from the device to the domain controller:
Test-NetConnection <DC host name> -Port 389
Repeat for ports 88, 135 and 445. Each test should return
TcpTestSucceeded : True.
Resume the migration
Once the issue is resolved, either reboot the device or restart the PowerSyncPro Migration Agent service in Services (services.msc). The Migration Agent then continues the migration.
PowerSyncPro Migration Agent supports Offline Domain Join (ODJ) for Active Directory targets. See how it works.