PeopleSync Knowledge Base
PeopleSync Knowledge Base
Breadcrumbs

Change the Ports of an Existing AD LDS Instance

Applies to: Existing PeopleSync AD LDS instances. PeopleSync Backend R2026.08 (26.8) or later is required for separate LDAP Port and Use SSL settings. The example changes LDAP 389 → 1389 and LDAPS 636 → 1636; other free ports can be used.

Check first: If System Settings → Directory Service uses this AD LDS instance for PeopleSync authentication, verify its custom-port compatibility with messageconcept support before changing the listeners. The Console steps below cover LDAP Address Lists.

Check the instance

  1. On the AD LDS server, run dsdbutil.exe "list instances" quit.
    Confirm PeopleSync-LDAP, record its current ports, and identify its Windows service in Services. Record the current PeopleSync, client, and firewall port settings.

  2. Confirm the new ports are free:

PowerShell
Get-NetTCPConnection -State Listen -ErrorAction SilentlyContinue |
    Where-Object { $_.LocalPort -in 1389, 1636 }

Change the ports

  1. Stop the PeopleSync service.

  2. Stop the PeopleSync-LDAP service.

  3. In an elevated Command Prompt, run dsdbutil.exe. Enter one line after another:

     activate instance PeopleSync-LDAP
 ldap port 1389
 ssl port 1636
 quit

  4. Start the service PeopleSync-LDAP service.

  5. Start the PeopleSync service.

  6. Run dsdbutil.exe "list instances" quit to confirm both ports.

Update PeopleSync and clients

In PeopleSync Console → System Settings → LDAP Address Lists, enter the server name without an inline port:

Connection

LDAP Server

LDAP Port

Use SSL

LDAP

ldap.example.com

1389

Off

LDAPS

ldap.example.com

1636

On

Set Use SSL before entering custom port 1636; toggling it can reset the port to 636.

Update other LDAP clients and firewall rules for the selected ports.

Verify

  • In ldp.exe, connect on 1389 without SSL and 1636 with SSL; confirm RootDSE and an authorized bind on both.

  • Publish an LDAP Address List from PeopleSync and test a client lookup on its new port.

Restore previous ports

If validation fails, stop the service. In dsdbutil.exe, activate PeopleSync-LDAP and set ldap port and ssl port to the recorded values. Restart the service, restore the previous PeopleSync, client, and firewall settings, then repeat the connection and lookup checks. If the instance does not start with its previous settings, restore its AD LDS backup.

References