Hi PaciB,
Thank you for the quick response and detail. The ISA Server is also going to be used as a proxy and the server will be on the domain as requested.
The LAN subnet is 10.0.0.x /24 - will connect to the local switch
The WAN subnet is x.x.x.x /30 - will connect directly to the SHDSL router
There is no subnet for the DMZ. If I were to create a subnet for the DMZ , where will this connect ?
If I was to publish OWA 2003 or other services , can this be done with 2 NICs ?
Main Topics
Browse All Topics





by: PaciBPosted on 2009-08-27 at 05:36:28ID: 25197224
Hi,
If you want to have a DMZ, then you absolutely need 3 NICs: One for internal network side, on for DMZ side and one for external side.
Start by install Windows 2003 and configure the NICs and IP layers...
There are some questions you must ask to yourself and answer and informations you must collect before proceeding :
1) Do you ISA server need to be member of a domain ? If yes, then your ISA server need to resolve internal DNS names AND external DNS names. That requires a specific DNS configuration
2) What are the IP ranges you use in your internal network, including all the branch office that may use this ISA server?
3) What is the IP range of your DMZ network?
If you have these informations, you should start by configuring IP on NICs before going on with ISA installation.
Give precise names to your NICs, avoid use of default names like "network connection #1" that Windows proposes after installation. Rename you NICs with names like "LAN", "DMZ and "External".
Start by configure the external NIC: give IP address and mask matching with what your ISP give to you. Configure IP gateway on this NIC. THE EXTERNAL NIC IS THE ONLY NIC THAT MUST HAVE A IP GATEWAY CONFIGURED! Don't configure DNS servers for now.
Configure your DMZ NIC: very simple, only IP address and mask.
Configure you internal NIC: IP address and mask only for now.
Then, if you internal network has several IP ranges you must create specific IP routes to explain your ISA server how to join these IP ranges.
As an example, if your internal NIC on ISA has to following parameters: IP address = 10.1.0.254, mask = 255.255.0.0 and if you have another internal network using ip range 10.2.x.x with mask 255.255.0.0 then you need to type the following command on ISA to add the ip route:
ROUTE ADD 10.2.0.0 MASK 255.255.0.0 w.x.y.z -P
(where w.x.y.z is the IP address of the internal routeur that allow you to reach the internal subnet 10.2.x.x, and -P means that this route must be permanent and will not disappear after a reboot).
Do like that for every internal IP subnet.
Make pings to some of the internal computers (using IP address because until now you have not DNS resolution) on every internal subnets to verify IP routing is ok.
Now about DNS, if your ISA server must not be member of a domain (ISA is standalone server) then go on IP configuration of the external NIC and configure external DNS addresses that your ISP gave to you.
If your ISA server must be member of internal domain then ISA must be able to resolve external DNS names to give access to Internet but also resolve internal names to locate domain controllers... For my part, in this situation, I install DNS service on ISA server and configure this DNS service with no DNS zone but only DNS forwarders: I use a conditional forwarder for Active Directory domain suffix "mydomain.local" and mention IP addresses of internal DNS servers, then I add a unconditional forwarder to external DNS servers. Finally, I configure all NICs to use 127.0.0.1 as DNS server.
Doing that, ISA server use its own DNS service to resolve any dns name. If the DNS suffix of the name matches with domain dns name then the conditional forwarder send the request to an internal DNS server, else it sends the request to the external DNS.
When you have done that, and have validated the DNS resolution by doing some ping on internal and external DNS names, you can join the domain (if your ISA need to be a member).
Then you can install ISA. It's easy. During installation, ISA server installation wizard will detect multiple NICs and will ask you for internal IP ranges. You must include all IP ranges that are not externals (meaning LAN and DMZ ip ranges). You can easily indicate these ranges by selecting all internal and DMZ NICs. ISA will automatically generate ip ranges by looking at NIC configuration and IP routes.
Have a good day.