Page 1 of 1

ConnectMeNow v4 – Mounting Network Shares Quick and Easy on a Mac

ConnectMeNow v4 – Mounting Network Shares Quick and Easy on a Mac

As a macOS fan I keep being surprised that Apple still hasn’t implemented some obvious improvements, like a dual pane Finder or … an easier way to mount network shares.
And the latter is what ConnectMeNow is all about – nothing new to those familiar with previous versions of ConnectMeNow (CMN).

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“).

For this reason I created ConnectMeNow – initially just for personal use.
Its sole purpose being to mount network shares quicker and easier, and have easier access to SSH connections.
ConnectMeNow supports protocols like SMBCIFSFTPSSHWebDAVNFS and AFP.

Note: if “mounting” doesn’t mean anything to you, then know that mounting (in this case) refers to making network drives, for example from another computer or NAS, appear on your Mac so you can access them quicker and easier.

Besides this being a fully from scratch build version, this version now is available as 64bit application for Intel and Apple Silicon – signed an notarized.

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
The action of attaching a directory located on a different computer, shared over a network, to your computer as if it was a local disk drive.
(under Windows this is often a drive letter)

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.), a shared USB stick connected to your router, or even a full size server. The Operating System of these “computers” does not need to be relevant, as long as it supports one of the needed protocols.
For example most NAS devices, like a QNAP NAS, run a Linux variant, however can share directories in a Windows originated protocol (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.

Naming convention for Shares, Sessions, etc … 

ConnectMeNow was originally designed to just support SMB (Samba) network shares, but as usual with my silly “little” projects, things went out of control.
So not it supports NFS, SSHFS, FTP, AFP, etc. which are all still legit “network shares”.

Since I frequently use SSH, I’ve added SSH as well. However, SSH is technically not a network share, rather a remote shell/terminal access.
As you may notice, I still use the phrase “share” quite often, and with that (incorrect as it may be) I’m also referring to SSH connections.


ConnectMeNow – How did we get to version 4?

Even though previous versions worked well, I just could not resist making a new version.
The main reason was actually to try to reduce the load on the system as much as possible.

In previous versions I’ve used polling for certain activities, which isn’t ideal.
So to reduce that, I’ve used some new techniques and API calls, and kernel related tricks.

Additionally, I found myself annoyed with the occasional beachball appearing.
To avoid that I’ve added multithreading, so that mounting, unmounting and status checks, all happen in separate tasks, that are only created if needed of course.

A bonus for this all, is that I now have Apple Silicon hardware available, so a native ARM64 version is available now as well.

Some of the less relevant tools found in v3, I did remove to try to make the application more task oriented and light weight.
Additionally, I hope I changed the settings so that things are more intuitive.

To distinguish from previous version, I also changed the icon design.

Quick overview of Features

ConnectMeNow has quite a lot to offer.
It has most of the functionality as v3, just improved some of the functions and added a few new features.

Just to name a few …

  • Protocols support for SMB, AFP, NFS, SSH, SSHFS, WebDAV and FTP.
  • Dark Theme support, in the menu bar as well
  • Auto Mount at startup
  • Auto Mount after a network change, with the option to do this only for a specific gateway (network)
  • Auto Remount after waking up from sleep or standby
  • Auto Mount when a device appears in the network
  • Support for Fallback servers, for when a server is not available
  • SSHFS (needs macFuse) support with automatic password entry or SSH keys
  • SSH support with automatic password entry or SSH Keys
  • Support for Generating and Installing SSH keys on server(s)
  • Mount, unmount, and Reveal-in-Finder from the ConnectMeNow menu
  • Open or Close SSH connections straight 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 preferred mount directory
  • Mount/Unmount notifications related to the shares defined in ConnectMeNow
  • 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
  • Much more detailed debug log, with option to debug to Console
  • Intel 64 bit and Apple Silicon native applications (signed and notarized)
  • Icon visible in dock when opening settings
  • More modern design of the application
  • and more … oh, and it’s still free …


Some things to pay attention to …

You can import v3 settings, but this will be based on a best effort … 

During the life span of v3, I’ve used 2 different ways of storing the settings. Both should work with the import tool.
However, some of the features in v4 have changed, so keep in mind that the settings are imported based on a best effort.
After an import it is a good idea to briefly go through the settings and verify things.

  Older ConnectMeNow (v1 and v2) settings are not supported.

FTP is unfortunately READ ONLY … 

Unfortunately, Apple’s implementation of the FTP protocol only allows us to mount an FTP connection as “read-only“.
If anyone knows about a macFuse add-on that supports read/write FTP, then please leave a comment below, I’d be happy to look into this as an option.

SSHFS requires macFuse … 

If you’d like to use SSHFS, and I can actually recommend giving it a try, then you must install macFuse (also known as OSXFuse) and their SSHFS extension.

  macFuse and the SSHFS add-on are both FREE.
  SSHFS is actually quite a bit faster than some SMB implementations.
  Bonus: macFuse allows you to add support for other filesystems to your Mac as well (for example, read/write support for ext3 and NTFS drives).


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, so other users can find it as well.

ConnectMeNow has also been mentioned in one of the MacObserver Podcasts before.
Feel free to visit MacObserver / MacGeekGab for cool Mac related topics.

MacGeekGab - Excellent Mac related Podcasts


Download ConnectMeNow

You can choose either the Intel version or the new Apple Silicon version (a.k.a. ARM64, AARCH64 or M1/M2 version).
Note that these straight up are native binaries, so pick the right one for your system – these are not so called “fat” binaries that hold both versions.

Not sure what version to use …? 

To find out if your Mac is Intel or Apple Silicon based, click     “About this Mac“.
Look next to the word Processor or Chip in the opened window.
An Intel Mac will specifically mention the name “Intel“, where as an Apple Silicon Mac will say “Apple“.

Note: The Intel version will run on an Apple Silicon Mac as well. It is just a little less efficient since Rosetta needs to be started as well and translate the Intel code to ARM while running.

You can downloaded here:


Download - ConnectMeNow4-v4.0.1-macOS-arm64.dmg 

Filename:  ConnectMeNow4-v4.0.1-macOS-arm64.dmg
Platform:  Apple macOS
Version:  4.0.1 ARM64
File size:  3.2 MB
Date:  2022-11-23
 Download Now  Send me a cup of Coffee    

Download - ConnectMeNow4-v4.0.-macOS-x86-64.dmg 

Filename:  ConnectMeNow4-v4.0.1-macOS-x86-64.dmg
Platform:  Apple macOS
Version:  4.0.1 Intel
File size:  2.7 MB
Date:  2022-11-23
 Download Now  Send me a cup of Coffee    

Beta version

If a beta version becomes available, then it will be listed here.

Currently there is no beta version available.

Installing ConnectMeNow

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

Installing ConnectMeNow v4

Installing ConnectMeNow v4

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 the files 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 3 files related to ConnectMeNow:



Supported Protocols

The protocols, you may or may not have heard of, supported by ConnectMeNow are (same as v3):

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 very well may be – 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 a very commonly used protocol for those accessing web servers, but more so for developers or admins who know what they are doing (most of the time anyway hahah).

  FTP shares are Read Only: due to limitations of macOS’s FTP implementation, a FTP network share can only be mounted as read only!

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 this was thought as an alternative to FTP, allowing the user “easier” and more reliable access to their web servers (WebDAV is after all 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.

  SSHFS will only work is macFuse is installed, with its SSHFS add-on.

SSH: I do have to get into my NAS, Firewall or Raspberry Pi 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, path (this is typically the share-name on the “server”, not to be confused with the actual directory on the server), username and password.

Some protocols allow for some extra wiggle room, where the user fro example can define a specific network port, or pass special command line parameters.

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 Daily use – The Menu bar

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

ConnectMeNow4 - Empty menu

ConnectMeNow4 – Empty menu

But once you’ve created shares, and optional menu groups, things will look different for sure.
(The menu looks quite similar to what you may have seen in v3)

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

Additionally we can make groups in the menu, which can be a horizontal line, a group name, or both.
Here for example the group “QNAP File Shares” and “SSH Connections”.
Note: the first menu group will never have a horizontal line and a group name will always show in gray (under the horizontal line, if applicable).

When clicking an inactive item (for example “Bender AllShares (SMB)”), ConnectMeNow will try to mount or open 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“.

ConnectMeNow4 - Menu Features

ConnectMeNow4 – Menu Features

Adding Shares

This chapter tries to briefly show you how to define new shares, with their basic settings and advanced option.

Adding shares is done by selecting the “Settings” – “Share Definitions” option in the ConnectMeNow menu.
This will open the preferences window where you can define shares.

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 ) in the lower left corner of the settings window.

Share Details – The Basic Settings needed for every share

By default you will be presented with the basic details of a share.
As you can see, there is a tab for more advanced settings – for each individual share.
Most users will not need the advanced settings.

  Notice the Test Mount button at the bottom right to test if your mount/share settings are working as expected.
After a successful test, you can use the Test Unmount button to unmount or close your share.

Example Share setting

Example Share setting

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 Title” 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. This is optional, so you can uncheck the “Auto Menu Title” option if you’d rather type a name yourself.

Share Type

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

  As mentioned before: SSHFS requires macFUSE to be installed with the SSHFS add-on.


In the next steps, the selected protocol may or may not support certain options and will be displayed accordingly.

For example:

SSH and SSHFS do not support the selection of the path on the server – so that field will not be shown when setting up an SSH or SSHFS share.


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

Auto Mount when ConnectMeNow start

Each connection can be mounted right away when ConnectMeNow starts by selecting this option, which happens usually when you start your Mac or login to your Mac.

On Mount, reveal in Finder

This option, opens up Finder, showing the mounted drive (or its content) after a successful mount.

  SSH does 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 Address” – I mean, where else would we go right?
The “server” can be even the smallest computer and this can be entered as an IP address (recommended) or a computer name.

The Ping button allows you to test and see if you Mac can ping the set server.

  Here we enter only the IP address or computer-name – do not add the path on the server or any protocol indictors!

  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.

  Not all network devices support being pinged, and some even have ping intentionally disabled.


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

  Normally there is no need to change this value. Only do so if you know what you’re doing.


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 (FTP).

  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.


The “Domain” name is typically only needed in a corporate setting where a domain controller is being used – consult your IT administrator if needed.
Domains are rarely used in private/home settings – leave it blank if you’re not sure.


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).

  To reveal a passwords, if hidden, the administrator password will be requested.


