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!
I've just "upgraded" my Mac to macOS Tahoe 26.4 (from 26.3, where ConnectMeNow 4.0.18 worked without issues). Since that "upgrade", ConnectMeNow fails to mount any of my Samba shares from my local Windows 10 PC. Sometimes I see a notification saying that a mount attempt failed; more often the attempt fails with no error or warning notification of any kind.
I can mount the same network shares using the built-in support in Finder or using the mount command in Terminal, so there isn't a network issue or a problem with the share configuration; it's just ConnectMeNow that doesn't work.
I've upgraded to ConnectMeNow 4.0.19 beta to see whether it fixes the problem, and it doesn't. Looking for additional suggestions about how I can debug and correct this problem.
Version: 4.0.19 (Build 82)
OS: macOS Tahoe 26
Version 26.4 (Build 25E246)
ARM (64 bits) application
Debug log extract:
17:16:58 │ Mount requested for: "SMB eBooks" 17:16:58 │ - Max Attempts = 1 │ Attempts Left = -1 │ Last Attempt = n/a 17:16:58 │ - Doing default short mount delay (1 second) 17:16:59 │ - Starting mount background task 17:16:59 │ - RETRY MOUNT TIMER: Started 1 minute timer for remount attempts 17:16:59 │ - Enabled timer for potential extra mount attempts 17:16:59 │ - Thread started 17:16:59 │ Mount status update: │ Mount/Open Networkshare feedback (SystemDefault): │ Mount attempt with Calling Apple NetFS API: │ │ - LOGIN -- No login │ URL: smb://myPC/D/Users/myUserName/Documents/Books/eBooks │ Mount directory: macOS will mount against a mount directory in "/Users/first.last/myPC" │ - NetFSMountURL: Error - Internal error 17:16:59 │ Thread - Calling for forced status update (only shows results if something changed) 17:16:59 │ -- STATUS UPDATE - THREAD CALLBACK ------------------------------------------------ │ 17:16:59 │ Update type │ - Initial read : - │ - Timed Interval : - │ - Get Network info : - │ - Forced Update : YES │ │ Status Interval : 10000 milliseconds │ Interval Interrupts : 500 milliseconds │ Failed mount after : 30000 milliseconds │ │ Default gateway : 192.168.1.1 (MAC: 24:41:FE:60:15:BB) │ 17:16:59 │ - Mount Status Updated: Counted 1 active share(s) 17:16:59 │ - Matched 0 Network shares. (1 unknown) 17:16:59 │ │ -- STATUS UPDATE - COMPLETED ------------------------------------------------------
The "NetFSMountURL: Error - Internal error" message seems as though it's preventing the Mac from finding the matching network share.
I'll have to "upgrade" my Mac to Tahoe 26.4 first to do some testing.
Will reply later this afternoon 😊
Note: I thought Windows doesn't like it that one mounts without login credentials? Since you mentioned that all worked will with Tahoe 26.3, I'll assume I'm recalling that wrong.
Just upgraded to 25.4 and ... ConnectMeNow mounts shares to my NAS just fine.
One thing though, a notification appeared asking me if ConnectMeNow is allowed to find devices in the local network.
Did you get this message, and if so: did you click allow?
If you missed it, you can find it under:
System Settings -> Privacy & Security -> Local Network -> ConnectMeNow4.app should be enabled.
Please let me know if this fixed the issue. 😊
