Just got myself a Windows 2003 web edition server and bought a copy of Visnetic firewall.

I have tried installing Visnetic twice now and both times it has completley screwed the server, took support 2 hours to get it back online last time. I followed the How-To posted by PressCMS and im not having much luck.

I just spoke to Tech support and the guy told me that there wasnt really much point in installing a firewall, should i bother?? and if so someone please give me some tips so i dont break the server again.

Thanks

interesting point --

for one, if you install a firewall, it slows your server bunch. for example, doing server to server fxp within RS network, you should get something like 7mbits/second. but when you turn on firewall, you should only see something like 50k/s to even the low of 5k/s which is as slow as phone modem.

so if you don't have firewall, your sever will run faster and frees up resources (kerio eats about 20mb memory and scanns every damn packet for virus. but i never runs windows server without it. never never never.

so my question is, what would hacker do to a server which is completely patched with latest thing from MS. I guess they could send some troijan and get access to the server?

Just curious,

I don't notice any slowdown with visnetic. Your CPU will be 2-3% higher -- but that's a small price for security.

If you don't want a slow-down, then don't use a home firewall -- get a real one.

ALWAYS run a firewall. Simple as that.

Ok so i have to install a firewall.

Any ideas why my server refuses to reboot after i install visnetic?

1) Kerio Winroute 5 isn't home firewall
2) Obviously you aren't using it anymore, so I guess I have to install visentic and do site to site transfer within RS network to see if I can get 7mbits/s

3) I guess EV1tech misinformed one of their customer

Can you give me some more details? When you say reboot do you mean the server wont come back up at all or it comes back up with a ruleset that means you cant access it? How are tech support fixing this and what are they saying is the problem?

Happy to help if you can give me some more to go on...

Problem solved, seems the bios was set wrong on the server so it was nothing to do with visnetic after all. Tech support fixed it and its working great now

Now I am scared of visnetic even though it wasn't visnetic 's fault