# 389/TCP/UDP, 636/TCP, 3268/TCP, 3269/TCP (LDAP)

## Nmap

```shell
nmap -sC -sV -sS -sU -p T:389,636,3268,3269,U:389 --script="ldap* and not brute" <IP-address-DC> -oN nmap-ldap.txt
```

* -sC = utilización de secuencias de comandos predeterminado.
* -sV = identificación de servicio y su versión.
* -sS = escaneo TCP SYN (stealth/sigilo).
* -sU = escaneo puertos UDP.
* -p T:389,636,3268,3269,U:389 = únicamente los puertos 389/TCP, 636/TCP, 3268/TCP, 3269/TCP y 389/UDP.
* \<IP-address-DC> = dirección IP del controlador de dominio.&#x20;
* -oN = guarda resultado del escaneo en archivo nmap-ldap.txt.

## LDAPDomainDump

```shell
mkdir ldapdomaindump
ldapdomaindump <IP-address-DC> -u "<ACME.LOCAL>/<user>" -p "<password>" --no-json --no-grep -o ldapdomaindump
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://pentesting.mrw0l05zyn.cl/escaneo-y-enumeracion/servicios/389-tcp-udp-636-tcp-3268-tcp-3269-tcp-ldap.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.