Speed up log on to W2k server

A brand new computer running W2k pro is slow to log in to W2k Server. Someone said I have DNS problem. Any suggestion on how to increase log on speed?
ch12345Asked:
Who is Participating?
 
mikecrConnect With a Mentor Commented:
You DON'T NEED FOWARDERS in an AD domain. Why would you set up forwarders in an AD domain????? The client machine only needs to look at the DNS server to resolve names for internal DNS queries if it is logging into the network. It will search for the SRV record of the domain controller, resolve the name and then begin kerberos authentication process. To resolve names properly, there needs to be a host record and SRV record for the domain controller in DNS. You need to configure the client to point to the DNS server in it's tcp/ip properties or pass this information via DHCP. Also, if your running WINs you need to configure this also. This can help with name resolution for the server also.  I neglected to ask however, is this a domain controller that your logging into or a member server?
0
 
steinmtoCommented:
You need to have you w2k pro computer pointing at the dns on your windows 2000 server.  Then on the dns for the windows 2000 server have it configured with fowarders.
To do this do in to DNS under administrative tools.  Then with the dns management tool open right click on your server and go to properties.  Click on the fowarders tab and add your isps dns servers.  If this is greyed out you need to delete the (.) under the foward lookup zones.  You will have to wait about 5 min for this to take effect.  Then go into Dhcp or if you comuter is using a static address and change the dns to point at the ip of the server that host the dns.

Tom
0
 
steinmtoCommented:
If there is no fowarders how would you resolve internet dns?
0
 
mikecrCommented:
The DNS server, since it is not a root server, would use it's root hints to query root servers to resolve names. You should not have to use forwarders unless your having problems resolving names on the internet thru your root hints and normally that's not needed. You have to be careful using forwarders on an AD domain that clients log into because if the DNS server is busy, it can forward your request out onto the internet. This is not normal however it can happen. If your using an AD domain and all of the clients are Windows 2000, you should be using AD integrated zones for ease and security reasons. The root hints would take over to resolve any requests to the internet.
0
 
ch12345Author Commented:
Is this a domain controller that your logging into or a member server?

It's domain controller. I did exactly what you have said. The log on on one machine seemed a bit long and a vendor who came to my company criticized it. I guess putting IP of my domain controller to DNS in client machine is all I need to do.
0
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.