Installing SSH Keys … 

For SSH and SSHFS you will see an Install SSH key button. Clicking this will make ConnectMeNow try to install SSH keys on your server so a password is no longer needed when connecting to this server. Installing the keys requires username and password to be entered. Once the keys have been installed, blank the password so ConnectMeNow know to use the key instead of a password. For more information, read this article: SSH Login without a Password.


Advanced Options – For specific purposes

Under this tab you will find settings for less common features, often used by the more experienced users or exceptional circumstances.

Auto Mount Options

Besides the Auto Mount option that gets triggered when ConnectMeNow gets started, I’ve included a few other options.

ConnectMeNow4 - Advanced Auto Mount

ConnectMeNow4 – Advanced Auto Mount

Mount on Appear (not recommended)

The first one, is when a certain IP address appears in a network.
For example, the share you configured is on the server with the IP address
ConnectMeNow will keep looking for that IP address until it finds it, and mounts it when it does.

The reason why I would not recommend using this option is that there is no standard mechanism where a newly appearing IP address will report to your Mac.
This means that every so many seconds, ConnectMeNow has to check if the IP address is in the network, by trying to ping it.
As you can imagine, this does not only take resources of your Mac, but also generates quite a bit of network traffic which may be undesirable.

Mount On Network Change

When your Mac changes network, for example because you plugged in an Ethernet cable, or switched WiFi network, macOS will alert ConnectMeNow.
This could be a good moment to try to mount a drive, for example when you arrive at the office with your laptop.

