Re: Router DNS and Gateway question...

Tech-Archive recommends: Fix windows errors by optimizing your registry

First and formost: IS IS WORKING NOW OR ARE YOU HAVING TROUBLE? Explain any trouble you are having or think you are having.

Second: Are both routers configued to pass out the same IP range via DHCP on the same network and connected to the same "switch"? Are both routers assingned the same internal IP of 192.168.1.1? This would NOT be the way to do it.

Having said that, ans assuming it is working now (it wouldn't be working right if the answer to the above question is yes)... the following is some general advice.

Assuming your are NOT running a DOMAIN: I would set the Router DNS entries 1 and 2 to be the ISPs name servers. I'd leave the current client (and servers) setup the same as they are, using the router for a Gateway and Internat DNS.

If the server(s) are a Domain Controller(s), all the DHCP clients should be set to the DCs IP for DNS and the Router's DHCP server should be disabled.

-Frank

"James Newman" <jnewman33@xxxxxxxxx> wrote in message news:Qfedna8PT7I4m0XUnZ2dnUVZ_r6WnZ2d@xxxxxxxxxxxxxxx
Hey all,

I have inherited and small Windows Server 2000 network with two servers
and 16 workstations. There are some settings that are not what I would
expect and wanted to see what the experts would think. :)


The service provider is providing two static IP's and there are two
routers each set to one of the IP's.

Both routers then feed into a switch that has the servers and
wokstations connected.


Question 1:

On both routers the DNS portion of the static WAN setup looks like this:

DNS1 - Internal address of the main server
DNS2 - Service providers DNS server

Is this correct in some situations?



Question 2:

Both servers are using the same gateway 192.168.1.1

Does this create problems?



I hope I have described things clearly. Any help is greatly
appreciated.


James


.

Relevant Pages

  • Re: Page Cannot Be Displayed
    ... 159211 Diagnoses and Treatment of Black Hole Routers ... Les Connor [SBS MVP] ... > It appears that the problem isn't on the servers, ... Ethernet adapter Network Connection: ...
    (microsoft.public.windows.server.sbs)
  • Re: Joes Twisted-up Network
    ... How do you get these routers to work toghether in an AD DC enviroment ... I do not see a DNS option on the LAN side of these routers. ... >> seperate public IP's on each router for two servers. ... >> the XP machines get but the servers are crucial. ...
    (microsoft.public.windows.server.networking)
  • RE: Chosing a hosting server.
    ... (you can remotely control them). ... > 50 wireless nodes would control them enough for a start. ... > for your servers, ... > front routers for my network. ...
    (freebsd-isp)
  • Re: Help In network configuration.
    ... The DLink and many other routers will easily meet your requirements. ... the private IP addresses of your Central Servers. ...
    (microsoft.public.win2000.networking)
  • Re: Joes Twisted-up Network
    ... Your first DC will host a DNS zone with the same name as your AD domain ... > seperate public IP's on each router for two servers. ... > the XP machines get but the servers are crucial. ... These routers may not work but I am not ...
    (microsoft.public.windows.server.networking)