We are running active directory with Cisco Network Registrar DNS and
DHCP. I will start with an example since its the easiest way to
explain this issue. A user, lets call him Bob, has an old computer
that is named "BOB" on the network. Bob needs to get his computer
upgraded to a more powerful computer. The help desk then switches
Bobs computer out for a new one, when the old one is offline, the new
computer is turned on and configred with the name "BOB". Our problem
is that DNS/DHCP has not updated the record for BOB, it has instead
created a new record named BOB-1. This is ofcourse breaking kerberos
within active directory since machine authentication fails since Bobs
desktop is really not named BOB-1. I know that DNS/DHCP is doing this
because it thinks there is a duplicate named machine on the network by
seeing a new MAC address for a record that already exists. I would
like DNS/DHCP to update the record with the new MAC address, not
create a new record.

Is this something I need to fix on the workstation side or is this a
configuration problen on our DNS/DHCP servers.

any help would be great.

Thanks

I am unfamiliar with "Cisco Network Registrar DNS and DHCP", but Windows DNS
and DHCP do not do what you are describing.

--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
www.akomolafe.com
www.iyaburo.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
"justin koestler" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> We are running active directory with Cisco Network Registrar DNS and
> DHCP. I will start with an example since its the easiest way to
> explain this issue. A user, lets call him Bob, has an old computer
> that is named "BOB" on the network. Bob needs to get his computer
> upgraded to a more powerful computer. The help desk then switches
> Bobs computer out for a new one, when the old one is offline, the new
> computer is turned on and configred with the name "BOB". Our problem
> is that DNS/DHCP has not updated the record for BOB, it has instead
> created a new record named BOB-1. This is ofcourse breaking kerberos
> within active directory since machine authentication fails since Bobs
> desktop is really not named BOB-1. I know that DNS/DHCP is doing this
> because it thinks there is a duplicate named machine on the network by
> seeing a new MAC address for a record that already exists. I would
> like DNS/DHCP to update the record with the new MAC address, not
> create a new record.
>
> Is this something I need to fix on the workstation side or is this a
> configuration problen on our DNS/DHCP servers.
>
> any help would be great.
>
> Thanks