Problems installing DSL router with win 2000 server

I have two networks on different sites, almost identical running 2000 server on a dedicated machine with about 10 client PCs running a mixture of NT, 2000 and XP. With internet access via a isdn router

I need to upgrade the router and access to ADSL, but when I connect the new DSL router to the network (having removed the ISDN router) the windows 2000 and XP machine take in excess of 15 mins to boot

Without the server the PCs boot fine and access the ADSL line as normal. The problem occurs only when the server is connected.

The DHCP is set on the router and disabled from the server as with the ISDN set up. I have tried two different types of router, both give exactly the same result. The servers are basic installation of server 2000 with nothing added

Is the Server a DC?
What is the DNS setup of all the machines?
what is the DNS setup of the server?
Is the LAN Nic set to be the highest priority Nic?


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"hartwood" <(E-Mail Removed)> wrote in message
news:A7772CBE-5C1D-4B8D-9D90-(E-Mail Removed)...
> I have two networks on different sites, almost identical running 2000
server on a dedicated machine with about 10 client PCs running a mixture of
NT, 2000 and XP. With internet access via a isdn router.
>
> I need to upgrade the router and access to ADSL, but when I connect the
new DSL router to the network (having removed the ISDN router) the windows
2000 and XP machine take in excess of 15 mins to boot.
>
> Without the server the PCs boot fine and access the ADSL line as normal.
The problem occurs only when the server is connected.
>
> The DHCP is set on the router and disabled from the server as with the
ISDN set up. I have tried two different types of router, both give exactly
the same result. The servers are basic installation of server 2000 with
nothing added.
>
>
>

Thanks for respondin

Yes it is a D
All machines and server obtain DNS from the ISP
Only one NIC in each machine

"Hartwood" <(E-Mail Removed)> wrote in message
news:24A49328-734F-4B84-9298-(E-Mail Removed)...
> All machines and server obtain DNS from the ISP.

There's the problem. All the machines *must* use the DC as their DNS
server. The DC itself must use 127.0.0.1 (localhost) for its DNS Server.

With in the DNS Server configuration itself, there must be a Forwarder's
List created that contains the ISP's DNS. So the process is like this, all
machines look to the DC's DNS first, but if it cannot resolve the FQDN then
it passes the request on to the DNS Servers listed in the Forwarder's List.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

So if I have this right

I need to reset the DC dns to 127.0.0.1 and the client machines must look to the servers ip address for their DNS (10.0.0.1

Dere

Yes.
And then create the Forwarder's List in the DNS config itself.

The 127.0.0.1 is more dependable to use on the NDS itself even though you
could also use its own normal IP or 10.0.0.1. That because the 127.0.0.1
will always be there while situations and problems could arise that might
cause the 10.0.0.1 or the Nic to not be available, then the server would
wake up, not see itsef in the mirror and run screaming down the hall. But it
should always be able to see 127.0.0.1 except for the most drastic
situations.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

"Hartwood" <(E-Mail Removed)> wrote in message
news:A3E58D24-E724-4B2A-A18B-(E-Mail Removed)...
> So if I have this right.
>
> I need to reset the DC dns to 127.0.0.1 and the client machines must look
to the servers ip address for their DNS (10.0.0.1)
>
> Derek
>