I have comodo firewall and recently I have noticed that even with no
other
programs running at startup there are dozens of log entries like this
one:
Description: Information (Access Granted, IP = 209.133.121.235, Port =
29807)Protocol: TCP
IncomingSource: 90.202.177.58:53292
Destination: 192.168.0.2:29807
TCP Flags: SYN
Reason: Network Control Rule ID = 5
I'm getting worried because the sources are from all over the world
and they
all target port 29807. I could configure comodo to stop these but then
I
couldn't use bittorrent,so that's not an option.
Could someone please cast some light on what's going on here?
Is this a sign of malware(though I have scanned)?
Thankyou.
Access granted on port 29807. That means you allowed the software
firewall to allow those connections, or specified an application rule
that lets a listening process to accept those connections on that port.
Maybe Commodo's firewall doesn't provide enough details as to what
process is listening on that port to actually accept those connection
requests. You could run "netstat -a -b" in a DOS shell or use Nirsoft's
CurrPorts to see what process is listening on that port.
Re: What is the trick to get Windows XP firewall to stay on (after a reboot)? ... > While I did not explicitly state that the EPRT and PORT commands reached... > Windows Firewall did not start a listen according to netstat -a and Port ... So, while a proxy would result in a new listening socket, a firewall does ... client sending a PORT command that it has chosen to send. ... (microsoft.public.windowsxp.network_web)
Re: What is the trick to get Windows XP firewall to stay on (after a reboot)? ... > While I did not explicitly state that the EPRT and PORT commands reached... > Windows Firewall did not start a listen according to netstat -a and Port ... So, while a proxy would result in a new listening socket, a firewall does ... client sending a PORT command that it has chosen to send. ... (microsoft.public.windowsxp.basics)
Re: What is the trick to get Windows XP firewall to stay on (after a reboot)? ... > While I did not explicitly state that the EPRT and PORT commands reached... > Windows Firewall did not start a listen according to netstat -a and Port ... So, while a proxy would result in a new listening socket, a firewall does ... client sending a PORT command that it has chosen to send. ... (comp.security.firewalls)
Re: What is the trick to get Windows XP firewall to stay on (after a reboot)? ... > While I did not explicitly state that the EPRT and PORT commands reached... > Windows Firewall did not start a listen according to netstat -a and Port ... So, while a proxy would result in a new listening socket, a firewall does ... client sending a PORT command that it has chosen to send. ... (microsoft.public.security)
Re: Doesnt Zonealarm prevent programs from listening? ... >with Zonealarm....>listening according to Kerio. ... Surely a firewall should prevent listening too??? ... the process creates a socket on a port and starts listening on ... (comp.security.firewalls)
