Sometimes your machine opens up on certain ports (29, 68) if these ports are filtered, which means they are stealth through a firewall, nothing is wrong. Else some attacker can scan these?
Did you get the full green circle here on this test: http://www.seifried.org/freescan2/
Polonus
Their statement for closed ports is a little misleading:
Closed means that a service is not listening on this port, but also that this port is not filtered, if a service were run on this port it would be accessible to the Internet and potentially be dangerous.
These closed ports would only be accessible if I allow access. ZA would warn me if one of these ports where accessed and an would block access unless I gave permission.
This is a score on a scale of 1 (bad) to 5 (good), this score indicates a rough measure of how secure your computer is. Please note that even a single open port with a vulnerable application behind it, such as Windows file sharing or a web server can result in your system being compromised. You can increase your score by disabling uneeded services, or by installing and configuring a firewall.
Summary of scan results
Number of open TCP ports: 0 Number of closed TCP ports: 0
Number of filtered TCP ports: 68 Number of closed and/or filtered UDP ports: 0
Number of open and/or filtered UDP ports: 29
You all were very modest, because you did not mention your
Security Score = 5. Congratulations. Check all the processes you are running are legit, run protocols as far as you absolutely need them.
“Worn-out” is an oldfashioned word, to-days’ word is “busted”.
I was using Outpost Firewall 3.0 when I tested. 8)
Security Score: 5
This is a score on a scale of 1 (bad) to 5 (good), this score indicates a rough measure of how secure your computer is. Please note that even a single open port with a vulnerable application behind it, such as Windows file sharing or a web server can result in your system being compromised. You can increase your score by disabling uneeded services, or by installing and configuring a firewall.
Summary of scan results
Number of open TCP ports: 0 Number of closed TCP ports: 1
Number of filtered TCP ports: 67 Number of closed and/or filtered UDP ports: 0
Number of open and/or filtered UDP ports: 29
Number of open TCP ports: 0 Number of closed TCP ports: 0
Number of filtered TCP ports: 68 Number of closed and/or filtered UDP ports: 0
Number of open and/or filtered UDP ports: 29
Probably . . . Not. Most people who arrange to fully stealth port 113 never have any trouble connecting to any remote servers they commonly use. If, after stealthing port 113, you do experience connection delays, such as when sending or retrieving eMail, you’ll know it immediately since it’s usually quite apparent, and you’ll know that your ISP is using an IDENT-dependent eMail server. (But this is not common.)
The trouble experienced by most security conscious people, is that port 113 can sometimes be rather tricky to stealth . . .[/i]
so let’s say if you assigned your DHCP server to start with 192.168.0.2 and end with 192.168.0.100, just forward it to 192.168.0.101 , or 102, 103, 104… even 201… doesn’t really matter…
Very interesting Sasha!Again i learn something new(god i love this forum), as you can see from my screenshot i have no need for doing that the port is fully stealthed(luckily) for me , but i’m sure it’ll help Thomas ;D