Slow Logins

[Guest]

I am running windows server for the first time and have set up a working
active directory, but it takes 15+ minutes to login. The server is running
windows 2003 server on 4x550 MHz PIII Xeon CPU's 1024 MB ECC PC133 RAM and a
10/100 Mbps NIC. It is connected to a 10/100 Mbps switch connected to 25+
clients. The clients are running windows 2000 pro on PIII 800 MHz CPU's with
512 MB of PC133 RAM using 3com 10/100 NICs. When logging on locally to the
server it is fast, from a client very slow!

 

[Danny Sanders]

How do you have DNS set up? What DNS server do the clients point to?

hth
DDS W 2k MVP MCSE

 

[Guest]

They are set up to go through a different dns server, since the domain
controller has no access to the internet and CANNOT be configured to have
internet access while each client machine goes through our school's proxy to
get to the internet, i will try using the domain controller's dns

 

[ptwilliams]

You *must* use internal DNS when a member of an NT 5.x domain. You will
have to configure the DC to forward to the proxy server, another internal
DNS server or an external DNS server. But the DC must point to itself, and
all clients to it (and other internal DNS servers for this domain if there
are multiple DCs and many clients).

--

Paul Williams

http://www.msresource.net
http://forums.msresource.net
______________________________________
They are set up to go through a different dns server, since the domain
controller has no access to the internet and CANNOT be configured to have
internet access while each client machine goes through our school's proxy to
get to the internet, i will try using the domain controller's dns

 

[Enkidu]

I can see where Danny was going. AD recquires a working internal DNS.
Well, technically the DNS could be on the moon, but it must support
SRV records and preferably a couple of other things too. Practically,
it will have to be internal.

When the DCs DNS is set up you must configure the clients to *only*
use that DNS server and no other. Don't configure the second DNS in
the clients to the ISP's DNS. That won't work and *will* cause
problems.

Configure the DNS server's forwarders to contact the ISP's (or other,
external, DNS) and configure its own NICs to reference itself for DNS.

The intent is for clients to request DNS info from the internal DNS
for everything - Domain information and Internet information. The DNS
server relays requests for DNS information to the Internet DNS
servers, such as the ISP's DNS servers.

If you can't allow the DC/DNS server to access the Internet for DNS
services, then you have a real problem.

Cheers,

Cliff