NoobITdirector
IS-IT--Management
- Apr 6, 2011
- 10
Hey guys,
I have a block of 5 IP addresses coming in through fiber to my server closet. Currently, I have XXX.XXX.XXX.218 acting for all web services, including IIS, exchange, SQL, and a few other services running on dedicated ports. I'm wanting to run OWA in exchange on a XXX.XXX.XXX.219 due to our email demand and the fact that port 80 and 443 are already consumed.
I understand that Exchange has to be in direct communication with the AD server and that all exchange users need access to the domain for authentication and email. What would be the best route for setting up a method so that I can bring a completely separate IP address into the network?
I have a Netgear UTM50 firewall and two 48-port 1GBps switches. The UTM50 has 2 WAN ports - only one being consumed. From what I understand (and I may be totally wrong) the UTM50's second WAN port is for load balancing and fail-over.
How do you guys manage multiple IP addresses in?
I have a block of 5 IP addresses coming in through fiber to my server closet. Currently, I have XXX.XXX.XXX.218 acting for all web services, including IIS, exchange, SQL, and a few other services running on dedicated ports. I'm wanting to run OWA in exchange on a XXX.XXX.XXX.219 due to our email demand and the fact that port 80 and 443 are already consumed.
I understand that Exchange has to be in direct communication with the AD server and that all exchange users need access to the domain for authentication and email. What would be the best route for setting up a method so that I can bring a completely separate IP address into the network?
I have a Netgear UTM50 firewall and two 48-port 1GBps switches. The UTM50 has 2 WAN ports - only one being consumed. From what I understand (and I may be totally wrong) the UTM50's second WAN port is for load balancing and fail-over.
How do you guys manage multiple IP addresses in?
