old DHCP server still shows up

I decommissioned an old server over a year ago (Server Name: SRV01)

I built a NEW server (Windows 2003 Server) and made it a domain controller, added DNS, WINS and DHCP.

Upon launching the DHCP console (which is empty by default), I right-clicked 'DHCP' and selected 'Add Server'

When the 'Add Server' dialog box appears there are two sections. The top section allows you to add (or browse) for a DHCP server. The bottom section allows you to select from a list of 'detected' DHCP servers. In that list I see my OLD server! (srv01.domain.com)

What??
Is the DHCP console telling me that it still 'sees' SRV01 on my network, or is it reading that from a registry key, or (most likely) does my entire Active Directory network think SRV01 is still around, and just down for the time being?

I dont want to start having network slowdowns because Active Directory still thinks SRV01 is around somewhere.

Any ideas? I'm not experiencing any issues yet (that I know of), I have 2 domain controllers, all servers are Windows 2003 Server ... just makes me nervouse that SRV01 is showing up in this list.

(By the way I know for 100% certain that there are no devices on my network called SRV01, there are no machines with that name when I browse the network or scan active directory. There's no leftover record in DNS called SRV01 and if I ping SRV01 I get no reply ... I'm not going crazy ;-)
LVL 10
ecarboneAsked:
Who is Participating?
 
DenverRickConnect With a Mentor Commented:
On your new Server:
1. Make certain that it's own address is the only DNS Server in the Network Setting.
2. In a command prompt:
    a. Net Stop Netlogon
    b. Net Stop DNS
    c. Ipconfig/flushdns
    d. ipconfig/registerdns
    e. Net Start DNS
    f. Net Start Netlogon
Then refresh re-check the _msdcs.  The new server must appear there, if it won't, you have a bigger DNS problem somewhere in your configuration.

If the new server does show up then delete all the other servers records.

Let me know the results.

DR
0
 
DenverRickCommented:
It's reading it from your DNS records which I assume were obtained from the old DNS Server as well.  Go into DNS on the new Server and delete all the records for the old server.  Especially in the _msdcs.domain.local (or whatever) tree.
0
 
ryansotoCommented:
I would also run a metadata clean up and see if the old server is still in Active Directory
http://technet.microsoft.com/en-us/library/cc736378.aspx
0
Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

 
ecarboneAuthor Commented:
DenverRick,
In DNS, if I expand Forward Lookup Zones | domain.com | _msdcs ... the old server is listed:
(In fact, it's the ONLY server that is listed in there).

under _mcdcs it has a CNAME:

FQDN:
   f94e5e04-86be-4629-ad48-7bd18c71d149._msdcs.domain.com
FQDN for target host:
   srv01.domain.com

Should I just delete it?
(By the way in DNS this is the ONLY place where SRV01 exists.)

Thanks for your help!
0
 
DenverRickCommented:
On your new Server:
1. Make certain that it's own address is the only DNS Server in the Network Setting.
2. In a command prompt:
    a. Net Stop Netlogon
    b. Net Stop DNS
    c. Ipconfig/flushdns
    d. ipconfig/registerdns
    e. Net Start DNS
    f. Net Start Netlogon
Then refresh re-check the _msdcs.  The new server must appear there, if it won't, you have a bigger DNS problem somewhere in your configuration.

Let me know the results.

DR
0
 
ecarboneAuthor Commented:
tried above steps on srv08 (one of my two NEW dns servers)
srv01 still appears.
srv08 did not appear.

also i noticed this ... (may or may not be related)

in active directory sites and services
sites | default-first-site-name | servers

in that screen i see 'srv01' (along with my other servers)

perhaps when i decommissioned srv01 last year i didnt follow all of the steps to properly remove it from the domain, so active directory and dns think the server is still around.
0
 
DenverRickCommented:
Could be.  However, if the CNAME records for the current DC's are not right you will definitely have problems.

Install Server Tools (from 2003 CD) and run Netdiag and DCDiag on each DC and advise what errors you get.
0
 
ryansotoConnect With a Mentor Commented:
As I stated you should run a metadata clean up this will remove all old DC's from the domain
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_22043974.html
0
 
ryansotoCommented:
Apologies I pasted the wrong link
Link to clean up metadata
http://technet.microsoft.com/en-us/library/cc736378.aspx
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.