Page 1 of 1
Forum

Welcome to the Tweaking4All community forums!
When participating, please keep the Forum Rules in mind!

Topics for particular software or systems: Start your topic link with the name of the application or system.
For example “MacOS X – Your question“, or “MS Word – Your Tip or Trick“.

Please note that switching to another language when reading a post will not bring you to the same post, in Dutch, as there is no translation for that post!



MacOS 13.7.5 SMB co...
 
Share:
Notifications
Clear all

[Solved] MacOS 13.7.5 SMB connection

13 Posts
3 Users
4 Reactions
471 Views
(@watagan)
Active Member
Joined: 2 weeks ago
Posts: 7
Topic starter  

Am using a MacOS Ventura server. Mounting a Ventura 13.7.5 share consistently fails since this latest update and also the latest 13.7.6 betas, however the following connection commands work:

In Finder: smb://server_name._smb._tcp.local/server_share_name

In Terminal: mount_smbfs //server_name._smb._tcp.local/server_share_name ~//mount_point_name

Connections using SMB were fine in earlier Ventura versions. NFS has also worked well for all Ventura versions, so currently using it to connect.

ConnectMeNow fails to connect using the standard system call method, and I am able to ping the server. I would rather avoid re-installing Ventura as a fix, which going on many web comments does not appear to be reliable anyway.

Is there any way to replicate the above commands in ConnectMeNow?


   
ReplyQuote
 Hans
(@hans)
Famed Member Admin
Joined: 12 years ago
Posts: 2865
 

Hi Watagan,

sorry to hear you're running into issues - I can imagine how frustrating that may be.
I see you're not the only one in this new Apple bug 😕 (I do recommend reporting it here as mentioned in that post).

Since I do not have any Mac running Ventura, it is difficult for me to test anything.

Some suggestions:

  • Did you try mounting (in CMN) with the "Mount style" - "Commandline" under the "Advanced Options" of a share?

  • Did you try using "name of computer._smb._tcp.local" as the server name? 
  • Alternative: 'name_of_computer.local" (which is more common)

Please let us know if any of this worked 😊 


   
ReplyQuote
(@watagan)
Active Member
Joined: 2 weeks ago
Posts: 7
Topic starter  

@hans I had tried the command line option. Ping in CMN works using "name_of_computer.local" but not "name_of_computer._smb._tcp.local" so I assume that is the problem. Anyway, it is not an urgent issue as NFS connects well with CMN. It was just that other menubar based SMB connector apps work using the longer server name, as does Finder, and I was hoping CMN could be configured to work as well. I will wait for the next Ventura beta. Sadly the laptop is too old for any MacOS later than Ventura. Thanks for the reply.


   
ReplyQuote
 Hans
(@hans)
Famed Member Admin
Joined: 12 years ago
Posts: 2865
 

Did you try OpenCore? My old Mac Pro (2013) and super slow 12" MacBook (2016) run Sequoia just fine with the help of OpenCore. 😀 

Then again: I can understand why someone would prefer to stick with what Apple recommends.

 

Back to the issue at hand:
So I understand you tried IP address and "name_of_computer.local", and you tried API and Commandline (Mountstyle).
I can see why "name_of_computer._smb._tcp.local" will not work. Did a test with my own server and this results in:

ping: cannot resolve name_of_computer._smb._tcp.local: Unknown host

 

You could try disabling the ping before mount. This can be set in two places:

Under Preferences (global setting):

Under each share (Advanced Options - this only has an effect when the global setting is unchecked):

This way CMN will try to mount without doing a ping first. CMN leaves it up to the API or commandline statement to resolve the host.
However, I would expect the "Commandline" style to fail as ping couldn't resolve the host either. I could be wrong since mount_smbfs seems to work for you? The API style is a whole different beast that may, or may not, accept this type of host name.


   
ReplyQuote
(@watagan)
Active Member
Joined: 2 weeks ago
Posts: 7
Topic starter  

As far as I know OpenCore does not support Touch ID on the 2017 and 2019 Intel Macbooks that I have, which would be very inconvenient.

I've tried disabling ping in CMN as you suggest, globally and for the specific share, without success.

FYI there is an older app called QuickNAS ( https://dosdude1.com/quicknas/ ) that sits in the menu bar and does connect to Ventura with the required syntax, but it supports only SMB and AFP and I require SMB and NFS.

Fortunately there are many ways to skin a cat! Would be nice if I could use a CMN icon in the menu bar to simply pass the required syntax to mount_smbfs as QuickNAS appears to do. CMN is much more feature rich and so definitely preferred.

Many thanks for your suggestion though. There are workarounds, and Apple may yet fix Ventura in a future release.


   
ReplyQuote
 Hans
(@hans)
Famed Member Admin
Joined: 12 years ago
Posts: 2865
 

Not having touchID would b an argument to not take the OpenCore route indeed.

QucikNAS - never hear of it and it looks dated. Then again; if it works, it works.
My best guess its using commandline statements.

CMN uses "mount_smbfs" for commandline mounts for SMB shares.

If builds it like so (without the [ and ] brackets of course):

mount_smbfs [options] //[domain;][username][:password]@[URL] [mountpath]

So unless I overlooked a ping attempt, entering "name_of_computer._smb._tcp.local" could work, assuming your earlier statement that mount_smbfs worked from Terminal. Maybe the log window reveals some details that could be helpful to debug this.

 

Note that for me "name_of_computer._smb._tcp.local" does work for my NAS.

1) This is what I entered (even using the API call mountstyle)

2) Make sure for the share the ping before mount is disabled

3) Makes sure global ping (Preferences) is dsiabled as well

Log window shows this as well:

17:41:08 │ Mount requested for: "SMB Downloads (marvin._smb._tcp.local)"
17:41:08 │ - Max Attempts  = 1
         │   Attempts Left = -1
         │   Last Attempt  = n/a
17:41:08 │ - Doing default short mount delay (1 second)
17:41:09 │ - Starting mount background task
17:41:09 │ - RETRY MOUNT TIMER: Started 1 minute timer for remount attempts
17:41:09 │ - Enabled timer for potential extra mount attempts
17:41:09 │ - Thread started

17:41:09 │ Mount status update:
         │ Mount/Open Networkshare feedback (SystemDefault): 
         │ Mount attempt with Calling Apple NetFS API:
         │ 
         │ - LOGIN: Username and Password known - User login with hidden window
         │   URL: smb://marvin._smb._tcp.local/Downloads
         │   Mount directory: macOS will mount against a mount directory in "/Users/hans/MountPoints"
         │ - NetFSMountURL: Mount succesfull - API did not return an Error code, wait for confirmation

 


   
ReplyQuote
(@watagan)
Active Member
Joined: 2 weeks ago
Posts: 7
Topic starter  

Working! Thanks for sending your syntax through, it helped me to construct the correct mount_smbfs command in CMN. It turns out that Ventura does not like the full share address, just "/username". Maybe this is a Mac SMB requirement, not sure. I was also able to go back to the simpler "computer_name.local" as the server address, enabling ping again, otherwise a computer offline error occurred.

I also updated to the latest Ventura RC (22H625) this morning and Finder on my Sequioa machine (24F74) still does not connect even though the Ventura machine is visible on the network. So it appears this may be a Finder issue given the terminal command works.

Will let you know if there are any further issues/comments but so far the CMN configuration has worked given at least one reboot of the Ventura machine.

Again, many thanks....


   
Hans reacted
ReplyQuote
(@watagan)
Active Member
Joined: 2 weeks ago
Posts: 7
Topic starter  

PS, I bought you a coffee, hope it was received OK! Cheers...


   
Hans reacted
ReplyQuote
(@watagan)
Active Member
Joined: 2 weeks ago
Posts: 7
Topic starter  

A couple of posts above I should have said "/share_name" rather than "/username".


   
ReplyQuote
 Hans
(@hans)
Famed Member Admin
Joined: 12 years ago
Posts: 2865
 

Awesome! Glad to hear we got that to wok again 👍 

And ... thank you very much for the coffee!
Never a requirement, but very very very much appreciated!

I'll tag this topic as solved 😊 


   
ReplyQuote
 Hans
(@hans)
Famed Member Admin
Joined: 12 years ago
Posts: 2865
 

Posted by: @watagan

PS, I bought you a coffee, hope it was received OK! Cheers...

p.s. again: it is VERY much appreciated 😊 

 


   
ReplyQuote
(@stephenharrington)
New Member
Joined: 1 week ago
Posts: 1
 

Posted by: @watagan

Working! Thanks for sending your syntax through, it helped me to construct the correct mount_smbfs command in CMN.

Hi @watagan, any chance you could put up some screenshots/examples of your final CMN config for those of us having a little trouble following where this ended up?

Cheers Mate!


   
ReplyQuote
(@watagan)
Active Member
Joined: 2 weeks ago
Posts: 7
Topic starter  

Hi @stephenharrington hopefully you can expand the image below and read it. I've entered example details where the share or "Path:" is the user folder on the Ventura machine. You can use either a computer name or IP address in the "Server Address:" field. "Username:" and "Password:" are for the Ventura share account. You can mount the share to a custom mount point using the Advanced Options tab. Name your connection in the Menu Title field and enable it via the checkbox. Try the Test Mount button to check your entries. Trust this helps.

CMN works fine because it uses standard terminal commands. As we know there is a problem at the Ventura 13.7.5 end when connecting the usual way with Finder on another Mac. Sequoia works well with Finder on Ventura when connecting to a Sequoia share, but not the reverse.

 


   
ReplyQuote
Share: