Originally posted by: GeoffS
Interesting! Unfortunately (understatement, I'm sure) the server is running Win2K Pro SP4 🙂
I tried ZoneAlarm, but it didn't work well for me in an ICS configuration on the "router" system. It would probably work fine if you've only got one NIC in the system, as it worked very well on other's systems when there was only one network interface.Originally posted by: GeoffS
What about ZoneAlarm... I used to use that but haven't used it in a couple of years...
The only concern I really have when I put this on the new IP is that it's not behind a firewall at all. I was thinking of using a LinkSys broadband router (BEFSR41 v3) as the firewall... seems to work well at home... anyone think that is a bad idea or not enough security? I'd hate to get hacked the first day it's up!
Originally posted by: GunDog
The only concern I really have when I put this on the new IP is that it's not behind a firewall at all. I was thinking of using a LinkSys broadband router (BEFSR41 v3) as the firewall... seems to work well at home... anyone think that is a bad idea or not enough security? I'd hate to get hacked the first day it's up!
While this router is real good, (use it myself) it offers minimal protection at best. It can block pings and such but you really need a decent firewall package as well.
Force
Originally posted by: n0cmonkey
Originally posted by: GunDog
The only concern I really have when I put this on the new IP is that it's not behind a firewall at all. I was thinking of using a LinkSys broadband router (BEFSR41 v3) as the firewall... seems to work well at home... anyone think that is a bad idea or not enough security? I'd hate to get hacked the first day it's up!
While this router is real good, (use it myself) it offers minimal protection at best. It can block pings and such but you really need a decent firewall package as well.
Force
While I don't disagree with the layers approach, I do think that a small home NAT box provides a decent beginning to a security plan.