A funny issue - not really a problem but mildly irritating. Our domain has
morphed from NT 3.51 to 4.0 to 2000, and finally 2003.

We've had to phase out hardware (of course) along the way. Also, we've
renamed servers along the way. At a certain point we had a server named
"helpdesk". It was PDC under NT 4.0 and we upgraded it to 2000. It also
happened to be our DHCP server.

Ever since 2000, when we go to the DHCP MMC, then select "Managed Authorized
Servers" - we get a list of computer names that are no longer valid. The IP
Addresses now belong to the *real* DC's that run DHCP, but the names aren't
correct. I've scowered DNS/WINS and can't find where this authorized list
is maintained. We don't have a computer named "Helpdesk" anymore and for
the life of us we can't figure out where this DHCP applet is grabbing the
name.

Anyone have any good ideas??

brian

The list is maintained in Active Directory. "netsh dhcp show server" will
show the servers as they are listed in AD. Then you should be able to do a
"netsh dhcp delete server <bad name> <ip address>, followed by a "netsh
dhcp add server <correct name> <ip address>.

Danny

--------------------
>From: "Brian Roberson" <(E-Mail Removed)>
>Subject: DHCP - managing authorized servers
>Date: Thu, 29 Jan 2004 18:37:08 -0500
>Lines: 21
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
>Message-ID: <(E-Mail Removed)>
>Newsgroups: microsoft.public.win2000.networking
>NNTP-Posting-Host: tech.lmi.org 198.3.128.12
>Path:
cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.
phx.gbl
>Xref: cpmsftngxa07.phx.gbl microsoft.public.win2000.networking:53158
>X-Tomcat-NG: microsoft.public.win2000.networking
>
>A funny issue - not really a problem but mildly irritating. Our domain has
>morphed from NT 3.51 to 4.0 to 2000, and finally 2003.
>
>We've had to phase out hardware (of course) along the way. Also, we've
>renamed servers along the way. At a certain point we had a server named
>"helpdesk". It was PDC under NT 4.0 and we upgraded it to 2000. It also
>happened to be our DHCP server.
>
>Ever since 2000, when we go to the DHCP MMC, then select "Managed
Authorized
>Servers" - we get a list of computer names that are no longer valid. The
IP
>Addresses now belong to the *real* DC's that run DHCP, but the names aren't
>correct. I've scowered DNS/WINS and can't find where this authorized list
>is maintained. We don't have a computer named "Helpdesk" anymore and for
>the life of us we can't figure out where this DHCP applet is grabbing the
>name.
>
>Anyone have any good ideas??
>
>brian
>
>
>

__
Danny Slye
Microsoft Support Professional
MCSE

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit. Thanks!

Danny,

This worked for two of the fouled up DHCP servers. I have two remaining
that it refuses to delete. Do you know the location in AD (ADSIEDIT) where
I could manually can these from AD?

Brian


"Danny Slye - [MSFT}" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> The list is maintained in Active Directory. "netsh dhcp show server" will
> show the servers as they are listed in AD. Then you should be able to do
a
> "netsh dhcp delete server <bad name> <ip address>, followed by a "netsh
> dhcp add server <correct name> <ip address>.
>
> Danny
>
> --------------------
> >From: "Brian Roberson" <(E-Mail Removed)>
> >Subject: DHCP - managing authorized servers
> >Date: Thu, 29 Jan 2004 18:37:08 -0500
> >Lines: 21
> >X-Priority: 3
> >X-MSMail-Priority: Normal
> >X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
> >Message-ID: <(E-Mail Removed)>
> >Newsgroups: microsoft.public.win2000.networking
> >NNTP-Posting-Host: tech.lmi.org 198.3.128.12
> >Path:
>
cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.
> phx.gbl
> >Xref: cpmsftngxa07.phx.gbl microsoft.public.win2000.networking:53158
> >X-Tomcat-NG: microsoft.public.win2000.networking
> >
> >A funny issue - not really a problem but mildly irritating. Our domain
has
> >morphed from NT 3.51 to 4.0 to 2000, and finally 2003.
> >
> >We've had to phase out hardware (of course) along the way. Also, we've
> >renamed servers along the way. At a certain point we had a server named
> >"helpdesk". It was PDC under NT 4.0 and we upgraded it to 2000. It also
> >happened to be our DHCP server.
> >
> >Ever since 2000, when we go to the DHCP MMC, then select "Managed
> Authorized
> >Servers" - we get a list of computer names that are no longer valid. The
> IP
> >Addresses now belong to the *real* DC's that run DHCP, but the names
aren't
> >correct. I've scowered DNS/WINS and can't find where this authorized
list
> >is maintained. We don't have a computer named "Helpdesk" anymore and for
> >the life of us we can't figure out where this DHCP applet is grabbing the
> >name.
> >
> >Anyone have any good ideas??
> >
> >brian
> >
> >
> >
>
> __
> Danny Slye
> Microsoft Support Professional
> MCSE
>
> This posting is provided "AS IS" with no warranties and confers no rights.
> Please reply to the newsgroup so that others may benefit. Thanks!
>

