MobileConnect, NetExtender are not working with NSA4650 Gen6, with New Firmware 6.5.4.15-116n
What a Irony.. Sonicwall sent us an email of CVE on firmware version 6.5.4.14-109n and older versions, that SSLVPN users who have locally managed account immediately update their password to prevent unauthorized access. After upgrading firmware to the latest one 6.5.4.15-116n, we noticed that Sonicwall NetExtender is not supporting.
Didn't they test everything (NetExtender & MobileConnect) in lab before pushing new firmware?
They released new firmware because of SSLVPN bug, but with this new firmware SSLVPN is NOT EVEN accessible via NetExtender and Mobile Connect.. LOL..!!
they mentioned that NetExtender is supported GEN 6/6.5 - 6.5.4.14-109n, not AFTER. then why they release new firmware for Gen-6 which does not have compatibility with Sonicwall NetExtender.
We have whole site not accessing SSLVPN thru netextender. Though we can access SSLVPN service from web portal, but its not use.
Answers
Even with security notices we rarely upgrade to the latest firmware release because frequently they mess something up.
Rule of thumb: Never upgrade production devices with the latest firmware, always test the firmware first and rule out major issues…
Hello @Aman2108 - Sorry to read that you are facing Issues post the firmware upgrade to 6.5.4.15-116n. Currently , there is an Issue with remote users using Mobile Connect being unable to connect after upgrading to 6.5.4.15-116n.
Information about this is available here :
https://www.sonicwall.com/support/knowledge-base/mobile-connect-breaks-after-upgrade-to-sonicos-6-5-4-15/240903132324983
Now, If your remote users using Netextender are also unable to connect after the upgrade to 6.5.4.15-116n then its best to work with our Support Team to identify why this is not working.
@Vivek - Yes NetExtender is also not working after upgrading firmware to latest version on Gen6. i have raised support ticket and still waiting for their response.
@TKWITS - Yes mate, you are right.
As Sonicwall sent us separate email about CVE - we proceed to upgrade firmware otherwise we wont upgrade any firmware till 2-3 months of release date.
Is their anyway to download/get the firmware update hotfix without a contract? I can't even email support without it telling me to reference to a existing case and when I try to open a case, I need a contract to even do anything which we don't have for any firewall we have access to.
Hello Vivek, we are also experiencing the issue "Mobile Connect being unable to connect after upgrading to 6.5.4.15-116n", this on 2 different SonicWalls.
On the page you mentioned, it says: "A Hotfix firmware is available to address this Issue".
If the hotfix firmware exists, please make it available for download so that your customers can fix the issue! And this without having to create a support ticket.
With best regards.
I totally agree, since this is a known and identified issue at Sonicwall, it is a complete nonsense to have to sign up for a support contract in order to get the fix firmware. Instead of just making it available in the mysonicwall portal.
Hi @TheoAdmin - Hotfix Firmwares are not made available via downloads on mysonicwall.com
By reporting a case to support , we are able to triage and make sure that the correct Hotfix Firmware(s) are being provided.
Hi Vivek, I did indeed create a support ticket on 27.09.2024. The ticket has the number 44637279.
To this day, I still have not received a response from SonicWall technical support. The situation is urgent.
@TheoAdmin - Sorry to read about this. Let met get the appropriate team members looped in on this to help you out.
We are also having this issue. However, I can still use mobile connect on my Iphone. Going to call in to support this morning.
Hello Vivek,
From my recent experience with tech support, Sonicwall does not release hotfix firmwares via mysonicwall to ensure that users pay for support licenses to get these famous Hotfix firmwares.
Except that in this case, the bug was introduced by SonicWall with version 6.5.4.15-116n
Sonicwall then asks users to pay to get a bug fix that they themselves are the origin of.