Re: 2 Gateway's on 1 NIC on Windows Server 2003

THis fixed the problem. Thanks a million for your help! And now I have a
better understanding of how this all works. Thanks everyone!

"Neteng" wrote:

> OK, from the AVServer, you can not ping anything on 192.168.10.x correct? It
> only has two routes, one for the local subnet, 192.168.1.x and one default
> route for all other traffic, 0.0.0.0 pointing to 192.168.1.250. (I know you
> know this, just keeping it straight in my head). To get to the 192.168.10.x
> network, you need the following static route in the AVServer.
>
> route ADD 192.168.10.0 MASK 255.255.255.0 192.168.1.1 -p
>
> The -p is to set it persistent, so it won't disappear after a reboot. Try
> this and let me know how it goes.
>
>
> "Jwolfer" <Jwolfer@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:3CE2B582-C342-4938-8D98-5BE5DF8E842C@xxxxxxxxxxxxxxxx
> > Here is a network diagram.
> >
> > http://pride.fites.net/netlayout.jpg
> >
> > We have 2 ISP connections. 1 Comcast Cable and 1 PlanetCable DSL
> >
> > The reason for this is that comcast will not reverse resolve our Mail
> > Server's IP address/and/or name. So we use a local isp to handle our
> email
> > routing and dns service.
> >
> > Comcast has the speed though, so that is what we have our VPN tunnel
> coming
> > in through, as well as all internet activity and FTP.
> >
> > Essentially what is going on here is... for my AV server to process
> incoming
> > email for virus control and spam filtering, it is has to have the same
> > gateway as the router connected to the DSL modem (1.250)... and NOT that
> of
> > the router connected to the Cable modem (1.1).
> >
> > All clients point to the gateway of the cable modem (1.1)
> >
> > My clients at our remote office have a gateway of their router connected
> to
> > their internet connection (10.1)
> >
> > 10.1 can see 1.1 just fine. 1.1 can see 1.250 just fine, but 10.1 cannot
> > see 1.250 at all.
> >
> > I currently have 1 NIC in my AV server. Its connected to the same switch
> > that my 2 routers are connected to. So, to direct traffic in/out of the
> DSL
> > line, it has to have the same GW IP as the router connected to the DSL
> line
> > (1.250)
> >
> > The problem is, my 10.x clients cannot see my AV server (cannot even ping
> > it) since the AV Server is on 1.250
> >
> > Hope that helps.
>
>
>
.

Relevant Pages

  • Re: ISA Einstellungen für Internetzugang am Server
    ... Du musst die IP Adresse des Routers als Gateway auf der externen ... kann ich dir nur raten einen DSL Router zu kaufen. ... Für den Zugriff von Exchange auf SMTP Server brauchst du einen Paketfilter, ... Damit du am SBS Surfen kannst, musst du nur dem IE die interne IP des ISA ...
    (microsoft.public.de.german.isaserver)
  • 2 Gateways on 1 NIC on Windows Server 2003
    ... A local ISP DSL ... This is necessary due to the fact that since we host our own mail server, ... Something Comcast does not offer. ... Because the router has an IP addy of 1.250, I need to designate the Gateway ...
    (microsoft.public.windows.server.networking)
  • Re: Anyone tri-homed SBS2003?
    ... Keep the cable modem and look into tzo.com. ... Chris wrote: ... >>not sending the email to just one server to ... > relay off of your dsl ...
    (microsoft.public.windows.server.sbs)
  • Re: Fedora Box with TWO NICs
    ... > Cable modem side, but then the DSL NIC becomes useless. ... > server and provide file services from the LAN side. ...
    (Fedora)
  • Re: SBS2003 Firewall as good as Routers?
    ... The gateway on the server will still be the router as normal, ... firewall, and you wouldnt believe what that thing is stopping!!! ... >the SBS2003 server directly to the cable modem. ...
    (microsoft.public.windows.server.sbs)
Loading