When trying to remove stale items i'm getting

"There is no such object on the server"

stumped..

brian
"Danny Slye - [MSFT}" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> The list is maintained in Active Directory. "netsh dhcp show server" will
> show the servers as they are listed in AD. Then you should be able to do
a
> "netsh dhcp delete server <bad name> <ip address>, followed by a "netsh
> dhcp add server <correct name> <ip address>.
>
> Danny
>
> --------------------
> >From: "Brian Roberson" <(E-Mail Removed)>
> >Subject: DHCP - managing authorized servers
> >Date: Thu, 29 Jan 2004 18:37:08 -0500
> >Lines: 21
> >X-Priority: 3
> >X-MSMail-Priority: Normal
> >X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
> >Message-ID: <(E-Mail Removed)>
> >Newsgroups: microsoft.public.win2000.networking
> >NNTP-Posting-Host: tech.lmi.org 198.3.128.12
> >Path:
>
cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.
> phx.gbl
> >Xref: cpmsftngxa07.phx.gbl microsoft.public.win2000.networking:53158
> >X-Tomcat-NG: microsoft.public.win2000.networking
> >
> >A funny issue - not really a problem but mildly irritating. Our domain
has
> >morphed from NT 3.51 to 4.0 to 2000, and finally 2003.
> >
> >We've had to phase out hardware (of course) along the way. Also, we've
> >renamed servers along the way. At a certain point we had a server named
> >"helpdesk". It was PDC under NT 4.0 and we upgraded it to 2000. It also
> >happened to be our DHCP server.
> >
> >Ever since 2000, when we go to the DHCP MMC, then select "Managed
> Authorized
> >Servers" - we get a list of computer names that are no longer valid. The
> IP
> >Addresses now belong to the *real* DC's that run DHCP, but the names
aren't
> >correct. I've scowered DNS/WINS and can't find where this authorized
list
> >is maintained. We don't have a computer named "Helpdesk" anymore and for
> >the life of us we can't figure out where this DHCP applet is grabbing the
> >name.
> >
> >Anyone have any good ideas??
> >
> >brian
> >
> >
> >
>
> __
> Danny Slye
> Microsoft Support Professional
> MCSE
>
> This posting is provided "AS IS" with no warranties and confers no rights.
> Please reply to the newsgroup so that others may benefit. Thanks!
>

using adsiedit



find the Dhcproot object in the following AD path DN:
CN=NetServices,CN=Services,CN=Configuration,DC=domain,DC=com



display the attribute Dhcpserver, and remove the corrupt or unwanted
servername/ip address value



once the entry is removed restart the Dhcp server service



They should appear correctly now, you may have to re-authorize them



--------------------
>
>
>Danny,
>
>This worked for two of the fouled up DHCP servers. I have two remaining
>that it refuses to delete. Do you know the location in AD (ADSIEDIT) where
>I could manually can these from AD?
>
>Brian
>
>
>"Danny Slye - [MSFT}" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed)...
>> The list is maintained in Active Directory. "netsh dhcp show server"
will
>> show the servers as they are listed in AD. Then you should be able to do
>a
>> "netsh dhcp delete server <bad name> <ip address>, followed by a "netsh
>> dhcp add server <correct name> <ip address>.
>>
>> Danny
>>
>> --------------------
>> >From: "Brian Roberson" <(E-Mail Removed)>
>> >Subject: DHCP - managing authorized servers
>> >Date: Thu, 29 Jan 2004 18:37:08 -0500
>> >Lines: 21
>> >X-Priority: 3
>> >X-MSMail-Priority: Normal
>> >X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
>> >Message-ID: <(E-Mail Removed)>
>> >Newsgroups: microsoft.public.win2000.networking
>> >NNTP-Posting-Host: tech.lmi.org 198.3.128.12
>> >Path:
>>
>cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10