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!



Share:
Notifications
Clear all

New to CMN, when I open macbook, my shares are not auto connected, why?

6 Posts
2 Users
0 Reactions
150 Views
(@cptanpanic)
Active Member
Joined: 2 weeks ago
Posts: 5
Topic starter  

So I am new to Mac, and was happy to find ConnectMeNow, but am still working out how to use it. So I have 4 shares defined in CMN, and have Advanced Options->AutoMount->On Network Change set, but when I open my macbook, the drives are not always mounted. What do I need to check?


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

Hi cptanpanic! 

So, your Macbook is probably connected to your network over WiFi (Ethernet would be more stable).
I also assume you're using the latest macOS version (eg. Sequoia 15.4 or something similar).

Most likely your Mac briefly looses the shares because your Mac was closed and sleeping. It happens to mine every now and then as well (didn't used to be this way). This is a macOS "feature", and a rather slow one at it 😊 - effectively not really changing network.

Option I use:

Under the advanced settings of a share, enable "On Server IP appear" and "On network change" (you already have that one checked).
It takes the make a minute to see the network was gone and have CMN remount the share. Quite annoying, but it works.

You can try these 3 options (under Preferences):

You could try "Quick unmount on network loss" together with "remount mounted drives on Wake Up from sleep".
Since I haven't use these options in a while either, I better go try them on my Mac as well 😊 


   
ReplyQuote
(@cptanpanic)
Active Member
Joined: 2 weeks ago
Posts: 5
Topic starter  

Thanks, I already had the "Remote mounted drives on Wakeup" selected, so I guess that isn't fixing my issue. But yes I am using the latest OS, over wifi to SMB shares on the local network. I will try using the "On Server IP address appear" option. Question, how does this relate to the "Mount Attempts" can I assume that I can still leave this at the default 1, and the network polling doesn't count as a retry? And this count only counts after server ip address appears?


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

"Mount attempts" is independent of all settings.
It just does a number of attempts to mount when doing any mount.
So if would do these attempts as well in your situation 😊 

Feel free to set it to a higher number - once a share is mounted successfully it will stop trying.

Originally this was intended for devices (NAS for example) do a few attempt after using Wake On LAN. 


   
ReplyQuote
(@cptanpanic)
Active Member
Joined: 2 weeks ago
Posts: 5
Topic starter  

So I don't understand your comment. So lets say I enable "On Server IP address appear" option and server goes down. App will then start polling network every 10 seconds. So does mount attempts of 1 mean it will only poll network address one time, and if server is not available it would never try again?


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

No it means it will poll until it finds the machine, and only then it will do a mount attempts.

The problem it is trying to fix:
Most devices can be seen and pinged even before it fully booted up. So the share may not be available right away. The extra attempts is to give operating system of that device some time to make their share(s) available. This typically happens with NAS devices, but my Windows computer has the same "issue". 

I hope that makes more sense 😊 


   
ReplyQuote
Share: