Re: Makes no sense to me?

Ok.

I read the post and I know it will work but there is no way I can make the
third network. (at least in my view)

This whole fiasco is because of My ISP and two mailservers. One primary and
one backup. This is why i am trying to do this.I need to share the mailboxes
internally.


thank you Steve
Joe

"Steve Duff [MVP]" wrote:

> Your post is a little confusing. A NIC by itself cannot "join two routers". But
> not understanding never stopped me before :-)
>
> What I think you want is to have two NICs in EACH server.
>
> One NIC on each server connects to a corresponding router and nothing else.
> These are your 192.168.0.* and 192.168.1.* networks.
>
> The other NIC on each server and all the workstations all lconnect to a common,
> shared switch defined on a third IP network (say, 192.168.3.*)
>
> Next, enable RRAS (routing services) on the servers. Enable "NAT" routing
> (this is required because the routers won't have any idea how to reach the
> 192.168.3.* network). Define the external side of NAT as the NIC network
> that connects to the router.
>
> Set the default gateway IP on the workstations (via DHCP or manually) to the
> 192.168.3.x address of the server you want to handle that workstation's traffic.
> The default gateway on each server is of course the IP of its corresponding router.
>
> Presto. Everything on the LAN can now talk to everything else. (The routers are not able
> to see the 192.168.3.* network, but that should not be a problem as the server
> NAT takes care of the translation for return traffic.)
>
> There are simpler ways to achieve this. If your routers support defining static networks
> on an interface (Linksys calls it "advanced routing", Cisco calls it "secondary networks",
> etc.) you can create a configuration where the routers themselves route the traffic in and out
> on the LAN side, doing what is sometimes called 'routing on a stick.' This elimiates
> the need for routing on the servers.
>
> Another way to do this is to simply interconnect everything to one switch, and open
> up the network masks so that devices see everything as part of one LAN. Again, this
> is tricky to spell out without knowing a lot of details, and DHCP can be a problem.
>
> It is really hard for me to take you down one of these roads without knowing a whole
> lot more about what you have and what you're trying to do. What I described above is a
> sort-of general solution that should handle most cases gracefully.
>
> Best of luck.
>
> Steve Duff, MCSE, MVP
> Ergodic Systems, Inc.
>
>
> "Joe" <Joe@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:496C3025-8610-4EA3-BE5D-B27E50A80F9C@xxxxxxxxxxxxxxxx
> > Hello, Please bear with me?
> >
> > I am in a situation in which I am forced at this time to be by my current
> > ISP (this will soon change) Here goes:
> >
> > I have two routers and each is assigned a static Public IP by my ISP.
> > I have the two routers because MY ISP at this time cannot assign multiple
> > IP's to a single router/component.
> >
> > I have two servers and I need them to have two different public IPs which
> > they have. In order to have the servers networked internally I had to add
> > another NIC to one of the servers and connect one to Router A and one to
> > Router B.
> > I set the IP at 192.168.1.1 for router A and this is the interface in the
> > browser to access the admin. Router B has the default of 192.168.0.1 to
> > access the admin.
> >
> > My problem is from one server I can access all interfaces in the browser.
> > Going in the opposite direction I can not access but one Interface. However I
> > can share files. I cannot however get this server to join the DC and I think
> > it may have to do with this problem. My Xp machines access the DC no problem
> > and join. The server will not.
> >
> > Please note that the XP machines are not connected any differently than this
> > server that cannot join the Domain.
> >
> > The second NIC in the DC has a IP structure of
> > 192.168.0.5
> > 255.255.255.0
> > NO GTWY
> > NO DNS
> > This is the Nic that is connecting the two routers and ultimately the entire
> > network.
> > Any questions or suggestions I would really appreciate it. Sorry for the
> > long explaination.
> > Thanks
> > Joe
> >
> >
>
>
>
.

Relevant Pages

  • Re: ConnectComputer Problem
    ... I'm a little confused by your network configuration. ... Switch2 --- SBS Server ... switch has internet access all the time, the second switch has the client ... NICs ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... laptop plugged into port on DSL router. ... service, e-mail, and RWW is available to all users on the network. ... The server is a SBS2003 SP1 Standard box without ISA, ... of the two NICs by clicking the Advanced tabs, it won't open that box, ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot browse the network after migration
    ... the cause is the multiply NICs are all enable NetBT. ... >>> browse the network. ... >>> 189101 Understanding NetBIOS Resource Record Flags ... >>> NetBIOS setting from the DHCP server. ...
    (microsoft.public.windows.server.migration)
  • Re: Missing domain controller in network neighborhood
    ... (2 NICs) ... network (My Network Places> Entire Network> Microsoft Windows ... Routing and Remote access is working well. ... It's a Windows Server 2003 Standard and as of today it is ...
    (microsoft.public.windows.server.dns)
  • RE: How Does ISA 2004 Performs Routing
    ... Since I'm still not very clear about the network topology, ... The output of "IPconfig /all" command on ISA and an internal computer. ... >referring to routing between the 2 NICs but was referring to how the ISA ... >server itself routed to the next proxy server in the proxy chain. ...
    (microsoft.public.isa)