Re: Makes no sense to me?

Hello Phillip

I want to get this a little clearer in my head.

I think I need to expain a little first.In my mind the routers come between
the Servers and the Internet? It didn't seem that way in your post.

I am not sure what is first here the servers or the routers to the internet?
In my setup/Config. It is like this

1) NAT Router A gets ISP IP and DNS and then is translated in to the IP of
192.168.1.6
This is statically set to the AD/DC into one NIC. Router A starting or IP is
192.168.1.1
I have opened ports in the router to pass through the needed ports to this
server.
The Router to the ISP is set like this:

69.65.81.xxx
255.255.255.0
69.65.81.1

24.233.167.167
24.233.167.168


This servers NIC is set like this
IP 192.168.1.6
SB 255.255.255.0
GTWY 192.168.1.1

DNS 192.168.1.6
#####################################################

THe second NIC is like this

IP 192.168.1.4
SB 255.255.255.0
NO GTWY

DNS 192.168.1.6
###################################################


This second NIC connects directly to the other Router B


The other server is the same with a different ISP IP and Internal IP range.

I am not too sure of the post that is what I am trying to get here.

Thank you so much
Joe
"Phillip Windell" wrote:

> "Joe" <Joe@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:88E1658A-D030-43E1-BBCB-3FED538D8341@xxxxxxxxxxxxxxxx
> > 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.
>
> "Sharing mailboxes internally" doesn't make any sense,...what does that
> mean? Well, forget that for now,...let's deal with the original issues.
>
> I have a completely different take on this, If you want to hear it.
>
> First!...Run one Nic in all computers. Do not put two nics in them.
>
> 1. The IP# of the NAT Devices you gave is only the Internal LAN Side of the
> Devices,...it is not the real IP# of the Devices as far as the ISP is
> concerned.
>
> 2. Reconfigure the NAT Devices to use the same IP Range on the Internal LAN
> side except use different IP#s. Example, one device would be 192.168.1.1
> and the other would be 192.168.1.2. If these NAT Devices are not capable of
> letting you configure them this way, then replace them with ones you can
> becuase they are not suitable for what you need to do.
>
> 3. If they are running a DHCP Service on them then disable that on one of
> them and leave it run on the other. However I would recommend not using DHCP
> at all from them and run DHCP from one of your suitable Servers.
>
> 4. For the Servers you need published to a Public IP#,......They probably
> call it by some other name in the NAT Device's documentation,...but you want
> to do a Static NAT between one device and one of those Servers. Then repeat
> the process between the other NAT Device and the other Server. Each Server
> will use the NAT Device it is "associated" with as its Default Gateway.
>
> 5. All other machines will use the particular NAT Device for their Default
> Gateway according to which Line you want them to use for Internet Access.
>
> Second.....your Domain "joining" and "dependability" stuff.....
>
> 1. WINS is still a good idea to keep around. Consider running it on the
> DC(s).
>
> 2. All machines ( I meant ALL machines) use only the DC's AD/DNS for their
> DNS Setting in their TCP/IP config. Do not use any other DNS IP#.
>
> 3. On your AD/DNS Server,...add the ISP's DNS IP# as a Forwarder in the
> Forwarders List.
>
> This is the standard design technique recommended by MS.
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
> -----------------------------------------------------
> Understanding the ISA 2004 Access Rule Processing
> http://www.isaserver.org/articles/ISA2004_AccessRules.html
>
> Microsoft Internet Security & Acceleration Server: Guidance
> http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
> http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp
>
> Microsoft Internet Security & Acceleration Server: Partners
> http://www.microsoft.com/isaserver/partners/default.asp
> -----------------------------------------------------
>
>
>
>
.

Relevant Pages

  • Re: Is this a wise configuration?
    ... A have a single DSL connection to the internet at my house. ... connection goes through a router, ... With this many "test" servers running, however, there are many ... Generally referred to as "DMZ" when you search for firewall info ...
    (comp.os.linux.networking)
  • Re: Routing table question.
    ... The servers at either end are not acting as gateways. ... router at each site that acts as our internet gateway, ... If these servers are the only machines on the LAN which can access the ... to the Internet router by default. ...
    (microsoft.public.windows.server.networking)
  • Re: Routing table question.
    ... The servers at either end are not acting as gateways. ... router at each site that acts as our internet gateway, ... If these servers are the only machines on the LAN which can access the ... to the Internet router by default. ...
    (microsoft.public.windows.server.networking)
  • Re: Problem with some network connections
    ... 1) If you're using MS ICS or Windows ... After installed a new router or cable modem replacing dial-up to access ... the Internet, you can't access some web sites. ... I have problem with some servers -> when I try to connect I receive> timeout message. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Makes no sense to me?
    ... I think I tried this with the NAT routers and it wouldn't allow me to access ... Reconfigure the NAT Devices to use the same IP Range on the Internal LAN ... > at all from them and run DHCP from one of your suitable Servers. ... > Gateway according to which Line you want them to use for Internet Access. ...
    (microsoft.public.win2000.networking)