Having said that, randomly trying to mount a drive may work just fine, but we can even refine the attempts by limiting these attempts when certain Default Gateways appear.
Now quite a lot of Default Gateways (your router or modem) share the same IP addresses, since they need to be in a private IP address range, which can be:

  • Class A: to
  • Class B: to
  • Class C: to

This could cause a problem of course when your router at home has IP address, and the router at work for example as well.
Where these will be most likely be different is their MAC address.

So for identifying the right Default Gateway (router/modem), we can enter here the MAC address.
Since MAC addresses are a pain to find and enter, I’ve added some tools to help you find the right one.
Typically you just click the Detect Default Gateway button and IP address and MAC address will be pre-populated.

Note: The IP address is irrelevant for ConnectMeNow and is only shown for your reference.


Mount Style and Mount Location

ConnectMeNow allows you to mount in two ways, each with their own advantages and disadvantages.

ConnectMeNow4 - Advanced Mount Style

ConnectMeNow4 – Advanced Mount Style

System Call (uses the official macOS API)

The biggest advantage of using a System Call is that this is how Apple intended it to be done.
This is also the only method that (optionally) allows you to mount in /Volumes .

This would be the recommended method for the average user.

Command-line (uses plain Terminal commands)

Using the command-line option comes with the advantage of speed and options.
Downside though is that you can not mount in /Volumes .

Advantages are speed, and the option to add command-line options.
That makes it also more suitable for experienced user, or protocols that require special options in your setup, not supported by the standard System Call (API).

The extra options, like the example here “-o follow_symlinks” will be inserted into the command-line statement.
Be careful how you use this.

Location: Default or Custom

Typically, a network share is mounted or tied to an empty directory. This way the user can go to this directory like any other directory and access files.

By default macOS uses the directory /Volumes  to collect these shares.
For each mounted network share, macOS will automatically create a sub directory in the /Volumes directory.

However, the command-line functions to mount a network share however are not allowed to mount in that directory.
Instead of /Volumes, you can also make your own “mount” directory.
I like to use a directory in my home directory and call it /Users/<username>/MountPoints – but you can pick anything you want (as long as you have access to it to course).

Note: Using a custom path is supported by both mount styles.

With a custom mount directory, we have two options:

  1. The custom directory gets automatically a sub directory for each network share (like seen in/Volumes) – recommended.
  2. The custom directory will become the directory representing the network share (check “do not create sub-directory for mounting“).

I would recommend option 1 where we leave “do not create sub-directory for mounting” unchecked, unless you know what you’re doing.


Extra Options

Besides the Auto Mount and Mount Style options, you will find a few more handy little options here as well.

ConnectMeNow4 - Advanced Extras

ConnectMeNow4 – Advanced Extras


Before doing a mount attempt, a PING can be helpful to wake up a share or server (there is a global setting for this as well, see Preferences).

Now a PING is not how you wake a sleeping server, so for that we also offer a Wake On LAN option to wake up a server or NAS.

Note that for Wake On LAN (or WOL), we will need the MAC address of the server or NAS.
With the provided tools you can try to Detect the MAC address (if the first attempt fails, give it a second and try again).
Broadcast mask and port can be set here as well. Not sure what to use? Then just use the defaults by clicking Default.

It is a good idea to test if Wake On LAN works before relying on it, so clicking Test Wake On LAN is recommended to make sure.

Mount Delay

The mount delay is recommended when having to wake up a NAS or Server with for example Wake On LAN, or when accessing for example a new network.
Sometimes it takes a little before your Mac actually sees or can access such a device. This is where this can become quite useful.
As an example: my very old backup NAS takes less than 5 seconds to become visible for my Mac. So for that one I set the mount delay to 10 seconds to give it some breathing room.

Run Script after Mounting

After a mount completes, it can sometimes be useful to run a script.
Think about activating a printer, or a script that makes a copy of certain files and even puts the server back to sleep if you want it to.

Try this for the fun of it: say "server access, granted"

Fallback Server

The Fallback server allows you to select another server for when the mount to this share 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 this list.

  This fallback server must be using the same protocol.

  To avoid endless looping: prevent using a fallback server that has a fallback server as well.



Adding Menu Groups

Adding a group works in a similar way. Click the “Add Group” button ( Add Menu Separator ) in the lower left corner of the Shares window.
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 :

  • The group title (Menu Title) is optional, leave it blank if you do not want to use a label here,
  • A group can have a horizontal line, but this is optional,
  • If the horizontal line is the first item in the menu, then this line will not be shown (a limitation of the menu),
  • The Menu Label, or Group Title, will show as greyed/disabled in the menu to distinguish them from actual network shares.
