As I know, one external interface on ISA is allowed, why do not you give it a try for adding another NIC to be external :-))) I ever try it and do not know if it works, but my ISA is up and running with one external interfaces with hundreds of public IP addresses on it, everything is working perfectly then I can not give it a try in case might ruin my whole functional workings. PTH
- Do you want to add additional IP addresses on your ISA's external NIC ?
- Do you want to add another NIC on your ISA and use public IP address on additional NIC ?
- I just added bunch of public IP addresses to the external NIC of ISA. Thats it ! Out side world want to communicate with your internal servers, internal network, or with your published servers, they have to go through the ISA external NIC first. - for example I have DNS Host Record www.company.com 188.8.131.52 - I add 184.108.40.206 on my ISA's external NIC - I publish the internal web server which runs IIS - BOOM !www.company.com is behind a firewall. Is that simple ! - You have hundred websites and hundreds IP addresses of them, you have to add those hundreds of IP addresses to external NIC of ISA to let you publish the servers behind a firewall ( the alternative way is DMZ, with DMZ you do not need to publish, and DMZ NIC use public IP address and DMZ hosts using public IP addresses too, but DMZ NIC's IP addresses must be different with ISA external IP addresses)
- your question was " How many external interfaces can I have on my ISA ? " external interfaces commonly refers to NIC (Network Interface Card) thats why I thought you asked if you can add another NIC into your ISA and use public IP address for it parallely with your current ISA external interface. - Or you might have meant " how many public IP addresses you can add on ISA's external interface (Network Interface Card)" ??? :-))) ------------------------------------------------------------------------------------------ PTH
[This message has been edited by TheJackal (edited 06 April 2001).]
Oh my god! I can't believe it's that simple and I overlooked it. You are the MAN! I wanted to know how many interfaces that the ISA Server could have, thinking that was the only way to add internet IP's.
Can you have more than one external interface? Thanks again.
Here's something interesting in case you're having problems with multiple external IP addresses:
Q288247 > ---------- > SYMPTOMS > > ======== > > On machines matching the following configurations, ISA services may fail to > start. > > Number of IP Addresses Problem occurs or not > > 1 internal IP and 2 external IP address (total 3) no > 1 internal IP and 3 external IP address (total 4) no > 1 internal IP and 4 external IP address (total 5) occurs > 1 internal IP and 5 external IP address (total 6) no > 1 internal IP and 6 external IP address (total 7) no > 1 internal IP and 7 external IP address (total 8) occurs > 1 internal IP and 8 external IP address (total 9) occurs > 1 internal IP and 9 external IP address (total 10) no > 1 internal IP and 10 external IP address (total 11) occurs > > No other configurations were tested for this problem. > > This applies to active interfaces. This is true even in the case where your > configuration does not match the table above and ISA services start but > later if a user creates a VPN connection to the ISA box, or The ISA server > dials out with VPN or Modem and that causes it to have an additional IP > address, the ISA services may fail. One possible workaround is to un select > "QoS Packet Scheduler" from all interfaces in network properties. This does > not affect ISA Bandwidth control functionality. > > The problem is initiated by this file : bwserver.dll in CreateInterface > because of bad pointer arithmetics when enumerating addresses. > > RESOLUTION > > ========== > > A supported fix is now available from Microsoft, but it is only intended to > correct the problem described in this article and should be applied only to > systems experiencing this specific problem. This fix may receive additional > testing at a later time, to further ensure product quality. Therefore, if > you are not severely affected by this problem, Microsoft recommends that you > wait for the next Product Name service pack that contains this fix. > > To resolve this problem immediately, contact Microsoft Product Support > Services to obtain the fix. For a complete list of Microsoft Product Support > Services phone numbers and information about support costs, please go to the > following address on the World Wide Web: