Page 1 of 1

ConnectMeNow v3 – Mount Network Shares Quick and Easy on a Mac

ConnectMeNow v3 – Mount Network Shares Quick and Easy on a Mac
   170

macOS is great – I really like it a lot – but one thing it doesn’t handle all that great is … network shares.

In this day and age a little weird to still see this, especially from a company like Apple. We are more network connected than ever before – at home, in school and at work. We have network shares on our computers, want to access company network shares, or have a dedicated file server or NAS (Network Attached Storage) to store our information or make our backups.

Unfortunately, it is still cumbersome under macOS X to connect to those “shares” (also known as mounted network “Volumes“).

In Finder, a server doesn’t always appear right away, we need to go through a list of shares on a given “server”, get confused if we need SMBCIFSFTPSSHWebDAVNFS or AFP, and I’m not even mentioning the need to enter a username and password on protected shares.

For this reason I created ConnectMeNow – initially just for personal use.
But the arrival of the 64 bit requirement, mandatory signed applications, and notarization requirements, and Catalina issues, my original old version was simply outdated.

So after months of work, I’d like to present ConnectMeNow v3, which hopefully makes working with shares easier for you as well.




Content Overview

Mounting Network Shares with ConnectMeNow

So, let’s start by explaining what “mounting network shares” means.

The simplest explanation would be:

Mounting Network Shares
Attaching a directory located on a different computer, shared over a network, to your computer as if it was a local disk drive.

Note: this is most certainly not the most complete, technical or most correct description, but for most regular users this will suffice.

The “different computer” can be another computer, a NAS (Network Attached Storage – like from QNAP, Synology, Western Digital, Seagate, etc.), or even a full size server. The Operating System of these “computers” does not need to be relevant. For example a QNAP NAS runs a Linux variant, however can share directories in a Windows originated format (SMB), and be accessed by a macOS computer.

Out of the box, under macOS, you’ll need to go through some hoops to “open” such a Network Share.
Either the “server” is listed in Finder on the left, and you’ll have to click it to be confronted with selecting a share-name and entering username and password, OR you have to use “Go” menu in Finder and select “Connect to server” option – which comes with even more questions.

Both options are rather cumbersome, if not slow, if you ask me (Apple: please pay attention here – this is a rather poor user experience!).

So this is where ConnectMeNow is supposed to come in. I just got tired of doing all this manual labor.

On that note: The Finder is even with ConnectmeNow not the best way to get to your mounted network shares.
When using ConnectMeNow, the easiest way is by going to the “/Volumes/” directory on your Mac where you’ll find all mounted network shares that are active.
More about that later, since ConnectMeNow also allows you to create your own directory where a mount should be placed and ConnectMeNow has the option in the menu to reveal the mount in Finder with a single click.

ConnectMeNow – What happened to version 2?

Just a quick note on the versions of ConnectMeNow, because I already hear folks asking: what happened with version 2?

After having released the original version (1.x), I started tinkering with a new version. The missing version 2.
However, the arrival of Catalina forced me to bring out a beta of version 2, as the original ConnectMeNow is only 32 bits.
This unfortunately was not my only application that was affected by the shift to 64 bit – so I started running out of time – big time.

My quick and sloppy fix: compile the beta as a 64 bit application – which worked, but it was unfinished and Dark Theme support was kind-a crappy.

Having learned more about the inner workings of macOS, I decided to start again from scratch.
I’ve called that new version, version 3 to avoid confusion with the outdated version 2.

Quick overview of Features

I think ConnectMeNow has quite a lot to offer,… to name a few:

  • Protocols support for SMB, AFP, NFS, SSH, SSHFS, WebDAV and FTP.
  • Dark Theme support
  • AutoMount at startup, after a network change, and after waking up from sleep or standby
  • Support for Fallback servers, for when a server is not available
  • SSHFS (OSXFUSE) support with password entry or SSH keys
  • SSH support with automatic password entry or SSH Keys
  • Assistance to generate and install SSH keys on your server
  • Mount, unmount, and Reveal in Finder from the menu
  • Open or Close SSH connections from the menu
  • Indication in the menu if a connection is active or not
  • Grouping options in the menu
  • Official Mount (Apple API) or Fast Mount support
  • Mount in /Volumes/ or in your own prefered mount directory
  • Mount/Unmount notifications
  • Detection of Mount, Unmount, Standby/Sleep/Wake up, and network changes
  • Sharing of configurations amongst multiple Mac’s
  • Optional Ping and/or Wake On LAN before mounting
  • Run script after mount completion
  • Configuration backup and restore options

 

Heads-up!

FTP – Read only! 

Unfortunately, Apple’s implementation of the FTP protocol only allows us to mount an FTP connection as “read-only“.

SSHFS requires OSXFUSE (free!) 

If you’d like to use SSHFS, and I can actually recommend giving it a try, then you must install OSXFUSE and their SSHFS extension.

Note: to my surprise, SSHFS is often faster than SMB. Added bonus: OSXFUSE allows you to add other filesystems to your Mac as well (ext3, NTFS, etc).

Your Mac keeps waking up … 

Even though not related to ConnectMeNow; Something I have noticed on my Mac Pro – after midnight it kept waking up frequently, no matter what settings I used (incl. Disabling Power Nap, waking up from network traffic etc). I found that WiFi seems to be triggering this – I disabled WiFi and since then my Mac kept sleeping all night long … (Catalina 10.15.1 and 10.15.2)

 

Getting started with Mounting Network Shares and ConnectMeNow

Ok, so much for a quick intro, let’s get started with ConnectMeNow.


p.s. if you like ConnectMeNow, then a friendly request to please like it at Alternativeto.Net as well.

Download ConnectMeNow

ConnectMeNow is now 64 bit, signed, notarized and Catalina compatible. You can downloaded here:

DOWNLOAD - ConnectMeNow-v3.0.5-macOS.dmg 

Filename:  ConnectMeNow-v3.0.5-macOS-64bit.dmg
Platform:  Apple macOS
Version:  3.0.5
Size:  2.9 MB
Date:  2020-03-06

Direct reference link:  https://www.tweaking4all.com/downloads/ConnectMeNow-v3.dmg
 Download Now 

Installing ConnectMeNow

Installation is easy: open the DMG file you have just downloaded and drag the ConnectMeNow icon to the Applications directory.

Install ConnectMeNow

Install ConnectMeNow

Uninstalling ConnectMeNow

Removing ConnectMeNow is pretty easy as well: simply drag the ConnectMeNow icon from the Applications directory to the Trashcan.

You may also want to remove the configuration files, even though they are small, by simple dragging this directory to the trash, where “<username>” is your username. Note: In case you used a custom location for your configuration file, then you’ll have to remove those as well.

These are the only files related to ConnectMeNow.


/Users/<username>/Library/Preferences/ConnectMeNow

 

Supported Protocols

The protocols, you may or may not have heard of, supported by ConnectMeNow are:

SMB, one of the most commonly used protocols for so called “Windows shares” or “Samba Shares’.
Note: back in the day there was CIFS. macOS still supports (kinda) CIFS, by implementing this in SMB. This can come with some issues, but it usually points to your server or NAS being very old and in desperate need for an update so it starts working with more recent SMB versions.

NFS or Network File System started in the mid 80s as a protocol to share disk space amongst different computers. It is still supported by quite a few platforms, but it is not used as much as SMB. You will find NFS on most Linux/Unix based machines, where it has its origins as well (Sun).

AFP or Apple Filing Protocol is Apple’s protocol for working with network shares. Obviously this protocol is typically only used on Mac based computers, and if the stories are true – which I think they are, even Apple is dropping it in favor of SMB.

FTP or File Transfer Protocol, has been around for quite some time and is often used to share files with a web server. For the longest time, FTP was the only way to download files from the Internet. It still is one of the most used protocols for those accessing web servers, but then I’m more talking about developers or admins who know what they are doing (most of the time anyway hahah).

  Warning concerning FTP: a network share can only be mounted as read only! This is a limitation of the FTP implementation under macOS.

WebDAV or Web Distributed Authoring and Versioning, is not used very much either. I’m not 100% sure if this is really the fact, but to me it feels like an alternative to FTP, allowing the user “easier” and more reliable access to their web servers (WebDAV is afterall a HTTP extension – read: web server)

SSHFS or SSH File System, is maybe a little bit of an odd duck here. It runs file sharing over the SSH protocol. This comes with interesting possibilities, especially when a server or NAS is already running SSH (Secure Shell, kinda like a remote DOS prompt), since there is no need to install another network sharing protocol. The latter being great when you have no say in what is being installed on said server.

Now that I mentioned SSH: I do have to get into my NAS every now and then with SSH, so I have added SSH support as well.

  SSH is not a network file share protocol like the other protocols mentioned here. It is most commonly used for a remote terminal/shell/DOS prompt.

Protocol Parameters

For sharing a directory using a network share, most protocols rely on these parameters:

Server address, directory or share-name on the “server”, username and password.

Some protocols allow for some extra wiggle room, where the user can define a specific network port.

In a more professional environment, SMB shares can also require you to provide a so called “domain” name.
The use of domain is something you’ll see in companies, rarely at home.

 

ConnectMeNow in More Detail

I’ve included quite a few features and options in ConnectMenNow, so I’ll try to list them.

After starting ConnectMeNow, you’ll see a new icon in the menu bar of your Mac.
As you can see, ConnectMeNow does support Dark Theme:

ConnectMeNow in your MenuBar

ConnectMeNow in your MenuBar

At first start, the menu will be quite empty – after all, you’d still have to add your shares.

ConnectMeNow - Empty Menu at First Start

ConnectMeNow – Empty Menu at First Start

But once you’ve created shares, some additional features will be revealed.

The menu will show icons based on the selected protocol and they will indicate if a share or connection is active.

Additionally we can make groups in the menu, either by just using a horizontal line, or by adding a group name.
Here for example the group “QNAP SSH” – the horizontal line will always be there, except for the first item in the menu.
When setting a group name, it will show greyed out under the horizontal line – but using a group name is optional.

When clicking an inactive item (for example “Bender AllShares (SMB)”), ConnectMeNow will try to mount or activate the connection.
However when the connection is already active (eg. “Marvin AllShares (SMB)”) then a sub-menu will appear.

For mounted network shares this will show the option to reveal the mounted share in Finder (“Reveal in Finder“) or to “Unmount Share“.
With active SSH connections, you will see the option to “Close SSH Session“.

ConnectMeNow - Menu Features

ConnectMeNow – Menu Features

Adding Shares to ConnectMeNow

Adding shares is done by selecting the “Preferences” option in the ConnectMeNow menu.
This will open the preferences window where you can define shares, do some generic settings, and review Network info.

Adding a new network share or SSH connection is done by clicking the “Create new share or SSH connection” button ( Add a new Share or SSH Connection ).

Basic Settings

By default you will be presented with the basic settings. Not many users will need the advanced settings.

Example Basic Settings

ConnectMeNow – Example Basic Settings

Buttons and their purpose

On the left side, you’ll see a list of defined shares. At first this list will be empty of course.
Below that list you will see a few buttons and this is what they can be used for:

ConnectMeNow Buttons
 Button  Purpose
Add a new Share or SSH Connection Add a new network share or
SSH Connection
Add Menu Separator Add a new Horizontal Line
or a Menu Group
Copy a share Copy the selected connection which
can then be used as a base for a new share
Mount a share for testing Open/Mount the selected connection
which can be used to test a settings
Unmount a Share Eject/unmount or close the selected
network share or SSH connection
Move this share one position up Move selected share one position
up in the list/menu
Move share one position down Move selected share one position
down in the list/menu
Sort shares by name Sort all shares alphabetically
This will ruin menu groeps!
Delete selected share Remove the selected share
Delete ALL shares Clear the entire list
This will remove ALL shares!

 

After clicking the “Add new share” button, a new form will appear and in this form you can start by entering what the name should be in the menu, by entering this in the “Menu Label” field.

You’ll see a few options below that line allowing ConnectMeNow to automatically name your share based on selections you’ll make, like name of the server, connection type (mount type), remote path and if it utilizes Wake On Lan or not.

Mount Type

The next step is making a selection of what type of connection we’d like – set “Mount Type” to the preferred protocol.
When doing so, you may see some fields change or even disappear. This is related to the capabilities of the selected mount type.

In the next steps, the selected protocol may or may not support an option and therefore it will or will not be shown.

For example:

SSH and SSHFS do not support the selection of the path on the server – so that field will not be shown.
SSH additionally will not create a mount, rather it will open a shell window – so there is no option to reveal it in the Finder or define its mount path.

Use HTTPS

The WebDAV protocol supports HTTP and HTTPS – it is recommended to use HTTPS by leaving “Use HTTPS” checked.

Mount At Start

Each connection can be setup when ConnectMeNow starts by selecting “Mount At Start“, usually when you start your Mac or login to your Mac.

Reveal on Mount

Optionally, you can have Finder automatically reveal the mount after a successful mount, by checking “Reveal on Mount“.

  SSH will not mount to a directory, so Reveal on Mount will not be available with this protocol.

Server Address

For every server “kind” we will need to enter the “Server URL” – I mean, where else would we go right?
This can be an IP address or a computer name.

  This should be only the IP address or computername – do not add the path on the server!

  Note: Using computer names only works well, when your DNS knows the IP address that goes with this computer name. Not all setups work equally well with this when your Mac cannot retrieve the IP address based on the computer name.

Port

Some protocols allow you to use a specific TCP/IP port number, for example: SSH, SSHFS, WebDAV and FTP.

  Unless you know what you’re doing: leave the port number blank or to its default value.

Ping Test

This button allows you to do a quick ping to the server to see if it responds, which can be convenient to verify the Server Address.

  Not all network devices allow you to ping them. Some have ping disabled intentionally.

Path on Server

Not all protocols support this (for example SSH and SSHFS), but this is typically the share name on the server (SMB) or the actual path on the server (FPT).

  When left blank certain protocols, for example SMB and AFP, may result in a popup window asking for what share you’d like to access when mounting a network share – or the mount may fall all together.

Domain

The “Domain” name is only needed in a corporate setting where a domain is being used.
This is rarely used at home, and when used in a corporate setting you may want to consult with your IT administrator.

Mount Location

The mount location is used for all protocols except for SSH (since SSH doesn’t really “mount”).

In the mount process, a network share will be “linked” to a specific directory, for this specific mount (so each “mount” has its own directory) – your Mac creates this directory for you and it is by default located in the  /Volumes/ directory.

Now in ConnectMeNow, we can actually replace  /Volumes/ with something else, and ConnectMeNow will create a unique directory name for your mount, in that custom directory for you if needed.

