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

MacOS 13.7.5 SMB connection

2 Posts
2 Users
0 Reactions
15 Views
(@watagan)
New Member
Joined: 10 hours ago
Posts: 1
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: 2860
 

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
Share: