Network Management

FortiGate node in the SolarWinds Platform is automatically detected as a Windows server in IPAM when added as a DHCP server

A FortiGate node is added to the SolarWinds Platform but DHCP is not recognized correctly when added in IPAM.

First published date

6/1/2026 3:29 PM

Last published date

6/1/2026 3:29 PM

Overview

You are able to successfully add a FortiGate node to the SolarWinds Platform. However, adding the node as a DHCP server in IPAM fails.

IPAM only has native DHCP integrations for:

Windows, Cisco (incl. ASA), ISC, and Infoblox.

Product section

IP Address Manager

Cause

FortiGate DHCP is not supported in IPAM.

Resolution

Monitor and manage DHCP servers

FortiGate DHCP is not supported in IPAM, so IPAM can’t properly add it as a DHCP server or pull scopes/leases/reservations.

Because FortiGate isn’t a known DHCP type, the “Add DHCP Server” workflow ends up treating it like a Windows DHCP server, which is why you see it auto-detected/labeled that way. Functionally, it still won’t work correctly – there’s no FortiGate-specific DHCP logic behind it.

You may Submit a feature request for Solarwinds Products to help prioritize this improvement.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.