Re: Routing with Multiple NICs.

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



Actually the machine is SBS 2003. And I'm not actually using it as a
router - at least not that I'm aware of. It's main purpose is Exchange
Server, DNS and DHCP. The DHCP hands out IP addresses and the address of
the DNS server and address of the gateway. The gateway address it gives to
clients is that of the cable modem. The server itself actually accesses the
internet via the second NIC which is connected to a DSL modem.

All machines are currently pointed at the server for DNS and the server is
set to forward foreign URLS looksups to a outside server.

We don't really want everyone using the DSL because not only are we running
Exchange server over this DSL put we have a web server as well and all the
web traffic for this server comes in over the DSL. We want to ensure that
when employees are browsing the net, downloading files (or whatever) it
doesn't affect the response of the web server or mail server. Does this
make sense?

Unfortunately - since the server has 2 NICs seems to be an issue when
processing DNS. Like I said - if a user opens up their browser and types in
a URL - it literally takes 5 to 10 seconds for the page to start to display
and all the while the status bar of the browser indicates it is looking up
the site. Once the site starts to load it seems to go very fast but the
initial lookup just drags.... If we change the DNS on the client pc to
point to the cable modem rather than the DC - the client PC is blazingly
fast when browsing the web... It almost as if the client PC sends a DNS
request to the server. THe server looks up the information and then when it
attempts to respond - the response is sent to it's default gateway (DSL)
which doesn't work because the clients aren't on that network. After a
timeout or whatever - the in figures it out and sends the response to the
correct NIC and the reponse gets back to the client. Can that happen?

Thoughts?

"Bill Grant" <not.available@online> wrote in message
news:%23oAd80DpIHA.3860@xxxxxxxxxxxxxxxxxxxxxxx
There are a couple of things to note here. First up, you should not be
running a DC/DNS server as a router (except with SBS server which is built
to run that way). There are all sorts of problems which arise if you do.

The second is that, if you are running a domain, all machines should be
using the local DNS. To resolve foreign URLs, set this DNS to forward to a
public DNS service.

I would recommend that you reconfigure your network so that the DC has
only one NIC. Set all machines, including the DC to use the DSL router as
the gateway but use the DC for DNS. (ie manually set the DC to do this and
reconfigure DHCP so that the client machines do as well).



"Brian Patterson" <me@xxxxxxxx> wrote in message
news:eINxbkCpIHA.3976@xxxxxxxxxxxxxxxxxxxxxxx
I have a server 2003 machine that runs Exchange server. This server has 2
network cards. [LAN] card is obviously connected to a network switch that
all users in the office use (since the server is also the AD domain
controller) and this network also has a cable modem on it. The WAN card
in this machine connects to a network switch that is then connected to a
DSL modem (and this card is the only one that has a gateway defined). The
reason for this is that all email comes in through the static IP address
of the DSL modem and when we send email - it goes out through the DSL
line.

Server 2003 is running a DHCP server that hands out IP address and sets
everyones DNS to that of the server and their gateway to that of the
cable modem that is on the LAN in the office. We prefer everyone in
office use the cable modem and that the DSL line is only used for Email
(in a nutshell). We have noticed that when users change their DNS not to
use that of the server - their internet speed is really fast! *But* when
we go with what DHCP hands out (using DNS on the server) everything runs
really slow. I used performance monitor to check DNS and it is running
fine. I then disconnected the DSL from the server and disabled that NIC
and all the machines in the office started to move a lot faster.

I concluded that I have some strange routing issue going on or
something - because of the way I have the server set to use a different
gateway that the clients in the office should use. Could someone
possiblely shed some light on what I could possibly do to correct this
issue? If you need more details - I would be happy to provide them.

TIA!
Brian




.



Relevant Pages

  • Re: How to enable communication between Two different lans (subnets)/ domains 2003 server based? Ass
    ... You will also almost certainly have DNS problems running a domain behind ... server domain, with a DHCP server running on one of the 2003 boxes. ... the "inner" subnet can see the original subnet and the Internet, ... The .227 machines can see the machines on the 192.168.1.0 subnet and the ...
    (microsoft.public.windows.server.networking)
  • Re: Help with Swing Migration
    ... you can't use your server name references consistently in the ... then the IP address for the Primary DNS Server ... >> the SBSnameDC, then the IP address I should enter into the Primary DNS ... >> DNS entries for the two machines. ...
    (microsoft.public.windows.server.sbs)
  • Re: Group Policy and DNS
    ... > is our only server so it is doing DNS, DHCP, AD, etc. ... I narrowed down to a DNS issue, ... > The machines that are getting the policies ping the server ...
    (microsoft.public.win2000.dns)
  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... The name.local entries are used by my apache server to implement ... change button, more button, the "Primary DNS suffix of this ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)