We have 2 options here:

  • Use the default mount location, which mounts your share in  /Volumes/
    This is the default macOS mount location.
  • Use a custom path, which allows you to mount your shares in a different location.
    The default path I use is the directory “MountPoints” in your home directory ( ~/MountPoints/).

 

  The main reason to use a custom path is SPEED. Mounting to a custom path seems to go a lot faster.

  You can set a different custom path per share, however I would not recommend that – stick to one “Volumes replacement” directory to avoid confusion.

  Since SSHFS uses OSXFUSE, mounting in the default location is not supported since Apple has locked down this directory. Third party applications have no direct access to  /Volumes/.

Login

Naturally we like to keep things secure so login credentials can be used as well (username and password),
If not entered, when mounting a share, you will be asked for username and password.

The password can be revealed, however you will be asked for permission to reveal this information. This can only be done by an admin (which usually is you).

  For SSH and SSHFS: Generate & Install SSH Key – ConnectMeNow supports using a password for SSH and SSHFS. However, using SSH keys instead of a password is safer. Please read the section at the end of this article, on the use of SSH keys for more information.

Fallback Server

The Fallback server allows you to select another server for when the mount to this server fails.
Which can be practical for the use of backup servers, or for example use share1 for when you’re at home, and share2 for when you’re at work (laptop).

If the fallback server fails as well, then ConnectMeNow will try to mount the fallback server of the fallback server, etc.

  A fallback server must to be defined as a regular share before it appears in the list.

  This fallback server must be using the same protocol.

  To avoid endless looping, only 4 fallback servers can be set in sequence.

Warning Messages

In some scenarios a helpful tip or warning will be displayed at the bottom of this form – please do take the time to read these messages!

Advanced Settings

To accommodate some special wishes, you can also do some advanced settings by clicking the “Go to Advanced Share Settings” button.

Returning to the basic settings is done by clicking the “Back to Basic Share Settings” button when the advanced settings are being displayed.

ConnectMeNow - Example Advanced Settings

ConnectMeNow – Example Advanced Settings

Ping before mount and/or Wake on LAN

When checked this option will first send a quick ping for a share is being mounted.
This can be useful when a server, or other network device, switches to a low power mode (for example spinning down the hard disks).
The ping can then possibly trigger the server to spin up its disks, allowing for a speedier mount process.

  When Wake On LAN is enabled, this ping will be done before the Wake On LAN – just in case the server is already awake.

Wake On LAN before mount attempt

It is not uncommon, to save money on power, or because you are environment conscious, to have your network devices to go to sleep when not used for a while.
This option allows you to send a wake-up call to the server, so we can actually reach it and mount our share or open up our SSH connection.

You’ll find a few functions here that may make things a little easier.
For example a button to paste the MAC address or IP mask (“Paste“),
a button to have your Mac try to find the MAC address (“Detect“) which will be based on the “Server Address” field in the basic settings,
and a button to “Test Wake On LAN“.

  See also: miniWOL v2 – Quick and Easy Wake On LAN Utility where you can also find more information on how Wake On LAN works.

Run script on mount

This was a special request; some users like to run a shell script after mounting a network share.
Since I have no use for it myself, testing has been minimal so your mileage may vary.

Attempt Auto Mount on Network Change

ConnectMeNow keeps an eye on your network connections. When checking this option, ConnectMeNow will try to mount this network share if the server is available.

Adding Groups to the Menu

Adding a group works in a similar way. Click the “Add Menu Separator” button ( Add Menu Separator ).
This will create a new horizontal bar for the menu.
Optionally you can give this “group” a title by entering text in the “Menu Label” field.

Notes :

  • If the horizontal line is the first item in the menu, then this line will not be shown (a limitation of the menu),
  • In case you used a group title (Menu Label) and want to remove it; simply blank the “Menu Label” field,
  • The Menu Label, or Group Title, will show as greyed/disabled in the menu to distinguish them from actual network shares.

 

Preferences & SSH Keys

The tab “Preferences & SSH Keys” gives you access to some more generic preferences.

ConnectMeNow - Preferences and SSH Keys

ConnectMeNow – Preferences and SSH Keys

Default Values for new Shares

In this section, you can predefine some values for when you create a new share.
This can save you some time when having to enter a lot of shares, or for example when you always like to use the same settings.

The displayed fields work the same as the same fields seen when you create a new share.

An additional option you will find here is the option to make a backup, or do a restore of your settings and your shares – which can be convenient for backup purposes or for when you’d like to copy the settings to another computer and you do not have the option to share these settings for example through DropBox (more about the below).

When restoring a backup: keep in mind that your current settings will be overwritten!

ConnectMeNow Settings

These settings are for ConnectMeNow in general.

With the option “Start ConnectMeNow on computer start“, your Mac will automatically start ConnectMeNow when you boot your Mac and/or login to your Mac.
This will add or remove ConnectMeNow from the “login items” in your Mac’s System Preferences.

Next to this option you will see the option “Remount shares after waking up from sleep“.
The purpose of this function is to check if all mounted shares are still available after your Mac wakes up from standby or sleep mode.
ConnectMeNow gets notified by macOS when your Mac goes to sleep, and at that point quickly checks which connections are active.
macOS will also notify ConnectMeNow when your make wakes up again.
At that point, ConnectMeNow will compare existing connection with the connections that existed before your Mac went to sleep.
If there are connections missing, ConnectMeNow will try to remount those connections automatically.

  Remount after waking up does not waste any extra resources – macOS will just notify ConnectMeNow automatically.

ConnectMeNow can show mount/unmount event notifications, but not all of us are fond of these kind of notifications.
Unchecking the “Show Notifications” mutes all ConnectMeNow notifications.

Having mentioned notifications; ConnectMeNow has been setup so that macOS will actually tell ConnectMeNow when a network share is being mounted or unmounted – this way the icon in the menu can show you if a connection is active or not.

However, an SSH connection is not really a mount action and therefor macOS will not report a new SSH connection or the disappearance of such an SSH connection.

The work around in ConnectMeNow is using a timer, that during idle time will check and see of an SSH connection is active or not.
This is activated through the “SSH Status check“, and every x number of seconds, if idle, ConnectMeNow will check the SSH status.

If you have “SSH Status check” disabled; the menu of ConnectMeNow will not show you if an SSH connection is active or not. So if you don’t care for this indication for SSH, or if you do not even use SSH: feel free to disable this option.

Now the next item is the “Custom Preference Location” – one of my favorites.
The idea behind this was to share my ConnectmeNow preferences amongst all my Mac’s and with the old ConnectMeNow I have seen some users even do this company wide.

Naturally, sharing my settings through a network share would work, but it kinda defeats the purpose since we’d need to mount the network share first before ConnectMeNow can actually access these settings.

So for this purpose I use DropBox – since DropBox is synced amongst my Macs automatically (same for Google Drive, OneDrive etc.).
In my case I’ve created a separate directory in DropBox that holds my settings and each Mac uses ConnectMeNow, pointing to this DropBox directory.
Each time I change my settings, the other Macs will be in sync as well.

In case you’re selecting a location that already holds ConnectMeNow settings, then ConnectMeNow will give you a choice: use the existing settings or replace them with the settings it just found.

Note: ConnectMeNow v3 is NOT compatible with settings from older ConnectMeNow versions (v1 or v2)!

By default the Preference window will open in the center of the screen, and not all of use “love” that.
So I’ve added the option to “Remember window position” so the next time the Preference window opens, if this option has been enabled, it will open in the same place again.

SSH RSA Key

See the section below on SSH keys for more detail.

In short: here is a tool that can generate an SSH key for you, or verify that it exists.

The default location will be used for this (  ~/.ssh/  ) and it will generate the files “id_rsa” and “id_rsa.pub” for you.

Network Info

This tab is more of an information tab than anything else. I’ll admit … I loved playing around with this, but I’m not sure anyone really needs it, but it has been quite helpful for me while testing and I enjoyed tinkering with it.

You will find 3 sections here:

ConnectMeNow - Network Information

ConnectMeNow – Network Information

Network Info

This section shows you the existing network connections your Mac is aware off.
You can see per connection if they are active, what their IP address is and what their device name is (en0, en1, etc).

WiFi Info

In this section you can see the WiFi access points that your Mac is seeing … or totally nothing if you do not have WiFi or WiFi has been disabled.

Per WiFi access point you can see the channel, signal strength, if it is password protected, what the access point name is and (bold) if your Mac is using an access point.

Current ARP Entries

This is a list of entries ARP on your Mac, is aware of.
This list keeps changing over time, and pressing “update” every now and then will show you more and more devices your Mac seems to see in the network.

SSH Logins – Use a Password or a SSH Key …?

Standard SSH can be used with either a username and password, or by using a username and a so called “SSH Key”.
The latter being more secure and often much faster than just using a regular password.

ConnectMeNow supports both methods, and deep down this is also used for SSHFS, since SSHFS uses SSH as well.

Now, using those “SSH Keys” is all nice and dandy, but it can be a little cumbersome if you have never used it, or only have used it maybe once or twice in the past.

  More detail on how these “keys” work can be found in the article: SSH Login without a Password

ConnectMeNow does provide a few tools that can make life easier;

 

  You have to create these keys (a private and a public key) only ONCE!

  If you generated new keys, for some reason, you will need to copy the new keys to server again!

  The “Generate & Install SSH Key” or just “(Re)Install SSH Key” will only appear if username and password are entered!

  ConnectMeNow will only use SSH Keys when the password is blank!

 

Generate Private and Public keys, and Push the Public Key to the server

For the server to work with these kind of keys, we will need to give the server our so called “public key”, which can be done with the button “Generate & Install SSH Key” or “(Re)Install SSH Key” (if you already have a key generated before) in the form where we define our shares.

  1. Your login credentials are required to push the public key to the server – so enter your password and username.
  2. Click the button “Generate & Install SSH Key” and ConnectMeNow will generate keys if needed, and it will try to push the public key to the SSH enabled device.
  3. Once successfully pushed to the SSH device: clear the password field – this way ConnectMeNow knows that it should use the keys instead of the password.
  4. Leave the username as is – it is still used to setup a connection.

Login with SSH keys

Once you’ve pushed the key to the server and you cleared the password field of the share, ConnectMeNow can start using the keys to login to your SSH enabled device. But it will only use the key if you actually cleared the password field.

All the steps combined in a short video

Here a short video how this works.
In this video we had not yet generated any SSH keys. We just started out with creating a new SSH connection.

The steps I followed in the video:

  1. Create a new share (click the Add a new Share or SSH Connection button)
  2. Enter a name for the share in the “Menu Label” field
  3. Set “Mount Type” to “SSH
  4. Enter the server address
  5. Check “Login with credentials
  6. Enter username
  7. Enter password (this is where the button becomes available)
  8. Click “Generate & Install SSH key
    (since you have a key after this, the button will read “(Re)Install Key” for the next connection you’d want to use this for)
  9. Click “Yes” when ConnectMeNow asks me to blank the password (button disappears now!)
  10. Click the “Mount a share” button to test the connection (click the Mount a share for testing button)
  11. Terminal pops up and logs into your SSH enabled device.

 

  Keys can optionally also be generate on the tab “Preferences & SSH Keys“, you’ll see a button “Generate SSH key” in case you do not have an SSH key stored in the default SSH directory on your Mac (  ~/.ssh/  ). This default directory is where SSH will try to find the key when you start a connection with a server.

Donation options


Donations are very much appreciated, but not required. Donations will be used for web-hosting expenses, project hardware or a motivational boost (a drink or snack). Thank you very much for those have donated already! It's truly AwEsOmE to see that folks like our articles and small applications.

Please note that clicking affliate links, like the ones from Amazon, may result in a small commission for us - which we highly appreciate as well.

Comments


