Slow logging into 2000 domain

  • Thread starter Thread starter Joe
  • Start date Start date
J

Joe

Hello,
We have 5 xp pro hosts joined to a windows 2000 server domain. When logging
into all workstations the logging on screen just sits for a lagging 2
minutes before the desktop finally appears. I checked the "domain
name.local" zone records and noticed that the internal IP address assigned
to the xp host was incorrect. Also noticed that the router/firewall
providing DHCP services was only assigning the DNS IP address from the ISP
but not he internal IP address of the 2000 server providing DNS. I included
the IP address to the internal DNS, but it still did not show up in the host
upon renewal of IP parameters. I have the 2000 server configured to forward
the DNS recursive queries to the ISP DNS already. Shouldn't the DHCP include
the IP for the internal 2000 DNS server? Event logs on the xp host shows
errors. Below are examples.What am I missing? Thank you for any suggestions.
Source: DnsApi
ID:11165
system failed to register host

Userenv
1054
Windows cannot obtain the domain controller for your computer network.

Joe
 
Joe said:
Hello,
We have 5 xp pro hosts joined to a windows 2000 server domain. When
logging into all workstations the logging on screen just sits for a
lagging 2 minutes before the desktop finally appears. I checked the
"domain name.local" zone records and noticed that the internal IP address
assigned to the xp host was incorrect. Also noticed that the
router/firewall providing DHCP services was only assigning the DNS IP
address from the ISP but not he internal IP address of the 2000 server
providing DNS. I included the IP address to the internal DNS, but it still
did not show up in the host upon renewal of IP parameters. I have the 2000
server configured to forward the DNS recursive queries to the ISP DNS
already. Shouldn't the DHCP include the IP for the internal 2000 DNS
server? Event logs on the xp host shows errors. Below are examples.What am
I missing? Thank you for any suggestions.
Source: DnsApi
ID:11165
system failed to register host
Click to expand...

You has to setup and use DHCP, DNS (and Wins) on the server. You MUST
disable the DHCP on the router. I cant think off any good excuses to use
DHCP on a router if there is a server in the network.

/Per W.
 
I have the 2000
Your AD clients must point to the DNS server set up for the AD domain.
For Internet access set up your AD DNS server to forward requests and list
your ISP's DNS server as the forwarder, or use root hints.


See:
Best Practices for DNS Client settings in Windows 2000 server and in Windows
Server 2003

http://support.microsoft.com/default.aspx?scid=kb;en-us;825036

Setting Up the Domain Name System for Active Directory

http://support.microsoft.com/default.aspx?scid=kb;en-us;237675



How to configure DNS for Internet access in Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;300202





hth

DDS W 2k MVP MCSE
 
First Thank you for your reply,
I agree with your statement, this enables automatic DNS registration.
I just inherited this network. My best quess is this: the reasoning for the
dhcp services on the router is that the client or previous technician
started to add xp homedition units to the environment to save money.
Obviously someone was not doing their job correctly otherwise I would not
be having this issue. Now it's my challenge to make it work. Appreciate the
input. ;-)
 
XP Home cannot join the domain. XP home is a standalone only. Your domain
member workstations must use the domain DNS server for name resolution. As
one of the other posts suggested, you can either point the local DNS server
to your ISP's DNS server as forwarded or, as long as you don't have a root
(".") zone, your DNS server is completely capable of handling Internet DNS
name resolution. I agree with all of the other posts. You sould disable DHCP
on the router, and use the DHCP service on your Windows 2000 server. It is
much more configurable. Be sure to set the scope or server options for DNS,
WINS (if you use it) and router (default gateway). Then you'll have to
reboot the workstations or do an "ipconfig /release" followed by an
"ipconfig /renew". You can test with "nslookup <domain name>" from the
command line. You should be able to resolve the name of your domain. If
not - check your settings again. Even though the home computers can't join,
they can use the local DNS server.

....kurt
 
Joe said:
First Thank you for your reply,
I agree with your statement, this enables automatic DNS registration.
I just inherited this network. My best quess is this: the reasoning for
the dhcp services on the router is that the client or previous technician
started to add xp homedition units to the environment
Click to expand...

<<klipp>>

Let me guess, DELL?

/Per W.
 
Back
Top