Barracuda Network Access Client Status & Disconnect Issues

Hello,

Thank you for reaching out to us regarding this,

Would you be able to update to the latest version of RDM 2024.3.29.0 and let me know if you encounter the same behavior?

I'm also wondering if this was working for you previously without issues or is this a new configuration?

Best regards,

We are already running 2024.3.29.0 which is the latest production version. We already opened a support ticket and they suggested reporting the condition here. They offered a temporary workaround that is not great

Hello,

Thank you for your reply,

I see; I will move your topic to the Feature Request section.

Best regards,

Hello,

Thank you for your patience,

After moving your case to the Feature request section, I've discussed this behavior with our development team.

Unfortunately for most VPNs RDM is limited to interacting with them using Command Lines for the disconnect what is being used is:
nacvpn.exe -disconnect -profile "<Your Profile>"

If you use this command manually outside RDM does it disconnect the VPN as expected?

For your problem with the Green icon not changing after disconnecting the VPN this would be expected behavior in most cases since RDM has no way to keep track if the VPN is closed or not after using the command line, using the "Use adapter to detect Connection" option may help with this.
Best regards,

When we run the command line even when using the run as administrator the nothing happens. The connection remains open.

Setting the "Use adapter to detect Connection" did not fix the green status indicator.

Based on the form posts shown below it looks like the NACVPN.EXE may have been partially deprecated in favor of PowerShell commands. One of the threads is 5 years old the other is a year old. However, it sees as though movement is incredibly slow on making the integration fully operational.

Any Idea as to when this integration will be fully functional?

https://forum.devolutions.net/topics/41101/barracude-network-access-50266

https://forum.devolutions.net/topics/31080/support-for-barracuda-nac-vpn-client-5xx

Using the PowerShell command "disconnect-vpn" closes the active Barracuda NAC VPN connection. However, the experimental integration will not run the PowerShell directly as an embedded before or after close event. Additionally, the integration will not run the PowerShell command from a linked Macro/script/tool entry. However, the command works correctly if run manually from a macro/script/tool entry.

The integration also will not use the linked (vault) credentials it will only accept credentials entered directly into the VPN entry.

Hello,

Thank you for your reply,

I will reach out to our development team to discuss this further and keep you updated with any news I receive,

Best regards,

The RDM release notes for version 2025.24.0 indicate that the barracuda NAC linked credentials issue was resolved. However it has not been resolved.

Hello,
Whn you try Copy username or Copy Password, does it resolve the linked credentials?

Regards

Prior to release V2025.1.24.0 putting the credentials directly into the Barracuda NAC entry did work when establish the connection. Placing the credentials in the Barracuda NAC entry has no affect on the green indicator or closing the connection from RDM. V2025.1.24.0 does not fix any of these issues and causes new issues.

Hello,

Thank you for your reply,

As we discussed during our session I will be doing some testing using the executable you provided and will keep you updated in our case directly.

Best regards,

Hello,

We’ve made improvements in the latest internal version:

• The disconnect should now work properly when closing the Barracuda VPN.
• Linked credentials should now work correctly.

As for the VPN status not updating in RDM, this remains a limitation for most VPN types. We’ll look into whether Barracuda’s status command can be used in a future update.
Let us know if the fixes work on your side.

Regards,