macOS Sequoia network issues

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.

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.

, 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?

Perhaps they are hoping to encourage the last few holdouts to leave it off like it should be set.

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?

I looked at the wifi site and it says "fixed". It's just that I don't have any previous Sonoma OS backup. I don't know if it's really so, but today I was told by the helpline that on Macbooks with an Apple silicon chip, you can't return the old operating system for a new one. What is your experience?

My configuration is a MacBook Pro 14 M3

Is this a bug? Why would they release an update with such a major bug? Think how many people went to update Homebrew and are banging their heads against the wall? I really can-not believe they are this incompetent.

Hope_I_Am_helpful wrote:

Is this a bug?

It's either a bug or a design feature.

Why would they release an update with such a major bug?

Maybe they meant to do that.

Think how many people went to update Homebrew and are banging their heads against the wall?

Makes me smile. 😄

I really can-not believe they are this incompetent.

Me neither. 😈

JustinHowe wrote:

If that really is a reasonable short-term fix, shouldn't take much time for security tool vendors to catch up with how the new network stack services are making their requests and processing responses.

Security tool vendors have had access to Sequoia since June.

After updating to macOS 15.0.1, I started having problems with connections, to be specific with Apple Remote Desktop. I also tried using other apps like VNC Viewer but I still have the same issues with the remote session where connection dropping every few minutes. I try everything but only what works seems to be turning the Firewall off. I turned off the firewall and didn't get a session disconnection for a while.

Unfortunately Apple has become worse than Microsoft with updates. The previous version (macOS 14) had a problem with HDMI connections on M2 chips and still hasn't been fixed. This is totally unfair because Apple devices are too expensive to have issues like this!

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?

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.

This problem is still with my M1 MacMini (LAN cable to modem). There doesn't seem to be a pattern except that at start-up the internet will work, then stop a little time after that (but not always). Then, I switch on WiFi (it works, most times) and then switch off WiFi and go back to LAN only. Sometimes this doesn't work, and I need to restart and that works...half the time. It just crashed again while I was typing this (fortunately, I copied what I had typed and pasted it in) - I had to switch on WiFi again to get internet access. Had. Enough.

Turns out that this server is the only computer in the building that does not have Ntiva installed. So that was not an issue.

However, server now stays on for random length of time. Rebooted yesterday morning and it stayed on until 4 AM today. Had to reboot twice today, getting about 2 hours on a boot.

I used set it up to reboot every day of the week at midnightusing:

sudo pmset repeat restart MTWRFSU 00:00:00

Now looking for a way I can have our remote webpage monitoring service send a message that can be used to trigger a reboot.

I applied 15.1 as well. Initially seemed okay, but now my secondary copper interface is flaky; Finder open on a share across it will randomly drop some or all listed files, and I have to close the tab and reopen from network locations > my server > my share > mydir

I didn't have problems with my wi-fi randomly disconnecting until I updated 15.01 to 15.1. My wi-fi connection drops at least 6 times a day; my primary network will not auto-connect, I have to select it. I updated my wife's MacBook Air from macOS 14 Sonoma to macOS 15.1 Sequoia and boy is she really mad at me for updating her computer since she is having the same wi-fi issue. There is absolutely no problem with my network as I use YouTube TV and it is on the same network as our laptops.