Authenticating on AD 2025 with invalid user returns NETBIOS connection timed out

[Dfte]

Strange behaviour there, authenticating with a non existing user on windows server 2025 (DC) produces a NETBIOS connection time out

Will see later if we can hack something to get the correct error and/or switch the message output.

[NeffIsBack]

Yeah had the same behaviour when testing my 2025 DCs. Looks like the SMB connection just times out with NTLM and a wrong password. Kerberos works flawlessly tho.

Possibly this is just new behaviour with WIN2025, not sure if there is something we can do about that. Could also be a bug in impackets smb implementation though

[Dfte]

I think I found, see:

With the User logon name it doesn't work but it does work with the user logon name pre win 2000:

Lol

[NeffIsBack]

Lol okay, is this a bug in windows?😂

[Dfte]

Is there a colition issue thing there ?

[Dfte]

Si that means DC2025 doesn't allow authenticating with accoutns with more than 14 chars in their usernames ? rofllll nice side effect I guess ?

[NeffIsBack]

Si that means DC2025 doesn't allow authenticating with accoutns with more than 14 chars in their usernames ? rofllll nice side effect I guess ?

O think successful auth still work, just unsuccessful ones time out for some reason. Not sure if that's related to the length tho :D