search

lgandx / Responder

Responder is a LLMNR, NBT-NS and MDNS poisoner, with built-in HTTP/SMB/MSSQL/FTP/LDAP rogue authentication server supporting NTLMv1/NTLMv2/LMv2, Extended Security NTLMSSP and Basic HTTP authentication.
GNU General Public License v3.0
5.46k stars 774 forks source link

MultiRelay - Nothing happening #168

Closed Scaum closed 3 years ago

Scaum commented 3 years ago

Hello,

I'm having an issue making responder work with MultiRelay. While using Responder only (with SMB and HTTP on) I can gather the hash from my target. However, if I turn SMB and HTTP off in Responder.conf and launch MultiRelay in the background, I can still see the poisoning happening in responder but MultiRelay doesn't show anything and the attack fails silently. image image I also tried with the MultiRelay included in kali but got the same result: image

Am I missing something ?

Versions:

lgandx commented 3 years ago

Hi, thanks for your report. Could it be that SMBv1 is not enabled on the target? In the same tool folder, there is a script called RunFinger.py. That script allows you to see among other things if SMBv1 is enabled on the target.

Cheers,

Scaum commented 3 years ago

Sorry for the late reply, didn't have time to test again until now. This was indeed the issue ! I knew to check that SMB Signing wasn't required but didn't think about the fact that 'Disabled' made no sense for SMBv2. Clearly my bad here, but maybe RunFinger should not mark Signing has Disabled if SMBv1 isn't Enabled ?

Thanks for taking the time to answer !