Hi there,
just installed the new SonicWall NetExtender client (10.3.0) and RDM is not able to call it anymore. I think that the issue is that in the program folder there's no necli.exe anymore, but a nxcli.exe instead.
Can you try to look at that? RDM entries are now broken (for NetExtender VPN).
Thanks.
Hello,
Thank you for your feedback.
Have you tried updating the Path properties of the SonicWall NetExtender in File - Settings - Application - Paths?
Best regards,
Érica Poirier
1b194664-126b-47a4-bc2f-debe1c272c5f.png
Hi,
please note that I specified that the exe file name is changed, not the folder path...
Hello,
Thank you for your feedback.
Have you tried renaming the .exe file to see if that helps?
Best regards,
Érica Poirier
Hi Nicola,
We will add support for this new executable name. As a workaround in the meantime you can make a copy of nxcli.exe named necli.exe, I just tested it it works with the current version of RDM.
Sébastien Duquette
Ok, thanks.
My main attempt was to notify to you the new version change.
Cheers.
WARNING: certificate acceptance message is changed as well, so I think a code change in RDM is needed.
22b00c42-cce1-4746-a544-5644fc611610.png
I can confirm that copying the file works - though in our case we also had to update the name of the name of the network adapter is looks for an IP on (previously it was "SonicWall NetExtender" and it's now "SonicWall_NetExtender_SSL":
2fa38012-60de-4138-9b3d-f7332bb9dbe4.png
I can confirm that copying the file works - though in our case we also had to update the name of the name of the network adapter is looks for an IP on (previously it was "SonicWall NetExtender" and it's now "SonicWall_NetExtender_SSL":
I confirm the same too.
Thank you for reporting it, we added the information to our ticket to handle those changes correctly.
Sébastien Duquette
Hello,
We've fixed the executable issue as well as the confirmation for the certificate.
For the certificate confirmation fix to work (sending "T" instead of "Y"), make sure that the executable is named "nxcli.exe" if you've renamed it to "necli.exe" as a temporary fix. We use the executable name to ensure that the correct confirmation is sent to the correct version of SonicWall.
You can expect these fixes to be in the upcoming 2024.3 version.
Regards,
Jafran Majeau
Thanks!
RDM 2024.3.22 is now available with the support for the new version of NetExtender.
Sébastien Duquette
Hi there,
back on topics. I'm using NetExtender 10.3.4 and there is something wrong. I have "Automatically accept the certificate" option enabled and sometimes I see:
Other times, if I wait, a "T" char is outputted:
Also, "Automatically delete profile on close" doesn't work, it remains saved within the client.
Any help?
Thanks
9a927ad1-39ae-4473-b04f-48394a2b153e.png
3e5866c2-647c-422d-adb2-68092a06aa49.png
Sometimes "Connection already existed"...
I see exactly the same issue as Nicola. @Jafran Majeau / @Sebastien Duquette perhaps something changed in their command line parameters?
It's unusable for me at the moment. I don't see any follow-up, so I'm trying to open a specific new thread.
Hello,
Thank you for your feedback.
We are sorry that the SonicWall entry no longer works on your end. We will investigate this internally and get back to you.
Thank you for being so patient.
Best regards,
Érica Poirier
Erica,
I suppose you need to investigate the new CLI commands and test his responsiveness. It seems quite different from the old one and not manageable from RDM at the moment.
Moreover, having NetExtender not deleting/saving the connection it's a mess (and security concern).
Thanks,
Hello,
You’re absolutely right in your observations here. Based on what you’ve described, it does look like something has changed again in the NetExtender CLI behavior.
I’ve checked internally, and our development team has opened a new case specifically to investigate this exact issue (including the inconsistent certificate acceptance behavior and profile handling).
We’ll keep you updated as soon as we have more information or a fix.
Thanks again for the detailed feedback it really helps us track these changes.
Best regards,
Carl Marien
Using 2026.1.15.0 64-bit (PreJIT), I now get slightly improved behavior; it now pauses to ask me to key a password into the popup terminal box.
Keying this in allows it to continue, but also kind of defeats the point.
Let me know if there's anything else I can try in the setup for the VPN?
Cheers,
Geoff