Takes clients 15 - 20 minutes to log on to W2K domain 2

[msbrew]

Small network with single W2K sp4 server with 8 W2K client workstations.

Takes clients 15 - 20 minutes to log on.
Is the long client workstation logon problem because the client workstations are pointed to ISP's nameserver and that their is no configured DNS server on the local network that does resolving on the lan?

Server Settings:

Host Name: server1
Primary DNS suffix: bchmed.com
Node Type: Broadcast
IP Routing Enabled: Yes
Wins Proxy: No
DNS Suffix Search List: bchmed.com

DHCP Enabled: No
IP Address: 192.168.5.10
SN Mask: 255.255.255.0
Default Gateway: 192.168.50.1
DNS Servers: 207.191.50.10 206.222.97.82
------------------------------------------------------
First Server Event Log error messages:
Computer: Server1
Source: Netlogon
Type: Warning
Category: None
EventID: 5781

Description:
Dynamic registration or deregistration of one or more DNS records failed because no DNS servers are available.
--------------------------------------------------
Second Server Event Log error messages:
Computer: Server1
Source: DnsAPI
Type: Warning
Category: None
EventID: 11151

Description:
The system failed to register network adapter with settings:
Host Name: server1
Adapter-specfic Domain Suffix: bchmed.com
DNS server list:
207.191.50.10, 206.222.97.82
Sent update to server: None
IP Adress(es):
192.168.50.10

The cause of this DNS registration failure was because of DNS server failure.
-------------------------------------------------
Workstations are DHCP clients that get their ip addresses from the ISP's onsite router that provides the ISP's DNS servers IP address information as well for connecting to the internet.

First Client Workstation Event Log
Computer: WS2K7
Source: DnsAPI
Type: Warning
Category: None
EventID: 11151

Description:
The system failed to register network adapter with settings:
Host Name: WS2K7
Adapter-specfic Domain Suffix: bchmed.com
DNS server list:
207.191.50.10, 206.222.97.82
Sent update to server: None
IP Adress(es):
192.168.50.26

The cause of this DNS registration failure was because of DNS server failure.
----------------------------------------------------

Second Client Workstation Event Log
Computer: WS2K7
Source: Userenv
Type: Warning
Category: None
EventID: 1000

Description:
Windows cannot determine the user or computer name. Return value (1722).


------------------------------------------------------

Is the long client workstation logon problem because the client workstations are pointed to ISP's nameserver and that their is no configured DNS server on the local network that does resolving on the lan?

 

[mlichstein]

Your DNS is not configured correctly on either the server or the clients.

The DC should point to itself for primary DNS and secondary should be left blank. The ISP should not be configured in the DNS tab of the TCP/IP settings of the DC or the clients at all.

Once you change the DNS settings on the server, run the following two commands:

ipconfig /flushdns
net stop netlogon & net start netlogon

This will register the records you are missing in DNS. Then fix the configuration on the clients (hopefully you have DHCP) and either do an ipconfig /flushdns or just reboot them.

The ISP's DNS server address should be entered in the DNS forwarders tab on your DNS server. Open the DNS console (dnsmgmt.msc) right click on the servername, properties, forwarders tab.

 

[msbrew]

I don't think DNS is installed. When I look at AD users and computers the server shows up as a DC but there is no DSN.

 

[mlichstein]

You don't see the DNS management console in start, programs administrative tools?

What happens when you go to start, run and type dnsmgmt.msc?

Did you make the changes I suggested?

 

[msbrew]

No, the DNS management console not there.

I can't make the suggested changes.

Can a AD exist without DNS installed?

 

[mlichstein]

No it can't. It doesn't have to be a Microsoft DNS server, but that is what is typically used.

Try going to start, run, services.msc. Look for the DNS server service. If it is there, is it started?

dnsmgmt.msc from start, run doesn't work either?

 

[msbrew]

DNS client service is there BUT no DNS server service. Dnsmgmt.msc doesn't run either.

 

[mlichstein]

Alright, then I guess we better install it. It's in add/remove programs, add/remove windows components, networking components.

Before you install the DNS service, point the server to itself for primary DNS and make sure secondary is blank.

When you install the DNS service, go into the DNS console, look under the forward lookup zones folder and let me know if there something there already. If not, you'll need to configure a zone.

 

[msbrew]

Thank you for your kind assistance.

 

[dearingkr]

Excellent advice, mlichstein!
Here's a star.

DNS configuration is one of the most common errors I've seen when setting up a new network.

My 2 golden rules of DNS are:

1. Public DNS servers should not be configured anywhere on your network except your server's DNS Forwarders

2. ALL devices on your intenal network should be configured to use your server(s) for DNS

MCSE CCNA CCDA

 

[msbrew]

Thank you all. DNS is set up and all is well.