Dead DC - Slow internet resulting

Hi All,

I'm having a problem with our network that I'm hoping someone can shed
some light on. The other day, one of our 2 DC's died (Hardware
failure) and we didn't bring it back up. We wanted to remove the
server completely from our AD network. This server was also a DNS
server. Now the internet in the office is dog slow. I feel it is
probably related to DNS since the old DC's IP is still listed as a DNS
server in my workstation settings. (sysInternal's BGINFO and in the
registry)

I have removed the server from the Domain Controllers in the AD Users
and Computers MMC. I have also run the
NTSD command line tool to remove the DC from our catalog. I then went
through using ADSI edit to remove all traces of the DC from the
catalog. And also went through DNS removing all references to DC2. I
then cleared the DNS cache on the workstation, removed and rejoined
the domain and rebuilt the network stack (netsh int ip reset), all to
no avail.

Workstations are still listing DC2 as an alternate DNS server. Is
there something I'm missing? How can I completely remove this server
and all traces from our network?

Thanks for the help.

AM

check DHCP, often DHCP is used to configure clients (check clients using
Ipconfig/all - see if the 'removed' DC is still listed as DNS server).

When network comes up, the first DHCP assigned DNS server is used for
address resolution. Your delay is possibly linked to timeout delay.


"AM" <(E-Mail Removed)> wrote in message
news:339d3ac8-1ebb-404c-98ed-(E-Mail Removed)...
> Hi All,
>
> I'm having a problem with our network that I'm hoping someone can shed
> some light on. The other day, one of our 2 DC's died (Hardware
> failure) and we didn't bring it back up. We wanted to remove the
> server completely from our AD network. This server was also a DNS
> server. Now the internet in the office is dog slow. I feel it is
> probably related to DNS since the old DC's IP is still listed as a DNS
> server in my workstation settings. (sysInternal's BGINFO and in the
> registry)
>
> I have removed the server from the Domain Controllers in the AD Users
> and Computers MMC. I have also run the
> NTSD command line tool to remove the DC from our catalog. I then went
> through using ADSI edit to remove all traces of the DC from the
> catalog. And also went through DNS removing all references to DC2. I
> then cleared the DNS cache on the workstation, removed and rejoined
> the domain and rebuilt the network stack (netsh int ip reset), all to
> no avail.
>
> Workstations are still listing DC2 as an alternate DNS server. Is
> there something I'm missing? How can I completely remove this server
> and all traces from our network?
>
> Thanks for the help.
>
> AM

Thanks for the reply. Ok, there were still those entries in DHCP. I
removed them. I also re-started the DHCP and WINS services. ipconfig /
release renew on client shows the DNS server is no longer listed. I
even restarted the workstation to be sure.

However, the internet is still a lot slower than before the DC died.
Where else can remnants of that dead server be?

AM

On May 28, 11:57*am, "Beoweolf" <Beowe...@home.net> wrote:
> check DHCP, often DHCP is used to configure clients (check clients using
> Ipconfig/all - see if the 'removed' DC is still listed as DNS server).
>
> When network comes up, the first DHCP assigned DNS server is used for
> address resolution. Your delay is possibly linked to timeout delay.
>

Beowolf, found the problem. It was a combination of the remnants of
the DNS entries in DHCP as well as one of our DNS forwarders was not
forwarding correctly. After I switched up the forwarders, network
seems to be back to where it was a couple weeks ago.

Thanks for the help.

AM

Hello AM,

Make sure the second DC is also DNS server and has correct Forwarders to
your ISP configured. Make sure the clients use only the domain DNS server.

For the dead DC follow this one to remove it correct from AD database etc.:
http://support.microsoft.com/kb/555846/en-us

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hi All,
>
> I'm having a problem with our network that I'm hoping someone can shed
> some light on. The other day, one of our 2 DC's died (Hardware
> failure) and we didn't bring it back up. We wanted to remove the
> server completely from our AD network. This server was also a DNS
> server. Now the internet in the office is dog slow. I feel it is
> probably related to DNS since the old DC's IP is still listed as a DNS
> server in my workstation settings. (sysInternal's BGINFO and in the
> registry)
>
> I have removed the server from the Domain Controllers in the AD Users
> and Computers MMC. I have also run the
> NTSD command line tool to remove the DC from our catalog. I then went
> through using ADSI edit to remove all traces of the DC from the
> catalog. And also went through DNS removing all references to DC2. I
> then cleared the DNS cache on the workstation, removed and rejoined
> the domain and rebuilt the network stack (netsh int ip reset), all to
> no avail.
> Workstations are still listing DC2 as an alternate DNS server. Is
> there something I'm missing? How can I completely remove this server
> and all traces from our network?
>
> Thanks for the help.
>
> AM
>