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

NCM and FortiNet Fortigate

RE: NCM and FortiNet Fortigate

Just loaded NCM, NCM is able to discover network and all the firewalls, NCM is not able to backup and of the FortiGate firewalls

Error Message - Connection Refused by <IP address>

Find more posts tagged with

Accepted answers

All comments

chad.every

There is a lot to mention but I'll start with the first two.

"Connection Refused..." This is coming from a firewall ACL. Either from the FortiGate directly or from a firewall in-between.
Once you allow SSH, look into making sure that NCM is correctly assigning the FortiGate Device Template. If you edit that node, at the very bottom of the page, you'll see 'Auto Determine'. That should be ok if it is correctly assigning the correct one. You can test explicitly changing that drop down to FortiGate to see if you get a different response.

More comments to come but I'll hold until we get there.

OdyaTech

Hi , i think this problem is related to encryption algorithms between solarwinds and fortigates.

stuartd

I've just posted about this here: SSH - Connection Refused Cipher Updates - An F.Y.I.

This is absolutely one o a combination of three issues:

You aren't on the latest Solarwinds or have the buddy drop installed
Your FortiOS is v7 and higher
If 1 is not true (i.e. you are on 2024.2.1) then are you are using an edited version of the Fortinet template? If so, go see my post linked above and add the two lines I listed there into your template.

I can 100% confirm that running FortiOS >7 with Solarwinds 2024.2.1 and either the default or an edited template for Fortinet that you won't get this error.

The reason, if you need to know, is that from v7 and higher Fortinet enabled 'strong-crypto' by default. Full details here.