You only use one Gateway and it must go on the External (DMZ) side. In the
Internal side you handle the routes to other internal subnets by using the
OS's Routing Table to create Static Routes.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html
Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp
Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------
"gmasson" <(E-Mail Removed)> wrote in message
news:092CD1FC-83DA-46D4-A6C4-(E-Mail Removed)...
> Hello:
>
> I have an issue with Win 2003 server, network Load balancing, and Routing.
>
> Set the Scene:
>
> 2 unique machines. Running Win 2003 Server and Cold Fusion. We had an
> internal network and a DMZ
>
> The machines have unique internal IP addresses on a /24 network.
> The machine are NLB to a single IP in the DMZ.
>
> The problem we have has to do with multihoming. We'd like to be able to
> manage the machines remotely, which does require a default gateway on the
> private side.
>
> And of course the machines havea gateway on the DMZ side for HTP replies
to
> find their way out.
>
> Currently we have a CFMHTTP request that is sent out thru the DMZ, and it
> fails more or 90% of the time. However when we remove the gateway from
either
> the DMZ side or the private side, the request goes out, with no issue.
>
> Is ther a way around this? Can Windows be coaxed into having 2 gateways on
> two separate networks? Note that the only path between the networks is on
the
> machine itself. The networks are isolated for security reasons.
>
> Thanx
>