Quote:
|
Originally Posted by ntl customer
Not sure if this goes in Computers or Internet, but I felt this was the most appropriate place seeing as it is a subforum for security issues.
I have Norton Personal Firewall 2001 and it has served me well for a good number of years, keeping this machine secure. However there has always been this annoying problem of the firewall closing ports or locking up completely and not allowing certain peer to peer software (WinMX is a problem) to open certain ports and requiring a complete system reboot to fix the problem.
<SNIP>
Does anybody have a solution that for my problem? It is really starting to drive me nuts!!! 
|
NIS has the habit of blocking ALL access to/from an IP address for 30 minutes if it sees that address has "attacked" your machine. This is what may be happening in your case. Rebooting resets the block.
You need to find the IP address of the remote system, then check your logs to see if a specific attack has been monitored. Find why the blocking action was taken.
If it is a Trojan Rule that is causing it, you need to check what traffic is coming in on what ports from the remote system. They may be using ports which are used by a particular Trojan, and this is giving a false positive. If so, you need to edit the relavent Trojan Rule to permit traffic from the specific IP address the remote system uses.
If anything other than a Trojan Rule is causing the blocking action, then this can be overcome by writing a new Firewall Rule. Again, you need to know the IP address of the remote, and what local ports are being affected. A way I use, is to write a temporary rule that allows everything on all ports in/out from/to anyone. Set this rule to be logged or monitored. Run the offending app or start you FTP server and try to access it, whichever you are fixing (do this one step at a time or the logs will be VERY confusing). Then either remove or disable the new rule (as this opens up your system!), then check the logs. You should see what traffic is running on what ports. You can then use this info to write the new rule. Repeat this proceedure for each issue.
Once you've created the new rules, all should be okay. It's just a balance between security and functionality!
Hope this helps