When managing your Cisco DHCP, ASA devices, and Windows DHCP servers with IPAM, you may encounter errors that refer to DHCP connection errors. Generally speaking, most of these errors are easy to address.
IPAM uses Windows RPC calls to retrieve the list of scopes, leases, and reservations. Since IPAM runs within a local service, IPAM requires a Windows username and password to authenticate with the remote DHCP Server. IPAM will first impersonate the provided user on the Orion NPM box, and then proceed with using RPC calls. The following are some common errors and suggestions for troubleshooting.
IPAM Reports “Bad username or password”
1) This error can occur when the valid user account on the Orion host has no meaning to the DHCP Server. Verify the account used is valid on the DHCP Server.
2) This error can also occur when the provided password is not correct on the DHCP Server. Verify that the provided account and password is both identical and functional on both the Orion host and DHCP Server.
IPAM Reports “The RPC Server is Unavailable”
1) This error can occur when the DHCP Server is unable to receive or respond to RPC Requests. Verify there is no firewall preventing the Orion host from performing RPC calls. A simple method is to verify with Administrator accounts that windows file sharing is possible. An alternate way to verify this is a telnet to the IP address provided in the Orion node on port 445. If the connection is not rejected, it is likely something else.
2) If this occurs intermittently, verify that the DHCP server has enough client access licenses.
IPAM Reports “Insufficient permissions”
1) Verify that the provided user account is part of the “DHCP Users” group on the DHCP Server.
If you do not yet own IPAM and you are tasked with managing DHCP servers, check out the following overview pages to learn what IPAM can do for you.