Tahoe doesn't connect to local network until after login?

Question

Tahoe doesn't connect to local network until after login?

Computers running previous versions of macOS (including macOS 15 Sequoia) would connect to the local network after booting and before a user had logged in. The computer would appear in Finder on other Macs on the network and I would also be able to screen share. I could even screen share into a Mac, reboot it, and the screen share would reconnect and show the log-in screen.

Computers running Tahoe do not connect to the network until after I have logged in. I do have FileVault enabled, but I had FileVault enabled before. This happens with all three of my Macs after updating them to Tahoe: 2024 Mac mini (M4 Pro), a 2021 Mac Book Pro (M1 Pro), and a 2023 Mac mini (M2).

It is particularly annoying, because one of Mac minis runs without a monitor or keyboard. I rely on screen sharing into it to access.

Interestingly, after logging in (and connecting to the network), if I log back out on one of these Macs, it stays connected to the network, which makes it seem like it's not a new tightening of security?

Anyone else seeing this?

Thanks.

Mac mini, macOS 26.0

Posted on Sep 15, 2025 10:52 PM

Reply

Answer 1

Oct 11, 2025 9:21 AM in response to kjk

Hi kjk, yes, it is still happening for me. Turning off FileVault does mean it connects to the network before logging in, but I had FileVault enabled before updating to Tahoe too and did not have this problem.

The new feature that you can ssh into a computer with FileVault enabled to enter the password, to get it to show on the network, isn't reliable for me. I wonder if they changed the network-access behavior after adding this feature because, in theory, you should now be able to remotely enable network access?

In any case, I ended up plugging in a tiny keyboard permanently to my headless Mac Mini so I can (blindly) attempt to enter the password.

Reply

Answer 2

Sep 16, 2025 5:42 PM in response to Russell Quinn

Russell Quinn wrote:

Oooooo, you're saying I can ssh into a headless/keyboard-less Mac, that's running Tahoe and using FileVault, to remotely unlock it?

If so, did you have do use its IP address or was its local hostname available?

It’s a documented change.

Search for ssh here: What's new for enterprise in macOS Tahoe 26 - Apple Support

Reply

Answer 3

Sep 15, 2025 11:04 PM in response to Russell Quinn

Russell Quinn wrote:

Computers running Tahoe do not connect to the network until after I have logged in.

I do have FileVault enabled, but I had FileVault enabled before. This happens with all three of my Macs after updating them to Tahoe: 2024 Mac mini (M4 Pro), a 2021 Mac Book Pro (M1 Pro), and a 2023 Mac mini (M2).

This is after you have shutdown and restarted more than once?

You can try forgetting the Network and then add it back in(?)

Easy enough to disable that FileVault and compare your results:

no insight or resolve—

You can file a bug report / submit your Apple Feedback here: Product Feedback - Apple

Call Customer Support (800) MY–APPLE (800–692–7753)

or on line https://getsupport.apple.com/

or call AppleCare Support at 1-800-APLCARE (800-275-2273)

Outside the USA—Contact Apple for support and service by phone

See a list of Apple phone numbers around the world.

Contact Apple Support - Apple Support

Reply

Answer 4

Sep 16, 2025 4:51 PM in response to Russell Quinn

Yes, it only fails to show on the network when FileVault is active. This is a change in behavior from previous versions of macOS.

Reply

Answer 5

Sep 16, 2025 4:54 PM in response to Russell Quinn

Russell Quinn wrote:

Yes, it only fails to show on the network when FileVault is active. This is a change in behavior from previous versions of macOS.

Ok Russell Quinn — good computing.

That is progress, appreciate your corroboration.

Reply

Answer 6

Sep 16, 2025 5:18 PM in response to MrHoffman

Oooooo, you're saying I can ssh into a headless/keyboard-less Mac, that's running Tahoe and using FileVault, to remotely unlock it?

If so, did you have do use its IP address or was its local hostname available?

Reply

Answer 7

Sep 16, 2025 1:18 PM in response to leroydouglas

Two Macs are connected to Ethernet, one to Wi-Fi. Forgetting network doesn't help. I will try and confirm if FileVault is a factor. Thanks.

Reply

Answer 8

Sep 16, 2025 6:27 PM in response to Russell Quinn

ssh into a booting system now works.

From Miguel (a****s@mastodon.social):

[Edited by Moderator]

Reply

Answer 9

Sep 16, 2025 7:57 PM in response to MrHoffman

...

Reply

Answer 10

kjk

Level 4

1,323 points

Oct 11, 2025 3:07 AM in response to Russell Quinn

Hi Russell,

did you resolve this? I have two Macs, a MBP and a headless Mac Mini connected by ethernet as well, and am having similar issues with auto local network access on startup since Tahoe.

Reply

Answer 11

Oct 11, 2025 7:51 AM in response to kjk

If the ssh reply does not address this, please post s new thread, and please include some details and background for your requirements, and for what is (not) happening with macOS 26.

Reply