[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1098
  • Last Modified:

How To Configure ISA 2006 With External NIC routing To Juniper Firewall - NO INTERNAL ISA INTERFACE

My client has a Juniper firewall with one leg on the private/internal network, one leg on the public and one leg on the DMZ.  So think of it being a "T-shape" logically.
My problem is that the client does not have a secondary firewall sort-of-speak so they refuse to get an executive exception to allow the ISA2K6 server to have a leg into
the private network from the DMZ.  It freaks them out, no matter how much I tell them (and show them) that it's secure if done correctly.  Anyway, I cannot have an internal
and external interface on the ISA2K6 server, which is acting as a revers proxy for the OCS2K7 environment, specifically it communicates with the OCS CWA server that sits
on the the internal/private network.

The ISA2K6 reverse proxy server is a virtual machine, on which I've created two NICs - both with IPs sitting on the DMZ.  I'm trying to get ISA2K6 to allow me specify both
NICs (NIC-A is supposed to be the internally facing one, but can't face internally so it's externally IP sitting on the DMZ).  NIC-B is normal...external and NATs to the public IP
that corresponds to the reverse proxy URL published to anonymous Internet Live Meeting/IM/Address Book users.

My difficulty is in telling ISA that there are no internally-facing interfaces and that NIC-A has to route its traffic to and from the OCS2K7 CWA server (on the internal
network) through the firewall address (the DMZ gateway) so that internal resolution will occur.  In theory this should work...two external interfaces...tell ISA that NIC-A must
route between its own IP which is in the DMZ to the firewall (it's gateway IP) and I can just let the Juniper firewall figure out the best way to route those packets from NIC-A
(on the DMZ) to the CWA server (on the private network)...all without having a specified internal interface as ISA2K6 neatly expects.

Any ideas on how I can pull this off??  Because I am going to be asked to do the same thing to the OCS2K7 Edge Server sitting in the DMZ also.  HELP!!
0
Monterio
Asked:
Monterio
  • 2
1 Solution
 
MonterioAuthor Commented:
Here's what I'm looking at now...  
OCS-Instate.png
0
 
pwindellCommented:
There is no such thing as a Single-Nic ISA with only an external Interface.  The Interface on an ISA is always an Internal Interface it is can only be used as a Web-caching proxy and nothing else.  ISA/TMG was invented and designed to be a full high-end Enterprise Firewall Product.  A single-nic ISA/TMG is pretty much a waste of money and a waste of time (IMO).
0
 
Jeff_SchertzCommented:
The best approach for your client is to have them define a second perimeter network subnet using a 4th interface on the JUniper if possible.  This way you can put two interfaces on both the Edge and and ISA servers as each interface needs to be in a separate IP subnetwork.

If this is not possible (inflexible customer or no remaining interfaces on Juniper) then you can still use a single interface on the ISA server.  A single interface on the Edge server though is more difficult to pull off: http://blogs.pointbridge.com/Blogs/schertz_jeff/Lists/Posts/ViewPost.aspx?ID=33
0
 
MonterioAuthor Commented:
there was no solution proposed that helped me.  Only one person replied and it was an opinion...no technical information that could help me with my problem.  so I'm accepting my answer and bowing out, since it's been two days and no one else has responded.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now