Slow performace of network

[mhburney]

Hi everyone,

Quite a number of times i have noticed that once i shutdown PDC (windows 2003 active directory) at work and allow BDC to take over after working hours the clients complain that not only the network but also their systems performance degrade ALOT!! and when they pull the network cable out the system returns back to its normal speed/performance.

Any clue why this might be..only reason i can find is that my BDC is quite slow as in low spec hardware. could it be?

Cheers!

 

[pagy]

Firstly there is no PDC or BDC with 2003 and active directory.

Could be a DNS issue, do both DCs have DNS installed and is it working correctly?

Do you use DHCP? What DNS server address are you sending out via DHCP? If you want redundancy you need DNS running on both DCs, the DNS zones replicated, (easy if they are AD integrated as AD takes care of that for you) and hand out both DC ip addresses for clients DNS.


Paul

MCSE 2003

"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[porkchopexpress]

Is the DNS service on the server you call the PDC? (Technically there isn't a PDC in Win2k3)

Also if the users have mapped drives or the system was using something in the sysvol/netlogon folder on the PDC then it could cause it to pause while waiting for a responce.

 

[mhburney]

well yuh i agree no BDC PDC concept with AD..but my secondary domain controller basically that way after working hours. anyhow...no DHCP either both have replicated DNS zones where updates are AD controlled. and i dont think there is anything that can make the systems work slow..another interesting bit i have notices is that not all clients go slow only a few systems have the problem which makes me think maybe there is something wrong with the clients.

basically iam still looking for an answer lets see

 

[porkchopexpress]

I still think it will be that the clients are looking for resources that are no longer there. Next time tell them to logoff and on again this should force them to authenticate to the second DC. Also check that they don't have and shared components on the first server e.g. redirected desktop, roaming profiles and so on.