Link to home
Start Free TrialLog in
Avatar of namylg
namylg

asked on

Slow logon if I don't add the DNS server IP address in TCP/IP

We have a Windows 2003 server running DNS in our office. We can all log on quickly using obtain a DNS server automatically.

Our remote office also has a Windows 2003 server but it does not have DNS activated. If clients log on using obtain a DNS server address automatically then it can take up to several minutes for them to log on. Ipconfig /all shows the correct DNS server address once they log on.

If they put in the DNS server IP address in TCP/IP then they can log on right away.

Do you have any suggestions on why obtain a DNS server address is so slow for them?
 
Avatar of chad
chad

when set to OBTAIN DNS automatically... where are the clients getting the DHCP info from?
What is set to the dns server of the clients when using dynamic?
Do you have a DHCP server in place?
How is the remote site connected to the main location?  vpn?
At your remote office set the DHCP scope to give out the DNS server at the main office. At the moment I pressume this is not happening, or at least not as efficiently as it should. You should either set your DNS entries static or issues them with your DHCP, AD relies on it too much for you to leave it to try and sort it out for itself.
Avatar of namylg

ASKER

When we set obtain DNS automatically it used the remote DHCP server's address. We have two DHCP server's in place. One here & one in our remote office. We are connected using a frame line.

 I checked the remote DHCP server's scope options and under 006 DNS servers it shows the value as our main office server. We are getting dynamic IP addresses issued o.k.
ASKER CERTIFIED SOLUTION
Avatar of zane_o
zane_o
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial