Samba not working on Sequoia

erickdobrasil wrote:

I don't really understand either adding ".local" or using "joesmith" instead of "Joe Smith" fixes access by Files app using smb.

"local" is a special reserved TLD (Top-Level Domain) for local devices. It's like ".com" or ".ca" but anyone can use ".local" because it's restricted to your local network.

Your user name of "Joe Smith" doesn't really exist very much. It's just a descriptive string tacked onto your real user name which is "joesmith". Apple calls this the "short user name". But it's really the only user name there is.

James Brickley wrote:

Syntax:

smb://DOMAIN;USER@HOSTNAME/SHARE/FOLDER

Example:

smb://user@imac.local/

What is interesting here... is that this traditional SMB syntax which was definitely not working yesterday on my computer is now working. I do not think I have even rebooted the computer in the meantime.

How can I say this with a good amount of conviction ? This syntax was used in an automator script that has been used for ages in previous versions of MacOs, was not working yesterday on Sequoia after the upgrade, but is now working again.

There is definitly something quirky happening here, but of course it may be specific to my computer. In any case, thank you for pointing out that my workaround was using Bonjour/Zeroconf syntax, I will definitely read up on that.

l4kr411 wrote:

MacOS is deprecating APF in favor of Samba. Windows uses nothing except Samba. Please where did you get your information?

Samba is a third-party SMB implementation. Windows uses the original made by them SMB implementation. macOS uses the Apple made SMB implementation. Samba is used predominantly on Linux.

Samba is not just another word for SMB.

erickdobrasil wrote:

The point is to test SMBD! Because it was not working from a remote system.

Well then that's the problem I guess. Can you describe this remote system? Operating system? Version? SMB version? Age? etc.

As part of an exasperation effort in another thread, I signed onto a VPN and tested a bunch of networking. Everything, including SMB worked fine. My server is running a vanilla Ubuntu 20.04.6 LTS with whatever that runs.

Additionally, some information to help you troubleshoot your initial problem:

Connections from others computers running older versions of MacOS at smb://mbp-de-matthieu or smb://mbp-de-matthieu.lan still work here.

Connections from an iPhone running iOS 18 to mbp-de-matthieu still work here.

Final addendum: upon further testing, SMB connections to ip adresses (smb://x.x.x.x) still work for other computers and ressources. However, they do not work with the own computer IP. smb://localhost doesn't work either.

erickdobrasil wrote:

I am trying to access my M2 mac mini running Sequoia from my iPhone using the Files app (connect to server).

Why not use iCloud? Or AirDrop? Both are infinitely easier.

Both systems updated to latest releases.

I realize that the whole world seems to expect perfection in nothing except for Apple .0 releases. But is that a reasonable expectation?

There is no such thing as the "latest releases". That phrase suggests "best", most up-to-date, most reliable, most advanced. Rather, you should have said, "both systems updated to the earliest releases". Then that would do a better job of setting expectations.

My recommendation is to learn how the seasons work. We don't plant tomatoes in the fall. That would be silly. We don't mow the grass in the winter. We don't shovel snow in summer. To every thing there is a season, and a time to every purpose (catchy, eh?).

Apple has a "spring release" in June. And then they have a "fall release" in September. If you want the most up-to-date, most reliable, most advanced version of anything, then you want the last versions before either of those releases. If you are focused more on reliability, then take it back one year.

For the Mac, that means Ventura 13.6.9. If you want something newer, then you could use Sonoma 14.6.1. The recent 13.7 and 14.7 releases came along with the "fall release". They might ultimately prove to be reliable, but I would recommend waiting. I have seen some reports of problems with 14.7. Apparently there is a new 14.7.1 on the way.

So if you want to use these early releases, by all means, go for it! Dig into details and learn some low-level networking. File some bug reports. In some cases, people might share your interests, but that's hit or miss. I was interested in a recent bug someone found regarding colorspaces in Preview. But I consider macOS file sharing to be a lost cause, so I don't care. In this case, I would rather recommend more reliable alternatives to help you get something practical done.

It’s great that it’s working now, however disabling the firewall is really never the right answer. I’m not trying to play SEC expert and/or preacher, it’s just sound advice. I would always look for some other way.

srutz wrote:

It’s great that it’s working now, however disabling the firewall is really never the right answer.

Why not. Is it because Microsoft used it to shift blame to the users instead of their poorly designed OS?

A Firewall is a network management tool. It is not an internet security device.

Wow, that was a fast response! Please learn to take some simple criticism. You could always tell one’s level of understanding as well as their ideology the second they start screaming about Microsoft totally out of context. Finally, please feel free to take a course on firewalls and the point of their true implementation. Good evening and stay calm.

Finally, please feel free to take a course on firewalls and the point of their true implementation. Good evening and stay calm.

I have taken several. I also earned certificates in various internet security subjects. Not that it matters. Pay your fee, get your B.

A Firewall is a network management tool used to sequester certain users and devices from other devices.

For instance, all users should not have access to accounting or HR devices. That separation is what a firewall provides. Using it to isolate one's computer from the internet is not what it is capable of doing.

Most users are already isolated from the internet through their NAT router.

The Application Firewall in macOS only serves to prevent other entities on the internal LAN from accessing that Mac. However, it only serves to block users from accessing their own devices. It has no capability to prevent the "hordes of baddies out on the Wild West of the Internet" from accessing their Mac. Their NAT router does that.

Please stop pushing the false security narrative.

Well connecting a machine to itself doesn't work for me on my iMac running Monterey (yes it's an obsolete machine, Sadly Apple wants more money from me) or my more recent MacBook Pro running Sonoma.

I suspect that failing to connect a machine to itself is a 'feature' not a bug.

erickdobrasil wrote:

connecting my M1 mac mini to itself

What's the point of that?