Re: Windows 2000 Server - Problems getting internet to clients

Just because a machine has two NICs, you don't have to use them. You can simply disable one of them. I suspect that Dell has SBS in mind for that config.

The basic problem with a DC having two NICs is that the machines then has two IP addresses linked to its name. This can cause problems with the browser service in particular, but can cause other odd problems. If the NICs are identical you can use NIC teaming, so that the machine effectively only has one IP address, but that is a different situation.

How were you planning to use two NICs? Using a DC as a router is not a good idea. If you are not using it as a router, the two NICs would be in the same IP subnet, and that is a no-no unless they are teamed.

"Michael Jarjoura" <mikejarjoura@xxxxxxxxxxx> wrote in message news:C39C9459.F904%mikejarjoura@xxxxxxxxxxxxxx
Bill,

Could you expound some on not using the dual NIC configuration?

I've got a brand new Dell Poweredge 2900 that has a dual NIC in it and I was
going to set each with their own IP address and set up as main DC.

Am I incorrect? It came from Dell that way?

Could you expound on the dual NIC issues?

Thanks in advance.

Mike

On 12/29/07 6:32 PM, in article eeS2KMnSIHA.1204@xxxxxxxxxxxxxxxxxxxx, "Bill
Grant" <not.available@online> wrote:

To be frank, that is not a sensible way to run your network. There is
really no reason to use your DC as a router when you have a device specially
built to do that for you. Running a DC with two NICs has been a problem
since NT days and it still is. Microsoft recommends that you do not
multihome a DC. The only exception is SBS which is designed to work that
way.

I would just use one NIC in the server and put it on the same hub/switch
as the client machines. If the Netgear has enough ports you can plug them
all directly into that. Switch off the DHCP function on the Netgear and run
DHCP on the server ( or just configure the clients manually, as you will for
the server). All machines, including the DC, use the router as their default
gateway but use the DC for DNS. (This is essential for AD to work properly.
DNS was probably the reason for you past problems).

If you haven't already done so, you also need to modify your local DNS
to forward to an external DNS service or to your ADSL router. (Mine works OK
if I forward DNS to 10.1.1.1, which is my D-Link ADSL router, but will also
work if I set it to forward directly to the DNS server at my ISP).

If you have not used DNS forwarding before, note that it may be disabled
in W2k. You need to delete the . at the top of the DNS tree to use
forwarding.

Briefly you will have a single network with machines all in the same
subnet using the Netgear as the gateway. All machines will use the DC for
DNS to resolve both local and foreign names and URLs. eg

Internet
|
public IP
Netgear
10.1.1.1
|
DC
10.1.1.21 dg 10.1.1.1
dns 10.1..21
|
|
workstations
10.1.1 x dg 10.1.1.1
dns 10.1.1.21

"iain" <iain.32czne@xxxxxxxxxxxxx> wrote in message
news:iain.32czne@xxxxxxxxxxxxxxxx

Hi all,

I am having bother with a small office network I manage. I am tech
savvy but am far from an advanced network guru. This one has got me,
and I would appreciate your help.

Here is the setup.

Client/Server Domain style network.
1x Windows 2000 Server (dual NICs) with 5x XP Pro Clients
NIC#1 is on the motherboard (gigabit ethernet), NIC#2 is a PCI
-NIC#1 goes to a Linksys switch which has the 5 clients connected to
it. The clients have static IP addresses/not DHCP.
-NIC#2 -was- connected to a Linksys wireless ADSL router (with 4 port
switch) which was connected to the phone line //I can't remember how
these IPs were allocated

We started experiencing internet problems...it was taking a long time
to access any web pages, often with pages not coming up at all. After
contacting the (ADSL) ISP they wanted me to check our side of the
connections.

To cut a long story short, I replaced the router (got a Netgear one,
can't remember the model sorry), server NIC card, and the RJ11 system.

I setup the router using its wizard to see that it all worked, and it
does. So the server now has internet. Getting the internet back to the
clients is not working though, I have fiddled about with the IP
addresses, subnets, gateways etc but haven't got the solution. I
clearly haven't got the right one, and as I said, this is a bit out of
my depth. The clients can't ping the router.

Next time I am at work I can get all the IP addresses for you of the
machines etc so you can better advise, but thought there would be some
of you who would know exactly what my problem is.

Myself and a friend have spent a lot of time trying to get this to work
already, with much googling going on as well, but have come to a dead
end and need some help.


General advice would be much appreciated. The person who helped me
install the network initially recommended we use the 2 NIC setup, but
if you have any other recommendations I am all ears.

Also, the Netgear router has a firewall in it, is it ok to relay on? or
should I get good firewall software for the server? or a seperate
hardware firewall entirely?

Thanks in advance for your help,

Hope you are enjoying the festive period

Iain


--
iain
------------------------------------------------------------------------
iain's Profile: http://forums.techarena.in/member.php?userid=38425
View this thread: http://forums.techarena.in/showthread.php?t=880523

http://forums.techarena.in





.

Relevant Pages

  • Re: Urgent! New router and big disaster
    ... NIC, you need to specify an external DNS server for DNS, instead of the ... Both NICs should point to his internal IP for DNS. ... forward ports to it reliably in the router. ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... Both NICs should point to his internal IP for DNS. ... forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW was working, but not since Sharepoint uninstall
    ... Merv hasn't accepted the distinction between a 'router' and a 'NAT router'. ... Two Nics, a static IP address, router ... Connection-specific DNS Suffix. ... calling CNetCommit::ValidateRouterConnectionProperties. ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... Both NICs should point to his internal IP for DNS. ... You should give your SBS a fixed external address so you can forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
  • SBS 2003 Prem CEICW Fails Network Configuration
    ... On a new install (2 NICs), the wizard fails the Networking bit. ... On CEICW start, select Broadband, local router with ip, pri and sec dns ... Connection-specific DNS Suffix: ... calling CNetCommit::ValidateRouterConnectionProperties. ...
    (microsoft.public.windows.server.sbs)
Quantcast