macOS Sequoia network issues

pest1 wrote:

why did Apple release an operating system update where many Mac owners have to to turn off the built-in firewall to get a stable internet connection?

Apple releases a new operating system every year. People line up with their download buttons like the biggest Black Friday sale ever held. They will even download special software to hack up their system just so they can run the operating system on unsupported hardware.

There is no number or severity of Apple bugs that could possibly stop this addiction to updates.

And Sequoia has been one of the most trouble free releases in recent years.

I have a problem with the ethernet connection. I send photos from Nikon Z8 camera to Macbook pro 14 M3 via LAN cable and ethernet adapter. After upgrading my system from Sonoma to Sequoia, my connection stopped working. "Connecting to computer" is constantly on the camera screen and nothing else. I tried turning off the firewall - it didn't help, reinstalling the utility from Nikon - it didn't help.

I set up a new LAN connection from the beginning with camera management in the utility - it didn't help. Can you please advise me of something I might have overlooked? That is, how do I get back to OS Sonoma?

Drakemm wrote:

I tried turning off the firewall - it didn't help, reinstalling the utility from Nikon - it didn't help.

I set up a new LAN connection from the beginning with camera management in the utility - it didn't help. Can you please advise me of something I might have overlooked?

Firewall is one thing. The next thing is also firewall, or rather, any other kind of 3rd party "privacy" or "security" app that hacks around with network internals.

Also check System Settings > Network > WiFi > Private WiFi address and make sure it is set to "fixed".

That is, how do I get back to OS Sonoma?

That's a different question altogether. Create a bootable USB installer. Boot to recovery. Erase the hard drive. Reinstall Sonoma, restore from backup created before installing Sequoia.

In my case, uninstalling the third party Sophos Endpoint Protection software seems to have resolved constant disconnections of my Citrix Workspace sessions and other strange networking issues I've been experiencing since OSX updated on Monday.

I use a cabled ethernet connection with a static internal IP address so Wifi random IP address wasn't the problem. Also the OSX firewall was - and still is - enabled.

Will be testing re-installing the SEP software later today, to see if it interacts with the OS in a more stable manner after going through a full install process onto the new OS version.

Update - the internet drop-out problem had returned when I turned on my Mac this morning. I switched it on and then off in Network settings and my LAN connection is back to normal. For those on WiFi only, try the same thing - turn WiFo off and on using Network settings.

If you are usign a LAN (cabled) connection, then you should probably NOT have WiFi also enabled. Having two interfaces on your computer both talking to your upstream (broadband router/provider) will likely cause interesting routing issues regardless of the Sequoia update.

After updating to 15.0.1 my Yahoo custom home page would only load half the time using Safari (ok with other browsers). After trying many attempts to fix I turned off the firewall and now no issue. I guess some type of bug with latest OS.

Note I said with my (temporary) fix - you need to turn the WiFi on in Settings> WiFi > move slider to 'ON', then let it connect to the modem, then in Settings> WiFi> move slider to 'OFF'. Magically, LAN starts working again. That is, once you have LAN working again, switch off WiFi.

OK, I've had enough of the drop outs. As a I posted, the only thing that seems to work, but not always now, is toggling WiFi off and on. I was doing something important on my Mac today and the internet dropped out again. After spending 10 minutes trying to get the internet working again, I had to start my work over. This is a very poor showing from Apple - is there a fix rumoured to be coming soon?

I had the same issue. I agree that after I turned WiFi off then on and my ethernet connection off/on the issue was resolved (so far). I use ethernet as prime and WiFi as second in the service order. Just turning off firewall did not work.

After pressing post on the above I closed the computer used to log on the server vis VPN and went to bed. Next day (27th) the problem has returned. Server Terminal app was left open on the server and when logging I found these strange lines on the terminal screen that appears to have been created by about 1 minute (26th) after I made the above post and close VPN connection.

=> Successfully stopped `httpd` (label: homebrew.mxcl.httpd)

==> Successfully started `httpd` (label: homebrew.mxcl.httpd)

lowerlevel@70-89-220-117-clean-air-engineering-il ~ % 

 [Restored Oct 27, 2024 at 5:48:45 PM]

Last login: Sun Oct 27 17:48:45 on ttys000

