I am out of usable IP's on my outside nic for use with ISA. I added 5 new IP's by adding them to the outside nic and ISA stopped working. No errors, just no more connectivity from outside or from inside - out. I took the IP's off, restarted and it was still not working. I reinstalled and that did not work either. Finally I uninstalled again, switched the nics so that outside was now the inside adapter and vice versam reinstalled and it worked (I have no idea why I even did this). Any ideas what would cause this? Am I adding IP's incorrectly, this way worked with 2004? Could IP's that were already being used cause this? I am asking because I am not confident in my ISP.
I added the IP's via the Network Connections in control panel to the outside nic card. That is the way I used to add ip's for 2004 and it was fine. Is there a new area in 2006 ISA management to add external IP's? I didn't see one. I checked all of the IP addresses that I was told to use after I posted with a port scanner and 2 were in use (I am going to change my isp). But why would isa still not work after I removed the offending ip's and restarted. I looked at the routing table and it looked ok?
Nothing in event viewer except a Netlogon saying can't find an ad box, which is reasonable since I cannot get anywhere after the IP addresses were added. I have been using ISA since it's inception and never had something like this happen. I think it is an ip conflict like I mentioned before but I don't know why it wouldn't start working again after I removed the IP's.
Some IP Confilct happens with the ISA, and when it happens the ISA just disconnect clients.
in the EventLog, it says that there was an IP conflict with the MAC address xxx.xxx
How can I stop this ? I mean the disconnection if an invalid IP address conflicts with the ISA. Am already working on a solution to make all IP`s DHCP and make a Group Policy to Porhibit users from altering the TCP/IP Properities. (No more Allowing Static IP`s to prevent the Conflict).... But till I do this, I want to stop the disconnection when there`s such a conflict.
That's an interesting problem. However, if the ISA Firewall was the original owner of the IP address, it shouldn't be disconnected. The client that was reconfigured would not be allowed to own the address. Are you seeing something different?