Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

RPC error when adding new DHCP server to IPAM

Hi, I am in the process of migrating my Windows DHCP servers to Windows Server 2022, the existing DHCP servers are Windows 2012 R2 and are integrated in to IPAM, which is version 2024.2.0. When I try to add the new 2022 DHCP server to IPAM I continually receive "The RPC server is unavailable" when the credentials are tested. The credentials used work with the existing servers and also allow a drive to be mapped and RPC management to be achieved from the IPAM server to the new DHCP server. Telnet to ports 135 & 445 from the IPAM server to the new DHCP server connect successfully. To troubleshoot I have completely disabled all windows firewall settings and removed all security products on the 2022 DHCP server. These actions have made no difference to the outcome, the error "The RPC server is unavailable" remains. If anyone in the community has any suggestions for further troubleshooting it would be helpful. Thanks in advance!

Find more posts tagged with

Accepted answers

donrobert5

On the Orion server:
1st Connection Error Test...........

1. Start > run > type MMC where allowed.

2. Click on File and then choose Add Remove Snap in and choose Event Viewer

3. When the popup appears click the radial button next to "Another computer:". Here you can Browse your network or just type the DHCP server name in the place provided.

4. click the check mark next to "Connect as another user" then click the "Set User" button.

5. Fill in the credentials used by IPAM to access DHCP.

If you can connect, try logging into the Orion server and see if you can login into the Orion Server using the same credentials as IPAM impersonates the specified account on the local computer to gain access.

https://solarwindscore.my.site.com/SuccessCenter/s/article/Test-failed-Access-is-denied-when-adding-a-DHCP-server-in-IPAM?language=en_US

I also found this on thwack.

thwack.solarwinds.com/.../rpc-issue-ipam

All comments

donrobert5

paulatwork

Hello,

Thanks for the input, it was most helpful! I should have used "Occams Razor" to deal with this because it was the most obvious and simple reason, which then also highlighted the fact that Solarwinds modules don't always interact with each other.

I ran the tests in the link and found the account was not connecting using "Eventviewer" but working correctly with another known account. The IPAM module was able to connect and scan the old servers but not the new, though running the same "RPC/Eventviewer" test from the Solarwinds IPAM module host to the old DHCP servers also didn't work with that same account, IPAM itself was able to interact with the DHCP services hosted on the old servers. After applying Windows updates to the Solarwinds IPAM host and restarting it, the IPAM service would then not communicate with the old servers as well, which suggests to me there was a "Windows cached creds" mystery happening in the background.

It then appeared someone had changed the password for the IPAM account a while ago and I guess as everything had remained stable IPAM remained connected to the old servers.

The second "gotcha" is that the credentials used by IPAM are stored separately from those stored in Orion, therefore make sure you change them in both IPAM and Orion! This gave me a quarter of an hour of confusion.

On the other hand as is always the case, I've learnt more about IPAM through this than I would have by reading the documentation.

If anyone wants to add to this, feel free.

Thanks to 'donrobert15' for the helpful reply!

donrobert5

Glad to help. You can mark my reply as an answer.