Ports being "used"

[Bry-fi]

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]

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]

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]

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]

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.