I have two domain controllers. The first one went down about a month
ago. It served as the primary WINS server. Around this same time one
of the applications we use started to get really slow especially
during printer operations. Under network settings user's systems were
changed to the secondary DC since all the stations were set to look at
the primary DC for DNS. This hasn't changed anything, and I also see a
DNS error in the event viewer. It looks as if the system is trying to
transfer information between the primary and secondary DC. That's fine
since the primary is down. I would expect that.

What I can't figure out is what is causing this slowness. ANy ideas?

It's a mostly Windows 2003 environment with XP clients.

Remember that not all applications use DNS for name resolution, so if you
haven't also corrected the WINS side of your name resolution you need to do
that.

--
Richard G. Harper [MVP Shell/User] (E-Mail Removed)
* NEW! Catch my blog ... http://msmvps.com/blogs/rgharper/
* PLEASE post all messages and replies in the newsgroups
* The Website - http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"nick" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I have two domain controllers. The first one went down about a month
> ago. It served as the primary WINS server. Around this same time one
> of the applications we use started to get really slow especially
> during printer operations. Under network settings user's systems were
> changed to the secondary DC since all the stations were set to look at
> the primary DC for DNS. This hasn't changed anything, and I also see a
> DNS error in the event viewer. It looks as if the system is trying to
> transfer information between the primary and secondary DC. That's fine
> since the primary is down. I would expect that.
>
> What I can't figure out is what is causing this slowness. ANy ideas?
>
> It's a mostly Windows 2003 environment with XP clients.
>