> For the complete documentation index, see [llms.txt](https://alham-rizvi.gitbook.io/alhamrizvi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alham-rizvi.gitbook.io/alhamrizvi/active-directory/02.-ntlm-disabled.md).

# 02. NTLM Disabled

NTLM is the legacy Windows authentication protocol — a challenge-response scheme built around your password hash. Many older or simpler AD attacks (pass-the-hash against SMB, NTLM relay, some spraying tools) depend on NTLM being available.

When an environment disables NTLM entirely (a real hardening measure some organizations apply), tools that default to NTLM auth fail outright:

```
STATUS_NOT_SUPPORTED
```

## What Changes For the Attacker

| NTLM-only workflow             | Kerberos-only equivalent                          |
| ------------------------------ | ------------------------------------------------- |
| `tool -u user -p pass`         | `getTGT.py` first, then `-k --use-kcache`         |
| Pass-the-hash                  | Convert hash → AES key → `getTGT.py -aesKey`      |
| No clock/hostname requirements | Strict clock sync + correct SPN hostname required |

## Worked Example — Same Task, Two Ways

```bash
# NTLM style (fails in a Kerberos-only environment)
nxc smb dc1.domain.htb -u jane.doe -p Password123 --shares

# Kerberos style (works)
getTGT.py domain.htb/jane.doe:'Password123' -dc-ip 10.10.10.5
export KRB5CCNAME=jane.doe.ccache
nxc smb dc1.domain.htb -k --use-kcache --shares
```

## Why It Matters

It's not just "same tools, different flag" — the entire mental model shifts. You stop thinking in terms of "username + password against a service" and start thinking in terms of "which ticket do I currently hold, and is it valid for this specific target hostname." Every step downstream (cross-forest auth, certificate auth, etc.) builds on this ticket-based mindset.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://alham-rizvi.gitbook.io/alhamrizvi/active-directory/02.-ntlm-disabled.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.