ConnectMeNow4 - Menu Group

ConnectMeNow4 – Menu Group


Application Preferences

ConnectMeNow also has a few settings, that cover the entire application and all defined shares.
You can find this in the ConnectMeNow menu, under “Settings” – “Application Preferences“.

You can toggle back and forth between Share Definitions and Application preferences with the buttons Shares and Preferences at the bottom of the settings window.

Most of these options are easy to understand, with a little hint …

Common Application setting



Information and Notifications

In this section you can Enable or Disable …

  • Notifications when shares are mounted or unmounted (only for those defined in ConnectMeNow!),
  • Warnings and confirmation dialogs, for example when you delete something,
  • Application hints (little text balloons when you hover over certain items).

Generic Application Settings

Here we can determine if …

  • ConnectMeNow should start when your computer starts,
  • ConnectMeNow should save and restore window positions and size,
  • and … if Passwords should be shown, or should always be masked (you can still look at them, but you’ll need to enter the admin password to reveal the passwords).

Mount Related options

Here we find some tools that are mounting related …

  • Should shares that were mounted when your computer went to sleep mode, be re-mounted when your computer wakes up?
  • Should all shares and mounts, defined in ConnectMenow, be quickly unmounted when there is no network?
  • Should all shares and mounts, defined in ConnectMenow, be quickly unmounted when ConnectMeNow is closed?
  • Should a server always be pinged first, before mounting a share (overrides setting for individual shares)?
  • Reveal in Finder show the content of the mounted share, or the directory content that holds the mounted share?

Network Polling

This doesn’t have much of a function anymore, since most detection mechanisms are bot implemented differently than in v3.
The only thing that would require polling is when you want a share to be mounted when the IP address appears in a network.

I would recommend a value between 30 and 60 seconds.

If none of the shares are set to “Auto Mount” – “On server IP address Appear“, then the “pollution” on your network will be negligible.
With pollution I mean: to detect an IP address in the network, ConnectMeNow will have no choice than trying to ping that IP address.
As you can imagine, this may be undesirable and maybe even unneeded.

Having said that; if not absolutely needed, the consider setting this to a higher value, and avoid using “Auto Mount” – “On server IP address Appear“.

For Admins only – Debug Logging

The two options here should by default be unchecked.
Debugging messages is great and all, but if not needed they produce more overhead than needed.
This isn’t anything dramatic of course, I just like to keep things “clean”.

Debug messages can be send to Console (found in Applications Utilities), which is fairly common for macOS applications, and can be enabled by checking “Log to System Console”.
Keep in mind though that this may not be as wonderful as one would hope, as messages do end up in a pile with tons of messages that are not very relevant for our purposes.
You can limit the messages by setting the filter in Console to “process“-“connectmenow4“.

To find our messages quicker, I’ve implemented a debug log window, as seen with ConnectMeNow v3, with more advanced features.
The messages in this window are much easier to go through and there is even a search function.

This Log Window can be accessed by simultaneously pressing Control Option  Command, which will reveal a Show Log and Clear Log button while keeping these keys pressed..

Less Common Application setting

These settings are less used, or modified, but can proof quite useful for specific users.



Settings Config File Location

As with previous ConnectMeNow versions, you can place the config file in alternative locations, so these are being backed up automatically, or shared with other users or computers.

I’ll illustrate this with how I use this myself.

I have more than one Mac, and I want them all to have ConnectMeNow configured the same way.
For this purpose I have defined all shares and settings on one Mac.
These settings will be saved in the default location:



Once I have everything configured the way I like it, I actually tell ConnectMeNow to copy it to a directory on Dropbox, by selecting the “Save preferences in custom path” option, and clicking the Dropbox button and selecting the directory where I want to save the config.

ConnectMeNow will now do two things:

  1. In the local config file, it will reference to that location in Dropbox, so it can find the shared config next time it starts.
  2. It will copy the config locally and to the Dropbox location each time it is saved.
Making a backup of your config

Having said that: Sharing files can like this can have its issues. Personally I have not encountered any, but that doesn’t mean it can go side ways at times.
This is why I have added the Backup Config and Load Config buttons – so you can make a backup of a config you like, and load it again if something went wrong.

Password Encryption

Please note that passwords in the config files are encrypted.

However,… everything can be hacked, and these files were not designed to protect Fort Knox either.
I do think the protection is pretty decent though, and it will take some effort (I hope) to decrypt the passwords.

System Admin Functions – Preventing Access to Settings

This little section was created with Schools and Companies in mind, where the user should not tinker with or copy settings like passwords and such. Not a 100% guarantee that a user will nog ruin your settings, but at least this is a hurdle for them to get to the settings.

The System Admin can lock down the preferences and share definitions window, so an Admin password is asked when a user wants to access the Preferences or Share Definitions.

The “admin password” is the password of the administrator of the Mac you’re using ConnectMeNow on.
So please be aware that your users should not have admin privileges on this Mac if you want to prevent them from accessing these settings.

When a user tries to access the settings, a popup will request the admin password.
If the user fails to enter the right password, a dialog will appear displaying the “Admin contact info”.
For example the phone extension or email of the system administrator or help desk that can assist with this.

Default New Share Template

Some values or settings for a new Share or Menu Group can be predefined here, and will be used as the initial settings of a new share or menu group.
The idea being that one can enter new shares quicker and more consistent.

