Big Sur 11.7.2 update on 2014 iMac causing VPN connectivity issues...

Question

Big Sur 11.7.2 update on 2014 iMac causing VPN connectivity issues...

Hi Folks,

I just updated my 2014 iMac to the latest relevant Big Sur MacOS version - 11.7.2 and it my VPN connectivity to work no longer works. I have other (newer) Macs which continue to connect fine - same network, same credentials, same settings/config.

I see there are some security updates/fixes in the 11.7.2 release notes, but it appears to have caused me this issue!

I've restarted a couple of times, tried recreating the VPN connection, tried different VPN targets but without any success.

Anybody have similar issues? Any suggestions on how to resolve?

Many thanks,

Dave

iMac Line (2012 and Later)

Posted on Dec 14, 2022 10:40 AM

Reply

Answer 1

Dec 15, 2022 3:39 AM in response to bigdavefleming

Based on the below, I reinstalled Big Sur, but it didn't make any difference.

Here's what I see in /var/log/ppp.log, the memory message looks suspicious?

Thu Dec 15 10:51:44 2022 : publish_entry SCDSet() failed: Success!
Thu Dec 15 10:51:44 2022 : publish_entry SCDSet() failed: Success!
Thu Dec 15 10:51:44 2022 : l2tp_get_router_address
Thu Dec 15 10:51:44 2022 : l2tp_get_router_address ***.***.***.*** from dict 1
Thu Dec 15 10:51:44 2022 : L2TP connecting to server ‘***.******.com' (***.***.***.***)…
Thu Dec 15 10:51:44 2022 : L2TP can't set L2TP server address: Cannot allocate memory
Thu Dec 15 10:51:44 2022 : IPSec connection started
Thu Dec 15 10:51:44 2022 : L2TP error sending Hello (Destination address required)
Thu Dec 15 10:51:44 2022 : Failed to send L2TP hello trigger. tried 0, max 10
Thu Dec 15 10:51:45 2022 : L2TP error sending Hello (Destination address required)
Thu Dec 15 10:51:45 2022 : Failed to send L2TP hello trigger. tried 0, max 10
Thu Dec 15 10:51:46 2022 : L2TP error sending Hello (Destination address required)
Thu Dec 15 10:51:46 2022 : Failed to send L2TP hello trigger. tried 0, max 10
Thu Dec 15 10:51:47 2022 : L2TP error sending Hello (Destination address required)
Thu Dec 15 10:51:47 2022 : Failed to send L2TP hello trigger. tried 0, max 10
Thu Dec 15 10:51:48 2022 : L2TP error sending Hello (Destination address required)
Thu Dec 15 10:51:48 2022 : Failed to send L2TP hello trigger. tried 0, max 10
Thu Dec 15 10:51:49 2022 : IPSec connection failed

Reply

Answer 2

Dec 21, 2022 3:13 PM in response to rosemeire177

I'm afraid I haven't solved/remediated the issue Rosemeire/All.

The 'Cannot allocate memory' error message above & the fact that it's only happening on this particular machine after updating the OS suggests a Big Sur bug to me.

d.

Reply

Answer 3

Dec 21, 2022 3:27 PM in response to bigdavefleming

Hi ,

I have a "dantesque" case that the worst besides the Forticlient VPN does not work I can't delete the app, the Forticlient is padlocked and even reinstalling and trying to change my user's permissions I can't remove that padlock and so little "delete"

Has anyone gone through this, if so how did you manage to delete an app with a padlock?

Thanks in advance,

Rosemeire

Reply

Answer 4

Jan 16, 2023 2:50 AM in response to rosemeire177

Hi! Been there, done that! I also tried Forticlient but couldn't get it to work. But I found a solution to delete the app:

Open terminal, cd to applications and type: sudo chflags -hv noschg FortiClient.app/

That will remove the padlock and you can then run sudo rm -R FortiClient.app/ to delete the app.

I'm still really annoyed at apple for not fixing this issue with the VPN-client. My current solution is to connect to VPN on an older Mac I have at home and running internet sharing on that machine to my work-computer. Not a very neat solution since I have to run all internet-traffic over the VPN if I want to access the web at the same time, but at least I can access the files in my office now.

Reply

Answer 5

Jan 18, 2023 3:37 PM in response to bigdavefleming

I am also having this problem after updating to BigSur 11.7.2. I am using an L2TP VPN connection set up on a 2015 Macbook Pro through the Network settings in System Preferences. It now refuses to connect due to the security changes in the update. I must be able to remote in for work! Any other recommendations for third-party VPN clients that could solve this problem? I see one vote for HotspotShield below. Any other fixes?

Reply

Answer 6

Feb 3, 2023 3:24 AM in response to April2023en

Hi all,

I upgrade 11.7.3 , and after finishing the updated version, the system opened/popup the message Fortclient Not Compatible with MacOs version, anyway..... Out of curiosity did this work for you?

Reply

Answer 7

Dec 15, 2022 7:14 AM in response to bigdavefleming

Contact your workplace network administrator. They may be able to advise you what to do. Maybe you need to update your VPN client based on your new system.

Reply

Answer 8

Dec 17, 2022 3:45 AM in response to bigdavefleming

Hi Folks,

I have the same issue. Can you share how you solved it? I would really appreciated for supporting.

Thanks in advance.

Regards

Rosemeire

Reply

Answer 9

Dec 17, 2022 12:15 PM in response to bigdavefleming

Same issue here on three computers that I updated from 117. to 11.72. I am the it admin and know exactly what I'm doing.

Reply

Answer 10

Dec 19, 2022 12:21 PM in response to bigdavefleming

Hi all some clue how can fixe it, please ! I am assuming the Mac it is so complicated nothing it is working , incompatible if you use different app Not support by IOS system.😬

Reply

Answer 11

yohanesc

Level 1

12 points

Dec 21, 2022 10:25 PM in response to bigdavefleming

Am using HotspotShield VPN and it work fine with the update of 11.7.2 Big Sur

Reply

Answer 12

Feb 3, 2023 1:50 AM in response to bigdavefleming

It looks like 11.7.3 fixed this issue.

Reply

Answer 13

Tisse

Level 1

13 points

Feb 3, 2023 3:59 AM in response to rosemeire177

The integrated Mac OS VPN client works again in 11.7.3. I never got forticlient to work even in 11.7.2 so I’m not surprised that it doesn’t work with the latest update.

Reply

Big Sur 11.7.2 update on 2014 iMac causing VPN connectivity issues...

Similar questions