This is a bit weird, and I don’t know how to diagnose further. I have Home Assistant set up and running, with the Samba share add-on configured and running.
- I can connect to Home Assistant via SMB from my older laptop running macOS 10.14 (Mojave). This has been working for a year.
- I can’t connect to Home Assistant from my new laptop running macOS 11.1 (Big Sur).
The error I receive in the Mac UI is:
There was a problem connecting to the server “home assistant.local”.
The server may not exist or it is unavailable at this time. Check the server name or IP address, check your network connection, and then try again.
This is the macOS Finder error you receive when the Samba server denies the connection, and indeed, when I look in the add-on’s logs, I see the rejection:
Denied connection from fe80::4b9:b17:f0d0:66f8 (fe80::4b9:b17:f0d0:66f8)
Connection denied from ipv6:fe80::4b9:b17:f0d0:66f8:53627 to ipv6:fe80::fd8c:19a5:c8eb:f70a:445
But this is where it’s weird. The IPv4 address for this laptop is most definitely on the allow_hosts
list. I’m not using IPv6 on my network. At all. Never have. So why is the connection attempt trying to use IPv6?
When I connect from the older version of macOS, the authentication message (success) shows an IPv4 address.
When I connect from the new laptop to my Synology NAS via SMB, it works fine. I’m not sure where to examine the connection details, though, so I can’t verify if Synology is just handling an IPv6 address without being asked.
I suppose I can try adding the IPv6 address to allow_hosts
but that seems like a band-aid, rather than solving the problem.
Any suggestions for further testing or diagnosis?