From what I can understand so far, you are creating a Tri-homed DMZ with the
web-hosting ADSL in the DMZ segment.. The fact that there are two internal
networks (the 192.168's) is beside the point. I don't think RRAS will work
with a DMZ that way,...at least I never heard of anyone doing it. It may be
able to, but I certainly wouldn't know how to deal with it off the top of my
head and I could not find any articles addressing the issue.
There can be only one Default Gateway and the NTL interface must be the one
with the Default Gateway, there is no question there,...it is an absolute.
Enter it in the normal GUI,...don't fool around with the Routing Table.
There is nothing in this situation that would require you to mess with the
Routing Table directly. Once the interfaces are configured correctly (IP#,
Mask, Gateway) it may be a good idea to clear the Route Table with "route
/f" from a command line, then reboot. On startup the Table is automatically
rebuilt based on the configuration of the Nics, as long as the Nics are
correct the Table will be correct.
The only way I know to easily use this server in the manner you are doing it
is to run ISA Server 2004 on it. ISA will work perfectly fine with the
Tri-Homed DMZ and is much more flexible than the previous ISA2000.
Some (most?) Hardware Firewalls, like our Watchgaurd 1000, also work fine
with a Tri-Homed DMZ and VPNs,...ours even has a special DMZ port for
exactly that purpose although we don't use it.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"Phillip Windell" <@.> wrote in message
news:O6h4%(E-Mail Removed)...
> What's NTL? Another provider? Another DSL line?
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
> "Greg Stanton" <(E-Mail Removed)> wrote in message
> news:0681E52F-243B-40CD-834F-(E-Mail Removed)...
> > I've drawn a diagram of the network:
> >
> > http://www.ioncomputers.net/network.gif
> >
> > I am using Windows Server 2003's remote access and routing setup.
> >
> > NTL is configured as a NAT with a basic firewall.
> > VPN machine likewise.
> >
> > Internal Network as a private connection.
> >
> > ADSL can be configured any number of ways but still won't respond unless
I
> > put in the static route of 0.0.0.0 (mask 0.0.0.0) and direct it to that.
> >
> > Please let me know if you'd like any screen-shots to clarify things.
> >
> >
> > "Phillip Windell" wrote:
> >
> > >
> > > "Greg Stanton" <Greg (E-Mail Removed)> wrote in
message
> > > news:0AC8DB64-2644-430E-AD1C-(E-Mail Removed)...
> > > > Currently I run Server 2003 Enterprise with four network interfaces:
> > > >
> > > > NTL Internet (the default gateway) (via nic)
> > > > Connection to the office (via a linux vpn over a nic)
> > > > Connection to other computer on the network (via nic)
> > > > ADSL Static IP connection (indended for web hosting) (via nic)
> > >
> > > > I am new to networking and part of a very small company, so any
advice
> > > would
> > > > be greately apprechiated - feel free to tell me how bad my current
> set-up
> > > is
> > > > so long as you can come up with something better!
> > >
> > > Do you have a Network Diagram?
> > >
> > > If these nics are all the same subnet then you have a horrible setup.
If
> > > they are different subnets, then I need a clear understanding of what
> you
> > > have. But I need specifics.
> > >
> > > --
> > >
> > > Phillip Windell [MCP, MVP, CCNA]
> > > www.wandtv.com
> > >
> > >
> > >
>
>