There are 170 comments. You can read them below.
You can post your own comments by using the form below, or reply to existing comments by using the "Reply" button.

  • Nov 25, 2019 - 8:16 AM Comment Link
    PingBack: www.tweaking4all.com

    […] requirements around it, I’ve created a completely new version of ConnectMeNow. Please visit this article where you can download the latest […]

  • Nov 25, 2019 - 8:32 AM - Simon Smith Comment Link

    Amazing software update, works perfectly!
    only issue i have is, i still cant connect to my stupid windows 7 guest share server
    is the anyway to enable the debug window like in version 2 to watch what the software does?

    Reply

    Simon Smith

    • Nov 25, 2019 - 9:11 AM - hans - Author: Comment Link

      Hi Simon!

      Thanks for the compliment! 
      Not required at all, but please do feel free to like it on AlternativeTo.net as well 
      OK after that shameless plug for my own tools …

      Debug Window

      You can enable the debug window by pressing the keys: CONTROL+OPTION+COMMAND (Windows keyboard: CTRL+ALT+WINDOWS).
      It will reveal the “Show Debug Log” button. While having the buttons pressed, click the button to open the log.
      I’ve hidden it intentionally, to avoid too many questions on my own debug log  .

      Windows Guest Shares

      Unfortunately, it will most likely not tell you what went wrong though.

      Ever since you first questioned this, I’ve been tinkering with Windows 10 and the guest login (I no longer have Windows 7 available), trying to figure out what the issue is. So far (as we already discussed) it seems a Microsoft choice to not allow guest logins. All the work-arounds I have seen on the Internet, have been useless, and none of them “open” the guest login option .

      Even though really utterly ridiculous, since Windows already comes with everything SMB, but maybe Samba can be installed on Windows … I’ve been looking, but haven’t been able to find it (yet).  It has been done on older MacOS versions, where they replaced Apple’s SMB version with an official Samba distribution. It was called SMBUp – but it not longer works (32bit vs 64bit).

      The only alternative I can think of, is making a specific users on that Windows machine, including password and access rights. But I fully understand that this is NOT what you’re looking for.

      Reply

      hans

      • Nov 25, 2019 - 9:22 AM - Simon Smith Comment Link

        thank you, i will have a play and see what i can do…
        i am still able to connect via the ‘Connect To Server’ in finder without any issues using the url ‘smb://Guest:@10.0.0.15/Hestor_Office’
        but you must use Guest as user and include the colon with a blank password!
        im not sure if your application sends a blank password if the user is Guest or not?

        also is it possible to have the debug window pop up rather than slide down as it doesnt fit on my screen https://i.ibb.co/ZmG0wHD/Screenshot-2019-11-25-at-15-14-43.png

        Reply

        Simon Smith

      • Nov 25, 2019 - 9:52 AM - hans - Author: Comment Link

        You could try leaving the password blank and use the custom mount path.
        This utilized the mount function (and the functions derived from it).
        It should do the same as what you’re describing. I hope anyway. It builds the same command though.
        It formats as such: 

        mount_smbfs //<domain>;<username>:<password>@<serveraddress>/<remotepath>

        I can’t test it here, but maybe you can try it on your end.
        So the command would become:

        mount_smbfs //Guest:@10.0.0.15/Hestor_Office

        Note that using the default mount may fail, since I just pass username and password to the macOS API, and I do not know if this API call will then use “Guest:” or just “Guest”.

        I’m curious about your findings, since Windows 10 is a beast when it comes to sharing directories. 

        The log window; I’ll consider adding a button that allows the box to disconnect and show as a separate window.
        It will take some work, but it is not impossible, so I’ve added it to the To-Do list – thanks for the suggestion 

        Reply

        hans

  • Nov 27, 2019 - 4:08 PM - Michael Comment Link

    How can I mount all shares from my NAS at once (SMB share)? I can only mount one share a time when I enter in the path e.g. /video

    Any help is appreciated

    Thank you!!!!!

    Reply

    Michael

    • Nov 28, 2019 - 4:21 AM - hans - Author: Comment Link

      Hi Michael,

      Very interesting question, I had not thought of that use-case! 
      What you could do, is mark all the SMB shares you’d like to mount at once as “Mount at start” (you’ll have to set this for each individual share).
      Selecting the menu option “Execute AutoMount” will then mount all the shares you have tagged.
      Keep in mind that this function was actually intended to have all tagged shares to be mounted when ConnectMeNow starts – so this may or may not be a desired side effect.

      Now,… if I’d implement a function to mount “groups”, I’d have to make some changes, but if there is a reasonable interest in such functionality, then I most certainly could consider it.
      For example by adding an option with each group (in the menu) saying something like “Mount Group”.
      I’ve added it to To-Do list as something to explore. If more users want this option, then I’ll try to figure something out 

      Reply

      hans

      • Nov 29, 2019 - 5:11 AM - Michael Comment Link

        Hans, thank you, much appreciated, it was never a problem with v1 until v2.1.4 Beta, groups were always working just be giving the IP, User and Password; Then a window opened to select the mounts; that was perfect for me, so I am sticking with 2.1.4 as for now :-)

        Thanks for your great work

        Reply

        Michael

        • Nov 30, 2019 - 5:01 AM - hans - Author: Comment Link

          Hi Michael,

          Oh, did you mean the popup macOS presents where you select the mount?
          In v1 I have used AppleScript to do certain mounts. I kind-a would have expected to see the same type of message when mounting against /Volumes.
          But I suppose that isn’t happening.
          Didn’t you have to select an individual share there as well?

          Reply

          hans

          • Dec 1, 2019 - 1:50 PM - Michael Comment Link

            Hi Hans,

            I am always getting a warning Unknown mount or User when I use /Volumes as path; I can only get it to work, when I mount a specific share like /video

            Best,

            Michael

            Michael

          • Dec 2, 2019 - 4:48 AM - hans - Author: Comment Link

            Hi Michael,

            OK, it was worth a try.
            To do a mount, the remote path needs to be defined, and it seems the Apple API wants that as well (just the the Unix “mount” and the command line “mount_smbfs”). Bummer.

            So what I could try to implement is a “group mount” function, but you’d still need to define the individual paths.
            At this moment I have no option to “explore” what mount directories a server would have. There may be a function for that, I’m just not aware of it.

            I’m not sure if this would be a workable solution?

            hans

          • Dec 2, 2019 - 12:54 PM - Michael Comment Link

            Hans, thank you again, I `ll stay with 2.1.4 for the moment, may be you will find a solution in the future

            Best,

            Michael

            Michael

  • Nov 29, 2019 - 2:58 PM - arlo Comment Link

    Great!

    So far so good except one little glitch.  I have two smb mounts that have spaces in their names.  when I try to mount them i get this pop up window from CMN that says “Access Violation”

    Reply

    arlo

    • Nov 30, 2019 - 5:03 AM - hans - Author: Comment Link

      Hi Arlo,

      thanks for the feedback. I’m surprised to hear there is a glitch with mounts that have spaces in it.
      Did you mean the remote directory path or the local mount path?

      Reply

      hans

    • Dec 2, 2019 - 4:54 AM - hans - Author: Comment Link

      Something to try:

      Say your remote path is “some path with spaces”, try escaping the spaces like so: “some\ path\ with\ spaces”.
      Not sure if that will work, but worth a try.
      Does this happen when mounting to “/Volumes” (default) or when using a custom path?

      Reply

      hans

      • Dec 4, 2019 - 3:54 PM - Arlo Comment Link

        space in the remote directory path.

        tried escaping, it gets really weird then.  I’ll try to capture a shot of it tonight and post

        i’m mounting to ‘/volumes 

        Reply

        Arlo

        • Dec 5, 2019 - 5:35 AM - hans - Author: Comment Link

          Feel free to email me at webmaster at tweaking4all dot com, since posting pics won’t work here in the comment section (intentionally, since in the past folks would post inappropriate pictures).
          I’d be happy to see if we can fix that issue! 

          Reply

          hans

          • Dec 9, 2019 - 3:07 PM - Daniel Comment Link

            I get the same problem, smb shares work great without spaces but the one I have with a space causes the access violation error. Im also using a domain if that helps.

            Daniel

          • Dec 10, 2019 - 4:36 AM - hans - Author: Comment Link

            Thanks for confirming!
            I managed to reproduce the problem and I hope to resolve it today … 

            hans

          • Dec 10, 2019 - 4:54 AM - hans - Author: Comment Link

            OK, weird as it is … I did find a way to fix this; replace spaces with %20 … (like in website URLs)
            I will implement this fix once I know for sure this is the best way to do it, but for now this trick works in the current ConnectMeNow.

            hans

  • Dec 3, 2019 - 4:10 PM - Christophe Comment Link

    Thanks for this new version!! I was actually holding off upgrading to Catalina because I rely on ConnectMeNow so much 

    I did run into an issue though – when I go into preferences, I can add my shares, however if I close preferences, and then go back into preferences, no matter what I click in the list on the left, the details section on the right stays empty – so I can’t edit any share once I have created it. Has anyone else reported this?

    Reply

    Christophe

    • Dec 3, 2019 - 4:15 PM - Christophe Comment Link

      I just found that when the Preferences window shows up, all I need to do is move the window a bit for the details the show when I click on a share!

      Reply

      Christophe

    • Dec 4, 2019 - 5:37 AM - hans - Author: Comment Link

      Hi Christophe!

      Glad you to hear you like ConnectmeNow 

      I presume the issue is resolved then?

      Reply

      hans

  • Dec 5, 2019 - 10:18 PM - Ray Knight Comment Link

    Tried ConnectMeNow 3.0.0 (Build 102) after upgrading to MacOS Catalina 10.15.1 and noticed that Apple once again broke how things so my Linux NFS shares would no longer mount.  Not having any success with ConnectMeNow either.  After configuring the mount I get:

    Mount failed

    Error: Mount Error

    Which doesn’t give me enough information to help discover what the problem might be.  If I use Default Mount location instead of custom path the error changes to:

    Mount failed

    Error: Error – Mount Failed (Error code: 1)

    Still not helpful.  Hoping you can tell me what I’m doing wrong!

    Ray

    Reply

    Ray Knight

    • Dec 6, 2019 - 4:33 AM - hans - Author: Comment Link

      Hi Ray,

      I’ve tested NFS with my QNAP NAS, since that was the only quick way I could test it.
      You could try using a custom mount point (so not using /Volumes) and see what happens?
      I presume it worked in the old ConnectMeNow, so if need be, I’ll try to incorporate the old method – but it will be a lot of work.

      Reply

      hans

    • Dec 6, 2019 - 6:01 AM - hans - Author: Comment Link

      My bad – I overlooked your statement; I see you’ve already tried default and custom mount point … 

      I do check the error messages returned from the API call (default) and the Mount statement (c-library). The useless error messages you see, are error I, or the function calls, couldn’t classify.
      Have you been able to do a manual mount (Terminal)? And if so: what is the statement you use?

      Reply

      hans

    • Dec 8, 2019 - 4:26 AM - hans - Author: Comment Link

      I did some testing (old ConnectMeNow, and Terminal) and found it to be failing in my test setup as well.
      From what I understand, and keep in mind that I’m a total newbie when it comes to NFS, is that the currently logged in user or userid (on your Mac) is being used to authenticate on your NFS server.
      I have to do some more digging though, and learn a LOT more on NFS in order to create a fix.

      Reply

      hans

  • Dec 7, 2019 - 12:30 AM - Troy Williams Comment Link

    Hi there! Thanks so much for writing this app! I’m a rookie to NFS and this app is much easier to work with, plus it’s a bit more useful in trying to troubleshoot what I’m doing wrong with a couple of NFS servers I’m experimenting with.

    I’ve been getting a few error codes though. It’d be helpful to know what they are so that I can try to pinpoint how my server is misconfigured. Would it be possible for you to post a list of them? In particular, Error Codes 5 and 13.

    Thank you!

    Reply

    Troy Williams

    • Dec 7, 2019 - 6:57 AM - hans - Author: Comment Link

      Hi Troy,

      I’m a total rookie when it comes to NFS as well and have come to the conclusion that the current user on your Mac is being used to setup the NFS mount. But I’ll need to do some more investigation and take a peek at my old ConnectMeNow version as that one seems to work somehow.

      From what I could find on the error codes;
      Error 5 indicates a communication issues (NFS3ERR_IO), which could mean pretty much anything from server not configured properly, to wrong server address or bad network cable.
      Error 13 is a “permission denied” or “access error” (NFS3ERR_ACCES), which means pretty much not much either. The server doesn’t allow access, so this could be the wrong server address, username, password etc.

      The RFC1813 document gives you more codes. These are NFS specific it seems, so I’m debating if I should or should not include them in ConnectMeNow.

      I did some command line testing and those failed exactly as you described (permission errors).
      I’ll try to dig into that some more, but it will take some time (since I’m a NFS noob as well).

      On that note, is there a specific reason why you’d want to use NFS (not saying that you shouldn’t use it)?

      Reply

      hans

    • Dec 8, 2019 - 5:44 AM - hans - Author: Comment Link

      While investigating what is going on here, I did find this interesting read: KODI – NFS Sharing from OS X letting us know that the “uid” is being used.
      I had just reconfigured my QNAP NAS, and I really never use NFS, so maybe I screwed up something there, not allowing my macOS uid to login (eg. my macOS username is unknown on my NAS).

      An additional note for QNAP, which may apply to other NAS devices as well, is the use of the correct port number (automatically) – source :
      By default, macOS connects to an NFS server using a “non-privileged” TCP/IP port, which means is a port number ≥ 1024.
      However, the [QNAP] NAS only accepts connections from a “privileged” TCP/IP port, so a port number ≤ 1023.
      For this purpose the option “resvport” needs to be set for Mac OS X to use a privileged port (command line mount).

      Note: command line access on my Mac still fails with “Permission Denied” or an “Operation not permitted”, even when using “sudo” for a mount.

      I’ll continue investigating this … feel free to post comments/suggestions that may help out 

      Reply

      hans

    • Dec 8, 2019 - 6:41 AM - hans - Author: Comment Link

      Just bumped into a few “interesting” observations (besides a lot of people complaining about NFS on macOS). 

      First of all:
      While trying to use “mount” in Terminal, to mount a Public folder, I’ve noticed that macOS (in Catalina anyway) seems to require “sudo”.
      Also: passing username and password does not seem to be an option for either “mount” or “mount_nfs” when trying to mount an NFS share.

      Another thing I have noticed;
      In CMN3, if you create a NFS share pointing to a share on your server that can be accessed as a guest, then CNM3 will actually mount it when using /Volumes.
      Using a custom mount point will fail however, and username/password seems to fail as well.

      On that note: the CMN2-beta showed the same behavior.
      As an alternative CMN1 and 2, had the option to use “oscascript”, which you can try in Terminal:

      osascript -e 'mount volume "nfs://192.168.1.100/Public"'

      Which will mount to /Volumes. Passing username and password however fails on my setup as well (for shares that require a username/password):

      osascript -e 'mount volume "nfs://192.168.1.100/Someshare" as user name "myusername" with password "mysecretpassword"'

      Naturally, this failing could be related to my new NAS configuration.

      Reply

      hans

      • Mar 5, 2020 - 4:18 AM - Bob Comment Link

        Hi,

        I was wondering if you fixed the mount problem with NFS? Because I cannot seems to get it to work with CMN 3.0.3.

        I keep getting error messages. I have tried with the following prefs:

        – Default mount (mounts in /Volumes/) error: permission denied

        – Use custom path error: Mount error

        When mounting the NFS share through terminal with this code everything works fine.

        sudo mount -t nfs -o resvport,rw mysynology_nas.local:/volume1/photos /Users/name/Photos
        Reply

        Bob

        • Mar 5, 2020 - 5:05 AM - Simon Smith Comment Link

          Hi,

          whats the ouput thats received in the debug log? hold down CTRL+ALT+CMD in preferences to reveal the ‘show debug log’ button

          i have however spotted a bug however

          if you enter an ip address or dns name then click the arrow on the path, it browses for the nfs shares which is cool

          BUT if you select one of them, its adding an extra value of Everyone at the end of the path rather than just the path name?

          /mnt/Drive1/SimonStore              Everyone
          Reply

          Simon Smith

          • Mar 5, 2020 - 6:43 AM - Bob Comment Link

            Thanks for replying! Yes I have noticed the bug, but even if I change everything the right way it still isn’t working.

            13:34:22: Trying to mount base/volume1/scanner
            Mount path : custom (/Users/myname/Mountpoints/)
            Mount response : Mount Error

            I have tried it with .local, domain and IP but non of them work

            Bob

          • Mar 6, 2020 - 3:31 AM - Hans - Author: Comment Link

            Hi Bob,

            (thanks Simon for chiming in!)

            I have a hard time testing with NFS, since and NFS mount on my QNAP seems to work just fine.
            However, it’s been a while that I tested this, so I’ll do some testing hopefully today.

            @Simon: Where do you see the extra value when selecting a path name?
            (just so I can reproduce the exact steps)

            Hans

          • Mar 6, 2020 - 3:34 AM - Hans - Author: Comment Link

            Note: 

            I managed to reproduce the “adding extra text” when selecting from the dropdown. In my test it added a bunch of spaces.
            So I’ll look into that one!

            Hans

          • Mar 6, 2020 - 3:46 AM - Simon Smith Comment Link

            little gif video for you :)

            its the dropdown when you select the arrow to browse shares,

            its shows all including Everyone but also adding extra spaces?

            Simon Smith

          • Mar 6, 2020 - 5:03 AM - Hans - Author: Comment Link

            @Simon: Awesome little GIF (I hope you don’t mind me posting it here – I didn’t see any privacy concerns)!!! 

            Yeah, I see where this is going wrong.
            I’ll do some testing here. it is most likely related to some parsing where unexpected output appears (unexpected by me hahah).
            I’ll get back to this today!

            Hans

          • Mar 6, 2020 - 6:42 AM - Hans - Author: Comment Link

            @Simon and @Bob:

            I have found the issue with the extra text, but this will need some testing.
            My QNAP doesn’t add a word or phrase there, but it does come with some extra spaces (like a lot of them), so for now I’m carefully assuming that if a double space is found in the text, that everything beyond and including that double space should be removed.

            In the meanwhile I’m unable to mount any of my NFS volumes (tried through FInder, tried Bob’s approach with sudo mount as well, and even this one in the QNAP Wiki [like Bob’s method]). Look into that one 

            Hans

          • Mar 6, 2020 - 6:57 AM - Hans - Author: Comment Link

            Alrighty – getting somewhere now. Seems QNAP has some very well hidden access rights for NFS. I haven’t found the correct one for read/write, but read-only does work with:

            mount_nfs 192.168.1.100:/Downloads /Users/hans/MountPoints/test

            Does this work for you guys as well?

            By the best of my knowledge, NFS doesn’t use a username/password combo.
            If anyone could confirm this, then that would be helpful as well 

            Hans

          • Mar 6, 2020 - 7:05 AM - Simon Smith Comment Link

            Hi Hans, works fine here,

            mount_nfs 192.168.168.123:/mnt/Drive3/ISOImages /Users/Simon/MountPoints/test

            altho my little snitch had a field day with denying every incoming connection from my NAS to rpcbind, rpc.statd and rpc.lockd
            so i had to allow the incoming connections to get write permissions working

            Simon Smith

          • Mar 6, 2020 - 7:20 AM - Hans - Author: Comment Link

            Thanks for confirming Simon! 

            I’ve fixed the “extra text” issue, modified the way a mount is execute when using a custom mount, disabled the login section when selecting NFS, and added a warning at the bottom concerning username/password and the non-privileged port use.

            I sure hope you guys know what you’re doing with NFS, since mine still only does a read-only mount (but that will be a QNAP issue or user-error on my end ).

            Onto the next bug you guys reported, so I can hopefully post an updated version today 

            Hans

          • Mar 6, 2020 - 7:51 AM - Hans - Author: Comment Link

            I’ve uploaded 3.0.4. 

            Hans

        • Mar 5, 2020 - 6:46 AM - Simon Smith Comment Link

          whats the error when using the /Volumes/? is it the permission denied error?

          daft one, have you tried restarting the comp?

          also have you tried typing everything in manually rather than using the search dropdown?

          Reply

          Simon Smith

          • Mar 5, 2020 - 7:28 AM - Bob Comment Link

            Thanks! I figured out the problem, it was the above check-mark

            Bob

          • Mar 6, 2020 - 3:34 AM - Hans - Author: Comment Link

            So I can reproduce; what checkbox did you mean? 

            Hans

          • Mar 6, 2020 - 4:46 AM - Bob Comment Link

            @Hans

            The check-mark is a preferences choice at my Synology NAS giving permission to allow connection from non-privileged ports. This needed to be check in order for NFS to work with macOS (High Sierra).

            I did post a screenshot yesterday but it seems that it didn’t uploaded well.

            Thanks for your support!

            Bob

          • Mar 6, 2020 - 5:10 AM - Hans - Author: Comment Link

            @Bob

            Thanks Bob – I don’t really use NFS, but I do remember reading something about that.
            A problem I had not encountered with my QNAP, but looking at it: pretty nice that Synology offers the option to allow this! 

            Posting pictures here can only be done by placing a link (like Simon did), and I can manually copy the image and place it in the post (if appropriate). Unfortunately, in past some user found it necessary to post inappropriate pictures. So I had to disable that option.

            As an alternative, registered users can post images in the forum. 

            Hans

  • Dec 10, 2019 - 8:04 AM - hans - Author: Comment Link

    UPDATE:

    Version 3.0.1 has been released today. Changes:

    – With NFS and SMB shares, the remote path can now also be selected from a dropdown list (note: for some servers you will need to enter username and/or password before this list shows)
    – Bug fix: mount shares with spaces and other characters in the remote path name

    Known issues;
    Mounting NFS shares that require authentication can fail. This seems related to username/password of macOS vs Server not matching. Any help or more insight is appreciated.

    Reply

    hans

    • Dec 13, 2019 - 4:35 AM - Simon Smith Comment Link

      thank you so much hans, not sure what you have changed or maybe its the new 10.15.2 update
      but i can finally connect to my windows 7 share with guest access, and no errors, it just works!!!

      Reply

      Simon Smith

      • Dec 13, 2019 - 4:45 AM - hans - Author: Comment Link

        I think maybe Apple changed something? Very good to hear though that it now works! Awesome! 

        Reply

        hans

  • Dec 22, 2019 - 11:35 AM - Loek Comment Link

    Hi, first time user. For some reason another app I have been using for a long time (Automounter, see appstore, just gives me Finder crashes).

    What is with the notifications for Timemachine mount/unmounts ?

    Reply

    Loek

    • Dec 24, 2019 - 8:45 AM - hans - Author: Comment Link

      Hi Loek,

      First off – You can disable the notifications: Preferences -> Preferences & SSH Keys -> uncheck “Show notifications”. 

      The mount/unmount messages are given to ConnectMeNow by the macOS API, and this API has no option to filter out certain messages (like mounting TimeMachine shares).
      I’ve stopped using TimeMachine a while ago (ran out of disk space on my NAS), so I’m not sure what these mount/unmount messages may look like.
      If there is a generic part in it, I could include it in the filter in ConnectMeNow that filters certain messages (it already filters messages like when Recovery is temporary mounted and such).
      The mount/unmount of TimeMachines shares is done by macOS by the way.

      Reply

      hans

  • Jan 3, 2020 - 10:03 AM - Jim Termini Comment Link

    Good Morning!  First time attempted user here.  I am, unfortunately, running Mac OS X El Capitan (10.11.6).  Due to a long standing bug in AppleScript, we are unable to upgrade beyond 10.11.6.

    When I download ConnectMeNow-v3.0.1 and attempt to open the .dmg file I get an error stating “The following disk images couldn’t be opened” –  “no mountable file systems”

    Any idea what might be happening?  I’ve had not other problems with other DMG files.

    Reply

    Jim Termini

    • Jan 4, 2020 - 5:50 AM - hans - Author: Comment Link

      Good morning Jim!

      Sorry to hear you’re running into issues with the DMG. 10.11.6 is quite old and I do feel for you not being able to upgrade.
      It could be that the older macOS version doesn’t support signed applications and/or notarized DMG’s – at least, that would be my guess.
      Aside from that, I do not know if ConnectMeNow 3 would run under macOS 10.11.6 – I quickly created a ZIP file for you (not notarized, not signed) to see if it works. Download here.

      Reply

      hans

  • Jan 8, 2020 - 7:24 PM - Rob Espinosa Comment Link

    I’m on MacOS Catalina 10.15.2 and could not get the app to work with either mounting of AFP or SMB shares on my Synology. I kept getting error code 2 failure on mount point regardless of what I did.

    I am able to mount through Mac Finder- Connect to Server and strangely ConnectMeNow even gave me a notification when I did it the standard way.

    I was also able to do a successful Ping Test from within the app.

    I spent half an hour trying everything I could think of, even manually setting the Path on Server and Mount Locations when the default options didn’t work.

    Is there just a problem with the new version on the latest Mac OS?

    Reply

    Rob Espinosa

    • Jan 9, 2020 - 5:29 AM - hans - Author: Comment Link

      I Rob,

      Sorry to hear you’re running into issues.

      I’m on Catalina 10.1.52. as well and use it daily for SMB mounts on a QNAP NAS, SSH for my NAS/Website/LibreElec, and SSHFS for my NAS and website.
      All without any issues, so I’m wondering about your settings and the log file. Instead of posting them here: feel free to email me at webmaster at tweaking4all dot com. I hope we can figure this out together. 

      Also, these are settings that should happen automatically:
      Check under  – “System Preferences” – “Security & Privacy” – “Privacy”:
      – Under “Files and Folders” check if “ConnectMeNow” is listed and has the option “Network Volumes” checked.
      – Under “Automation” check if these are checked: “System Events”,  “Terminal” (possibly listed twice)

      Reply

      hans

  • Jan 9, 2020 - 6:50 AM - Loek Comment Link

    Rob,

    I am also using 10.15.2. This app works like a charm with my two QNAP NAS (running latest FW).

    Small remark for the 4-disk TS-451, sometimes the connection is lost after returning from sleep mode, but either the app itself reconnects or a manual reconnect solves it. However, this occurs rarely (maybe once per week, my iMac is on for the complete week).

    Reply

    Loek

    • Jan 9, 2020 - 11:56 AM - hans - Author: Comment Link

      I noticed certain shares to unmount when my Mac (Mac Pro and MacBook Pro) is sleeping as well – which kind-a annoyed me, so that’s why I did an attempt to have ConnectMeNow restore the connection after coming out of sleep mode in case a previously mounted share had been unmounted. So far it has been working well for me. 

      If you look in the log of ConnectMeNow then you may see some interesting info on how often your Mac wakes up. I noticed, with WiFi enabled, that my Mac wakes up a LOT after midnight for unclear reasons. Disabling WiFi (I’m relying on wired ethernet anyway) calmed things down and my Mac actually sleeps when it is supposed to sleep. For the log I rely on the macOS API and event notifications.

      p.s. opening the log is done by opening “Preferences” and after that pressing CONTROL+OPTION+COMMAND  (CTRL+ALT+WINDOWS on a Windows keyboard) and the “debug” button should appear – clicking it will reveal the log.

      Reply

      hans

  • Jan 9, 2020 - 12:08 PM - Loek Comment Link

    Thanks for the suggestion about the log file.

    I have fixed ethernet and WIFI enabled (main reason was to have Airdrop enabled), but don’t see wake ups due to strange reasons. The iMac is in sleep mode when it’s supposed to be and only wakes up when I’m using it.

    Reply

    Loek

    • Jan 9, 2020 - 12:12 PM - hans - Author: Comment Link

      Hi Loek,

      My Mac Pro (2013) is maybe a little old by now (even though it runs great), maybe that’s why I get weird wake ups when WiFi is enabled 

      Reply

      hans

  • Jan 9, 2020 - 12:31 PM - JMV Comment Link

    Hi,

    In the overview section, list of supported protocols, you write *SMN*.

    Do you mean SMB ?

    ;-) best,

    Jean-Marc

    Reply

    JMV

    • Jan 10, 2020 - 5:01 AM - hans - Author: Comment Link

      Hi Jean-Marc!

      yeah … good catch! I did meant SMB … I’ve corrected the typo. 

      I had to laugh when I read that just now 

      Thanks for catching that and letting me know. It’s very much appreciated.

      Reply

      hans

  • Jan 15, 2020 - 9:59 PM - Pete Comment Link

    This software rocks! Thank you for making such a great software

    Reply

    Pete

    • Jan 16, 2020 - 5:16 AM - Hans - Author: Comment Link

      Thanks Pete!

      I very much appreciate that you took the time to past such a nice compliment!
      Definitely a motivator to keep doing this 

      Reply

      Hans

  • Jan 25, 2020 - 9:54 AM - James Comment Link

    It’s a great app ! 
    But I got some problems (I’m using 10.15.2) : 1. When I mount a SMB server successfully , the sub-menu will not appear , and the icons doesn’t change to activate mode ;2. I checked “Reveal on Mount” in the Preferences , but when I mount the SMB server successfully , nothing happened , Finder didn’t show up .
    In other comment , I saw you wrote this :Also, these are settings that should happen automatically:Check under  – “System Preferences” – “Security & Privacy” – “Privacy”:– Under “Files and Folders” check if “ConnectMeNow” is listed and has the option “Network Volumes” checked.– Under “Automation” check if these are checked: “System Events”, “Terminal” (possibly listed twice)
    But in my System Preferences , I only got “System Events” Under “Automation”, there are no “Terminal” Under “Automation” , and no “ConnectMeNow” Under “Files and Folders”, is this why I got the problem ? And why I didn’t get these settings ?

    Reply

    James

    • Jan 26, 2020 - 4:53 AM - Hans - Author: Comment Link

      Hi James,

      Thanks for the compliment and sorry to hear you’re running into issues … I hope the following can help:

      Short version:

      Try to execute this in Terminal:

      tccutil reset AppleEvents

      Long version (please read this first!):

      Both issues you seem to be running in, are related to the same internal function (detect a newly mounted or unmounted share).
      Both functions rely on macOS API reporting that a mount or unmount even occurred.

      A related function (if enabled in ConnectMeNow Preferences – Preferences & SSH Keys – ConnectMeNow Settings – check the option: Show Notifications) will show mount/unmount notifications – do you see any of these? It should give notifications when any share is mounted or unmounted – through ConnectMeNow, through Finder or manually (if you’d like you can test this).

      So the (missing) security settings could very well be related indeed – Apple made quite a mess with its “improved” security settings. 

      On that note: 

      1) When ConnectMeNow (or any other application for that matter) tries to access system events, or tries to execute an automation script, macOS will ask the user for permission – so you may have overlooked that when it was presented to you, or for some odd reason macOS didn’t ask. After macOS asks for this, the affected application (ConnectMeNow in this case) will be either whitelisted (you approved) or blacklisted (your did not approved/allow).

      2) Settings: Security – Automation (set automatically by macOS)
      3) Settings: Security – Files and Folders (set automatically by macOS)

      For both settings:
      There seems no way to manually add anything there. You can enable/disable listed items, but I’ve found that something is goofy there as well. When I tried to disable or remove ConnectMeNow, clicking the checkbox resulted in another app being disabled/enabled. So there seems to be a bug there with Catalina (10.15.2).

      4) Reset AppleEvents in Terminal:

      The following will most likely help: resetting the security settings for AppleEvents (macOS providing event info to applications that ask for it) – this did work for me and did ask me permission after starting ConnectMeNow again:

      tccutil reset AppleEvents

      Note that the this will reset all AppleEvents (for example mount/unmount events, but also others), so other applications may trigger macOS to ask for your permission again as well.

      I hope this helps – please confirm if it does 

      Reply

      Hans

      • Jan 26, 2020 - 7:36 AM - James Comment Link

        Thank you , Hans !

        I tried “tccutil reset AppleEvents” , and I approved ConnectMeNow to access System Events ( that is the only permission had been asked , my Mac didn’t ask permission for Files and Folders , is that all right ? ) .

        But the problem is still the same . By the way , I can see mount/unmount notifications , that works fine .

        Reply

        James

      • Jan 26, 2020 - 7:54 AM - Hans - Author: Comment Link

        Hmm, that is at least some improvement (the notification relies completely on the API call, and then triggers update of the icon and display of the submenu).
        Does the reveal after mount option still fail?

        Are you using PC names instead of IP-addresses? 
        Are you using the default mount method (in /Volumes/) or do you use “custom mount path” ?

        (I’m seriously just guessing now, since I have never encountered this issue)

        Reply

        Hans

      • Jan 26, 2020 - 8:01 AM - Hans - Author: Comment Link

        You can open the debug log, and see if you see anything weird there (granted: it may require a little more than average insight).

        You can enable the debug window by pressing the keys: CONTROL+OPTION+COMMAND (Windows keyboard: CTRL+ALT+WINDOWS).
        It will reveal the “Show Debug Log” button. While having the buttons pressed, click the button to open the log.

        When mounting a share, and this is just an example, you should see something like this:

        In this example:

        14:54:53 = mount attempt,
        14:54:54 = macOS reports a mount event,
        14.54.55 = ConnectMeNow tries to see if this is a known mount – if “In list” says “NO” then ConnectMeNow doesn’t recognize the created mount)

        14:54:48: Selected Share: Marvin MyShare (SMB)
        14:54:48: Updating Menu.
        14:54:53: Trying to mount 192.168.1.100/AllShares
              Mount path : default (/Volumes/)
          Mount response : All good
              Mounted at : /Volumes/MyShare
        14:54:54: Mount event - Volume Mounted /Volumes/MyShare
        14:54:54: Updating Menu.
        14:54:55: Mounted volumes: 
         -> Server : 192.168.1.100 (//yourusername@192.168.1.100/MyShare)
            Port : (default)
            Path : /MyShare
            User : yourusername
            Mountpoint : /Volumes/MyShare
            Mount Type : SMB (smbfs - 24)
            In list : Yes
        14:54:55: Updating Menu.
        14:54:55: Selected Share: Marvin MyShare (SMB)
        14:54:55: Updating Menu.

        (the bold items are some of the items that you’ll need to look at)

        Reply

        Hans

  • Jan 26, 2020 - 8:30 AM - James Comment Link

    The reveal after mount option still fail .

    I’m using IP-address .

    I’m using the default mount method now , but I tried “custom mount path” , still the same problem .

    My debug log seems fine :

    22:07:06: Trying to mount 192.168.1.204/86CC
          Mount path : default (/Volumes/)
      Mount response : All good
          Mounted at : 
    22:07:07: Mounted volumes: 
     -> Server : 192.168.1.204 (//GUEST:@192.168.1.204/86CC)
        Port : (default)
        Path : /86CC
        User : GUEST:
        Mountpoint : /Volumes/86CC
        Mount Type : SMB (smbfs - 2097176)
    22:07:07: Updating Menu.
    22:07:07: Selected Share: 86CC (192.168.1.204)
    22:07:07: Updating Menu.

    22:07:07: Mount event - Volume Mounted /Volumes/86CC
    22:07:07: Updating Menu.

    Reply

    James

    • Jan 26, 2020 - 9:38 AM - Simon Smith Comment Link

      ill just put my 2 pense work in here if i may

      i have a similar issue but its only related to the GUEST issue again that arose from the old version 2 and new version 3

      for some reason if i use a GUEST mount and try to mount, i get the successful notification and the drive appears on the desktop and in finder, and can browse files without any issues
      but finder never actually opens automatically
      BUT also if i then click the connectmenow app, the list of my drives doesnt show the mount as being mounted?
      so if you click it again to mount, i just get an error saying ‘ALREADY MOUNTED’

      HOWEVER again, none of the connectmenow funcs like ‘reveal in finder on mount’ or ‘unmount’ work for some strange reason?

      Reply

      Simon Smith

      • Jan 26, 2020 - 10:03 AM - James Comment Link

        Thanks Simon !

        It’s indeed the GUEST issue ! Problem solved !

        Everything works fine now , but I still doesn’t got “ConnectMeNow” Under “Files and Folders” setting , weird .

        Reply

        James

        • Jan 26, 2020 - 10:21 AM - Hans - Author: Comment Link

          As long as it works, I wouldn’t be too worries about it (everything work OK, right?).
          Since the first introduction of Catalina, the entire Security “features” has been very sketchy at best.
          But … Apple has been listening to bug reports, so hopefully, some time in the future it will display things correctly.

          Reply

          Hans

    • Jan 26, 2020 - 9:50 AM - Simon Smith Comment Link

      also tagging onto this my output is very similar

      in ‘in list’ doesnt appear for my share either?

      15:49:32: Trying to mount 10.0.0.15/Hestor_Office
      Mount path : default (/Volumes/)
      Mount response : All good
      Mounted at :

      15:49:33: Mounted volumes:

      -> Server : Win10._smb._tcp.local (//GUEST:@Win10._smb._tcp.local/%5BC%5D%20Win10)
      Port : (default)
      Path : /[C] Win10
      User : GUEST:
      Mountpoint : /Volumes/[C] Win10.hidden
      Mount Type : SMB (smbfs - 271581212)

      -> Server : 10.0.0.15 (//GUEST:@10.0.0.15/Hestor_Office)
      Port : (default)
      Path : /Hestor_Office
      User : GUEST:
      Mountpoint : /Volumes/Hestor_Office
      Mount Type : SMB (smbfs - 24)

      15:49:33: Updating Menu.

      15:49:33: Selected Share: Hestor_Office (10.0.0.15)

      15:49:33: Updating Menu.

      15:49:33: Mount event - Volume Mounted /Volumes/Hestor_Office

      15:49:33: Updating Menu.
      Reply

      Simon Smith

    • Jan 26, 2020 - 9:53 AM - Hans - Author: Comment Link

      Hi James and Simon (thanks for chiming in!):

      Simon: I think we’re onto something here!

      Seems the user “GUEST” may be causing the problem when I’m parsing the mount output.

      I assume you’ve entered the username to be “GUEST”, yet parsing the mount output (C-library) returns “GUEST:” and this user does not appear in the list ConnectMeNow maintains, since it is listed there as “GUEST” (without the semi-colon).

      Since a colon (under different circumstances) would be a bad character for a username anyway, I could tell CMN to strip that character from the username. CMN would then find the correct user name. The line “In List : Yes” is missing, so that would confirm this.

      This should be a quick fix – I’ll try to upload a patched version for testing to see if this resolves the issue (I have no shares here with guest access).

      Reply

      Hans

      • Jan 26, 2020 - 9:56 AM - Simon Smith Comment Link

        Hi Hans,

        glad we can help to fix this amazing program!

        for some reason for my mac to connect to our guest share
        I MUST enter the username ‘GUEST’, leave the password box BLANK and have the ‘login with credentials’ UNTICKED

        not sure why i need it to be unticked but i tried all sorts and the only way to get it working was have to have it unticked

        Reply

        Simon Smith

      • Jan 26, 2020 - 10:08 AM - James Comment Link

        Thanks Hans ! 

        Reply

        James

    • Jan 26, 2020 - 10:08 AM - Hans - Author: Comment Link

      I’ve just upload 3.0.2 – which hopefully resolves the “GUEST” issue.
      Please test it and please confirm if it does 

      Reply

      Hans

      • Jan 26, 2020 - 10:11 AM - Simon Smith Comment Link

        BINGO!

        THANK YOU HANS!

        Reply

        Simon Smith

      • Jan 26, 2020 - 10:16 AM - Hans - Author: Comment Link

        Awesome!!! 

        Reply

        Hans

      • Jan 27, 2020 - 4:47 AM - James Comment Link

        So quick !

        GUEST works fine now 

        Reply

        James

        • Jan 27, 2020 - 5:17 AM - Hans - Author: Comment Link

          Awesome!  

          Well, I was sitting behind my computer anyway and realized the wrong assumption I had made in the code – so it was a relatively easy fix (signing and notarizing the application actually took way more work haha). 

          Glad I could help!

          Reply

          Hans

  • Jan 28, 2020 - 4:15 PM - Christophe Comment Link

    Hi Hans,

    I love the new version of CMN, but I’m running into an annoying issue.

    When I have connected some SMB shares with CMN, and I lose network connection as a I move from one wireless access point to another, CMN just hangs. It doesn’t disconnect the shares, it just become unresponsive. When I force quit CMN, and try to restart it, I get an error message “The application “ConnectMeNow” is not open anymore.” and I can no longer start it until I reboot my laptop.

    Do you have any ideas as to what might be happening?

    Thx!

    Reply

    Christophe

    • Jan 29, 2020 - 3:38 AM - Hans - Author: Comment Link

      Hi Christophe,

      Sorry to hear you’re running into issues.

      I have not encountered this issue with my laptop, but maybe you could try something and hopefully we can see what may or may not be going on.

      1) Run your laptop as usual, with mounted shares, etc. – as you normally would.
      2) Open CMN – Preferences and open the debug window

      You enable the debug window by pressing the keys: CONTROL+OPTION+COMMAND (Windows keyboard: CTRL+ALT+WINDOWS).
      It will reveal the “Show Debug Log” button. While having the buttons pressed, click the button to open the log.

      3) Next do whatever you usually do where you lose your wifi connection and CMN hangs.

      It would be interesting to see what the log window is showing. It would also be helpful to know the settings you’ve used for the shares (including the Advanced settings).

      Since this potentially comes with a lot of data, please email me directly at: webmaster at tweaking4all dot com.

      Reply

      Hans

      • Mar 13, 2020 - 4:58 PM - Christophe Comment Link

        Hi Hans,

        I moved up to CMN 3.0.2 and I can no longer reproduce this issue :) I’ll keep monitoring, but it looks like all is now working as expected.

        Reply

        Christophe

      • Mar 14, 2020 - 4:59 AM - Hans - Author: Comment Link

        Thanks for the feedback Christophe! 

        Version 3.0.6 will come with a change that may affect this as well (introducing a helper tool).
        The current beta seems to work fine for most, but maybe wait until end of the weekend.
        I hope to have another beta available by then.

        Reply

        Hans

  • Feb 26, 2020 - 11:32 AM - Simon Smith Comment Link

    Hi,
    i have discovered a BUG
    if you use a SMB network share thats also a time machine backup, the app thinks its still mounted even tho you have ejected the network share

    1. i connect to my share fine from the app,
    2. laptop does a quick backup
    3. eject the mounted share (or disable wifi and then click the force eject option that appears)
    4. finder shows its vanished, but connectmenow still shows its mounted because timemachine has its stored in a hidden folder for when its next available to do a backup, in my case SimonLaptopBackup

    17:27:39: Mounted volumes: 
     -> Server     : 192.168.168.123 (//simon@192.168.168.123/SimonLaptopBackup)
        Port       : (default)
        Path       : /SimonLaptopBackup
        User       : simon
        Mountpoint : /Volumes/.timemachine/192.168.168.123/D9A58D03-9624-47DB-8229-5854D83E5AF5/SimonLaptopBac
        Mount Type : SMB (smbfs - 1048576)
        In list    : Yes
     -> Server     : 10.0.0.15 (//User@10.0.0.15/Hestor_Office)
        Port       : (default)
        Path       : /Hestor_Office
        User       : User
        Mountpoint : /Volumes/Hestor_Office
        Mount Type : SMB (smbfs - 24)
        In list    : Yes
    Reply

    Simon Smith

    • Feb 28, 2020 - 4:20 AM - Hans - Author: Comment Link

      Hi Simon!

      Nice catch!  (apologies for the late response)

      I haven’t found a golden rule (yet) to catch TimeMachine mounts, but having a hidden mount is something I could try to catch.

      Since I cannot replicate the issue here:
      After the mount “disappeared”, could you run the mount statement in Terminal and see if it is still listed there? 

      The data listed is the actual output of the mount statement, so theoretically the mount is still connected.
      Maybe Finder ignores it because it is a “special” mount (hidden)?

      I’ll try to do some testing next week to see if I can replicate this – but I’ll have to setup TimeMachine on my NAS first .

      Reply

      Hans

      • Feb 28, 2020 - 5:10 AM - Simon Smith Comment Link

        mount command output BEFORE i disconnect from share

        Simon@SiMacBookPro ~ % mount
        /dev/disk1s5 on / (apfs, local, read-only, journaled)
        devfs on /dev (devfs, local, nobrowse)
        /dev/disk1s1 on /System/Volumes/Data (apfs, local, journaled, nobrowse)
        /dev/disk1s4 on /private/var/vm (apfs, local, journaled, nobrowse)
        map auto_home on /System/Volumes/Data/home (autofs, automounted, nobrowse)
        //simon@192.168.168.123/SimonLaptopBackup on /Volumes/.timemachine/192.168.168.123/72EB2BAB-CC55-44E2-966A-E0429769EC42/SimonLaptopBackup (smbfs, nobrowse)
        /dev/disk2s2 on /Volumes/Time Machine Backups (hfs, local, nodev, nosuid, journaled, nobrowse)
        //simon@192.168.168.123/SimonLaptopBackup on /Volumes/SimonLaptopBackup (smbfs, nodev, nosuid, mounted by Simon)

        mount command output AFTER i disconnected from the SMB share and then is not visible in /volumes or in finder

        Simon@SiMacBookPro ~ % mount
        /dev/disk1s5 on / (apfs, local, read-only, journaled)
        devfs on /dev (devfs, local, nobrowse)
        /dev/disk1s1 on /System/Volumes/Data (apfs, local, journaled, nobrowse)
        /dev/disk1s4 on /private/var/vm (apfs, local, journaled, nobrowse)
        map auto_home on /System/Volumes/Data/home (autofs, automounted, nobrowse)
        //simon@192.168.168.123/SimonLaptopBackup on /Volumes/.timemachine/192.168.168.123/72EB2BAB-CC55-44E2-966A-E0429769EC42/SimonLaptopBackup (smbfs, nobrowse)
        /dev/disk2s2 on /Volumes/Time Machine Backups (hfs, local, nodev, nosuid, journaled, nobrowse)

        maybe you can just ignore anything listed in /Volumes/.timemachine ?

        Reply

        Simon Smith

        • Feb 29, 2020 - 6:05 AM - Hans - Author: Comment Link

          Hi Simon,

          It is indeed interesting to see these two before the unmount:

          //simon@192.168.168.123/SimonLaptopBackup on /Volumes/.timemachine
          //simon@192.168.168.123/SimonLaptopBackup on /Volumes/SimonLaptopBackup

          And then still see this one after the unmount:

          //simon@192.168.168.123/SimonLaptopBackup on /Volumes/.timemachine

          I  noticed something similar on mysetup. The path to my regular mount is identical to the one “mount” shows for the TimeMachine mount (even though on the server, these are 2 very different paths).

          For now I’ll consider including “/Volumes/.timemachine” in the next ConnectMeNow version, but I did notice that this path is not uniquely used by the different TimeMachine / macOS versions. 

          Another observation: the tmutil command (Terminal) should show the proper TimeMachine mount path … but it doesn’t.
          And after I disabling TimeMachine, it still keeps giving me the wrong path.

          tmutil destinationinfo

          I’ll try to incorporate this exception as soon as possible. Thanks for catching this! 

          Reply

          Hans

        • Feb 29, 2020 - 6:32 AM - Hans - Author: Comment Link

          Hi Simon,

          I just release 3.0.3 which should fix the TimeMachine issue.
          Please confirm. 

          Reply

          Hans

          • Feb 29, 2020 - 2:18 PM - Simon Smith Comment Link

            Hi,
            BINGO, seems to work perfectly now and
            its not confused over weather its still attached or not :)
            KEEP UP AMAZING WORK 
            Simon

            Simon Smith

          • Mar 1, 2020 - 4:03 AM - Hans - Author: Comment Link

            Awesome! 

            Thanks for the compliment and for the confirmation! 

            Hans

  • Mar 1, 2020 - 5:53 AM - Troy Comment Link

    Hi there, Hans!

    Quick question: Does the automount function have the ability to automatically re-mount an SMB server that had been offline after a period of time?

    In other words, say I’ve got an SMB server that I took offline for a few hours for maintenance. When I bring the server back online, will ConnectMeNow notice that the server is back online and re-mount it?

    Thanks again for the awesome work on this software!

    Reply

    Troy

    • Mar 1, 2020 - 9:23 AM - Hans - Author: Comment Link

      Hi Troy,

      Good question haha – I didn’t design ConnectMeNow that way, so I doubt it will do what you’re looking for.  

      I have looked into this though, they idea being:
      Automatically mount your favorite server when it becomes available in the network.

      Unfortunately, there is no mechanism to detect that a server comes online again.
      Well, with the exception of polling (for example) the Arp tables, which is not impossible, but also not 100% reliable.

      If you’d like to can test this by doing an

      arp -a

      which should list the “known” devices in the network (for your computer).
      You will notice that even a device that has been disconnected may or may not still be listed.
      And: a device that gets connected may or may not be listed promptly.

      As far as I could find anything on this, the data will stay in the Arp cache for 4 hours (according to Cisco info I found), making the data unreliable to detect if a network device disappeared or not.

      One could of course keep flushing the arp tables with:

      sudo arp -a -d

      And while testing this with a device, I noticed it picking up the device pretty quick when it comes online again.
      But flushing the arp tables every few seconds seems like a really bad idea, not to mention that it requires sudo access.

      The alternative would be pinging the server over and over again, until a ping is successful. 
      This is not a good idea either (IMO), since it will generate quite a bit of network traffic as well.

      So for now I do not have a good solution for this.
      I’m open to suggestions though 

      Reply

      Hans

      • Mar 1, 2020 - 9:39 AM - Simon Smith Comment Link

        Hi Hans,
        how does the ‘ping server before doing a mount attempt’ work?
        does that use arp or ping?

        could you not tag something off that?

        like send a ping every x seconds (set an option per share instead of globally to avoid pinging everything)
        then once you notice its gone offline, start monitoring til it comes back online
        then do a unmount and mount command but show an alert saying its was offline and then back online

        Reply

        Simon Smith

        • Mar 11, 2020 - 7:22 AM - Hans - Author: Comment Link

          Alrighty then … 3.0.6 may answer this question 

          Major change:
          I’ve created a helper tool, which (if needed) checks the SSH status and if a server is appearing in the network (if the new “AutoMount on Appear” option was set for this share).

          Some minor changes:
          Fixed a few typos, improved the Preferences screen a little, added (on the Basic Settings tab) an indicator which of the advanced options where enabled. Oh and the option to enter a home path (eg. ~/MountPoints) so a config can work for multiple users and the mountpath will be in their home directory.

          The helper will take some of the load of CMN, so the GUI will not be affected as much as before.

          AutoMount on Appear works like this:

          If checked for a share, the server of the share will be added to the checklist for the helper tool.
          If the helper tool sees it being online, CMN will try to mount the share.

          Since all servers need a little time to become available, it will be retrying to mount 10 times (until it succeeds or fails after 10 times).
          If the setting for “SSH and Server status check” is set to every 5 seconds, then this effectively means that CMN will try to remount for about a minute. Hopefully this is enough haha (did some testing with my 1st generation Raspberry Pi running LibreElec – and it worked very well).

          Now … AutoMount on Appear proved more of a challenge than I had hoped for.
          To avoid automounting to kick in right away after manually unmounting that share, I’ve added an override “stop” to it.
          This means that when you unmount your share in CMN (versus disappearing since the server went down), it will temporarily be flagged to ignore the “AutoMount on Appear” option, until you either mount the share again in CMN, or your Mac wakes up from sleeping, or you restart CMN.

          It’s definitely a beta … but give it a try 

          You can download the beta here.

          Reply

          Hans

          • Mar 12, 2020 - 1:43 AM - Troy Comment Link

            Upon first run of the program, I got the following error:

            “Access violation. Press OK to ignore and risk data corruption. Press Abort to kill the program.”

            System hardware is a 3Ghz Mac Mini 2014 running macOS Mojave 10.14.6 (18G3020). Also, it’s a machine that was running CMN for the very first time, in case that matters.

            Upon a second run of the program, it loaded happily. Is there any info I can give you to help debug?

            Troy

          • Mar 12, 2020 - 5:51 AM - Hans - Author: Comment Link

            Assuming you’re talking about the beta posted in the comment above (3.0.6); this new version uses a helper tool. Maybe that triggers the Access Violation.

            As for debug info, you’ll have 2 options:

            1) In CMN:

            Open the Preferences window, press and keep pressed CTRL+ALT+COMMAND, click the “Show debug log” button.
            However, this only works when CMN actually runs, and since the second run worked, I would assume you will not be seeing anything helpful. Unless it states something that it could not run the Helper Tool.

            2) In Console:

            Open Application -> Utilities -> Console. Set the the filter to “ConnectMeNow” (without the quotes).
            Ignore the font messages, this seems a bug in either macOS or in the development tool I’m using.

            Note:
            Posting debug logs here is not a good idea. Please use either the forum or email me directory (webmaster at tweaking4all dot com).

            Hans

          • Mar 12, 2020 - 7:32 AM - Hans - Author: Comment Link

            I was able to reproduce the error … not sure what it is causing though, but at least I can do some testing.

            I’ll at least be able to test.
            Thanks for reporting!

            Hans

          • Mar 12, 2020 - 12:20 PM - Hans - Author: Comment Link

            OK found the issue …. I hope.
            On some Mac’s the communication port between Application and Helper takes a little to initially get setup.
            I hope to have this fixed, so I uploaded a new build of the 3.0.6 beta (previous link works).

            Hans

          • Mar 13, 2020 - 1:30 AM - Troy Comment Link

            I’m about to give the new “Auto Mount when server appears” feature a try. However, I noticed that it says “there is a hard set limit to the amounts of times a mount will be attempted.”

            Would it be possible for there to be an option to specify how many attempts are made, and at what interval? Also, could it be possible for there to be an option for it to indeed attempt endlessly? Because honestly, that’s kind of what I need. If the server is offline, I need it to keep attempting forever until either the server re-appears, or I tell it to stop.

            The purpose of this is so that my headless Mac server will automatically re-connect to an SMB share on our internal intranet. I’m trying to minimize the need to remote into the Mac server to re-connect shares after maintenance on those shares.

            On a different topic, here’s a few quick nitpicks for the sake of polish:

            1 – When you click the “Advanced Options” zone at the bottom of the “Share Definitions” page, the button at the upper-right corner doesn’t change with the page. It still says “Go to Advanced Share Settings” when it should say “Back to Basic Share Settings”.
            2 – Maybe re-locate the “Go to Advanced Share Settings” button to the bottom of the “Share Definitions” page since you’ve got all the Advanced Options indicators down there anyway? Believe it or not, I obliviously didn’t even notice that upper-right button was even there, even though it was staring me in the face. I had been clicking the strikethroughed options at the bottom to get me to the Advanced Options page.
            3 – In the “Advanced Options” page, you have inconsistent word usage (“Auto Mount” and “AutoMount”)
            4 – What’s the difference between “Ping before mount” on the Advanced Options page versus the “Ping Server before doing a Mount attempt” on the Preferences & SSH Keys page?

            Troy

          • Mar 13, 2020 - 6:32 AM - Hans - Author: Comment Link

            Hi Troy,

            I think adding the option to set AutoMount attempts and interval is a good idea.
            I’ll add it right away after posting this reply.

            Advanced Settings button: excellent catch! I had not noticed this yet.  
            Right away fixed it (was an easy fix)!

            Button location: Yeah, I have been bothered by it myself, but haven’t found a good location yet.
            At the bottom it would either interfere with the warning messages or it would take too much space.
            Just by looking at it, I’ve moved it above the list of defined shares.
            It’s not perfect either, but at least it is easier to spot and things look a little cleaner.

            I’ve correct the “Auto Mount” inconsistency – thanks for catching that. 
            Let me know if there are more.

            The difference between “Ping before mount” on the Advanced Options page and “Ping Server before doing a Mount attempt” on the Preferences & SSH Keys page is this:

            The one on Advanced Options page affects the share you’re editing.
            The one on the Preferences & SSH Keys page is intended as the default value for when you create a new share.
            So when it is checked there, and you create a new share, the new share will have this option automatically checked.

            Maybe I should change the verbage there a little to make it more obvious … 

            Hans

          • Mar 13, 2020 - 3:41 PM - Troy Comment Link

            I think I may have found one more issue…?

            In the “Share Definitions” tab, if I click “Copy a Share as a base for a new share”, it does indeed make that copy, but any changes I make to that copy seem to also affect the original as well.

            Troy

          • Mar 14, 2020 - 4:57 AM - Hans - Author: Comment Link

            That does sound like an issue – I’ll add it to my checklist! Thanks for reporting! 

            On that note: I’ve implemented the request to set the number of retries for Auto Mount.
            The Interval can be changed by setting the Status Check polling frequency.
            Having 2 timers mixed would be an option, but it would als conflict potentially.

            Additionally, I’ve added and indicator in the list of shares, so we can see right away if a share is mounted or not.

            And I found 2 small bugs that I have resolved again.

            I hope to be able to release a new version by the end of the weekend (today will be quite busy, so I already know I won’t get to it).

            Hans

      • Mar 1, 2020 - 3:45 PM - Hans - Author: Comment Link

        Hey Simon,

        ping server before doing a mount attempt” just sends a ping to your server before it starts mounting a volume. This way the server gets some time to wake up (not the same as Wake On LAN). For example: my QNAP goes to a low power mode when not used for a while (disks spin down). The initial ping wakes the NAS up, which gives it a better chance that a mount succeeds.

        Pinging every x seconds is an option of course, but it will come with some tiny freezes for the application.
        Another potential issue is that some server configuration do not allow pings and will not respond even when they are online.

        An alternative I’m currently experimenting with is “nmap” which can do a port scan for a very specific port.
        I’ll have to see if this can be a better solution.

        On that note; in settings you’ll see “SSH Status Check every X seconds”.
        I could piggy back along with that and add an option to do a ping or nmap check (only for the servers that have this “auto recover” option enabled of course). Ideally I’d also only want to do this for the network in which the device is to be expected (for example for laptop users).

        I’ll keep trying and will see what I can come up with. 😊 

        Reply

        Hans

    • Mar 1, 2020 - 9:24 AM - Hans - Author: Comment Link

      p.s. thanks for the compliment – it is very much appreciated 

      Reply

      Hans

  • Mar 6, 2020 - 4:57 AM - Bob Comment Link

    Hi, I think I found a bug in CMN v3.0.3

    When setting the preferences for mount share type (under the tab Preferences & SSh Key) to AFP as default and you go back to create a new AFP share you get an FTP under mount type.

    And setting the preferences for mount share type (under the tab Preferences & SSh Key) to FTP as default and you go back to create a new FTP share you get an AFP under mount type.

    Reply

    Bob

    • Mar 6, 2020 - 5:00 AM - Simon Smith Comment Link

      Hello,
      i can confirm this bug
      i get the same thing here
      im sure Hans will have a look at it when he gets chance

      Reply

      Simon Smith

    • Mar 6, 2020 - 5:11 AM - Hans - Author: Comment Link

      Yep, that would be a problem haha … I’ll look at it asap.

      Thanks for the good description for reproducing the issue. 

      Reply

      Hans

    • Mar 6, 2020 - 7:50 AM - Hans - Author: Comment Link

      OK, I’ve fixed that one as well, and fixed another one I found.

      When a NFS is being mounted, it was looking for the username to identify the mount.
      Since there is no username, it wouldn’t detect it properly. Fixed that as well.

      I’ve uploaded 3.0.4.

      Reply

      Hans

  • Mar 6, 2020 - 7:52 AM - Hans - Author: Comment Link

    UPDATE:

    I’ve made version 3.0.4 available today.

    This version addresses a few NFS related issues, and one bug in the Preferences (concerning the default mount type).

    Reply

    Hans

    • Mar 6, 2020 - 8:12 AM - Simon Smith Comment Link

      OH NO was this rushed?
      its completely missing the app icon in the DMG and even the APP itself is missing…
      other than that, can confirm all works now and bugs fixed!

      Reply

      Simon Smith

    • Mar 6, 2020 - 8:15 AM - Simon Smith Comment Link

      also its now stuck an running icon in my menu bar when you first open it and wont disappear to menu bar like it use too

      Reply

      Simon Smith

    • Mar 6, 2020 - 8:30 AM - Hans - Author: Comment Link

      Hmm, good catch … probably an issue with another tool I’m working on (Apple has made a real pain to sign and notarize – so I had to create a tool for that, which I’m still working on as well).

      Reply

      Hans

      • Mar 6, 2020 - 8:37 AM - Hans - Author: Comment Link

        Found the issue – my new tool screwed up the Info.plist … 

        Reply

        Hans

      • Mar 6, 2020 - 8:58 AM - Hans - Author: Comment Link

        Fixed my new tool and re-uploaded 3.0.4 … please try again.

        (thx for catching that!)

        Reply

        Hans

        • Mar 6, 2020 - 9:00 AM - Hans - Author: Comment Link

          p.s. I did install it just now on my own system through the new DMG, and it starts OK now.
          If not: make sure your browser (or if you use one: your proxy) is downloading the correct file, if needed use this alternative link).

          Reply

          Hans

          • Mar 6, 2020 - 9:12 AM - Simon Smith Comment Link

            brill, icon fixed

            could you possible add an option in preference to allow dock or menu or both?

            as it seems the app is now stuck in the dock bar, always there and im sure it always use to be hidden and only shown in the menu bar by clock?

            Simon Smith

          • Mar 6, 2020 - 9:36 AM - Hans - Author: Comment Link

            I haven’t explored the dock on/off option yet.
            Right now it is handled by the Info.plist of the application – something I cannot control after the application started.
            I feel your pain though …

            A way to get it out of the menubar:

            1. Close the “good” ConnectmeNow.

            2. In Terminal:

            ps -x | grep ConnectMeNow

            which should give you something like this:

            98935 ??         0:07.77 /Applications/ConnectMeNow.app/Contents/MacOS/ConnectMeNow
             4750 ttys000 0:00.00 grep ConnectMeNow

            The first line is the one we need, and the first number on that line is the task you’d like to kill like so (different number on your system of course):

            kill -9 98935

            Hope this helps. 

            Hans

          • Mar 6, 2020 - 9:39 AM - Hans - Author: Comment Link

            I guess it’s been a long day haha … now I see that there is another booboo in the Info.plist.
            The icon should not be in the dock.

            Hans

          • Mar 6, 2020 - 9:41 AM - Simon Smith Comment Link

            that didn’t work either as that just completely kills the app all together and it vanishes both from dock and menu bar

            I’m not sure what’s changed in the compiler you have made but it was prefectly fine in 3.0.3, it was only visible in the menu bar

            Simon Smith

          • Mar 6, 2020 - 9:54 AM - Hans - Author: Comment Link

            I just gave it a new version number, 3 files with the same number can become confusing …

            I hope I didn’t make more mistakes … give it a shot: link
            (the link in the article is updated as well)

            Hans

          • Mar 6, 2020 - 9:57 AM - Simon Smith Comment Link

            BINGO! 3.0.5 perfect!

            when im paid next, im going to donate aswell as you do such an amazing job!

            keep up the amazing work!

            always here to help you with bugs/issues :)

            Simon Smith

          • Mar 6, 2020 - 9:57 AM - Hans - Author: Comment Link

            Sorry, had not read your reply yet …

            It’s actually my own tool that screwed it up.

            Since maintaining plists, signing, notarizing etc takes so much manual labor, I created a tool to do all this for me.
            Just happens to be that in the past few days I made some modifications, which results in some unexpected side effects.

            Let me know if 3.0.5 works better … I have to run an errand (about an hour ago haha)

            Hans

          • Mar 6, 2020 - 9:58 AM - Hans - Author: Comment Link

            Cross post haha …

            Glad it works, phew … Thanks for helping out! 

            Hans

  • Mar 6, 2020 - 8:27 AM - Luca Comment Link

    Hi Hans!

    I have recently bought a NAS and I have come across your very nice application, that is running fine under an old Sierra development (need to buy a new Mac this year).

    I have three issues that I would like to share with you.

    1) [Minor] I have two users on my Mac (me and my wife) and I have the Pictures folder set to rw for me and to ro for her, so that she won’t mess around too much. I have created a /mount folder, owner is me and group is me and my wife, with chmod ug+rw. Actually this is working, I can write in that folder and my wife can write as well. However, CMN3 won’t install her share in /mount if run from her account. I have solved it by creating a different mountpoint,  /mountjenny, with my wife as the owner, and everything works. Isn’t it possible to have the same mount folder for both users?

    2) [Minor] I have one folder in my NAS called Pictures and I have named it as Pictures in the list of servers. I would expect to see /mount/Pictures and instead I see /mount/Pictures (192.168.1.120) which is still OK but a little bit more complicated to manage (with the spaces, and parenthesis and so on). I am symlinking folders on my Mac and I just wanted to avoid this strange naming convention. Unofrtunately I haven’t found a way to change this. Is it possible or am I doing something wrong?

    3) [Major?] I have an UPS and yesterday I did some shutdown tests (in case of a poweroff). Once the NAS was completely down, I issued the mount command and I saw all my shares were still listed as mounted, but when I did an ls /mount, Terminal got stuck (couldn’t even press ^C). I didn’t play with Finder, just switched the NAS on again and after everything came online again, Terminal answered with the list of my two folders.

    I have read somewhere that you should add the nofail command to avoid this issue and that you may not even be able to boot if the share is down. Do you know if there is a way to improve this behaviour? I feel everything would hang if I click on something and the NAS is down for any reasons.

    Thank you very much for your very nice work and sorry for this long message, hope to hear from you soon.

    Reply

    Luca

    • Mar 6, 2020 - 9:32 AM - Hans - Author: Comment Link

      Hi Luca,

      Great to hear CMN work on Sierra – I have not tested that 

      1) I assume you have a photos share on your NAS, and both you and your wife work on the same Mac, and login individually. 

      I also assume that /Mount is on your Mac – just checking, since macOS these days uses the /Volumes/ directory for mounting disks and shares, and with newer macOS version you will have problems even creating /mount since the filesystem won’t allow you to do that.

      Either way, I’m a little confused trying to figure out what may be going wrong .. what version of CMN are you using?
      The most current version (3.0.4) would not mount again “/mount” but rather create a subdirectory in “/mount” to mount against.
      So this could be some sorts of access rights issue. Hence my confusion 

      2) The directory names are intentionally like that. The idea being, that a share named “Pictures” may exist on other network devices as well, and at that point it becomes harder to read what directory goes to what server (I actually have 2 NAS devices, with exactly that situation).

      At the moment, there is no way to change that in CMN. I used to be an option, but it confused the heck out of users. So I removed it.
      I’ll keep it on my “to explore” list, maybe something for in the future.

      3) I would assume that this is a macSO issues.

      Somehow (again; don’t know what CMN version you’re using) macOS did not give up yet on the network connection to your [shutdown] NAS.
      Therefore it will not report the share as unmounted to CMN either.
      The fact that “ls /mount” got stuck and resumed again once the NAS got online again, kind-a confirms that macOS had not given up on the connection yet.
      (probably a reason why certain network functions changed in newer macOS versions)

      Reply

      Hans

      • Mar 6, 2020 - 12:09 PM - Luca Comment Link

        Thanks Hans for your super-quick answer!

        1) All your assumptions are all correct. I did not want to mount everything under /Users/username/mountpoint because I backup the Users folder to the NAS so I fear that I would try to backup my NAS onto my NAS once I reach the mountpoint folder. I have symlinks wjose content is not copied (they are copied as symlinks) but that folder is not seen as a symlink. Hence I tried to use something outside of the /Users folder. Sierra allows you to sudo mkdir /mount and then I changed the ownerships. And yes, you are right, the shares are mounted under /mount, so if I do an ls -l I will see /mount/Pictures (192.168.1.120) and /mount/iMac (192.168.1.120) which is the other share I use. I am using the very last version because I have installed your program yesterday evening for the first time. As for the access rights, I logged into my wife account and I could do something like >/mount/test , so she has write permissions in the folder that I have created. I believe CMN would have the same permissions of my wife.

        2) OK Clear, maybe the spaces and the parenthesis confuse me; somethink like Pictures_192.168.1.120 could be easier (also for scripting purposes) but OK, no problems

        3) OK, so if the shares are not available anymore, then this issue should not appear? I will shutdown my NAS again, wait a while and see what happens, reboot the mac with the NAS down and see what happens, switch on the NAS and see what happens. I will report my output to you.

        Thank you very much!

        Reply

        Luca

      • Mar 7, 2020 - 4:28 AM - Hans - Author: Comment Link

        Hi Luca,

        As far as I remember, TimeMachine (assuming you’re using that to make backups) has the option to exclude certain items. For example excluding ~/MountPoints. I highly recommend that approach since newer macOS versions will not allow you to make a directory in the root directory, not even when using sudo. Note: to create a directory in root, for example under Cataline, you’d need to disable SIP, which I really cannot recommend as it affects the security of your Mac.

        If you’re working on the same Mac and you’d like to use a shared directory, then I’d use a directory in /Users/Shared or in the Public folder (see Apple Support). MacOS is familiar with this way of working, so I’d carefully assume this would be the most compatible way of working.

        Since I don’t like people answering my questions by not answering the question, and pushing me in another direction, I’ll try to continue with your /mount idea.

        One issue I can see here is that if CMN sees that a directory is already there, it may try to create a new directory name to avoid conflict – effectively breaking your scripts …  not something we’d want either.

        As far as spaces etc, you can always type a path with double quotes around them in Terminal.
        For example:

        ln -s "/mount/iMac (192.168.1.120)" "/Some complex path/to/some complex path/dir name with space"

        I pretty much always use this in my applications, since I have two options: either double quote or escape special characters (eg. instead of space type \space).

        The current naming is done with readability by humans in mind, so it looks more elegant.

        As for permissions; yes CMN would have the same permissions as the user (you or your wife).

        I’m adding the following option to consider to my To-Do list: name directories “Sharename (server)” or “Sharename_server“.
        I’ll try to implement this in the future, but for now I’m buried under a few other projects. 

        Reply

        Hans

        • Mar 9, 2020 - 11:09 AM - Luca Comment Link

          Thanks Hans for all your suggestions.

          I am indeed using TimeMachine to backup everything and actually I forgot to exclude the /mount folder, so thanks!

          I am also using another software and I will look into it to see if I actually can exclude that folder. After that, I will move from /mount to ~/mount, as I will soon buy a new Mac and will immediately face Catalina issues :-)

          I still didn’t find the time to do all the tests I promised to do, but as soon as I am done with them I will post the results.

          I can live with your idea of leaving the IP between brackets, so for the time being I am fine, thanks anyway for your proposal.

          Thanks again

          Reply

          Luca

        • Mar 10, 2020 - 5:05 AM - Hans - Author: Comment Link

          You’re most welcome.

          I’ve just added the option to enter a path in the user directory, and keep the tilde “~” in it.
          So for other users it will use their home directory as well.
          Since it is only a mount, this should work fine.
          For the login credentials, you’re probably better off each using your own – under the assumption that you have set the access rights correctly on your NAS of course.

          I’d assume that good backup software would skip mounted disks/shares anyway, otherwise it would result in huge backups (looking at my own NAS now haha).

          Reply

          Hans

  • Mar 13, 2020 - 9:54 AM - Chris Comment Link

    Backup / Export Settings 

    Restore / Import Settings failing!

    Please try yourself. I wanted to export settings, after I have started my Mac OS up and opened the Menu of ConnectMeNow (some connections in the list were empty, just “undefinied???”)

    Please repair it.

    Reply

    Chris

    • Mar 13, 2020 - 10:00 AM - Hans - Author: Comment Link

      Hi Chris,

      I actually used this function a few times this week, without any issue (while testing v3.0.6).

      What version of CMN are you using?
      Can you give more info on steps on how to reproduce?
      Did you make a backup before and were trying to restore it?
      If so: do you still have the backup file?
      Or were you trying to just make a backup?

      Reply

      Hans

      • Mar 13, 2020 - 10:08 AM - Chris Comment Link

        Thanks for your rapid reply!!!
        I have 3.0.5, but same problem was with 3.0.3.
        MacBook Pro with Catalina 

        Steps:
        Today I looked in Finder, there were only 2 Volumes readable and with symbols, other were empty and no symbols.
        So i looked in ConnectMeNow 3.0.3. There I saw it: 2 Volumes alright. The other Volumes were “(undefinied???)”. When I clicked on them, there were no fields, no check, nothing. Just empty.

        So I downloaded 3.0.5. I put 2 Volumes in. Backup, Restored, there were no entries. Yes, I still have the files. When I looked inside, there were all entries I made. But then I tried one or two new entries or changed them. Backup again, opened it with an editor. There were no changes in them.

        Reply

        Chris

      • Mar 13, 2020 - 7:17 PM - Chris Comment Link

        I found your beta (3.0.6) as in link above.

        I tested 3 Menus and 3 entries, backed up. Then I deleted 2 entries, restored from Backup. What happened? Every entry is gone. I looked in the backup file. There is really no entry.

        Reply

        Chris

      • Mar 13, 2020 - 7:29 PM - Chris Comment Link

        When connecting to webdav, I have problems. There is the Mac OS circle rolling and rolling, and ConnectMeNow is freezing.

        Reply

        Chris

      • Mar 14, 2020 - 4:51 AM - Hans - Author: Comment Link

        Hi Chris,

        apologies for the late reply 
        Of course you’re free to test 3.0.6, and I see you already found the link 

        You’re most certainly running into an interesting issue, which I cannot seem to reproduce (testing in Catalina 10.15.3 and in Mojave).
        Where do you see “(undefinied???)” ? This text is nowhere to be found in my code – so I wonder where you’re seeing this.
        Where did you install CMN? And where is your config file stored?
        (during my testing I use the default location and a config in my DropBox folder)

        The interesting part is that the code for backup/restore hasn’t changed at all in any of the v3.x CMN versions.
        I’d really like to get to the bottom of this, after all: it may not only affect you … 

        One thing to try: after restoring a backup: close down CMN right away and restart it.
        (just for testing purposes, this is not the way we fix this)

        As for the beachball when using WebDAV;
        The beachball is typically triggered by the OS (especially with 3.0.6). Do you get the beachball when doing a manual mount (eg. from Terminal)?

        Reply

        Hans

      • Mar 15, 2020 - 11:09 AM - Hans - Author: Comment Link

        I may have found a fix for the backup/restore issue.
        It seemed related to the fact that users can choose their own location for preferences, and that seemed to have a bug in it.
        I’ll include the fix with the next beta (may take a day or so).

        Reply

        Hans

    • Mar 15, 2020 - 7:06 AM - Hans - Author: Comment Link

      I finally found where you may have seen “undefined” … I was looking for “undefinied??”, but I was supposed to be looking for “?? [undefined]”.
      My bad – sorry!

      This implies that it could not determine the share type from the settings (in “NetworkShares.ini”).
      If you’re still experiencing this: would you be able to send me that file by email (webmaster at tweaking4all dot com) ?

      Reply

      Hans

      • Mar 15, 2020 - 10:42 AM - Hans - Author: Comment Link

        OK, I found where things may go wrong with the backup/restore of settings.
        I’ll try to find an elegant solution to resolve this.

        Reply

        Hans

        • Mar 17, 2020 - 2:00 PM - Chris Comment Link

          Sorry for my late reply too.
          Oh ok… before I write a lot again, i will test your new build as soon as possible :-)

          Reply

          Chris

  • Mar 13, 2020 - 7:48 PM - Chris Comment Link

    I found out, that the problems occur, when I put ConnectMeNow in my personal applications directory.

    Reply

    Chris

    • Mar 14, 2020 - 4:54 AM - Hans - Author: Comment Link

      Hmm, that is an interesting find.

      CMN uses the “/Users/<username>/Library/Application Support/ConnectMeNow” path to store its settings by default.
      If you define an custom path, it will use that one too (so you can share the config amongst several machines).

      I’ll take note of it and will check and see if there is any reason why this would go sideway.
      During testing I often start the application from the development directory (which is actually a directory in Dropbox haha).

      Reply

      Hans

  • Mar 16, 2020 - 7:03 AM - Hans - Author: Comment Link

    BETA UPDATE:

    I’ve just uploaded a new build of the beta v3.0.6 (build 134).

    A few bugs have been resolved, some minor cosmetic bugs, and hopefully resolved a bug with backup/restore of settings.

    Some additional changes:

    – In the preferences window, in the shares list, there now will be an indicator right away showing if a share is active/mounted or not.
    – When preferences are saved, the “old” preferences will be saved as a “.bak” file in the same location.
    – Indicator in the Preferences window when a status check is being done (if enabled).
    – Moved the button to go to Advanced Settings to the bottom.
    – Moved the button to go back to Basic Settings to the bottom as well (same location as going to Advanced Settings).
    – AutoMount when a server appears in the network: you can now set the number of retries when trying to mount a server that appeared (applies to all servers).
    – Server Path selection: Only show a dropdown box if a specific share type supports this (NFS and SMB).
    – Advanced Settings indicators are now clickable, and open the advanced settings highlighting the involved option.
    – Bug fix: enable/disabled toggle button bug fixed.

    Reply

    Hans

    • Mar 17, 2020 - 2:06 PM - Chris Comment Link

      I couldn’t wait and I just downloaded and tried your new build 134. It’s working like a charm now!!! GREAT WORK!!!
      WebDAV is also working fine now! Awesome, Hans!!!

      Anyway, if you want, I can deliver you a German version for ConnectMeNow?

      Reply

      Chris

    • Mar 18, 2020 - 5:06 AM - Hans - Author: Comment Link

      Hi Chris!

      Good to hear things work better now. 

      Note: I haven’t changed anything related to WebDAV, and even though I’m glad to hear it works well right now, I’d keep an eye on it.

      As for a German version … well, I’ve been looking in supporting multiple languages and my main concern with that is maintaining the translations.
      I’ve dealt with a few projects (not of my own) and keeping the translations up to date is a real pain. 
      So for now, I’d rather have a correct English version than a version in a different language with translation issues.

      I do appreciate the offer though – thank you! 

      Reply

      Hans

    • Mar 18, 2020 - 5:22 AM - Luca Comment Link

      Hi,

      Should I want to update, do I have to backup my settings before doing so or can I just install the new version and that’s it?

      Yesterday I saw a strange issue: I woke up the Mac from sleep and some folders in the NAS could not be reached anymore (0 folders were shown).

      I have two shares, one called iMac and one called FILM, mounted on ~/mount. I could successfully unmount the iMac share (by clicking on the unmount share button of the application) but I could not unmount the other one. I issued the mount command and I saw that in ~/mount I had FILM and FILM-1, so the same share was mounted twice (while before it wasn’t). I sudo unmounted them both via CLI, then mounted iMac and FILM through the application button, and everything worked fine.

      Maybe the new beta will solve this issue? But I also would like to make sure I do not have to configure everything from scratch when I upgrade

      Thanks

      Reply

      Luca

      • Mar 18, 2020 - 5:58 AM - Luca Comment Link

        A strange thing that I have found is the following. Here below you can see the list of mounted volumes

        Lucas-iMac:~ luca$ mount
        /dev/disk0s2 on / (hfs, local, journaled)
        devfs on /dev (devfs, local, nobrowse)
        /dev/disk1s2 on /Volumes/InternalStorage (hfs, local, journaled)
        map -hosts on /net (autofs, nosuid, automounted, nobrowse)
        map auto_home on /home (autofs, automounted, nobrowse)
        //jenny@192.168.1.120/iMac on /Users/jenny/mount/iMac (192.168.1.120) (smbfs, nodev, nosuid, mounted by jenny)
        //luca@192.168.1.120/iMac on /Users/luca/mount/iMac (192.168.1.120) (smbfs, nodev, nosuid, mounted by luca)
        //luca@192.168.1.120/FILM on /Users/luca/mount/FILM (192.168.1.120) (smbfs, nodev, nosuid, mounted by luca)

        but if I look at the /Volumes folder I see the following: no FILM and 6 iMac folders?

        The Disk_a1 stuff is related to an USB drive connected to my router. I just should see it once instead of 4 and it looks like it was not mounter either

        Lucas-iMac:~ luca$ ls -l /Volumes/
        total 8
        d--x--x--x+ 2 luca wheel 68 Mar 12 19:40 Disk_a1
        d--x--x--x+ 2 luca wheel 68 Mar 5 00:35 Disk_a1-1
        d--x--x--x+ 2 luca wheel 68 Mar 5 00:35 Disk_a1-2
        d--x--x--x+ 2 luca wheel 68 Mar 12 19:40 Disk_a1-3
        drwxr-xr-x 15 root wheel 578 Mar 6 09:09 InternalStorage
        lrwxr-xr-x 1 root wheel 1 Mar 5 00:33 Macintosh HD -> /
        d--x--x--x+ 2 luca wheel 68 Mar 12 19:40 iMac
        d--x--x--x+ 2 luca wheel 68 Mar 12 19:40 iMac-1
        d--x--x--x+ 2 luca wheel 68 Mar 12 19:40 iMac-2
        d--x--x--x+ 2 luca wheel 68 Mar 12 19:40 iMac-3
        d--x--x--x+ 2 luca wheel 68 Mar 12 19:40 iMac-4
        d--x--x--x+ 2 luca wheel 68 Mar 12 19:40 iMac-5
        d--x--x--x+ 2 luca wheel 68 Mar 12 19:40 iMac-6

        Reply

        Luca

      • Mar 18, 2020 - 6:16 AM - Hans - Author: Comment Link

        Hi Luca,

        Based on what I have observed so far (so this may not be entirely correct!):
        Normally, if a volume is already mounted, the macOS API and “mount” will both return “already mounted” even if it is mounted on a different folder.
        Well, if both use the same protocol, for example SMB. If however, both are mounted with a different protocol (eg. AFP and SMB) then a double mount could appear. 

        As for the mounts not appearing in /Volumes:
        Looking at the list, none of these are mounted in /Volumes. You’ll find them in ~/mount though.
        So your findings are odd for sure.

        As for the folder /Volumes, I have no control over what happens in there (depending on your macOS version).
        With recent macOS versions the user cannot manually mount against folders in /Volumes.
        To mount there, the macOS API needs to be used, or a mount through Finder.

        Also note: when using a custom directory (eg ~/mounts), CMN will create a directory for said share.
        Depending on how things run, a directory may be left behind after an unmount (try in Finder to see what is in the iMac folders).
        Having said that: I’ll try and see if I can come up with a cleanup procedure that is more effective.

        Reply

        Hans

        • Mar 18, 2020 - 9:53 AM - Luca Comment Link

          OK, sorry if I use this forum for this but it looks like you have a great experience with SMB and mounting in general…

          You are perfectly right (I did not notice that) that I have the shares under /Volumes and therefore someone else has mounted them. My setup also includes these two things:

          – With Finder, I have clicked on my mount folder and I have dragged the FILM folder (which is seen as a Volume) on the sidebar

          – I have created various symlinks between my home folder and the shared folders, and I have dragged the symlinks to Finder’s sidebar. I have done like that because otherwise, if I drag the NAS folder to Finder, whenever I unmount the share, the link in the sidebar disappears and I need to redo the procedures. With symlinks, everything stays there.

          drwx------    9 luca  staff    306 Aug 24  2019 Applications
          drwx------@ 5 luca staff 170 Feb 8 18:39 Applications (Parallels)
          lrwxr-xr-x 1 luca staff 65 Mar 12 20:03 Canon -> /Users/luca/mount/iMac (192.168.1.120)/Users/luca/Pictures/Canon/
          drwx---r-x+ 46 luca staff 1564 Mar 16 21:24 Desktop
          lrwxr-xr-x 1 luca staff 60 Mar 12 20:03 Documents -> /Users/luca/mount/iMac (192.168.1.120)/Users/luca/Documents/
          drwx------ 3 luca staff 102 Mar 12 20:55 Documents_old
          drwxr--r-x+ 780 luca staff 26520 Mar 17 22:41 Downloads
          drwx------@ 100 luca staff 3400 Mar 15 15:47 Library
          drwx---r-x+ 18 luca staff 612 Mar 17 15:56 Movies
          drwx------+ 3 luca staff 102 Feb 8 22:45 Music
          lrwxr-xr-x 1 luca staff 59 Mar 12 20:03 Pictures -> /Users/luca/mount/iMac (192.168.1.120)/Users/luca/Pictures/
          drwxrwxrwx+ 47 luca staff 1598 Mar 14 15:41 Public
          drwxr-xr-x@ 5 luca staff 170 Feb 17 09:10 QNAP Backup Config
          lrwxr-xr-x 1 luca staff 52 Mar 16 20:04 SD Auto -> mount/iMac (192.168.1.120)/Users/luca/Music/SD Auto/
          drwx------ 15 luca staff 510 Mar 12 21:02 SfondiSchermo
          drwxr-xr-x+ 4 luca staff 136 Feb 10 08:55 Sites
          lrwxr-xr-x 1 luca staff 66 Mar 12 20:03 iPhone -> /Users/luca/mount/iMac (192.168.1.120)/Users/luca/Pictures/iPhone/
          drwxr-xr-x 4 luca staff 136 Mar 12 19:55 mount
          drwxr-xr-x 72 luca staff 2448 Mar 1 15:21 scripts
          drwxrwxrwx 3 luca staff 102 Jun 5 2015 tmp

          But maybe, each time I click on that link in Finder’s sidebar, this is causing a share to be mounted in Finder?

          Maybe I can try to manually unmount those shares and see what happens?

          Reply

          Luca

          • Mar 18, 2020 - 1:53 PM - Luca Comment Link

            I found out that in the /Volumes folder all those entries were considered as no-access folders, probably orphaned.

            I could remove them and now no entries are generated, at least for the moment

            Luca

          • Mar 19, 2020 - 4:09 AM - Hans - Author: Comment Link

            Hi Luca,

            yes, you can remove the orphaned folders.
            Usually they are empty when you open them, a good indicator that it is safe to remove them.
            I have a new version of CMN ready that minimizes orphaned folders.

            The issue is this:
            When macOS handles everything though /Volumes, macOS will also remove the directory it made to mount to.
            However, when we use “mount” functions (Unix style lib calls), macOS will not manage the needed folders.
            So what I have done for non-standard mounts is to remove the directory after an unmount event.
            This of course requires CMN to be running at the time of unmount.

            When it comes to Finder, I can only say that I do not find Finder to be the best user experience.
            What you’re describing is one of the reasons why I prefer to use an alternative tool.
            I’ve been using PathFinder for several years already, and am liking it much more than Finder.
            PathFinder has its downsides as well of course, but when I mount something it will always be listed in the sidebar.

            Note: Whenever you mount through Finder, it will use /Volumes, and will cleanup after an unmount.

            As for the symlinks you’re using; I’m not sure what to tell you.
            You’ve thought things through for sure, but I’m not sure how “stable” it will be, in case you NAS is offline?

            Hans

      • Mar 18, 2020 - 9:38 AM - Hans - Author: Comment Link

        Forgot to mention: the new version uses the same preferences files.
        But it is NEVER a bad idea to make a backup of settings before testing a new version.

        In the meanwhile, I’ve modified the mount/unmount functions to clean up better when using custom paths.
        I hope to upload it today or tomorrow – still doing some testing.

        Reply

        Hans

        • Mar 18, 2020 - 9:54 AM - Luca Comment Link

          Thanks! Will do as you say

          Reply

          Luca

          • Mar 18, 2020 - 1:55 PM - Luca Comment Link

            Installed.

            Tried to login to my Mac with the NAS off, and everything went fine. I forgot to switch on the auto-detection of the share when it comes up but I tried with sleeping the Mac and waking it up and automatically, the shares came up. Very nice job indeed!

            Everything looks pretty good, thanks a lot!

            Luca

          • Mar 19, 2020 - 4:09 AM - Hans - Author: Comment Link

            Thanks Luca 

            Hans

      • Mar 19, 2020 - 4:40 AM - Hans - Author: Comment Link

        Just uploaded a new beta which should address the orphaned folders: download here.

        Note: existing orphaned folders will not be removed. You’ll have to do that manually.

        Reply

        Hans

        • Mar 19, 2020 - 11:44 AM - Luca Comment Link

          Thanks!

          I have downloaded it and installed it. Will let you know

          Reply

          Luca

          • Mar 19, 2020 - 6:25 PM - Luca Comment Link

            Waking up from sleep, I received an access error. I aborted and relaunched the application

            Luca

          • Mar 20, 2020 - 5:02 AM - Hans - Author: Comment Link

            Thanks Luca for reporting!

            Was it a simple error message and you didn’t see anything in the debug log?
            It could be cause by the cleanup procedure I’ve added. 
            I’ll do some testing.

            Hans

          • Mar 20, 2020 - 5:07 AM - Hans - Author: Comment Link

            Question: did you have anything mounted with a custom path (vs. using the default /Volumes)?

            Hans

          • Mar 20, 2020 - 6:18 AM - Hans - Author: Comment Link

            Just uploaded build 137.
            Hopefully it will address the access error message – please give it a try.

            2 Changes: only cleanup dirs for custom paths, and only try to delete an unmounted directory (do not display an error if it fails).

            Hans

          • Mar 20, 2020 - 1:06 PM - Luca Comment Link

            I didn’t check the logs back then and now it’s too late because I cannot see anything apart from the last seconds

            Anyway this didn’t happen again so I did not install the latest update. In case of further issues I will let you know.

            My shares are all mounted in the custom path

            Luca

  • Mar 19, 2020 - 4:41 AM - Hans - Author: Comment Link

    UPDATE:

    Just uploaded build 136 of the 3.0.6 beta.
    Feel free to download and test it.

    Reply

    Hans



Your Comment …

Do not post large files here (like source codes, log files or config files). Please use the Forum for that purpose.

Please share:
*
*
Notify me about new comments (email).
       You can also use your RSS reader to track comments.


Tweaking4All uses the free Gravatar service for Avatar display.
Tweaking4All will never share your email address with others.