reported MacOS 15 network problems

I am experiencing a similar problem.

And I have reasonable doubts about the newly added features along with the update.

In the topic Settings → Privacy and Security → Local Network, we found a part that sets you up to find and communicate with your local network device.

The apps registered on this list were able to communicate!

But I don't know how I can add it.

If API is added, maybe the pop-up will occur only when the app you are using calls the API.

I'm at a loss for words, but I fixed my iterm2 issue by finding under settings -> privacy & security -> local network and setting the slider to "on". I believe, but have no confirmation, this was related to a random popup following the update to 15.0.1 which asked if I wanted to "allow something to find local devices...." which I have zero context to answer so I said no. To me, as a network engineer, this is the height of hubris to mess with my otherwise fine network. Leave network settings under network please.

I'm having a very similar issue with iTerm2 ever since updating to 15.0. My home network has multiple subnets. I am unable to SSH to hosts on a different subnet and I receive "no route to host". Disabling Local Network access in Privacy & Security settings shows the same error on the same subnet, so I think it has something to do with 15.0's implementation of this feature. Could also be an issue with iTerm.

If I join the same SSID as the device I'm trying to connect to, everything works. But this is definitely an issue with the networking stack MacOS 15. I work from home and routinely need to SSH into services on this other network so this change is extremely disruptive. And the worst part... downgrading back to Sonoma requires a clean install because I don't have a backup.

In case there's a problem again try using the "nc" command in the terminal to see if you can make a connection. For example if the MS Windows host's IP address is "192.168.1.10" and the VNC server is using the default VNC server port 5900:

nc -zv 192.168.1.10 5900

If you see "succeeded" it means your iMac can make a VNC connection. If you see "Connection refused" it means your iMac can't make a VNC connection to the MS Windows host.

Have you considered using RDP (Remote Desktop Protocol) instead of VNC? I ask because RDP is natively supported on MS Windows and Microsoft's macOS and iPadOS RDP client "Windows App" (which is free) works well. Both VNC and RDP have their pros and cons but I've always had better luck with RDP.

The only people reporting problems are people using the built-in application firewall and/or VPNs.

There is a new setting in Network > WiFi > Private WiFI Address that can be changed from "rotating" to "fixed" if you are having problems.

Slammer99uk wrote:

Thanks, however been there done that, no change 🤦‍♀️😒

Thanks for clarifying. Unfortunately, so many people are reporting problems with those specific issues, they have to be addressed before anything else.

This is a more traditional networking question. What is the IP of your Mac and what is the IP of the Windows box? Should there be a route between them? Can you ping? Can you make a connection with some other protocol?

Just FYI... after playing around and looking at the routes... I noticed there was an odd route to a bridge100 interface. After looking into it a bit, I found that it's created by Internet Sharing. Disabling Internet Sharing and rebooting fixed the issue for me. Might be worth a try if you're having weird "no route to host" issues.

Thought about disabling the firewall?