Slow login to Domain (probable cause is DNS)

My users take 4-5 minutes to log into the server.  From looking at previous questions, I have an idea of what may be wrong...

I have 2 questions:

1.) How do I make sure that my user's profiles are being stored locally?  I browse to the profile tab of the user properties window, and local path is there, but empty.  Does this just mean it will use the default, or is it still retrieving the profiles from the server?

2.) I have a firewall, and one machine set up as the domain controller.  My firewall's DHCP hands out the DNS IPs that my ISP gave me (T1).  This works fine, but in looking around, I saw that I may need to configure DNS on the domain controller or there will be long login times...


Who is Participating?
Debsyl99Connect With a Mentor Commented:

And no, not a dingbat!

Ok so it sounds like there's no " . " zone which is good, because you can't use forwarders if it's there. In dns, right click the server listed immediately above the forward lookup zone folder, then click properties. This will bring up a box with numerous tabs. In interfaces, specify it's own IP address, ie that of the dns server you're working on. Click the forwarders tab, check enable forwarders and here enter the dns server ip addresses of your isp.

In the TCP/IP properties on the network connection for the server, again check that in the dns server list only it's own ip address is listed.

Then configure the client pc's to be supplied ONLY with the address of this dns server, not the isp. The forwarders enables the server to check the isp's dns servers for any names it can't resolve - ie it forwards the query. On the clients call up a command prompt -> start, run, cmd enter, and release and renew the ip's ie at the command prompt type ipconfig /release (enter - to reloease the ip) than type ipconfig /renew to pick the ip address up again from the firewall. To check type again at the client at a command prompt ipconfig /all to check the the isp's dns servers are no longer lited as dns servers for the client. Hopefully this should sort you out!

Deb :))

oBdAConnect With a Mentor Commented:
Well, if there is no profile specified in the user's properties, a local profile will be used.
But the profiles aren't the problem, it's your DNS settings. Your clients should *only* point to your internal DNS, and so should the DNS server itself. To provide internet access, delete the root zone (".") in your DNS, and configure forwarders to point to your ISP's DNS.

Frequently Asked Questions About Windows 2000 DNS and Windows Server 2003 DNS

Windows 2000 DNS and Active Directory Information and Technical Resources

HOW TO: Troubleshoot DNS Name Resolution on the Internet in Windows 2000

HOW TO: Configure DNS for Internet Access in Windows 2000

Setting Up the Domain Name System for Active Directory

Troubleshooting Common Active Directory Setup Issues in Windows 2000

How to Verify the Creation of SRV Records for a Domain Controller
Debsyl99Connect With a Mentor Commented:
Following on from odba's solution, You'll also need to configure the firewall dhcp to hand out the ip address of your 2000 dns server to the clients and as said, only that one.

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

protemusAuthor Commented:
ok, I understand, but I know nothing about configuring DNS.

All I know is that when I open DNS I get a tree with my servername with two subfolders:

"Forward Lookup Zones" and "Reverse Lookup Zones"

The only entry that has anything in it is "Forward lookup zones"

That has a folder ""

and within "" there are the following entries:
Name | Type | Data
(same as parent) | Start of Authority | [2],, admin
(same as parent) | Name Server |
servername | Host | ##.##.##.##

How do I perform those steps.... I know I must sound like a dingbat, but huh?

feiyauConnect With a Mentor Commented:
Try enableing the Userenv.log to full details .. you can see the actual login in progress and what is your logon doing at what time or instance. That may point you in the right direction. If you find any network related issue slow, you may have to even use Netmon.

UserEnvDebugLevel = 10002 (Hex)

Login again and you will find a log file in


protemusAuthor Commented:

Everyone was great!, my clients log on with no problem!

Thanks for all your help.

You know there really should be a HOW-TO for this configuration.  I have to imagine this is the default network setup for most 20-50 employee businesses!

Thanks again!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.