Page 1 of 1

Quickly connect Network shares on a Mac with ConnectMeNow

Quickly connect Network shares on a Mac with ConnectMeNow
   153

In this day and age we are more network connected than ever before – at home and at work. Some of us have network shares on their computers, want to access company network shares, or have a dedicated file server or NAS (Network Attached Storage) to store our shared information or make our backups.

Unfortunately, at times anyway, it can be rather cumbersome under Mac OS X to connect to those “shares” (also known as the so called mounted “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 SMBCIFSFTP, SSHWebDAV, NFS or AFP, and I’m not even mentioning the need to enter a username and password on protected shares.

Additionally, Wake On Lan is being supported as well.

I do have a NAS and I do have several shares on that device and … I just got freakin’ tired of going through each step over and over again. So, instead of complaining, I started looking for an application that would just that – and didn’t find one to my liking. So I just created one … free for all … enjoy!




Quickly connect Network shares on a Mac

So there it is … my network application, fully written in Lazarus Pascal. So far I have been very impressed with lazarus Pascal and until now Objective-C and SWIFT have not been able to get close to the conveniences it offers. I have to admit that my experiences with Apple’s prefered languages are somewhat limited, and each attempt I do I just get more and more confused and annoyed … anyone willing to coach me, please contact me … 

Anyhow, ConnectMeNow is a small application to quickly connect Network Shares on your Mac.

Again … Yes, your Mac can natively already connect to network shares, but it’s rather cumbersome if you ask me.

ConnectMeNow “lives” in the Mac’s menu bar – you know, the one you always see on the top of your [primary] screen – and shows a little drop down list where you can pick the predefined share you quickly wish to open.

It can start with your Login Items, you can define multiple shares, it can mount selected shares at startup, or on demand, use login credentials if so needed, supports several protocols (SMB, AFP, CIFS, FTP, SSH, WebDAV), and it won’t bother you when you’re not using it.

Without too much fuzz … you can download it here, straight from Tweaking4All, it’s FREE …
If you’d like to support me in these kind of small apps, which is VERY MUCH appreciated, then please feel free to look at the donation options on the top left of this page. The easiest and cheapest way to support me is by shopping at Amazon by using this link – it won’t cost you a cent.

DOWNLOAD - ConnectMeNow 

Platform: Mac OS X
Filename: ConnectMeNow.dmg
Version: 1.7.9
Size: 2.1 MiB
Date: August 2, 2016
 Download Now 

Upgrading from a version prior to version 1.5 … 

Version 1.5 introduces a new format to store username and password in an encrypted way. The old way occasionally would cause errors.

As of version 1.5, ConnectMeNow will try to automatically update your config to the new format, which in 99% of the cases will work very well.

However … if you run into an error message, close ConnectMeNow, delete the config file (~/.config/ConnectMeNow.cfg), and restart ConnectMeNow.
Unfortunately, in this case, you will have to re-enter your servers. Our apologies for the inconvenience.

Retina support 

For users with Retina a monitor or display, you can execute the following in Terminal to make ConnectMeNow look better. You’ll have to close ConnectMeNow, execute the following line, and start ConnectMeNow again:

defaults write com.tweaking4all.ConnectMeNow AppleMagnifiedMode -bool no

 

The Manual of ConnectMeNow

(included with the application, click “Help and About…” to read it)

The new ConnectMeNow Icon

The new ConnectMeNow Icon

ConnectMeNow offers a menu bar item, supporting the regular Mac OS X theme and the so called “Dark Theme”, to quickly open your favorite servers or server shares and supports SMB, AFP, FTP, SSH and CIFS. Note that CIFS is outdated and obsolete, and it’s better to use SMB instead, but some users still insist on using it and your Mac supports it (although I have noticed that CIFS mounts automatically revert to SMB).

ConnectMeNow in your MenuBar

ConnectMeNow in your MenuBar

Overview

 

Install ConnectMeNow

Simply open the DMG file and drag the application to yourApplications” folder and double click it from the “Applications” folder to get started.

Starting ConnectMeNow for the First Time

Starting ConnectMeNow for the first time is easy; simply double click the ConnectMeNow icon in your “Applications” folder. Select the “Preferences” option from the drop down menu to get the following screen (I have already added some shares):

ConnectMeNow - Preferences Window

ConnectMeNow – Preferences Window

There are a few basic functions you’ll find here, the following 2 options I’d recommend to have them checked, but it’s completely up to your preferences:

• “Start ConnectMeNow at computer startup“, will add ConnectMeNow to your Login Items (if checked), or remove it from your Login Items (when unchecked), so it can start when you turn your computer on or when you log in.

• “Mount volume(s) quietly“, makes it that ConnectMeNow, if checked, will not show any messages when mounting a share (volume), unless an error occurs.

• “Force un-mount on Quit or Shutdown“, if checked, will unmount all volumes on your Mac (except your root/harddisk of course) when you close ConnectMeNow (or shutdown your computer).

• “Detect network presence before mounting“, is useful for laptop users that are on the road often. This will detect the existence of a Network Connection before anything gets mounted or connected to.
– “Wait for X seconds after 1st fail“, will wait for X (default: 3) seconds to try to detect a network again, for networks that not up and running right away.
– “No error message when detecton fails“, will not show an error message when a Network Connection cannot be found.

 

The button “Quit” will terminate ConnectMeNow,
and “Close Window” will hide the preferences window but ConnectMeNow remains available in the menubar.

Clicking the “Tweaking4All” logo will open our web page …ConnectMeNow - Main Window

ConnectMeNow Menu

When you click the ConnectMeNow icon in the menu bar of your Mac, two possible menu’s might appear:

• Regular Menu

ConnectMeNow - Regular

ConnectMeNow – Regular

In this menu example, the first 6 items are defined shares or volumes. Here you can also access “Preferences“, “Help and About…” (you’re reading it) and “Quit ConnectMeNow“.ConnectMeNow - Regular Menu

ConnectMeNow - Preferences is Open

ConnectMeNow – Preferences is Open

When the Preferences window is opened, you will see a menu like displayed below.
The reason for this is that the menu has to (potentially) be rebuild when you make changes to your list of defined shares.

Click “Close Preferences” to close the Preferences window (changes are saved automatically). Click the menubar icon again and the regular menu will appear.

Defining Servers or Shares

To define a “server” or “share” for ConnectMeNow, simply press the “Add” button.
The details for the selected item in the “Defined Shares” list will appear on the right, where you can review or edit your item.

Note that you can test a share right away by clicking “Open“, note that the lack of a “Apply” or “Save” button is because ConnectMeNow will save your changes instantly.

The button “Remove” removes the selected item, and the button “Clear” will remove all items in the list.

The “Sort” button will try to alphabetically sort your shares, based on menu name.

• Name in Menu (by default automatically)

Here we optionally can define an alternative name as it will be shown in the menu.
When “Automatic Naming” is enabled, ConnectMeNow will try to use the Server Address and last directory of the Server Path.
Uncheck this option if you want to type something else.

Next to that you will see the “Add Server Type” option – which adds the protocol abbreviation before the menu name. You might find that practical to identify which connection type you’re looking at. The icons in the menu indicate this as well, but maybe you prefer to see this as text.

• Server Type (required)

ConnectMeNow supports the these basic server types:

windows8  SMB (default)

SMB, also known as “Samba” or “Windows share”, is the most commonly used type. Most NAS and Server models utilize this protocol. This is also the protocol when you share a directory on your Windows PC.

apple  AFP

Also known as the Apple File Protocol, is a typical Apple protocol – which even Apple seems to be abandoning – and is not used very often on servers unless you have a share made on your Mac or MacOS X Server.

windows  CIFS

This is the outdated and obsolete “Windows Share” variant, replaced by the newer SMB protocol.
Only use this if you think you have a need for it. Typically SMB sill perform better and be more compatible.

cloud  FTP

This is used for FTP connections, for example to your webserver. If you don’t know what FTP is, then you probably won’t need it.

nfs  NFS

NFS, or Network File System, is commonly used with Unix/Lunix like systems, which can include your NAS.
If you don’t know what NFS is then this is probably not for you. Keep in mind that pretty much any NAS defaults to SMB, so the use of NFS is only needed if you specifically set your NAS to use this protocol.

webdav  WebDAV

WebDAV, or Web Distributed Authoring and Versioning, allows you to access shares over http or https (both are supported). WebDAV, provides a framework for users to create, change and move documents on a server, typically a web server or web share. When accessing a WebDAV share the first time, especially when using HTTPS, you might get a certificate warning. This is common when selfsigned or outdated SSL certificates are being used. If you trust the source, then just click “Continue” and this question will not be asked again.

terminal  SSH

Although technically not a “share” or “volume”, I’ve added SSH anyway. I use this quite often myself to access my webserver or NAS through the Terminal. With this one too: if you don’t know what SSH is, you will not need this option.

Please keep in mind that we use a script to automatically login, which might reveal your password even though the script only exists for a fraction of a second. So please only use in an environment that you trust.

• Server Name or IP (required)

With Server Name or IP we mean just the server network name or IP address of the server, without the share path.
Examples:

192.168.1.100
myserver

• Shared Path (optional – only for SMB, CIFS, FTP, WebDAV and AFP)

With a Shared Path we mean the path of a share defined on a given server.
With most servers you define a shared directory which is accessed, versus just the server. For this to work you will need to enter the path of your shared directory.

If no Server Path has been defined, it will trigger a dialog, asking you what share to open on the server instead of directly opening a given share. This can be convenient if you have a server with multiple shares that you only occasionally open.

Examples:

/myshare/
myshare
/path/to/my/share/
path/to/my/share

The path for “//192.168.1.100/myshare” is “myshare” (“/myshare” and “/myshare/” work as well), and the Server Name (IP in this case) is “192.168.1.100“.
The path for “//myserver/path/to/my/share” is “path/to/my/share/” (“/path/to/my/share” works as well), and the Server Name would be “myserver“.

• SSH Port (required only for SSH)

When the selected protocol is SSH, then the Shared Path will be replaced with SSH Port, the IP Port number used for your SSH connection. Default this is port 22.

• Connect when ConnectMeNow starts (optional)

If checked for this particular share, ConnectMeNow will automatically and quietly try to mount this share as soon as ConnectMeNow starts.

• Connect with Credentials (optional)

Some shares are available to all, some just to particular users. If your share is protected with a username and password, then this option is needed.
Enter username and password so ConnectMeNow can connect with your login credentials.

Note : ConnectMeNow will store your password encrypted, you can verify this by opening “~/.config/ConnectMeNow.cfg” with a Text editor.

• Wake On Lan (optional)

WOL, or Wake On LAN, is used to “wake up” a NAS or server by sending a so called “magic packet”. Your server or NAS must have Wake On LAN enabled for this to work!
In this case, a Wake On LAN signal can be send before ConnectMeNow tries to mount a share.
Unfortunately, Wake On LAN needs the MAC Address of the network connection of your server or NAS.
With a little trickery, the MAC address can be retrieved based on the IP address or network name of your server, but this works only if the server is in your own (home or business) network, connected and running. Click “Find MAC address” to see if ConnectMeNow can find the proper MAC address. If this fails, you could try again, or manually enter the MAC address.

Additionally you can enter the UDP port that should be used for sending the WOL signal – default this is port 9.

You can click “Test Wake On Lan” to see if it works.

After sending a Wake On LAN signal, ConnectMeNow will wait 0 or more seconds for the server to actually wake up, before it tries to connect to the server.
It will use a PING to see if the server is awake. The wait time is a “time out”, so it will wait a maximum of X seconds.
If the server can be connected to earlier, then ConnectMeNow might mount earlier than the set wait time.

Opening a Share or Volume

Now that we know how to start ConnectMeNow and how to define our share(s) or volume(s), opening a share is easy. Simply click the ConnectMeNow icon in the menu bar of your Mac and select the volume or share you wish to mount.

If the chosen share was already mounted: no worries – nothing will happen.

If there is a problem with the share you wish to access, an error message will appear. Typically this is related to being unable to connect to the server or a typo in the Server Path. When defining a share, use the “Open” button to test your share.

Known Issues

Every program has it’s weaknesses and/or flaws.

  • Preferences Window with multiple desktops (Spaces)

Right now, it’s a known issue that when you uses “Spaces” on your Mac and you have multiple desktops (Spaces) defined, that ConnectMeNow will keep opening it’s preferences window on the screen where you opened the preferences for the first time in this session. So at times, when using multiple desktops, you might have to go find that preferences window.

  • Dark vs Light Theme

Another issue might be the icon update for those who switch theme (regular theme, versus “Dark” theme) while ConnectMeNow is running. The icon will not update until you either open “Preferences” or restart ConnectMeNow.

Uninstalling ConnectMeNow

Uninstalling ConnectMeNow is easy as well. Simply drag the ConnectMeNow application into the trashcan.

If you’d like to remove the preferences as well, then locate the file “/Users/<username>/.config/ConnectMeNow.cfg” and move it to the trash as well.

Note that the “.config” directory is by default hidden.

A quick trick in Terminal will remove the preferences as well:


rm ~/.config/ConnectMeNow.cfg

Change Log

v1.0 – Initial release

v1.1 – Bug Fixes

  • Fixed bug when passwords had special characters.

 

v1.2 – Added Features

  • Added support for FTP
  • Added support for SSH (only use on computers you trust, temporary script might reveal your password)
  • Added menu icons to identify server type (protocol)
  • Added force unmount on closing ConnectMeNow
  • Added option to add server protocol in Auto Naming
  • Added option to sort list of shares

 

v1.3 – Minor cosmetic changes

v1.4 – Added Feature

  • Detect network and optional delay added (thanks Wolfgang for testing!)

 

v1.5 – New Config File Format, Optimized binary size

  • New INI format that properly stores encrypted data
  • Binary has been reduced by about 40%

 

v1.51 – Refined the Detect Network feature

  • Network Detection will optionally not show an error message when a network cannot be found.

 

v1.6 – Added WebDAV support, improved protection when revealing passwords, and a new app icon

  • By request (and support of) of Whistle Master, I added support for WebDAV (HTTP and HTTPS).
  • When trying to reveal a password of a connection, a admin confirmation based on an admin account of your Mac (sudo etc) will be requested.
  • New ConnectMeNow icon
  • Server alias name entry bug fixed

 

v1.7 – Added Wake On LAN and NFS support

  • Added support for NFS.
  • Added support for Wake ON LAN.
  • Added function to retrieve MAC Address (might not always work) for Wake On LAN.
  • Minor cosmetic changes.
  • Minor code changes, making it easier to add support for other protocols in the future.
  • New icon for SSH (better visual)
  • Added ConnectMeNow version number in the menu

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.

Comments


There are 153 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.

  • Sep 22, 2015 - 9:12 AM - hans - Author: Comment Link

    UPDATE (v1.1):

    Wilfred tipped me on a small issue when usernames and/or password have special characters.
    This version 1.1 should resolve this issue.

    Reply

    hans

  • Sep 23, 2015 - 2:55 AM - Wolfgang Comment Link

    Perfect. Thanks Hans for another great piece of software!

    Reply

    Wolfgang

    • Sep 23, 2015 - 3:18 AM - hans - Author: Comment Link

      Thanks Wolfgang, for taking the effort to post a “thank you”!
      That is very much appreciated and makes it worthwhile writing little apps like this … 

      Reply

      hans

  • Sep 23, 2015 - 7:47 AM - Asger Comment Link

    Hi.

    Looks like at great little tool.

    Could you maybe make it possible to choose between SMB 2 and 3?

    I also have a problem with Macs not being able to shut down because SMB-connections hang. Could you maybe make a force-dismount option?

    Best regards, Asger

    Reply

    Asger

    • Sep 23, 2015 - 8:01 AM - hans - Author: Comment Link

      Hi Asger!

      Thanks for the compliment.

      As for choosing between SMB2 and 3, I doubt Apple provides the means for that, unless I’d integrate something like SMBUp, which basically replaces Apple’s SMB implementation with the latest Samba implementation. Seems like a lot of work though and some serious OS changes.

      As for force-unmount ,… well, that might be something to look into.

      I could make that an option, but the only way I know how to unmount a volume is with:

      umount /Volumes/<volume name/

      Does that “force” the unmount enough for the problematic volumes?
      Also: problems with unmounting could be related to open files/apps. Not sure if you have anything running that might cause that?

      You could also try:

      umount -fA

      Which should force (-f) all Volumes (-A) except the root drive.
      Let me know if any of these work, if so, then I could try to implement that on the “OnClose” event of my app. 

      Reply

      hans

    • Sep 23, 2015 - 8:16 AM - hans - Author: Comment Link

      If “umount -fA” worked for you (do it just before you shutdown your computer), then please let me know and I’ll implement it.

      Reply

      hans

      • Sep 23, 2015 - 9:09 AM - Asger Comment Link

        Thanks.

        I’ll let you know, but it it is a bit difficult for me replicate the error, as it only happens from time to time…

        Trying hard to pinpoint when it it is happening.

        Asger

        Reply

        Asger

      • Sep 23, 2015 - 9:47 AM - hans - Author: Comment Link

        Maybe it’s an idea to run “unmount -fA” each time you shutdown your computer and over time see if the problem did reoccur or not …? Just a though – I know it can be difficult to “debug” such a problem.

        Reply

        hans

        • Oct 21, 2015 - 10:25 AM - Asger Comment Link

          Unfortunately the script doesn’t help…

          We have used it now for weeks without success :-(

          But thanks for your input.

          /Asger

          Reply

          Asger

        • Oct 21, 2015 - 1:30 PM - hans - Author: Comment Link

          Hi Asger,

          Did you try the latest version, with the auto unmount option?

          Reply

          hans

    • Nov 29, 2015 - 11:04 PM - Luke H Comment Link

      Hello

      I also suffer this problem!  I think I narrowed it down to:  any time you connect to an smb:// share on another Mac running ElCapitan, then your client machine will hang with endless “spinning wheel of death” during restart or shutdown. Even if you disconnect the share before restarting. If you connect with cifs:// instead (which forces SMB1 protocol) you will not experience the hang.  I am trying to narrow this bug down myself but as of now it seems it’s just a bug in Apple’s SMB protocol. I even updated to the beta-4 of 10.11.2 (15C47a) and the bug still exists.

      Reply

      Luke H

  • Oct 6, 2015 - 4:45 AM - FreeMan35 Comment Link

    I’m using zsh, your application use just default terminal application. Ist it posible make optional this ? or get it from system
    Thank you

    Reply

    FreeMan35

    • Oct 6, 2015 - 5:09 AM - hans - Author: Comment Link

      Hi FreeMan35!

      I didn’t think folks would use a different shell – doh! 
      Are there any other shells out there, commonly used on the Mac, that you’re aware of?
      I could add this as an option in a next version, would be nice to have a relatively complete list then. 

      I’m assuming you’re referring to SSH connections, right?

      Reply

      hans

      • Oct 6, 2015 - 8:31 AM - FreeMan35 Comment Link

        Yes, I’m test just ssh connection. and I think I missunderstood,sorry. Your application not “mount” ssh connection. just quick connection. I thinked work like shfs.

        Just let you know, I perfer zsh with “.oh-my-zsh” I added profile for ssh and I defined shortcut.

        suggestion to lazy (like me :) )  mc (midnight commander [from brew]) is support ssh connection, can easyly copy/move site to site

        $> echo $0

        $>echo $shell

        commands give shell name in terminal

        thank you

        Reply

        FreeMan35

      • Oct 7, 2015 - 2:11 AM - hans - Author: Comment Link

        Thanks Freeman35,

        Yep, no mounting for SSH, just an attempt to quickly login. 
        Thanks for pointing out SHFS, I had not heard of that yet. It seems available under MacOS X, but requires a few “extras” like “Fuse for OSX“. In the near future I’ll play with it, but it not likely become part of ConnectMeNow – I like to keep these kind of apps as compact as possible, and I always like to avoid 3rd party apps.

        Thanks for the Shell tip too! 

        Reply

        hans

        • Oct 7, 2015 - 7:40 AM - FreeMan35 Comment Link

          please let me know about play result :) I have fuse for osx, just for test I tried only one time, and my result is not mount it :( but not try much, ‘cos not I have much time. on El Capitan

          Yes, your app. “ConnectMe Now” so helpfull. A few improvement been much better ofcourse. usually unix experts wantto use terminal, yes this good and best way, but if need a copy(s) file, why have to write many keyboards types? any tools (my choose is Double commander on osx) do this via just “F5” key.

          Thank you for answer, and I waiting good new from you ;)

          Reply

          FreeMan35

        • Oct 7, 2015 - 8:20 AM - hans - Author: Comment Link

          I’d like to improve the SSH shell opening, and maybe in the future support Fuse.
          For now, Fuse/SHFS support might have to wait as it’s not very common.

          What is the mount line for SHFS? (with /usr/bin/osascript and with /usr/bin/open)
          Not even sure if there is an easy way to detect SHFS (if it’s on the system or not)?

          Reply

          hans

          • Oct 8, 2015 - 1:38 AM - FreeMan35 Comment Link

            I found new links
            https://github.com/osxfuse/osxfuse/wiki/SSHFS
            https://blogs.law.harvard.edu/acts/2013/11/08/the-newbie-how-to-set-up-sshfs-on-mac-os-x/
            this links give more info for you I think ‘cos its has a source code
            http://macfusionapp.org/
            I wrote I’m not exprience on this, I only one try then remove it, ‘cos not work on my el capitan.

            FreeMan35

          • Oct 8, 2015 - 1:50 AM - FreeMan35 Comment Link

            Sorry I forget add.

            El capitan Platform Policy is:
            /system
            “/ bin” , “/usr” , “/sbin”  this folder permissions is 755 and
            can not change that.
            “[~]/Library” , “/usr/local” , “/Applications” are available to
            develeopers

            and “which appname” command returns  the pathnames of the files (or links) which would be executed in the current environment. can be more one lines, this mean 2 same file can be different search path.

            “find” command is give as well, but not fallow any environment, looking for all (gived) path

            FreeMan35

          • Oct 8, 2015 - 2:07 AM - hans - Author: Comment Link

            One of the reason why I have been weary about using SHFS/MacFusion is because 
            1) I’m already using Paragon tools for NTFS and Ext3
            2) These tools are pretty invasive to your system
            3) SHFS depends on HomeBrew, which is often a few steps behind

            (even though I love the HomeBrew initiative)

            Implementing the code myself is a bit beyond of what I’m trying to accomplish with ConnectMeNow though.
            I did look around for alternatives, but there is no “easy” way to implement this.

            If there is a specific mount line for it, then I could make it available if ConnectMeNow detects that SHFS is available. You know what I mean? 

            hans

          • Feb 7, 2017 - 9:13 AM - hans - Author: Comment Link

            Since I’m rebuilding ConnectMeNow (v2 in alpha test phase), I was wondering if you upgraded FUSE to the latest version (seems it might work under Sierra). If so, what would be the mount statement for this?
            (FUSE conflicts with Paragon Ext/NTFS so I have not installed it yet)

            See also my other commend from today…

            As an example, mounting a Samba share is done with ‘/sbin/mount_smbfs’ and the command line parameters would look like this:

            /sbin/mount_smbfs //[$domain;][$username[:$password]@][$server][$path] [$mountpoint]

            The following parameter variables are available: $domain, $username, $password, $server, $path, $port, $mountpoint

            hans

    • Oct 6, 2015 - 5:17 AM - hans - Author: Comment Link

      I’ve been looking a bit at my code, and I’m not quite sure where and when you’d like to use zsh. 

      Reply

      hans

  • Oct 15, 2015 - 3:43 AM - Wolfgang Comment Link

    Hello Hans, I am seeing problems with El Capitan. When the networks are not present, I get an error message and even when the networks are present (but no yet connected) it will fail to connect.

    Any suggestion what I should try? I am using AFP with the first two General Options checked. Thanks!

    Reply

    Wolfgang

    • Oct 15, 2015 - 1:18 PM - hans - Author: Comment Link

      Thanks Wolfgang for reporting.

      That’s interesting, I’ve developed it under El Capitan, but then again, I’m not an AFP user.
      Can you post the error message?
      Do you use a username and password?
      In the meanwhile I’ll try to setup an AFP share on my NAS and see what problems I run into.

      Reply

      hans

      • Oct 16, 2015 - 2:30 AM - Wolfgang Comment Link

        Hello Hans, 

        yes, I use username and password. The error message at start-up when it should connect the servers is (translated from German) “During the connection with Server “Tathros” an error ocurred. Possibly, the server is not present or currently unavailbale. Check the server name or the IP address ot the network connection and try again.”

        I am not using SMB, so I wouldn’t know.

        Reply

        Wolfgang

        • Oct 16, 2015 - 2:31 AM - Wolfgang Comment Link

          and: if I open finder and look under networks, it’s there and I can connect manually.

          Reply

          Wolfgang

      • Oct 16, 2015 - 4:21 AM - hans - Author: Comment Link

        Does this happen every time when you try to open the share through ConnetMeNow, or does it only happen when ConnectMeNow tries to connect during boot of your Mac?
        I’ve had issues (not ConnectMeNow specific) that my network connection sometimes is to slow and not yet connected when ConnectMeNow starts. A few seconds later it simply works because at that time the network is up and running.

        If that is the case, then I should probably add a delay at startup, waiting for a network to appear before trying to connect.

        If it happens all the time, then I’ll try to create a debug version so we can trace where it goes wrong.

        Reply

        hans

        • Oct 16, 2015 - 4:30 AM - Wolfgang Comment Link

          Strangeley enough, it does happen every time even if the network drives are already connected.

          Reply

          Wolfgang

        • Oct 16, 2015 - 4:43 AM - hans - Author: Comment Link

          Can you trying to use the IP address instead of the servername? (as a test)

          Reply

          hans

          • Oct 16, 2015 - 5:56 AM - Wolfgang Comment Link

            Ok, we are getting to the root of the problem! Changing the server name to the IP works fine when everything is running and I start CMN. No error messages anymore. However, when I have it activated at start up, it gives an error message for the first one but connects to the second one fine. So, the idea of having a short delay would possibly fix this.

            Wolfgang

          • Oct 16, 2015 - 6:32 AM - hans - Author: Comment Link

            Ah, that’s kind-a what I run into in my setup occasionally as well.
            Sometimes the network is not “up” yet or it cannot find a DNS entry for “myserver” but works perfectly fine with an IP address.

            I’ll have to do some digging, see if I can come up with a way to detect if any kind of network is already up and running.
            Maybe add a check that a server name is found in the DNS as well.
            This will take a little bit though,… 
            But I like it …!

            hans

          • Oct 17, 2015 - 6:44 AM - hans - Author: Comment Link

            Hi Wolfgang!

            I’ve added the option to check for any existing networks (better said: existing nameserver so it can resolve the server name).
            If that fails, it will wait by default 3 seconds, and try again. This value (3) can be changed in the preferences.
            If it fails again, then an error will notify you about that.

            Please give it a try, you can find it here.
            Is this helpful or resolving the issue?

            hans

          • Oct 17, 2015 - 6:53 AM - Wolfgang Comment Link

            It works! Thanks Hans!

            Wolfgang

          • Oct 17, 2015 - 6:54 AM - hans - Author: Comment Link

            Awesome! 

            Thanks for testing, it’s very much appreciated!

            hans

      • Oct 16, 2015 - 4:23 AM - hans - Author: Comment Link

        p.s. thank you very much Wolfgang for your help in testing this – it’s very much appreciated!

        Reply

        hans

    • Oct 15, 2015 - 1:41 PM - hans - Author: Comment Link

      p.s. are SMB shares working OK?

      Reply

      hans

  • Oct 17, 2015 - 7:39 AM - hans - Author: Comment Link

    UPDATE v1.4:

    This is a minor update, for those experiencing connection issues (thanks again to Wolfgang for his testing efforts!).
    It is now possible to add a minor delay when mounting a share, which is practical when your network is not right away available.

    Reply

    hans

  • Oct 18, 2015 - 9:35 AM - Rogier Comment Link

    Hello Hans,

    Great tool! I noticed a glitch when I tried to login (AFP) to my Qnap share as admin. It works the first time, but when I quit ConnectMeNow and restart (or when I restart my Mac), the tool won’t open. 

    Error message says: Stream read error. Press OK to ignore and risk data corruption. Press Cancel to kill the program. 

    I have to delete the config file and start from scratch. This all doesn’t happen when I login as another user on my Qnap.

    Any idea?

    Thanks!, 

    Rogier

    Reply

    Rogier

    • Oct 19, 2015 - 2:38 AM - hans - Author: Comment Link

      Hi Rogier,

      Thanks for the compliment, and thanks for taking the time to post an issue 

      that’s … ehm … interesting.
      Are you using any special characters in your username and/or password?

      Reply

      hans

      • Oct 19, 2015 - 7:34 AM - Rogier Comment Link

        Yes, in passwords. But also in the user password. The only differrence seems to be the admin login on the Qnap

        Reply

        Rogier

      • Oct 19, 2015 - 9:26 AM - hans - Author: Comment Link

        I’ll try to find out what the problem could be.
        Sounds like it’s problem with reading the encrypted password from the config file.
        Not sure yet how to resolve that.

        But I’ll do a little digging.

        p.s. The config file is plain text, if you remove the lines “Username: and “Password” (including the encryted “garbage”), and save it, you’d only loose username and password.

        Reply

        hans

      • Oct 19, 2015 - 10:34 AM - hans - Author: Comment Link

        Hi Rogier,

        I’ve created a 1.5 beta version (you can download it here). 

        It’s a ZIP file and this version will try (but probably fail in your case) to convert the old config to the new format. It seems INI files do not like encrypted gobbledygook … so I converted it to “normal” characters.

        If at first start you get an error message: delete the config file, and restart the application.

        Please let me know if it resolves the issue … 

        Reply

        hans

        • Oct 19, 2015 - 2:41 PM - Rogier Comment Link

          You’re right! It does run fine now, when I login as admin. Had to delete the config-file though. Strange that the error only happens on admin login… 

          Thanks!

          Reply

          Rogier

        • Oct 20, 2015 - 3:57 AM - hans - Author: Comment Link

          Hi Rogier,

          thanks for testing this version! 

          What appears to happen (in rare occasions) is that the encrypted password or username will generate an illegal character in the INI file, which pretty much makes it unreadable, or better said: The encrypted data is not being read right which causes an error (stream error) when trying to decrypt.

          I’m glad it’s resolved. I will post a new release today. 

          Reply

          hans

  • Oct 20, 2015 - 9:42 AM - hans - Author: Comment Link

    UPDATE v1.5:

    First of all: Thank you Rogier for finding the bug and testing the new version.

    This new version uses a better way to store encrypted data, and the binary has been reduced in size by about 40%.

    Reply

    hans

  • Oct 25, 2015 - 5:33 AM - hans - Author: Comment Link

    UPDATE 1.51

    Based on an idea of Wolfgang; if Network Detection fails (ie. laptop users that are not connected to a network), ConnectMeNow can optionally be set to be quiet about it, so you will not see an error message when it fails to find a network.

    Reply

    hans

    • Oct 28, 2015 - 11:47 PM - Wolfgang Comment Link

      Works fine so far. Haven’t detected a problem yet. Thanks Hans!

      Reply

      Wolfgang

    • Oct 29, 2015 - 2:25 AM - hans - Author: Comment Link

      Thanks for the feedback Wolfgang! And … thanks for helping out. 

      Reply

      hans

  • Dec 9, 2015 - 7:50 AM - Asger Comment Link

    Any chance for Kerberos authentication? :-)

    Reply

    Asger

    • Dec 9, 2015 - 8:04 AM - hans - Author: Comment Link

      Hi Asger,

      I most certainly can look into that – but I’ll admit that I have never used it myself.
      Any suggestions where I can find more info/details?

      I know it’s a method of authentication, but that’s as far as I’ve ever looked into it.

      Reply

      hans

      • Dec 21, 2015 - 8:57 AM - Asger Comment Link

        The cool thing about Kerberos is that if you change your Active Domain password, you won’t have to update every related apps’ passwords. 

        I’ll see if I kan dig up some useful info.

        /Asger

        Reply

        Asger

      • Dec 21, 2015 - 9:30 AM - hans - Author: Comment Link

        Yeah, I’d have to know a bit more about Kerberos, and I’d need to setup a test “server” to test connecting to it.
        Like I said: my experience with Kerberos is about zero 

        For connecting to servers, see if you can find how it’s done with the command line statements like “open” or “osascript” (AppleScript). For example, with the “open” statement (in Terminal):

        open smb://username:password@server

        I’d be very happy to implement Kerberos once I know how it’s done .

        Reply

        hans

      • Dec 21, 2015 - 9:37 AM - hans - Author: Comment Link

        I did find this article, but I’ll be te first to admit that I have no clue how this all works ….

        The MacOS X Man page that goed with kinit didn’t really tell me much more.

        Reply

        hans

  • Dec 21, 2015 - 3:26 AM - Stéph Comment Link

    Hi,

    I am trying to connect to a SMB server. Connect me know goes to the server but I receive the following comment. 

    “The folder “public” can’t be opened because you don’t have permission to see its contents.”

    The thing that is weird is that from a windows I can access with the same credentials… I have the new version of Yosemite and I get a little desperate…

    Please help me,

    Stéph

    Reply

    Stéph

    • Dec 21, 2015 - 8:53 AM - hans - Author: Comment Link

      Hi Stéph!

      First thing, before connecting with ConnectMeNow, is trying to connect to the SMB server through Finder. See if that work with the credentials you have in mind.

      ConnectMeNow uses Apple tools to connect, so if a connection fails (especially with SMB), then this would be a problem with authentication done by Apple’s implementation of SMB. Well, unless you’ve made a typo in ConnectMeNow of course, but I’m sure you’ve tried entering the password/username a few time already to make sure.

      If connecting through Finder works, then ConnectMeNow should work with the same credentials as well.

      Reply

      hans

      • Dec 21, 2015 - 9:00 AM - Stéph Comment Link

        Hi Hans,

        Thanks for the quick answer, well it doesn’t work with my finder either… It is a bit of a mess with this new Yosemite. 

        Anyway, thanks a lot,

        S.

        Reply

        Stéph

      • Dec 21, 2015 - 9:22 AM - hans - Author: Comment Link

        Hi Stéph!

        You’re most welcome!

        Apple’s SMB implementation has it’s flaws (to say it nicely haha).

        I have had users report that using CIFS instead of SMB seems to actually work better at times. So when trying to connect through Finder, you could try “Finder” -> “Go” -> “Connect to Server” and then enter the path (UNC) something like this:

        cifs://ipaddressserver

        Or with username and password:

        cifs://username:password@ipaddressserver

        (it’s early in the morning here, so I apologize upfront for typos )

        There are some command line alternatives (see also this article).

        As an alternative you could consider using SBMUp, which uses the official Samba implementation, but does come with some extra work to get the settings right.

        In the end, I assume anyway, we’d all like Apple to go back and support Samba again, natively … but it seems that Apple, the Samba team, or both, are not really willing to resolve or set aside their issues … so … we the consumer suffer the consequences. 

        Reply

        hans

  • Mar 25, 2016 - 7:46 PM - Mark Comment Link

    This really is a cool little nifty tool. Much appreciated!!! It works way better than other programs that I have previously used. I do have two questions about it. 1) Can the program be set to force an un-mount when there is a network change and the share is not available. 2)  The passwords for the network shares are encrypted. However, when you click “Reveal Password” it does not require an administrative password. It just shows it. My problem with that is if you let someone borrow your computer, they can see the password with out further authentication.

    Reply

    Mark

    • Mar 26, 2016 - 5:04 AM - hans - Author: Comment Link

      Hi Mark,

      thank you for the compliment and suggestions – those are always appreciated! 

      As for your suggestions:

      1) Your Mac should show a message when a certain network disappears, or shares are no longer available.

      2) That’s an excellent point, I did not think about that!
      I’ll add it to the “To Do” list! I’ll have to find a good way to do this, but for security reasons, I completely agree. 

      Reply

      hans

    • Mar 30, 2016 - 8:55 AM - hans - Author: Comment Link

      Hi Mark,

      I implemented your request to ask for admin password before revealing a password – enjoy 

      Reply

      hans

  • Mar 28, 2016 - 10:33 AM - Whistle Master Comment Link

    Really nice utility !

    I’m just missing the WebDav protocol with http(s) and it will be perfect :-D

    WM

    Reply

    Whistle Master

    • Mar 28, 2016 - 10:44 AM - hans - Author: Comment Link

      Thanks Whistle Master! 

      I’d love to explore working with WebDav, just do not have access to a WebDav share … (tried setting it up a long time ago on my webserver, but gave up pretty quick).

      Reply

      hans

    • Mar 30, 2016 - 8:54 AM - hans - Author: Comment Link

      Thanks again for helping out (providing WebDAV access and testing) 

      Reply

      hans

  • Mar 30, 2016 - 5:29 AM - hans - Author: Comment Link

    UPDATE:

    Added the Terminal statement to get ConnectMeNow to look better on Retina screens:

    defaults write com.tweaking4all.ConnectMeNow AppleMagnifiedMode -bool no
    Reply

    hans

  • Mar 30, 2016 - 7:41 AM - hans - Author: Comment Link

    UPDATE:

    Version 1.6 available!

    – WebDAV support added
    – Bug fix for Alias entry
    – Better protection for revealing passwords
    – SSH timeout increased
    – New Icon

    Reply

    hans

  • Apr 24, 2016 - 6:04 AM - Comec Comment Link

    The tool is great!!!

    A dream for me is, when there is an “wake on LAN” (wol) option with an additional waiting option.

    If have a NAS and the most time it sleeps… When I want to connect, I have to wake it with a another tool, must wait about 20 seconds and then I can connect to the share. :)

    Reply

    Comec

    • Apr 24, 2016 - 6:31 AM - hans - Author: Comment Link

      Hi Comec!

      Oh I like the idea of adding WOL!
      I had totally forgotten about that option – since my NAS runs 24/7.

      I have to do a little research and testing (need to setup a PC to accept WOL, but already found code to send WOL!!! ),… but I love the idea, so I will see what I can do and how fast I can implement this.

      Reply

      hans

      • Apr 25, 2016 - 4:30 AM - Comec Comment Link

        Sounds soooo great!!! Thank you very much and greetings from Frankfurt Germany! :)

        Reply

        Comec

      • Apr 25, 2016 - 5:26 AM - hans - Author: Comment Link

        Haha, yeah, I do like the idea very much – just have to give me a little time to implement this (have to setup something that responds to WOL, and maybe find code to determine the MAC address given a certain IP address, I hate entering MAC addresses). 

        Reply

        hans

      • Apr 25, 2016 - 5:34 AM - hans - Author: Comment Link

        Woohoo!
        Already found a trick for finding the Mac Address:

        $ ping -c 1 192.168.1.10
        PING 192.168.1.10 (192.168.1.10): 56 data bytes
        64 bytes from 192.168.1.10: icmp_seq=0 ttl=64 time=313.632 ms
        --- 192.168.1.10 ping statistics ---
        1 packets transmitted, 1 packets received, 0.0% packet loss
        round-trip min/avg/max/stddev = 313.632/313.632/313.632/0.000 ms
        $ arp 192.168.1.10
        aftv_bedroom (192.168.1.10) at 0:2b:3a:4f:69:ba on en0 ifscope [ethernet]

        The ping is sometimes needed to avoid getting this with Arp:

        $ arp 192.168.1.10
        192.168.1.10 (192.168.1.10) -- no entry
        Reply

        hans

      • Apr 26, 2016 - 9:30 AM - hans - Author: Comment Link

        I have a beta version available for testing with Wake On LAN build in …

        I can email it to you if you’d like, please let me know 

        Reply

        hans

        • Apr 26, 2016 - 9:46 AM - hans - Author: Comment Link

          Never mind email; 

          I’ve uploaded the 1.7 beta and you can download it from here.
          Changes: Wake On LAN and NFS support added.

          Reply

          hans

  • Apr 24, 2016 - 2:32 PM - Werwer Comment Link

    Can you plz support NFS.

    Thx :-)

    Reply

    Werwer

    • Apr 25, 2016 - 4:33 AM - hans - Author: Comment Link

      Hi Werwer,

      I can try to implement that, I would have to figure out how to connect to an NFS share (ie. I’d need to setup a NFS share and figure out how to connect to it).
      Any suggestions how to help with this would be most welcome.

      Reply

      hans

    • Apr 25, 2016 - 6:14 AM - hans - Author: Comment Link

      Could you test the following for your NFS share (in Terminal)?

      osascript -e 'mount volume "nfs://server/path/to" as user name "yourusername" with password "yourpassword"'

      (obviously, you’ll have to replace “//server/path/to”, “yourusername” and “yourpassword”) 

      Reply

      hans

    • Apr 26, 2016 - 9:32 AM - hans - Author: Comment Link

      Hi Werwer,

      I have no means of testing NFS, but I did build in support in a beta version (1.7) if you’d like to test this.
      Please let me know so I can email it or make it here available for download.

      (other NFS users are more than welcome to test as well)

      Reply

      hans

    • Apr 26, 2016 - 9:45 AM - hans - Author: Comment Link

      I just uploaded the new beta (1.7), keep in mind that it’s beta, please test the NFS mounting (if you’d like, you can test Wake On LAN as well).
      Download it from here.

      Reply

      hans

  • Apr 28, 2016 - 6:09 AM - hans - Author: Comment Link

    Request:

    Is anybody willing to test the new version 1.7?

    I’ve added NFS support and WOL (Wake On LAN) support, but unfortunately, I do not have a NFS share available to test, and I do not use WOL for any of my machines.

    You can download the test version here.

    Reply

    hans

    • May 6, 2016 - 1:55 PM - Comec Comment Link

      Hi,

      many thanks for your hard work! But the WOL don’t work… :( 

      Reply

      Comec

      • May 7, 2016 - 6:47 AM - hans - Author: Comment Link

        Based on your request, and the coincidence that my Brother in Law was looking for a simple WOL application, I created miniWOL.
        It’s not released yet, but the code I use for WOL, is what I’d using in ConnectMeNow as well.
        Could you test this one? You can download the test version here.

        Reply

        hans

    • May 7, 2016 - 4:52 AM - hans - Author: Comment Link

      Hi Comec!

      On it! I noticed the same thing – too bad I have nothing using WOL here, so I had to go to my brother-in-law to test and found a little bug.
      I’ll try to upload a new version today.

      As for the bug;

      – The last byte of the magic packet wasn’t done right
      – Most machines do not seem to respond to a WOL on port “7”, where as other require port “7”.

      Still trying to find more details, but so far I’ve narrow it down to:
      – Most machines use default port 9
      – Some machines use port 7, since port 9 actually seems to shutdown the machine instead

      Reply

      hans

  • May 9, 2016 - 6:17 AM - hans - Author: Comment Link

    UPDATE:

    Released v1.7 with new SSH icon, NFS support (please test!!) and Wake On Lan support.

    Reply

    hans

  • May 11, 2016 - 4:38 AM - ernie Comment Link

    After a few days all my shares get lost, vanish like a hot wind from the preferences window. Total emptiness.

    Happens with previous versions 1.6 for example and Yosemite and El Capitan.

    Did not find it under known bugs.

    best regards,

    ernie

    Reply

    ernie

    • May 11, 2016 - 4:58 AM - hans - Author: Comment Link

      Hi Ernie!

      Wow, that’s not good to hear – I use ConnectMeNow daily and have not ran into this issue (El Capitan).
      The config file can be found in /Users/<username>/.config/ConnectMeNow.cfg.

      So after making a new config, make a backup of that file – just in case.
      When it disappears, check if the file is still there or not.
      The “.config” directory is hidden en used by several other 3rd party applications as well.

      Since nobody else has reported this, could it be that you have an application running that might “clean up” things?
      (just guessing right now, since I have no idea where to look for)

      Reply

      hans

      • May 11, 2016 - 12:05 PM - ernie Comment Link

        I will look into and we’ll see what happens in the config folder. As of now there are only 2 things stored

        ConnectMeNow.cfg, Name My TV Series Folder

        WOL isn’t fully working. My DS216+ wakes up nicely on Port 9 but always at about 70 seconds (time you can ping the DS on start) the Prog tries to mount the shares no matter what delay time i add for the full boot time   

        Reply

        ernie

      • May 12, 2016 - 3:49 AM - hans - Author: Comment Link

        Hi Ernie!

        I just got another report from a German user who ran into the same issue. Strange. I can’t reproduce the problem here but I’ll see what I can think of. Please let me knwo what happens to the config file when it happens again!

        As for the WOL; awesome feedback!
        I do not have much to test with here, so I’m glad someone does .
        What happens is that a WOL is being send out (which works), and after that it will (during the wait time) ping the “server”. As soon as it gets a reply, it will try to mount. Maybe that’s to early or I goofed up (I’ll double check today).

        Reply

        hans

      • May 12, 2016 - 5:42 AM - hans - Author: Comment Link

        Created a fix for the WOL issue … you can download a test version here.

        The difference:

        Before, while waiting for the mount delay, ConnectMeNow would be looking for the server to be available with PING. If found online, before finishing the wait time, it would stop waiting and try to mount. So the wait time effectively could be shorter than the time set.

        That, in hindsight, seemed not such a good idea after all. So now it will wait the set delay time, no matter what. After that it will ping and see if the server is there and mount.

        Reply

        hans

      • May 12, 2016 - 6:04 AM - hans - Author: Comment Link

        I think I might have found a possible cause of loosing the config.

        It seems there is a bug with Lazarus Pascal, which does not give the proper location for the config files, according to Apple Guidelines. Maybe that interferes, even though it has worked for me just fine with this and other applications.

        I will see if I can rewrite the config save/load procedure to a location that is more appropriate.

        Reply

        hans

        • May 12, 2016 - 7:17 AM - ernie Comment Link

          happened again real fast,

          yesterday evening config file looked that way

          [General]

          StartAtStartup=1

          QuietMount=1

          ForceUnMount=0

          ServerCount=4

          WaitForNetwork=0

          RetryWaitForNetwork=1

          WaitDelaySeconds=20

          QuietFail=1

          INIVersion=1.5

          [Server_1]

          etc…

          today after computer restart

          [General]

          StartAtStartup=0

          QuietMount=1

          ForceUnMount=0

          ServerCount=0

          WaitForNetwork=0

          RetryWaitForNetwork=0

          WaitDelaySeconds=3

          QuietFail=0

          INIVersion=1.5

          Hope that helps..now i’m gonna test the testversion für WOL

          report back in

          Reply

          ernie

        • May 12, 2016 - 8:02 AM - hans - Author: Comment Link

          FYO, I just uploaded a beta (1.7.2) again, this time it stores the configuration file in the Apple dictated location.

          You can download it from here.

          Reply

          hans

          • May 12, 2016 - 8:03 AM - hans - Author: Comment Link

            Woops, just looked at your post …

            Let me check that out, since “ServerCount” seems to reset to zero … so it’s not related to the file location.
            Oh well, … I’ll check it out right away!

            hans

  • May 12, 2016 - 7:43 AM - ernie Comment Link

    tested the WOL again with theses settings

    [General]

    StartAtStartup=0

    QuietMount=1

    ForceUnMount=0

    ServerCount=1

    WaitForNetwork=1

    RetryWaitForNetwork=1

    WaitDelaySeconds=60

    QuietFail=1

    INIVersion=1.5

    [Server_1]

    Address=DS216plus

    Path=home

    SSHPort=

    Alias=SMB: DS216plus (home)

    AutomaticAlias=1

    AddTypeToAlias=1

    Type=0

    UseLogin=1

    ConnectAtStart=1

    ShowsInMenu=1

    SendWOL=1

    WOLMountDelay=120

    WOLPort=9

    for the first 3 times in a row WOL was sent, and at about 30 seconds i got the connection error and now something is angry a me

    and i don’t longer get a WOL sent and an immediate conncetion error.

    gonna test it using AFP and see whats happening

    Reply

    ernie

    • May 12, 2016 - 8:24 AM - hans - Author: Comment Link

      Just uploaded yet another version … 

      I modified the WOL mount delay again, hopefully better this time.
      I also made some modifications, in an attempt to prevent “ServerCount” to go to zero.

      Make sure it’s showing v1.7.3.
      Thanks Ernie for testing – it’s much appreciated since I cannot test it here.

      Reply

      hans

      • May 12, 2016 - 9:16 AM - ernie Comment Link

        didn’t work at all (no reaction from the DS on WOL), then it WORKED one time exactly like it is supposed to work with unchanged settings 

        but now i’m back to a sitting duck 

        Reply

        ernie

      • May 12, 2016 - 9:34 AM - hans - Author: Comment Link

        Really? Wow. That’s disappointing ….

        You’ve tested 1.7.3, DS in standby obviously. First time WOL worked, never ever after that again.
        Did you get an error message? Something like:

        ‘I was unable to connect to the server xyz.

         Wake On LAN was sent, but the server could not be PINGed after x seconds.

         Would you like to try to Mount the share anyway?’

        Or any other messages?

        Reply

        hans

      • May 12, 2016 - 9:48 AM - hans - Author: Comment Link

        I just had friend test the WOL code (which I use in miniWOL as well), and he can repeatedly use it without any issue.
        So that’s at least good news. Well, he’s running Windows and his NAS is a QNAP.
        My brother-in-law uses it with a Windows server, works fine too.

        So there must be something going weird right after the WOL …

        (maybe a good idea to test miniWOL with your DS – which port are you using?)

        I can add some debug messages if you’d like to test that.

        Reply

        hans

        • May 12, 2016 - 12:52 PM - ernie Comment Link

          miniwol test imac2011 ,osx 10.11.4 ,Port 9, Router FritzBox 7490, DS216+

          1. turned DS216+ off -> entered mac adress manually and /or copy&paste = no joy

          2. turned DS216+ on -> let miniwol retrieve mac adress -> turned DS off = joy (WOL tested more than 5 times in a row after this)

          3. after mac restart -> you probably can guess what happened or in this case did not happen 

          Did a few test rounds all with the same result as described above.

          I’m gonna test this again with Yosemite. That should be interesting 

          Reply

          ernie

          • May 12, 2016 - 1:44 PM - hans - Author: Comment Link

            That sounds like WOL, for some goofy reason, is not working well.
            Do you use any other application to send WOL packets to the DS?
            If so, I assume this uses port 9 as well? (some devices prefer port 7)

            The MAC Address should not change … so that would be a very weird thing if that would actually happen.
            When you try the auto-find option for the MAC address, does this result in the same MAC Address?

            hans

          • May 12, 2016 - 2:36 PM - hans - Author: Comment Link

            If you’re using another WOL tool that works well, do you have a link to it, so I can sniff packets and see what is different?

            hans

  • May 13, 2016 - 1:21 AM - nicx Comment Link

    Is it possible to add auto-connect to printers in a future version? :)

    Reply

    nicx

    • May 13, 2016 - 4:26 AM - hans - Author: Comment Link

      Hi Nicx,

      Ehm, that is an interesting question.
      I always assumed Mac OS X connects to network printers automatically … mine does anyway (Dell printer and Epson printer).
      Can you describe what you mean with this? Or are you referring to a share on the printer (my Dell for example has a SMB share for internal memory and USB drive)?

      Reply

      hans

      • May 13, 2016 - 5:12 AM - nicx Comment Link

        I have a bunch of printers on a windows printserver, actually I add them logon-script-based with commands like:

        do shell script "/usr/sbin/lpadmin -p printer1 -E -v lpd://192.168.0.201 -P /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/Resources/Generic.ppd -L \"Printer1\" -o printer-is-shared=false"

        I love your tool and I just wondered if I could add printers automatically with this tool too. At the end it would be great if I could export the config of ConnectMeNow and give it to a colleague.

        Reply

        nicx

        • Feb 11, 2017 - 12:31 PM - hans - Author: Comment Link

          Hi Nick,

          I have a test version of v2 ready, which allows the execution of a shell script or application after a mount – ie. Your printer mounts could be executed like that. I’m debating if I should make a printer a “Server Type” but so far lpadmin works a little different than the usual suspects.

          If you’d like test v2, feel free to let me know and I can email it.

          Reply

          hans

          • Feb 12, 2017 - 12:46 AM - nicx Comment Link

            great news, I would love to test the new version and give feedback :)

            nicx

          • Feb 12, 2017 - 3:27 PM - hans - Author: Comment Link

            I’ve made a test version available: link

            Please note that it will not use the old config file (I’m still debating if I want to create code to import the old config or not – not sure how critical it would be). Please make a backup of the config first … 

            A few notes on the changes can be found below, short version:

            Mounting can be done the old way (in /Volumes) but that might trigger a dialog for username and password, or you can use the “new” way which creates a mount point in ~/MountPoints (both will be seen by Finder, Path Finder, etc).

            Additionally, besides the previous functions, volumes can be auto mounted based in the WiFi you’re connected to and a script can be run after a mount event.

            Oh and I improved Wake on LAN and the general look of the application, like buttons and such and move the preferences to a separate window. Currently a debug window is available as well, if need be.

            Let me know what you think 

            hans

      • May 13, 2016 - 5:20 AM - hans - Author: Comment Link

        Well, right now ConnectMeNow doesn’t support that, obviously.
        I’ll do some research and check how generic this script would be, and which parameters are variable (for other users).

        As for sharing the config, that already is pretty easy.

        For ConnectMeNow v1.7.2 and newer: 

        Copy this directory:

        /Users/<username>/Library/Application Support/ConnectMeNow

        For ConnectMeNow version 1.7.1 and earlier:

        Copy this file:

        /Users/<username>/.config/ConnectMeNow.cfg

        Both obviously to the same location on the Mac of your colleague, with a different username in the path of course.

        Reply

        hans

      • Feb 7, 2017 - 9:16 AM - hans - Author: Comment Link

        Since I’m working on v2 … let’s see if we can define this for printers in a generic format – any help/insight would be appreciated since I have never played with this hahah …

        See also my other commend from today…

        As an example, mounting a Samba share is done with ‘/sbin/mount_smbfs’ and the command line parameters would look like this:

        /sbin/mount_smbfs //[$domain;][$username[:$password]@][$server][$path] [$mountpoint]

        The following parameter variables are available: $domain, $username, $password, $server, $path, $port, $mountpoint

        Considering your previous code, we could go 2 routes;
        1) Implement printer support straight,
        2) Run a script after successfully mounting a drive, which then triggers the “mounting” of printers.

        Reply

        hans

  • May 13, 2016 - 3:42 AM - ernie Comment Link

    MAC Address stays the same. Big difference is between entering manually or Auto-find option. Auto-find works until the next system reboot.

    I’m using 2 other apps for WOL, No.1 DS Finder iOS, No.2 my Router (only when i am not at home).

    Am i the only one with this strange behavior? Cause i’m running a clean install of El Capitan only for about a week.

    I’ll report back once i tested this with Yosemite.

    Reply

    ernie

    • May 13, 2016 - 4:20 AM - hans - Author: Comment Link

      Hi Ernie!

      Ehm, what do you mean with “Auto-find works until next system reboot”?
      Auto find is supposed to find the Mac Address, place it in the Mac Address field, and store it. You wouldn’t need it after that.
      Well, that is, if you Mac Address stays the same, which it should.

      I see if I can test DS Finder for iOS, see what they do differently.

      Oh, I’m pretty sure that you’re not the only one with this behavior. Something must be “off” or not as robust as I’d hoped with sending the WOL signal. I doubt El Capitan or Yosemite will make a difference.

      Thanks again for hanging in there while I try to fix this. 

      Reply

      hans

  • May 13, 2016 - 4:57 AM - ernie Comment Link

    “Auto-find works until next system reboot”? Well it means…

    DS off -> enter MAC Address manually/copy&paste -> WOL doesn’t work

    DS on -> enter MAC Address with Auto-find -> WOL does work -> Computer reboot -> WOL doesn’t work again (MAC Address still in the prefs window and yes it is the same Address)

    Hanging in there.

    Reply

    ernie

    • May 13, 2016 - 5:49 AM - hans - Author: Comment Link

      Ah OK, that makes more sense. 
      If you open the config file, and look for the entry for the DS, what does it display on the Mac Address line?

      Reply

      hans

    • May 13, 2016 - 5:55 AM - hans - Author: Comment Link

      Maybe it’s an idea to start a forum topic about this, I started one here.
      Otherwise there will be way too many posts under this article ….

      Reply

      hans

      • May 13, 2016 - 7:06 AM - ernie Comment Link

        unable to reply to this topic as a registered user on the forum…you really hate me that much by now?  

        Send me an email to splaxxxxx… and i will send you the config file(s)

        Reply

        ernie

        • May 15, 2016 - 10:45 AM - hans - Author: Comment Link

          Haha, no I am actually quite happy with users like you who report issues and help fixing the issues 

          I am however traveling at the moment (just arrived in Houston, Texas) so I can’t test anything at the moment, but can build new versions.
          B.t.w. did the forum now work again?

          Reply

          hans

  • Jun 20, 2016 - 1:10 PM - Siggi Comment Link

    Is it possible to connect time based to NAS, for example every day 7.00 PM?

    Reply

    Siggi

    • Jun 20, 2016 - 4:04 PM - hans - Author: Comment Link

      Hi Siggit,

      thank you for the suggestion/idea.
      Right now, this is not an option. I will consider this for a next version … if there is enough interest in it.

      Reply

      hans

  • Jul 7, 2016 - 4:37 PM Comment Link
    PingBack: www.ifun.de

    […] OS X-Freeware ConnectMeNow richtet sich an Mac-Anwender, die häufiger auf Netzwerkspeicher und entfernte Server zugreifen […]

  • Sep 5, 2016 - 3:24 AM - Reke Comment Link

    Hi,

    thank you for the great Application.

    It is possible to add a function, that run´s applications after mount a network drive?
    For example: My Volume “News” is mounted and than “Indesign” run´s automatically.

    Reply

    Reke

    • Sep 5, 2016 - 8:37 AM - hans - Author: Comment Link

      Hi Reke!

      I like that idea! Maybe I’ll add the option to start an application or script.
      I’m currently working on v2.0, so I will most certainly consider adding this option. 

      Reply

      hans

  • Sep 6, 2016 - 2:06 AM - Reke Comment Link

    Hi Hans,

    i have an other idea :D

    Maybe it is possible to add a function, that realize a fallback solution.

    For Example: We have 2 Servers. One Server for the production and one Server for Backup.

    Our Team connect to Server 1.

    If Server 1 doesn´t run because of a crash or any other reason than should connectmenow automatically connect to Server 2.

    Reply

    Reke

    • Sep 6, 2016 - 6:53 AM - hans - Author: Comment Link

      Hi Reke,

      Actually not a bad idea. 

      I will add it to the idea list for v2. However, since this fallback option might be used rarely, I might not implement it.
      Depends a little on how complex and/or convoluted the interface becomes after all the good ideas 
      I had to revamp the entire look to make space for a lot of new these functions.

      Reply

      hans

  • Sep 26, 2016 - 4:04 PM - Anthony Clarke Comment Link

    After upgrading to Sierra, upon startup its asking me for passwords for share drives, that are already in my settings!!

    Reply

    Anthony Clarke

    • Oct 1, 2016 - 5:30 AM - hans - Author: Comment Link

      Hi Anthony,

      this is a known bug with Sierra. Unfortunately, Apple has yet again changed things in the name of “security”.
      I’m working on ConnectMeNow v2.0, however I’m in the middle of moving to another country, so it will take a few weeks before I get to have time to work on that.

      I apologize for the delay and inconvenience. 

      Reply

      hans

  • Oct 1, 2016 - 12:14 AM - Bodo Comment Link

    Hallo Hans,

    I’m very impressed about this real Lazarus on a Mac project. I was familiar with Delphi and since I switched

    to mac I have just tried to make some software development using Xcode. I succeeded a little bit but the effort -compared to Delphi- seems to be much more higher. Anyway, I believe, that Lazarus on the Mac platform is still (very) buggy: Frames around typical controls like static fields, panels, bevels are not really possible (Carbon), Some attempts with cocoa widgetset were annoying: Speedbutton lost his frame, DBGrid scrollbars without any slider in it, scrolling behavior within the grid was like a hazard jump… So my conclusion is, designing a user interface is not really possible, you should walk around the bugs and not present properties compared with those in the windows world.

    What are your experience? What will really work and what should never be tried.?

    My tries with the database components (SQLite) were very positive, they behave as expected; user interfacing is more a mess.

    Bodo.

    Reply

    Bodo

    • Oct 1, 2016 - 5:53 AM - hans - Author: Comment Link

      Hi Bodo,

      First of all: Thank you for the compliment.

      I agree with you on XCode: it’s cumbersome and a pain to work with or get used to. Not just how the IDE works, which is a big pain in my opinion, but also the forced languages. I know C etc, but I don’t like working with it. Not to mention Objective C. And not liking a language makes getting used to things even a bigger hurdle.

      I really love working with Lazarus, but I have to agree that Lazarus seems a little more complex to work with than Delphi when you start using it the first time – but I also found that some of the issues are based on what you’re used to and what not. Certain Delphi specific things can be quite cumbersome as well when you’re new to Delphi. It’s a matter of getting used to I suppose.

      Of course Lazarus has it’s limitations as well …

      As for Mac specific use, I notice that indeed the widget sets aren’t perfect. Certain items do not behave as expected, other are simply not available or look odd. In part I’ll have to blame the Mac users for that. Whenever I report a bug in the Lazarus forum, very very very few Mac users assist – if any assist at all. For example, when seeking confirmation of a bug, then it might happen that nobody is responding (unlike Windows and Linux issues). Even though it’s very clearly a bug.
      On that matter as well; Most [current] Mac users do not even report bugs.

      So I’d blame the Mac users for not actively participating … a Mac user does not need to be an expert (I’m definitely not an expert). But I have found that the kind developers are willing to think and work with you if you actually do participate. It’s definitely a learning curve … it has been for me.
      But I have reported bugs and I have actually posted a bug fix in their bug reporting tool.

      The second problem (thank you Apple!) is that Apple has dropped GDB (debugger) support. They switched to another debugger which is not compatible with Lazarus, which makes it challenging to work with Lazarus and a Debugger. I wish either Apple or the Lazarus team would included a signed GDB with either XCode or Lazarus.

      The third problem is (again: Thank you Apple) that Apple is abandoning Carbon and only actively works with Cocoa. Lazarus however does not yet have a fully functional Cocoa widget-set. Again something where help is needed from Mac developers in both coding and reporting bugs. Coding for Cocoa is way over my head, it would assume knowledge of Cocoa and objective C.

      So far I have been able to get things to work I’d want them too. Well, at least for 99%.
      There is the occasional issue, which is caused by widget set limitations, or lack of good documentation. For example, getting an icon in the menubar proved more complicated than I had expected, only to find out that I had to use a not documenten function to refresh the dropdown menu with this icon.

      I would say that building a GUI is most certainly do-able. Sometimes it takes a few efforts to get it right though.
      As you can see, I have build a few applications using Lazarus. It’s very do-able. The more you work with it, the easier it becomes.
      Other (non-XCode) IDE’s show similar limitations as well and most of the time are even more limited.

      I even tried the latest Delphi version for Mac development. I definitely works.
      However, the widget set is not behaving like the native components, and the executable becomes ginormous. Not to mention that cross platform development only works for Windows and Mac (and Android and iOS), but not for Linux.
      Don’t even talk about the cost of Delphi. I develop for fun, I simply do not have the budget to buy Delphi XE10.

      So I’d play more with the GUI to find possibilities and limitations, and participate where you can in the Lazarus Forum to report and/or confirm bugs on the Mac. Without bug reporting, devs will not know what to fix either. 
      Sorry for the long reply … if you’d like to continue the Lazarus on a Mac topic; let’s start a topic in the forum so we do not go too much off topic here – I’d be happy to chat with someone like me who wants to work with Lazarus on a Mac!

      Reply

      hans

  • Oct 2, 2016 - 5:19 AM - freeman35 Comment Link

    look at this link http://bugs.freepascal.org/view.php?id=28800

    and see message (0086388)Zeljan Rikalo : Work fine here. 

    he talk about linux. I was asked osx. and this is not first answer like this. mattias has a same answer on mail list, different topic. And when clik to compile button, show compiler message, In delphi still continue. mattias remove it and in mail list him answered for this “On 13-08-2014 13:00, Mattias Gaertner wrote:
    > I never use it. Maybe this dialog can be removed.” this answer after removed.

    So I wrote dentist click application, it was finished. I worked as long as 3(three) years just with this project. finally, I delete lazarus, fpc and ALL MY PROJECT that project never trustable. that project is just home work, and can be just hobby. So no need to talk about them. I lost three years, if I were you, you don’t wanna loose 1 second about them.

    Reply

    freeman35

  • Nov 9, 2016 - 1:20 AM - nicx Comment Link

    Hi, another idea for V2: Would it be possible to define existing VPN connections for a share, so if a VPN connection is needed ConnectMeNow will automatically start the given VPN.

    Reply

    nicx

    • Nov 9, 2016 - 7:14 AM - hans - Author: Comment Link

      Hi Nick,

      I have not worked with VPN’s on my Mac (not a big VPN fan), but I will add this to the “wishlist” – I might be able to squeeze that in if I find out how to detect VPN’s … 

      Reply

      hans

  • Nov 24, 2016 - 8:59 AM - Arlo Miller Comment Link

    Will you be updating this for OSX Sierra to deal with apple’s stupid lockdown of the /volumes folder that forces the password dialog to always come up, even if you’ve saved it to keychain?  https://forums.developer.apple.com/thread/51045

    Reply

    Arlo Miller

    • Nov 25, 2016 - 8:41 AM - hans - Author: Comment Link

      Hi Arlo,

      I most certainly will! I created the application for my own use and it’s bugging me as well haha … 

      Unfortunately, I just moved from Europe to the US and that has taken quite a bit of my time.
      The idea is to start building v2 in the next few days … 

      Reply

      hans

  • Dec 25, 2016 - 8:27 AM - hans - Author: Comment Link

    Apple seem to have addressed the password request in macOS Sierra … (link)

    1) Make sure you’re running macOS Sierra 10.12.2
    2) Open Terminal, which is in the Utilities folder of your Applications folder.

    Enter the following command, then enter your administrator name and password when prompted:

    sudo defaults write /Library/Preferences/com.apple.NetworkAuthorization AllowUnknownServers -bool YES

    To return to the previous, more secure behavior (recommended), enter:

    sudo defaults delete /Library/Preferences/com.apple.NetworkAuthorization AllowUnknownServers

    This however is not stopping me from further developing v2.0 … but for some this might be a helpful fix for the moment.

    Reply

    hans

    • Dec 25, 2016 - 11:02 AM - hans - Author: Comment Link

      Note:

      In the Apple KB article, they made a mistake – it has the word “write” in the second line (to go back to the old situation).
      I have corrected this here (and reported it to Apple).

      Reply

      hans

  • Feb 7, 2017 - 9:10 AM - hans - Author: Comment Link

    FEEDBACK REQUEST:

    Hi all!

    As some of you know, I’ve been working on a new version of ConnectMeNow for which I’ve started completely from scratch – which is not only reflected in code, but the general GUI is now more MacOS like.
    I’ve already implemented a few of the requests;

    1) Mounting can be done in 2 ways now …

    By mounting into /Volumes/ or by mounting into a specific mount directory (as of macOS Sierra, I can no longer create directories in /Volumes/). The method that mounts in /Volumes/ can potentially ask for username/password (as seen with one of the Sierra updates), whereas the new method will not.

    2) Automount volumes based on WiFi SSID’s being available.

    So when at home, it sees that I connect to my home WiFi and therefor mounts to my NAS shares automatically. When I am at work, it sees the work WiFi and mounts the work shares instead.

    3) Optionally run a script or start an application after a succefull mount.

    4) Improved Wake on LAN – hopefully working with Synology NAS devices better.

    By rebuilding everything, I decided to implement a more flexible way to add protocols.

    As an example, mounting a Samba share is done with ‘/sbin/mount_smbfs’ and the command line parameters would look like this:

    /sbin/mount_smbfs //[$domain;][$username[:$password]@][$server][$path] [$mountpoint]

    With this information, and a small dump of the ‘mount’ statement (in Terminal) would help me implement a new protocol without having the protocol available on my computers.

    The following parameter variables are available: $domain, $username, $password, $server, $path, $port, $mountpoint

    My request for those with exotic protocols; please let me know what this would look like for your protocol, and any additional information you can provide. For example, if case 3rd party applications/drivers are needed, where to get them etc.

    Reply

    hans

    • Feb 12, 2017 - 3:28 PM - hans - Author: Comment Link

      I’ve made a test version available, for those interested – download it here.
      This version will not use the settings from previous ConnectMeNow versions and SSHFS has not been tested, so backup your old config first – just in case. 

      Please post feedback! 

      Reply

      hans

      • Feb 16, 2017 - 1:39 AM - Reke - Author: Comment Link

        Hello Hans,

        thank you for developing another Version of Connectmenow. I want to test the beta Version, but if connect to a Share or want to test it, Connectmenow crashed and i can open or close it anymore. My OS is Mac OS Sierra 10.12.2. My Java Version is Java 8-Update 121.

        Reply

        Reke

        • Feb 16, 2017 - 8:50 AM - hans - Author: Comment Link

          Hi Reke,

          I’m sorry to hear your running into issues with the Beta (you’re the first one to report their findings, so thank you for that!).
          ConnectMeNow doesn’t use Java, so that would not be related to any issues.

          Does ConnectMeNow show an error message?
          Optionally you can enable ‘Debug Mode” in the preferences window, and click the “Show Debug Window” button – this should open a text window showing messages as things happen. Maybe we can catch where it “explodes” 

          Reply

          hans

          • Feb 17, 2017 - 12:47 AM - Reke - Author: Comment Link

            Hi Hans,

            i used the debug modus, but if i want to connect every window crashed and i can´t close it. If i want close the App, it comes the Apple Beach Ball.

            <img src='http://up.picr.de/28343005jz.jpg' border='0' alt='Bild'/>

            Reke

          • Feb 17, 2017 - 8:21 AM - hans - Author: Comment Link

            Hmmm, that’s strange – thank you for testing! I will have to go and see what’s going on that might cause this.
            So to reproduce: start the application, mount a volume, app stuck?

            hans

          • Feb 17, 2017 - 8:27 AM - Reke - Author: Comment Link

            Hi,

            yes i mount a share or test it and the app crashed. So i must make a restart to open the app again.

            Thank you.

            Reke

          • Feb 17, 2017 - 8:53 AM - hans - Author: Comment Link

            Could you tell me what kind of share this is?
            And if it is using /Volumes or the new mount method (second tab for a given share)?

            hans

          • Feb 17, 2017 - 8:56 AM - Reke - Author: Comment Link

            I use a apple share also afp and with the Volume function.

            Reke

          • Feb 17, 2017 - 9:23 AM - hans - Author: Comment Link

            Would you mind trying it without the Volume function? This might help me pinpoint the issue.
            Can you also check if there is a directory in your home directory called MountPoints?
            (~/MountPoints)

            hans

          • Feb 18, 2017 - 12:54 PM - hans - Author: Comment Link

            I think I found what might have caused this issue …
            Please try (when you get to it) beta-2, you can download it here (same link, just the updated version).

            hans

          • Feb 20, 2017 - 2:08 AM - Reke - Author: Comment Link

            Hi Hans,

            Thank You for your invest. But the problems doesn´t solved. So if i want to connect without Volumes, with Volumes, new Beta Version, the app stuck too.
            Maybe we could do a meeting with TeamViewer? Maybe i make a mistake

            Reke

          • Feb 20, 2017 - 8:41 AM - hans - Author: Comment Link

            Hi Reke!

            Hmm, that’s strange, especially since the method with “/Volumes/” is identical to the one used in the previous ConnectMeNow version – that versions works OK on your computer right?

            hans



Your Comment …

Friendly request to 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.