search

SpiderLabs / 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
4.45k stars 1.67k forks source link

Ports being "used" #124

Open Bry-fi opened 7 years ago

Bry-fi commented 7 years ago

I start up my computer and run responder than this comes up

[!] Error starting UDP server on port 5355, check permissions or other servers running. [!] Error starting UDP server on port 5353, check permissions or other servers running. [!] Error starting TCP server on port 80, check permissions or other servers running. [!] Error starting SSL server on port 443, check permissions or other servers running. [!] Error starting TCP server on port 445, check permissions or other servers running.

[!] Error starting TCP server on port 139, check permissions or other servers running. [!] Error starting UDP server on port 88, check permissions or other servers running. [!] Error starting TCP server on port 88, check permissions or other servers running. [!] Error starting TCP server on port 1433, check permissions or other servers running. [!] Error starting TCP server on port 21, check permissions or other servers running. [!] Error starting TCP server on port 110, check permissions or other servers running. [!] Error starting TCP server on port 389, check permissions or other servers running. [!] Error starting TCP server on port 25, check permissions or other servers running. [!] Error starting TCP server on port 143, check permissions or other servers running. [!] Error starting TCP server on port 587, check permissions or other servers running. [!] Error starting UDP server on port 53, check permissions or other servers running. [+] Listening for events... [!] Error starting TCP server on port 53, check permissions or other servers running.

I checked networkmanager and I don't even have dnsmasq installed. I nmaped myself and none of these ports are running. However, this program works fine on kali nethunter.

myalcin81 commented 6 years ago

You should kill active process. You can check active process list with " ps -a " command or you can check running ports with "netstat -al" who is running on it

lokori commented 6 years ago

I seem to have the same issue with the most recent version of Responder. Definitely netstat and ps do not show any processes in those ports so it has something to do with Responder. I'm running it in Kali as root so binding to low ports shouldn't be an issue.

hktalent commented 5 years ago

me too,mac os X

[!] Error starting UDP server on port 137, check permissions or other servers running.
[!] Error starting UDP server on port 5353, check permissions or other servers running.
[!] Error starting UDP server on port 138, check permissions or other servers running.
[!] Error starting TCP server on port 80, check permissions or other servers running.

$ netstat -ant|grep LISTEN|grep -E "\.\b(137|5353|138|80)\b"
tcp4       0      0  *.80                   *.*                    LISTEN

36 #45

Ap6pack commented 5 years ago

This was the error is was having: [!] Error starting TCP server on port 80, check permissions or other servers running. The way i fixed it was by killing my Apache server while using Responder.