Solving a VPN Connection Problem with VPN Enabler on macOS Mojave


This solution probably applies only to systems that were previously running macOS Server to provide VPN services.

The system I’ve been using to run Indigo for home automation has been stuck on High Sierra, due to the removal of support for the VPN server in the macOS Server application under Mojave. But running an older OS isn’t ideal, for several reasons, so I started searching, again, for a method to provide VPN services under Mojave.

After some brief searching, once again, I found positive reviews for VPN Enabler, a handy, low-cost tool ($15) that provides a GUI for the built-in VPN server in Mojave. The VPN services are still present in later version of Mojave; Apple simply removed the ability to administer it from the Server application (the Server application doesn’t work at all in the latest versions of Mojave).

Continue reading

Macs Unable to Connect to Wi-Fi After Changing Network Mode (Cisco Wireless Router)


One day, while modifying the wireless settings for our Cisco wireless router, I discovered a rather stupid problem. It surfaced when I changed the Network Mode for the 5 GHz network from Mixed to Wireless-N Only. This seemed to make sense since we don’t have any devices using Wireless-A. This is in reference to 802.11a in case anyone was wondering if I had actually meant 802.11ac, which my current router does not support.

And that’s the moment when I was disconnected from Wi-Fi and unable to reconnect. Two different Macs (one MacBook Pro and one MacBook Air) were unable to connect. Once again, I resorted to searching and found the solution. It seems, that for whatever unknown reason, when Wireless-A is disabled on my router then all Macs will decide that they require a different feature enabled in order to connect. In this case WMM (Wi-Fi Multimedia).

The reason for this seems more absurd considering that the support doc implies that it must be enabled in the first place but, before changing the Network Mode, those devices connected just fine with it disabled.

Enabling this capability on my router solved the problem. I’m not sure why. It doesn’t seem to be a feature that should be required simply to connect to a wireless router but there’s no question that enabling it resolved the problem. More details are available via the linked support page included below:

Wi-Fi: Unable to connect to an 802.11n Wi-Fi network

mControl 3 Activation Problem – License File


Our house experienced a power surge caused by a nearby lightning strike that damaged one of our A/C units along with a few other devices. Today I figured out that it damaged the network ports on the Airport Extreme Base Station along with the ethernet port on the ASUS system, which is my home automation server.

Fortunately, the ASUS box also has wireless so I was able to shift all of the network services over to the wifi adapter. I had to re-establish the built-in VPN server, among other annoyances. Since the ethernet port was no longer usable I decided to disable it in Windows 7.

Well, that caused a stupid problem.

mControl 3 has activation. I’m not a fan of activation.

I noticed the service was no longer working and wouldn’t start. When I viewed mControl’s log I saw the following message every time I attempted to start it:

The Installation Code of the license file does not match with Code 2. Please contact your System Administrator.
mServer License Code=Hacked/Hacker, Ver=.

My version isn’t hacked. I paid the commercial price (less because it was an upgrade from a previous version that I had also paid for). At first I thought that perhaps the license information was damaged but then I remembered that I had disabled the ethernet port and I noticed that there were some entries in the log during the activation check that hinted toward a check of the network device.

I re-enabled the built-in ethernet port. Sure enough, the software passed the activation check and started up. It seems to use a hardware identifier that’s part of the network card for activation.





Improving Battery Life With A New MacBook Pro (15″, MacBookPro8,2)


The Short Version: Using gfxCardStatus to manage the graphics mode made a notable difference. Uninstalling McAfee Security made the most difference.

This week I started using a new 15″ MacBook Pro (MacBookPro8,2) with OS X 10.7 (Lion). It wasn’t long before I noticed a dramatic difference between the battery life of the new MacBook Pro and that of my previous 17″ MacBook Pro, which was about two years old.

In the System Preferences I had noticed that I couldn’t configure the system to only use the integrated, low-power graphics card. Rather, I had to choose to enable “Automatic graphics switching” (in “Energy Saver”) or disable it. If it’s disabled then the computer automatically uses the high-performance, battery-draining graphics card.

Last night I began to suspect that the system wasn’t properly switching to the low-powered card. It turns out that I was almost correct.

Continue reading

Enable or Disable OS X Screen Sharing from the Terminal


If you have a need to enable or disable Screen Sharing from a terminal in OS X the commands are very simple. I’ve used these commands in 10.6 (Snow Leopard).

sudo touch /etc/ScreenSharing.launchd

sudo rm /etc/ScreenSharing.launchd

Source: | Starting VNC remotely via kickstart

Updated 06/07/2012: It seems that the process for doing this has changed in OS X Lion based on a post in Ryan’s Tech Notes. I used these commands and they worked as described.

sudo /System/Library/CoreServices/RemoteManagement/ -activate -configure -access -on -clientopts -setvnclegacy -vnclegacy yes -clientopts -setvncpw -vncpw mypasswd -restart -agent -privs -all

sudo /System/Library/CoreServices/RemoteManagement/ -deactivate -configure -access -off