Join the Conversation

To sign in, use your existing MySonicWall account. To create a free MySonicWall account click "Register".

SonicWall NetExtender 10.3.0, OTP authentication failure issue

NickNick Newbie ✭
edited November 29 in SSL VPN

After updating SonicWall NetExtender to 10.3.0(21), I've been unable to use my existing OTP for two-factor authentication. The connection drops immediately after entering the OTP. I've noticed that reverting to 10.2.341 resolves the issue. Has anyone else encountered this problem? It seems like there might be a change in the OTP behavior specifically in version 10.3.0(21).

Category: SSL VPN
Reply
Tagged:

Answers

  • BWCBWC Cybersecurity Overlord ✭✭✭

    With the built-in TFA or external (Radius)?

    I already opened a ticket for this.

    —Michael@BWC

  • atpedatped Newbie ✭
    edited December 3

    Do you get the error "Cannot get response from server" when you connect? I have a ticket open for that and found that it wasn't related to MFA or RADIUS, but rather to the Tunnel All mode. Does your SSL VPN have Tunnel All enabled? If so, try disabling it. Or alternatively enable "Exclude local network" under Properties → Connection Settings. If that fixes your issue, join the club.

  • BWCBWC Cybersecurity Overlord ✭✭✭

    In my case it's not Tunnel All related, connection works fine when unbinding the Token from the User on the Authentication Server.

    —Michael@BWC

  • BhsantosBhsantos Newbie ✭

    Hi Michael, I have the same problem.
    Did sonicwall support provide feedback?

  • BWCBWC Cybersecurity Overlord ✭✭✭

    No feedback for now, but they tried to reach me today. Sadly I wasn't able to take the call because it was unscheduled and I was busy otherwise. It's very rare that I sit here and just wait for a call from SNWL support co,ming out of the blue.

    But I'am hopeful we can find a time slot to move this forward.

    —Michael@BWC

  • Dave_SmithDave_Smith Newbie ✭

    Hi, I can confirm, this is affecting me too. We have tunnel all enabled. I rolled back to 10.2.341 to fix. There's an option in 10.3, worded like "disable tunnel all for local networks" and for one session, it resolved the problem, but came back after a reboot.

  • BWCBWC Cybersecurity Overlord ✭✭✭

    My ticket is on pending closed, Radius C/R Issue acknowledged and we have to wait for a fixed NXT 10.3 release, no ETA.

    —Michael@BWC

  • NickNick Newbie ✭

    I opened a case. The customer support reply "The issue has been fixed, and our backend team will release a new Nx release as soon as possible. I will keep you posted."😃

Sign In or Register to comment.