FreeNAS – Authentication Issues with Windows 10

After upgrading my FreeNAS server to the latest version the other evening I started to experience some issues with my Windows 10 workstation being able to authenticate with and then access the files on the FreeNAS Server.

After some checking around it became apparent that there was an issue with the user authentications. The following appeared to fix the issue –

Change the logging level on the FreeNAS server for the SMB service so that the issue was visible – Services > SMB > Log Level ‘Normal’

View the log file and see the authentication issues – tail -f /var/log/samba4/log.smbd

Verify that your password in Windows and on the FreeNAS server match.

Delete any shares on the Windows client that may have cached credentials – net use * /d

You may also want to look at setting ‘ntlm auth = yes’ in the ‘Auxiliary parameters:’ section of the SMB Services Configuration

Python & SNMP

There is an excellent SNMP Simulator available –

Install the required libraries before trying to use –

tenscripting3 and a HomeTroller Zee

I’ve just started working with a HomeSeer HomeTroller Zee device, something I am looking at using to help monitor the temperature in my house and control the heating, provided by a number of FIR (Far Infra Red) panels – Something recently purchased from Future Energy Solutions

In order to help develop some custom scripts on my HomeTroller Zee I started looking around and came across tenScripting3. This uses various plugins and addons for Microsoft Visual Studio to help write and debug your scripts.

The plugins can talk directly to your HomeSeer installation in order to update scripts and also monitor activity in real time, however, in order to do this it requires a Windows File Share, or in the case of Linux, a SMB share…

The HomeTroller Zee doesn’t come with Samba enabled by default and I was a little hesitant about messing about with the build of linux that is supplied pre-installed.

However, all is not lost. By using an intermediate system (Centos), it is possible to create a SMB share that is visible to your Windows Machine running Visual Studio and also share out the HomeSeer folder from your HomeTroller Zee…

We end up with something like this –

Visual Studio and the tenScripting3 apps think they are talking to the HomeTroller using a Windows File Share, however, they are talking to the CentOS server, which in turn is talking to the HomeTroller. The best part is that you don’t need to make any changes to the HomeTroller as that part of the connection uses SSH, which is already in place!

In order to get this working I did the following.

CentOS Server

Built a standard CentOS machine running as a virtual server – using VirtualBox on the desktop running Visual Studio,

Install samba

Configure Samba


Edit the sshfs configuration file to allow Samba to share it out /etc/fuse.conf

Create the folder where you are going to mount HomeTroller

Finally, mount the HomeTroller remote filesystem

If all has gone well you should now be able to browse from your windows PC and see the HomeTroller files & folders.

What time is now?

Configuring the time on a Centos box –

First we make sure we have a backup of the current timezone configuration, then we set it to the required timezone.

Then we install the ntp daemon if not already installed. We then switch it on, get the current time and start the daemon.

rsync – Quick Reference

rsync is great to keep two folders or machines in sync, either locally or remotely. However, there are loads of command line options that can look complex for the initial user.

I have used the following command to sync one folder to another –

Notice that when you specify the source you must have a trailing ‘/’ to indicate the source directory. The destination is then specified by the directory you want to sync the files into.

By default rsync will not delete any files in the destination that it does not find in the source.

In the example above –

a – archive, this will sync folders recursively and deals with symbolic links and other special files. It also preserves dates, times, owners etc.
n – dry run – just show on the screen what will be done. Nothing is actually moved, created/deleted.
v – verbose, additional output onscreen.
P – Progress & Partial, shows progress of transfers and also allows restart after partial sync.

You may have noticed in the above example that both folders are in /mnt/…… I am using a Centos server to sync some folders from a HDA NAS system back to a Windows Home Server. Both systems are presenting shared drives that the Centos server has mounted and is then scanning in order to complete the rsync. The windows files shares are mounted using mount.

When entering the above commands you will be prompted for the password of the user supplied in order to access the fileshare.

Android Marshmallow – Vonage Extensions App does not ring

A few months back I decided to move over to a VOIP (Voice Over IP) service for my home telephony. It gave me several advantages over a standard POTS (Plain Old Telephone Service) type connection. Mainly the ability to use softphone clients on my mobile to allow me to answer my home phone when out and about without the cost of call diversion, and also cheaper calls.

However, after a couple of months of use and one Android update later the softphone client stopped ringing on incoming calls – they flashed up on screen but the phone did not ring.

After a number of emails back and forth with Vonage support and also some trial and error I have come up with the following solution that will now allow the ‘Extensions’ App to work once again –

  1. Go to settings on mobile.
  2. Select applications option
  3. Click on Application Manager
  4. Select Extensions application
  5. Click on Permissions
  6. Slide to on the “Storage ON” option
  7. Press and hold the power button on the phone and then select the ‘Power Off” option from the menu.
  8. Once the phone has powered down, wait 10 seconds and then switch your phone back on using the power button.

Note – Selecting the ‘Reboot’ option will not fix the issue. A full power cycle is required in order to implement the fix.