Import DHCP leases fails.
hello,
i'm trying migrate dhcp 2008 r2 new server 2012 dhcp server.
i'm following steps in following teamdhcp article.
the problem i'm having import of existing leases.
once config , leases exported current server, i'm running running following command import server config, , 1 of scopes initially:
import-dhcpserver –computername <new dhcp server> -leases –file c:\dhcp\export\dhcpexp.xml -backuppath c:\dhcp\backup\ -verbose -scopeid 10.3.37.0
the command imports data successfully, including reservations, not import active leases.
the following error returned upon attempting import each active lease.
import-dhcpserver : failed add ip address lease 10.3.37.x on server <servername>. : the
remote procedure call failed. (1726)
at line:1 char:1+ import-dhcpserver -computername <servername> -leases -fil ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ categoryinfo : notspecified: (10.3.37.11:root/microsoft/...cpserverv4lease) [import-dhcpserver], cimexc
eption
+ fullyqualifiederrorid : win32 1726,import-dhcpserver
import-dhcpserver : failed add ip address lease 10.3.37.12 on server <servername> :
there no more endpoints available endpoint mapper. (1753)
the error occurs when new dhcp authorised or unauthorised, bindings enabled or disabled.
i've left server authorised , ensured dhcp server object has replicated throughout forest, , present in adsiedit, , tried scope import again. same error.
can assist please?
regards
matt
matt
hi,
specific root causes 1753 error include:
- the server app never started (i.e. step #1 in "more information" diagram located above never attempted).
- the server app started there failure during initialization prevented registering rpc endpoint mapper (i.e. step #1 in "more information" diagram above attempted failed).
- the server app started subsequently died. (i.e. step #1 in "more information" diagram above completed successfully, undone later because server died).
- the server app manually unregistered endpoints (similar 3 intentional. not included completeness.)
- the rpc client (destination dc) contacted different rpc server intended 1 due name ip mapping error in dns, wins or host/lmhosts file.
for more information , resolutions please refer to:
hope helps
Windows Server > Windows Server 2012 General
Comments
Post a Comment