Re: Error DHCP Windows 2008 R2, DHCP client is not a reserved clie

Sorry, I communicated with MS Support in German.

Than you for the translation Meinolf

Kind regards
Christoph

"Meinolf Weber [MVP-DS]" wrote:

Hello Ace Fekay [MCT],

I'll try to translate, i know this language:-)


After some testing i realized, that this error happens if you try to reserve
ip addresses outside the scope range but inside the scope-subnet.

With Windows 2008 it is possible to reserve addresses in a scope that are
outside of the scope range.

This results in windows 2008 R2 in the error message: The specified DHCP
client is not a reserved client.

Then i have to extend my scope and have to work with more exlusions.

Remark:
Migration with netsh has worked.
With the server migration tool it is also smart
- check out

Video, Migrating DHCP using the Windows Server 2008 R2 Migration Tools
http://edge.technet.com/Media/Migrating-DHCP-using-the-Windows-Server-2008-R2-Migration-Tools/

DHCP Server Migration Guide
http://technet.microsoft.com/en-us/library/dd379535(WS.10).aspx

Thank you very much for your feedback.

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


"Christoph Jandek" <ChristophJandek@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in message news:2FC7B06C-0728-4F17-B5D7-2E8D35E18863@xxxxxxxxxxxxxxxx

Sorry, I am not familiar with this language. Do you have a
translation?

Ace

Nach einigen Tests ist mir aufgefallen, dass Reservierungsversuche
von IP Adressen auserhalb des Scope Ranges aber innerhalb des
Scope-Subnetzes zu diesem Fehler führen.

Bis Windows 2008 ist es möglich IP Adressen innerhalb des Scope
Subnetzes
zu
reservieren, die außerhalb des konfigurierten Scope Ranges liegen.
Mit Windows 2008 R2 führt dies zu der bekannten Fehlermeldung: The
specified DHCP client is not a reserved client.

Dann werde ich eben meinen Scope erweitern und mit mehr exlusions
arbeiten müssen.

Anmerkung:
Die netsh Migration hat funktioniert.
Mit dem Server Migrations Tool ist die Migration auch sehr smart
- siehe
Video, Migrating DHCP using the Windows Server 2008 R2 Migration
Tools
http://edge.technet.com/Media/Migrating-DHCP-using-the-Windows-Server
-2008-R2-Migration-Tools/
DHCP Server Migration Guide
http://technet.microsoft.com/en-us/library/dd379535(WS.10).aspx
Danke für euer Feedback

Christoph

"Christoph Jandek" wrote:

Very good point - in a new scope, reservations can be added.

For the migration I used this article:
http://support.microsoft.com/kb/962355
How to move a DHCP database from a computer that is running Windows
Server
2003 to Windows Server 2008
I'm in contact with MS Support. He mentioned to use the Windows
Server-Migrationtools for Windows Server 2008 R2.
I'll check this, though I have problems installing the tools on
Windows
2003
R2 and the process seems not that simple.
Hope I can fix it without doing the migration again.

"Ace Fekay [MCT]" wrote:

"Christoph Jandek" <ChristophJandek@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message
news:45B99580-ECE3-4CCE-9582-8042C8C972B0@xxxxxxxxxxxxxxxx

It is possible that the migration method, since it has not been
officially
released yet, could be the issue.
One of the Microsoft engineers monitoring the Social forums link,
did mention it hasn't been release yet in the following link.

http://social.technet.microsoft.com/Forums/en-US/winserverMigration
/thread/c3523239-28bf-419e-b266-98ed670b84e2

He did mention the following article Did you use the following
article
to do
the migration?
How to move a DHCP database from a computer that is running Windows
NT Server 4.0, Windows 2000, or Windows Server 2003 to a computer
that is running Windows Server 2003
http://support.microsoft.com/default.aspx/kb/325473

As a test, if you were to create a new scope, does it still occur?

Ace

The Server running DHCP Server is a Windows Server 2008 R2 DC.
There are no EVents it EventID# 20018 in the LOGs.

DCIAG reports no error.

The DHCP DB was migrated from Windows 2003 using
"netsh dhcp server import c:\w2k3DHCPdb"
The Server is authorized in the AD and it is serving clients.
Existing,
migrated reservations are working fine.
Christoph

"Ace Fekay [MCT]" wrote:

"Christoph Jandek" <ChristophJandek@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote
in
message
news:4B9C0871-2571-4816-B0BC-5D3C5D8C81C8@xxxxxxxxxxxxxxxx
Hello,

I cannot add a reservation to a DHCP scope on windows server
2008
R2
Errormessage: The specified DHCP client is not a reserved
client.
The DHCP server is authorized in AD and has no problems to offer
and
renew
leases.
With Windows Server 2003 R2 and Windows Server 2008 (no R2)
there
is no
problem to reserve clients.
Does anybody know this problem and can help me?

Kind regards,
Christoph
Is the Windows 2008 R2 DHCP server a DC?

Is there an EventID# associated with this error in Event viewer?
If
so,
is
it EventID# 20018? If not, please let us know, as well as if
there
are
other
eventID errors on the DCs.
According to the following, it may not be authorized or the DHCP
server
is
not joined to the domain.
Error Message:The specified DHCP client is not a reserved client.
Explanation: Stand-alone DHCP servers are not allowed to operate
when
Active
Directory is operating. ...
http://technet.microsoft.com/en-us/library/cc976339.aspx
-- Ace

This posting is provided "AS-IS" with no warranties or guarantees
and
confers no rights.
Please reply back to the newsgroup or forum for collaboration
benefit
among
responding engineers, and to help others benefit from your
resolution.
Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA
Messaging
Microsoft Certified Trainer
For urgent issues, please contact Microsoft PSS directly. Please
check
http://support.microsoft.com for regional support phone numbers.



.

Relevant Pages

  • Re: Error DHCP Windows 2008 R2, DHCP client is not a reserved clie
    ... This results in windows 2008 R2 in the error message: The specified DHCP client is not a reserved client. ... Migration with netsh has worked. ... Migrating DHCP using the Windows Server 2008 R2 Migration Tools ...
    (microsoft.public.win2000.networking)
  • Re: SwingIt Pain and Suffering
    ... BTW - I did purchase the Advanced Windows Small Business Server 2003 Best Practices book and consumed large parts of it before starting this project. ... That being said, I do feel like his documentation could greatly benefit by having some more detailed check points for verifying the health of AD at various steps along the way, and what steps to take or resources to consult if the replication doesn't seem to be going according to plan. ... BTW, even after discovering this constraint and disabling the firewalls on my destination server as part of the base OS install, replication still initially failed and I was dumb founded to find the firewall reenabled. ... I did complete the AD replication from the migration computer to the destination computer as planned. ...
    (microsoft.public.windows.server.sbs)
  • Re: NT4 to 2003 with Dell2650
    ... PDC for good; ie Will the accounts stay on the PDC to allow me a testing ... The Recommended Migration Order is listed below for your reference: ... Yes, after completion of ADMT, you may logon to the new Windows Server 2003 ...
    (microsoft.public.windows.server.migration)
  • Re: Wide area failures?
    ... The W2003 server is the DNS host/primary nameserver. ... was informed just this afternoon that DHCP updating to the DNS server ... to create a Windows Domain Server and apply ADS in the near future. ...
    (microsoft.public.windows.server.dns)
  • RE: migrating users and other from win2k to win2003
    ... You may migrate the users, NTFS permissions, IIS and DNS to the new Windows ... Server 2003 system by using the Active Directory Migration Tool. ... This article assumes that the source domain is a Windows 2000-based ...
    (microsoft.public.windows.server.migration)
Loading