Quote:
|
PS: u seems to be running an FTP server, HTTP server and SMTP server. I hope you know that already.
|
What made you say this alib_i?
If this is what you are referring to...
Code:
TCP 0.0.0.0:21 0.0.0.0:0 LISTENING 516
TCP 0.0.0.0:25 0.0.0.0:0 LISTENING 516
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 516
Please do correct me if I'm wrong but I believe even though these addresses along with their respective ports are under the "Listening" state[which clearly states that its acting as a "server" under TCP/IP semantics] the address 0.0.0.0 is a non-functional address w.r.t the internet.
Client/server model cant have a possible 3 way handshake with this as a IP address.Moreover the range from 0.0.0.0-0.255.255.255.
I'll try digging up a RFC & post the equivalent rfc number here when I find one.
Although netstat does a pretty good job of mapping ports to application I prefer to use
Fport.Which virtually does the same job but with a bit of ease & functionality.
I would suggest the original poster to issue netstat/fport when you connect to the internet without having any services running i.e browser,chat apps.
This will rule out safe connections from any malicious connections like a trojan listening to a particular port,or a server which you have unknowingly started like IIS by default.
Oh btw keep the firewall enabled or if you dont have one get one.