Preferences Tools

At the bottom you will find some obvious buttons:

  • Reset Preferences to defaults will reset all settings – this will not change or delete your defined shares.
  • Reset the Share Template to Defaults which will not affect existing defined shares of course.
  • Import v3 Config will do a best effort attempt to import ConnectMeNow v3 configurations. Since some features have changed or no longer exit, I’d recommend verifying the new settings after an import.
  • And, as mentioned before, the option to make a Backup Config of the config file, and the option to Load Config of such a backup at a later time if needed.

Support Us ...

Your support is very much appreciated, and can be as easy as sharing a link to my website with others, or on social media.

Support can also be done by sponsoring me, and even that can be free (e.g. shop at Amazon).
Any funds received from your support will be used for web-hosting expenses, project hardware and software, coffee, etc.

Thank you very much for those that have shown support already!
It's truly amazing to see that folks like my articles and small applications.

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


There are 55 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 19, 2022 - 3:44 PM - John Comment Link

    Hans, you’ve outdone yourself again. Special thanks for adding M1 CPU support!
    Since this must have kept you busy for several weeks, I’d like to send you a coffee or a beer your way.
    Well done!



    • Nov 20, 2022 - 6:12 AM - Hans - Author: Comment Link

      Thanks John!

      And thanks for taking the time to post a thank-you and sending me some coffee! 

      It is very much appreciated 



  • Nov 19, 2022 - 9:49 PM - Thomas Comment Link

    I had to manually “stretch” the size of the preferences settings window to get a hold of the “Tools” line with the import, backup config line. It was hidden some how and when I stretched the window size about 2mm it appeared. Is that the way it is supposed to be? MacBookPro 13″ (2016) intel on Ventura.

    Thanks for letting us have your tool!




    • Nov 20, 2022 - 6:50 AM - Hans - Author: Comment Link

      Hi Thomas,

      Thank you for posting a thank-you as well! 

      Thanks for the feedback as well.
      And … no, that is not how this should have been.
      Bummer – I’ll look into this right away.

      p.s. what resolution is your screen?
      I found these spec for your laptop: 2560-by-1600 native resolution with supported scaled resolutions: 1680 by 1050, 1440 by 900, 1024 by 640.



    • Nov 23, 2022 - 10:03 AM - Hans - Author: Comment Link

      Version 4.0.1 should resolve this. Seems a Ventura specific issue. 



  • Nov 20, 2022 - 2:58 PM - Ash Comment Link

    I tried out v4 earlier and I am unable to connect to NFS shares. 

    The shares are configured the same as I had them in v3. I can still mount them using v3, or manually via finder. Checking through logs, I think there’s just an error about timeout, but that’s about all I can see. I have the shares set to connect with System Call in /Volumes (same as v3). 

    If I am connected to the share (via v3 or Finder) and use the “Test Unmount” function it does unmount the drive as expected, but I can’t seem to get “Test Mount” working at all.

    It does, however, work fine with SMB shares on the same server, and on another NAS. I unfortunately don’t have a second server setup with NFS to see if it’s an isolated issue, but given that I can still connect with v3 and finder makes me think I’ve either misconfigured it somehow, or v4 isn’t able to mount NFS shares. 

    I also noticed the same issue of needing to resize the window that Thomas experienced. For reference, I am using an M1 Mac Mini (Ventura 13.0.1) and an Asus VG289 (3840×2160 native resolution) scaled to 2560×1440. 

    Outside of that issue, v4 has been working great so far, and I appreciate the effort you out into the app! I



    • Nov 21, 2022 - 8:45 AM - Hans - Author: Comment Link

      Hi Ash,

      Thank you for reporting issues! It’s much appreciated.

      NFS has always been a though cookie for me since I never use it, and am therefor not the most experienced person on that topic.
      I also do recall macOS being a little finicky about NFS – something about the ports being used.

      • Tests I did on my Intel Mac running Monterey:

      I tried NFS v4 on my QNAP NAS, and initially both System call and Command-line style failed. In Terminal I even got a “RPC not found” error.

      Well, all that changed when I tried just one single attempt using the Command-line style, with the “-o nfc” option (in ConnectMeNow).

      After that every NFS mount variation I tried just worked – even the ones that failed before, and even without the “-o nfc” option.
      Even switching my NAS to NFS v2/v3 did not have any impact. It just kept working.
      Great for testing – not so much. 

      • Tests on my M1 Mac running Ventura:

      With NFS v2/v3 and v4 on my NAS and every call with the command-line worked just fine, even without the “-o nfc” option.
      However … every System call just fails. Doing some online searching, some other (not ConnectMeNow) users report similar struggling with NFS and Ventura – but I’m not sure how much of that is related to the odd behavior we see here.

      I’ll do some testing to see what the issue may be.

      As for the resize issue: I’ve been able to reproduce this on my M1 Mac, just not on my Intel Mac haha. Odd. I hope to find a fix for that as well.

      Thanks again for reporting – I’ll post an update when I have one (soon)! 



      • Nov 21, 2022 - 5:48 PM - Ash Comment Link

        Thanks Hans! I appreciate your time taken to try and debug this, especially as it is a feature that you don’t use. 

        I’ve been playing around  with it again tonight, and I am unable to find any combination (System Call/Command Line/-o nfc) that can mount the NFS shares. 

        I have also tried enabling NFS shares on the snyology NAS (NFS v2, v3, v4) to see if the issue was with the unRaid NFS implementation, with no luck at all. Similarly to my previous post, the NFS shares on the synology NAS connect okay using v3.0.7, but not in v4. 

        I noticed something interesting after I deleted all config files for both v3 and v4 tried starting from scratch. In version 3.0.7 if I enter the server IP address it provides me with a dropdown list of available NFS shares. However, in v4, this drop down list does not populate for NFS shares. It does, however, appear for SMB shares. 



        • Nov 23, 2022 - 4:10 AM - Hans - Author: Comment Link

          Hi Ash,

          that’s an interesting find.
          So to populate the NFS shares list, I use the Terminal command “showmount“, which works something like this (IP = IP of my NAS):

          showmount -e

          This should list NFS shares.
          The odd thing is that I use the exact same function in v3 and v4 … 
          Can you try this command in Terminal?

          Also please try:

          smbutil status 

          p.s. if you’re OK with it, we could move this conversation either to the forum or to email.



        • Nov 23, 2022 - 8:16 AM - Hans - Author: Comment Link

          Just did a few tests myself on my M1 Mac running Ventura and “showmount” works just fine for my NFS share on my QNAP, and lists the shares.

          I did some additional tests today, on Intel Monterey and on M1 Ventura, and all variations worked with both (at the same time) NFS v2/3 and v4 enabled on my NAS. System API mounting in /Volumes and in a custom path worked. Commandline, with and without the “-o nfc” options, both worked as well.

          You said this worked before with v3 – and I totally believe you on that one – can you test this again?
          Your v3 config file remains untouched by v4.
          The mount function should be identical to the code in v3 – so if v3 works, but v4 does not, then I have to go find my magnifying glass and see if I by accident some changed something.

          Doing a manual mount, assuming you have the share “Downloads” and your NAS’s IP address is, should look something like this:

          cd ~
          mkdir test
          mount_nfs ~/test

          Unmount that same mount:

          umount ~/test

          Also note, even though probably not relevant; I have had at least 3 Synology users run into unexpected firewall issues on their Synology NAS. Try and see what happens if you disable the Synology firewall (assuming you do not open up your NAS to the Internet – which would be a bad idea to begin with).

          As for a CMN release with fixes: I did fix 2 small issues as well, but before releasing a new version, I’d like to make sure we got this NFS issue resolved as well.



        • Nov 23, 2022 - 8:17 AM - Hans - Author: Comment Link

          Maybe we should start a forum topic here … 



          • Nov 25, 2022 - 3:32 AM - Hans - Author: Comment Link

            Hi Ash,

            Not sure what happened, but I did see a forum post flying by from “controversialfigure”, describing what you’re running into, but for some odd reason the user and forum post are both gone (I still have the email message). In case this was you; did you remove the post? And/or did the NFS issues get resolved?


          • Nov 25, 2022 - 5:58 AM - Ash Comment Link

            Hi Hans,

            Yes, that was me posting, but I didn’t delete it. Not sure what happened with that one. 

            I’m still having issues with it connecting in v4.0.1. The shares are now populating in the drop down list after the latest update. 

            “Showmount” worked as intended, and also manually mounting and u mounting the drives from the command line with the code you suggested.

            I am still able to connect with v3.0.7 too without any issues. 

            Thanks again,



          • Nov 25, 2022 - 10:49 AM - Hans - Author: Comment Link

            So the mounts not showing was a dumb mistake on my end – I utilized smbutil (which I did with v3 as well!) to see if a server is available.
            Since you had mentioned that smbutil failed; do you have SMB enabled on your server? Should not be related to the NFS question of course, I was just wondering.


    • Nov 21, 2022 - 10:35 AM - Hans - Author: Comment Link

      FYI: I did find out why the buttons were not visible at the bottom of the preferences screen.
      The “title” or “caption” of the group-boxes in Ventura use a different (taller) spacing than in previous macOS versions.
      This results in the content needing much more vertical space than in other macOS versions.
      I have a work around for that – so the next version will have that fixed.

      Doing some more experiments with the NFS situation before releasing an update.



  • Nov 22, 2022 - 9:09 AM - wea Comment Link

    v4 not working with VPN :( 



    • Nov 23, 2022 - 4:01 AM - Hans - Author: Comment Link

      Hi Wea,

      Since ConnectMeNow doesn’t really do anything with VPN – VPN is a “network” completely independent of ConnectMeNow.
      Could you provide more information? I’d love to resolve an issue if there is one. 

      p.s.: Just tested it with a WireGuard connection, and that one worked with ConnectMeNow.



  • Nov 22, 2022 - 2:55 PM - Guido Comment Link

    Thanks a lot. Apple Silicon support is really appreciated. The content of my NAS shares is now displayed much faster.



  • Nov 23, 2022 - 9:54 AM - Hans - Author: Comment Link

    UPDATE 4.0.1

    Minor bug fixes after release

    – Import v3 config; no longer importing former Windows postion (since windows are sized differently in v4)
    – Bug fix: Window height issue due to macOS Venture issue where a group-box caption is taller than other macOS versions
    – Bug fix: Auto mount forgot to verify if a share was even enabled or not



    • Nov 23, 2022 - 11:08 AM - Guido Comment Link

      Did the update and now shares are not connected anymore. Even if I try to trigger the connection manually, nothing happens.



      • Nov 23, 2022 - 2:41 PM - Guido Comment Link

        Update: after one hour everything seems to be fine again. Somehow strange.



        • Nov 24, 2022 - 12:38 AM - Guido Comment Link

          It seems that it is not working 100%. This morning only 3 of 5 shares were connected automatically. The settings are the same for all shares. 



          • Nov 25, 2022 - 2:10 AM - Guido Comment Link

            OK. CMN 4.01 is not working.If I add a share it will not connect automatically. If I click “Execute Auto Mount” nothing happens. Same for unmount. Only after I quit CMN and open it again my 5 shares will be connected. But they are shown in CMN as not connected (no green dot and no flash).After my NAS starts up in the morning no share will be connected automatically. And so on.
            It is possible to redownload Release 4.0?
            I deleted CMN 4.01 3 times including the three config files but that did not change anything to these issues.


      • Nov 25, 2022 - 3:09 AM - Hans - Author: Comment Link

        Hi Guido,

        apologies for the late response.

        Are you by any chance running on Apple Silicon and/or Ventura (you can copy the version info straight from the CMN menu)?
        I’ve noticed some odd behavior like this on my M1 – same version on Intel has zero issues. It is almost like (at times like mounting doesn’t do anything or is waiting for something until the end of days to actually execute the mount. This happens only on my Apple Silicon Mac, but since I’m doing some extreme and odd tests, I figured it may be because I keep pushing it a little too far. A reboot always “cleared” this (had it happen twice in the last 3 weeks).

        On the v4.0.0 differences: nothing you describe should be related to any of the changes in 4.0.1.
        Naturally, I can never assume anything for 100%. Would you be able to post your version info?



  • Nov 23, 2022 - 11:54 AM - bernd Comment Link


    Unfortunately, version 4 does not work with an active VPN connection. The program shows the message “no network avaiable”. Ping to the host works but the program can’t mount the resource. After disconnecting from the VPN everything works, after logging in again the resource remains mounted but the message “no network avaiable” returns. 

    Version 3 has no problem with this.

    Thanks for your hard work!

    Best regards, Bernd




    • Nov 25, 2022 - 10:28 AM - Hans - Author: Comment Link

      Hi Bernd,

      apologies for the late reply, I had almost forgotten to reply 

      Would you mind posting the version info of CMN and your OS?
      Easiest way to get this: CMN menu -> Help and About -> Version info to Cliboard.
      You can paste it here in the comments and should look something like this:

      Version: 4.0.1
      OS: macOS Monterey
      Version 12.6.1 (Build 21G217)
      Intel x86-64 (64 bits) application



      • Nov 25, 2022 - 1:22 PM - Bernd Comment Link


        Version: 4.0.1

        OS: macOS Monterey

        Version 12.6.1 (Build 21G217)

        ARM (64 bits) application



      • Nov 26, 2022 - 5:44 AM - Hans - Author: Comment Link

        Yikes, ARM again … 

        Can you describe your VPN setup?
        I’d assume you have some regular network connection (Ethernet or Wifi) and a VPN connection running over that connection?
        When connected to your VPN, does ConnectMeNow show “NO NETWORK AVAILABLE” in the settings window, above the list of shares?



        • Nov 27, 2022 - 7:42 AM - Bernd Comment Link

          Its a OpenVPN over Ethernet. No Wifi.

          “When connected to your VPN, does ConnectMeNow show “NO NETWORK AVAILABLE” in the settings window, above the list of shares?”




          • Nov 29, 2022 - 11:33 AM - Hans - Author: Comment Link

            I think I found the issue in your particular case ….

            With your VPN connection you may not have a default gateway configured – unlike my setup where I use WireGuard, yet still have a default gateway defined.
            eg. certain traffic goes through Wireguard, but my local network is till active as well, where as in your case the VPN connect is the only network connection.

            I’m trying to find an alternative way to detect if there is an active network.
            Just detecting network or VPN is maybe not the most reliable way to do it.

            I’ll keep you posted! 


        • Nov 28, 2022 - 4:54 AM - Hans - Author: Comment Link

          Thanks Bernd – This is good info! 
           I’m doing some testing today, to see if I can reproduce the issue.



    • Nov 28, 2022 - 9:47 AM - Daniel Comment Link

      I’m having the same issue on my corporate VPN connection. I’m using the ARM version on my M1 MacBook Pro.



      • Nov 29, 2022 - 12:07 PM - Hans - Author: Comment Link

        Thanks Daniel for the confirmation!
        I think I found the issue – please see my reply to Bernd.
        Seems you guys have a VPN only setup which appears to have no default gateway – I learn something new every day 

        So now I have to find a way to detect if there is a network, or introduce the option to ignore network availability.
        (terminal suggestions are welcome)



        • Nov 29, 2022 - 1:55 PM - Daniel Comment Link

          Thanks, Hans. My company doesn’t allow me to change any VPN gateway settings on my device. Perhaps instead of checking for the default gateway, you can ping a site such as to test for connectivity? Or maybe include a setting “Do not check for Internet connectivity on VPN” which can bypass this requirement?



        • Nov 30, 2022 - 4:07 AM - Hans - Author: Comment Link

          No worries Daniel.
          I wouldn’t expect any company to change their settings just for one application, and … it seem rather common for VPN users.

          Checking Google would not be a reliable way to do this. I’ve worked with VPN (for work) in the past where they blocked Internet access for security reasons.
          I’ll try and see if I can find a way to do network detection, and keep “Do not check network connectivity” as an option.
          I already found that VPN detection is not very reliable (eg. OpenVPN detected in one location, WireGuard in another etc) – but I think that should be transparent anyway.

          I may call for your (and Bernd) help in case I find a trick to do network detection.



    • Nov 30, 2022 - 5:14 AM - Hans - Author: Comment Link

      Hi Bernd and Daniel,

      in an attempt to detect if there is any networking going on under VPN, could either of you post the output if you run this command in Terminal while your VPN is active?
      I do not have access to a setup that at times runs VPN only like you guys do.

      ifconfig | grep 'status: active'

      I’m hoping to see something like this:

       status: active


      • Nov 30, 2022 - 7:15 AM - Daniel Comment Link

        I am seeing two “status: active” entries on VPN.



      • Nov 30, 2022 - 2:12 PM - Bernd Comment Link

        Yep. I see status: active.



      • Dec 1, 2022 - 3:42 AM - Hans - Author: Comment Link

        Awesome! Thank you for testing this!

        This one is trickier: just run:


        This will produce a much larger list – would you be willing to email me that list (just to not clutter this comment section – webmaster at tweaking4all dot com).
        Or, if you know what you’re looking at, mention the devices with the “status: active” statement?
        (device names look like something like these “utun0:“, “p2p0:“, “en0:” or “bridge0:“)



  • Nov 28, 2022 - 11:52 AM - Moondiver Comment Link

    I have tried the latest version 4.0.1, but I have the problem that my created shares are not saved. After a restart they are gone. What am I doing wrong?

    Then another question, my NAS always boots up at a certain time. How do I configure ConnectMeNow to always check if the NAS is already on and establish the connection.

    Many greetings,



    • Nov 29, 2022 - 12:04 PM - Hans - Author: Comment Link

      Hi MM,

      Ehm … configs that do not save … that’s a new one. I have not experienced this.
      Can you see if this file is being created?


      As for connecting to your NAS, you have a few options there. 
      I guess it depends a little on your workflow.

      Probably the most reliable way would be:

      Under Advanced Settings, of a defined share, check the options “On Server IP appear” and optionally “On Network Change” (nothing else needs to be set with these 2).

      As soon as ConnectMeNow sees you NAS because of this, it will start the mount procedure for this particular share.
      The following options are part of that procedure. You can use them as you see fit, to see what works the best and most convenient for your purposes.

      – Setting Mount delay to the number of seconds it takes your NAS to be “online” in case your NAS is rather slow in getting its services up and running.
      – Set “Mount attempts” to more than one, not sure which one would work best for your setup, just so mount failures are tolerated a few times.Say it takes your NAS 10 seconds from cold start to being available for mounting, then this would be a good value to use.

      I’d play with those options first.

      If you’re the only user, you could consider using Wake On LAN before mount instead of the power schedule you’re set for your NAS. But that’s totally optional of course.
      Note that PING Before mount may not be very useful in this case – ConnectMeNow has already seen the server because of the “On Server IP appear” setting. 



      • Nov 29, 2022 - 11:32 PM - Moondiver Comment Link

        Hi Hans,

        It’s a little curious. But the INI file was created. Nevertheless, after a restart the set up share is no longer available.

        MacOS: 13.0.1
        Apple Mac Studio



      • Nov 30, 2022 - 4:08 AM - Hans - Author: Comment Link

        Oh wow, that is super weird.

        Can you create a share or two, close the application, and send me that file -(webmaster at tweaking4all dot com?
        (remove sensitive info like username/password from the file)



        • Dec 1, 2022 - 4:20 AM - Eugenio Comment Link

          Hi, I have the same issue… Created shares are gone after a restart.

          I have a 2021 MacBook Pro with M1 Pro and Ventura 13.0.1



        • Dec 1, 2022 - 6:58 AM - Hans - Author: Comment Link

          Hi Eugenio – thank you for confirming.
          I’m testing on a 2021 MacBook pro M1 Max with Ventura 13.0.1 as well.

          Can you verify the file is begin created and if you open it with a text editor, see what is in the file that may resemble an entry of your share(s) – I don’t mind taking a look, if you’re comfortable emailing me the file.

          – Are either of you the only user on your Mac?
          – Do you guys maybe share the config with other Macs?

          The config file:



          • Dec 1, 2022 - 7:43 AM - Eugenio Comment Link

            Hi Hans thank you for your quick reply

            I tried quitting ConnectMeNow before restarting and it works fine, shares are saved.

            So the issue is only when restarting without without quitting the app.

            The config file is created but if I restart the shares are not saved in it, if I quit ConnectMeNow the shares are getting saved in the config file.

            I am the only user on this mac and the config isn’t shared

            Hope this helps


          • Dec 1, 2022 - 7:54 AM - Hans - Author: Comment Link

            Excellent find! This is really good info. Now I have to look where I goofed up. 


  • Dec 1, 2022 - 11:03 AM - Moondiver Comment Link

    I can confirm the behavior that Eugenio described. Quitting before restart save the shares.



    • Dec 1, 2022 - 11:32 AM - Hans - Author: Comment Link

      Thanks for confirming! Much appreciated. 
      I have it fixed in the next release. 



      • Dec 1, 2022 - 1:32 PM - Moondiver Comment Link

        That’s great  

        I have found something else.
        I have set up 2 shares to be mounted when the server is visible on the network. For each share I have set up a delay of 60 seconds. When I restart the computer, the first share (first in the share overview) is mounted after 70 seconds, but the second only after 220 seconds.

        Another point:
        Under Advanced Options I cannot select default Mount Path but only Custom Path. In the settings under Perferances Mount Path is set to default.

        Translated with (free version)



      • Dec 4, 2022 - 4:05 AM - Hans - Author: Comment Link

        Thanks for reporting Moondiver!

        I’ll fix these with the next release, hopefully in the next few days! 


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.