You have new mail.

lowerlevel@70-89-220-117-clean-air-engineering-il ~ % >....                                          

2024-10-26 22:48:41.548060 <Notice>: Last log repeated 1 times

2024-10-26 22:48:41.547173 (gui/501 [100003]) <Warning>: denied lookup: name = com.apple.contactsd.persistence, requestor = searchpartyuser[19692], error = 159: Sandbox restriction

2024-10-26 22:48:42.000201 <Notice>: Last log repeated 1 times

2024-10-26 22:48:42.000151 (system/com.openssh.sshd.6A33D7FA-D690-4228-9D58-38BB7C55BD07) <Notice>: internal event: WILL_SPAWN, code = 0

2024-10-26 22:48:42.000184 (system/com.openssh.sshd.6A33D7FA-D690-4228-9D58-38BB7C55BD07) <Notice>: service state: spawn scheduled

2024-10-26 22:48:42.000189 (system/com.openssh.sshd.6A33D7FA-D690-4228-9D58-38BB7C55BD07) <Notice>: service state: spawning

2024-10-26 22:48:42.000272 (system/com.openssh.sshd.6A33D7FA-D690-4228-9D58-38BB7C55BD07) <Notice>: launching: ipc (socket)

2024-10-26 22:48:42.001722 (system/com.openssh.sshd.6A33D7FA-D690-4228-9D58-38BB7C55BD07 [93499]) <Notice>: xpcproxy spawned with pid 93499

2024-10-26 22:48:42.001762 (system/com.openssh.sshd.6A33D7FA-D690-4228-9D58-38BB7C55BD07 [93499]) <Notice>: internal event: SPAWNED, code = 0

2024-10-26 22:48:42.001769 (system/com.openssh.sshd.6A33D7FA-D690-4228-9D58-38BB7C55BD07 [93499]) <Notice>: service state: xpcproxy

2024-10-26 22:48:42.001794 (system/com.openssh.sshd.6A33D7FA-D690-4228-9D58-38BB7C55BD07 [93499]) <Notice>: internal event: SOURCE_ATTACH, code = 0

2024-10-26 22:48:42.013150 (system/com.openssh.sshd.6A33D7FA-D690-4228-9D58-38BB7C55BD07 [93499]) <Notice>: service state: running

2024-10-26 22:48:42.013172 (system/com.openssh.sshd.6A33D7FA-D690-4228-9D58-38BB7C55BD07 [93499]) <Notice>: internal event: INIT, code = 0

2024-10-26 22:48:42.013207 (system/com.openssh.sshd.6A33D7FA-D690-4228-9D58-38BB7C55BD07 [93499]) <Notice>: Successfully spawned sshd-keygen-wrapper[93499] because ipc (socket)

2024-10-26 22:48:42.017663 (pid/93499 [sshd-keygen-wra]) <Notice>: uncorking exec source upfront

2024-10-26 22:48:42.017685 (pid/93499 [sshd-keygen-wra]) <Notice>: created

2024-10-26 22:48:42.021595 (pid/93499 [sshd-keygen-wra]) <Notice>: domain exec event

2024-10-26 22:48:42.021606 (pid/93499 [sshd-keygen-wra]) <Notice>: shutting down

2024-10-26 22:48:42.021616 (pid/93499 [sshd-keygen-wra]) <Notice>: cleaning up

2024-10-26 22:48:42.021623 (system) <Notice>: removing child:

Note that the Server Firewall has been on for months. The server is owned by a corporation and has 3rd party protection software installe and related user named Ntiva which is an admin User.

I will check with corporate IT tomorrow to see if Ntiva has messed with the server.

Had similar issue. After testing many combinations I found turning off "limit ip address tracking" in the details for each connection (WiFi and ethernet) appears to resolve. The latest update 15.1 did not fix the issue so this fix is a band aid .

Starbreeze wrote:

Yes, the firewall is enabled and is set by a configuration profile.

That will do it. You'll have to contact your IT admins and let them know it isn't working. Maybe suggest that they consider AppleSeed for IT next year. Then they would be better prepared.

So Apple enhanced network security by forcing us to turn off our Firewall when using certain apps like Teams. Niiiice.