Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Dear all...
I have one problem with our windows 2003 server and windows 2000 server and windows 2008 server.
when any user want to log in the domain from his computer, it takes long time. it takes around 3 to 5 minutes. and the funny thing is the following...
I have one old pc, where I can log in very fast. after some problems, I had to format and reinstall windows. I join the domain and I use the same username. now it takes 5 minutes to log in, exactly in the applying user settings phase. this means that there is some missing configuration in the pc or in the server.
is there any way to accelerate the log in procedure?Thanks.

ok... this is a good question... it point to ISP DNS. when I remove ISP DNS, it will log in quickly...
but note that before formatting, it points to ISP DNS, and it log in quickly....

domain machine must point to the ms dns server. This is the only dns server, [assuming dhcp autoupdate of dns is engaged or you manually entered the workstation in dnbs]that knows of your local pcs.
The isp certainly doesn't.
Without dns resolution the workstation resorts to broadcasts to get an answer and that is what adds the extra time.
Your ms dns server should have the isp's dns servers liked in the forwarders tab. This way when ms dns gets a request for an internet address like yahoo.com, which it doesn't know about, it sends the request to the isp dns servers when in turn reply.

Your guess is as good as mine.
You could have had an entry for your server in the hosts file which is also used for name resolution

I don't want to go to internet thru the server... I want a solution to accelerate the logging in. I use the server for active directory and not for DNS solution. I already have the router for this goal.
but I still don't know why two pc having the same configuration (DNS and others) and each one take a different time to log in. and it's not a couple of second, it's 5 minutes.

Omar,
Wanderer is right!
You can forward the external DNS to your ISP, however, since you only using your server for AD, following the following step: In your router, configure you DNS to include you AD IP address, some router allow up to three DNS, if yours does,make sure your AD IP is the last notwithstanding, if it only take use... do not include your ISP alternative DNS.
That's should solve your problem with your client logging in very fast and going directly on the internet.
To answer you question: the reason you laptop was working okay was that the DNS had a cache in the registry that was allowing your computer to locally point to the ISP DNS, my guess is, you had that laptop configure for the internet on the same ISP before you even set up you server environment... Need more help... contact me
www.karlwebdesign.com

omarmallat even though I explained the correct Microsoft dns setup, you seem to have missed what it was all about.
Go to ms web site/technet and lookup then read about DNS.
Your internet is not going thru the server. Only name resolution is and its tiny and fast.
You can configure as I detail for fast domain logons or decide not to and accept the consequences.

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |