From: Atlanta, GA
We have a webserver hosted at a third party. I am considering using ISA as a firewall on this machine simply because I am familiar with ISA and we use it internally. But I am reading that a lot if the functions are crippled when using the "Single Network Adaptor" template.
I have a handful of websites that are hosted on that machine, plus an SQL Server and a few other applications that require specific TCP Ports. Since it is hosted off-site, I will not need to have users connecting through it, or VPN usage, or anything else like that. I just want to be able to open and close specific ports on the machine, and be able to specify things liek what IP addresses are allowed to conenct via RDP, SQL, Etc.
I am having trouble finding any online info about the abilities of ISA 2004 in this single network adaptor configuration. From what I can read, it seems to be used specifically for web caching, etc. Is this the case, or can I use it as a firewall like this?
More importantly, is anyone in a similar situation and has it working?
Also, my other concern is installing it from a remote RDP Connection. I know when I did one of our test servers it automatically added the RDP connection to the allow list so I could reconnect after installation. That was the best part.
If no one knows, I do have the ability to set up a test server and try it.... which I plan on doing anyway..... But if someone knows for certain that it cant be done and I should seek another solution, then it will save me some time.
I've ripped and replaced a good number of packet filter "hardware" firewalls because simple network layer filtering can't cut it in the real world anymore. So, I always put 2-8 interfaces in the ISA firewall for both Web Proxy and network firewall features.
For info on the single NIC config (which I don't use, why buy a Ferrari and take three wheels off?), check this site for "unihomed".