windows 2000 server - dynamic update of the dns from dhcp failed

[jms2003]

Hello Guys !

I have this problem since the begininng : I set up a new w2k server CPD with DHCP (working fine), DNS associated with active directory.

I'm quite sure all options for updating dns from dhcp are well checked, but no entries are created in the dns.

Also, I had the same problem as many other guys : slow login, "domain controller for your domain could not be contacted" etc etc. I set dns of the cpd in clients settings : some are loging fine now (most of them) and quick, but a few are remaining slow.

Finally, the access to network drives is very slow, and the problem vanished if the pc is in workgroup.

I assume all this issues have the same origin, but what exactly...

Thanks in advance for your help friends (and if someone has a link to a good, complete, clear and simple tutorial for setting a CPD on win2k server, I take it !)

Chuss !

 

[ksukenny]

are you using dhcp or static ips on the clients? you can specify the dns server, gateway and other settings throught dhcp. also in order for dynamic dns to work you have to make sure you have the setting enabled in the tcp/ip properties of your nic. double check to make sure dns is set up properly and that your clients are pointed to the correct dns server. slow logins times are usually related to dns setup incorrectly.

 

[jms2003]

hi ksukenny

thanks for the answer.

Yes, client are using dhcp service from cpd server.
there is no problem with client to get ip from the dhcp and the leases are well shown in the dhcp clients leases list on the server. Setting the cpd adress as dns for clients solved the problem of slow loging for most of them.

And the options for updating dns is well checked on clients nic/tcp-ip properties.

And slow performance on network drives remains also (disapearing when setting pc in workgroup). precision : i saw exactly the same problem with xp clients on another 2000 domain.

 

[Seaspray0]

2000, XP, and 98 operating systems can do dynamic updating on their own. The client will attempt to update DNS. Is your dhcp set to always update your clients? Wrong! You only want dhcp to update your clients if they don't support dynamic update (Win95 and NT). You don't want both the client and DHCP updating DNS. You get a conflict of ownership and it can cause the record not to be created. Also, if your DHCP is on a different server than DNS, add it to the DNS Update Proxy group in active directory so it has permissions to update DNS for those clients that need it.