Well slap my thigh!

In console mode without a mouse use the following to copy and paste: Launch nano in multi-buffer mode (nano -F) CTRL-K cut the line you need. (As this cuts the line don't save this file when you are finished) CTRL-R to open a file into a new buffer (you can type the full path ie /etc/this.conf) CTRL-U to paste in the opened file

Step 1. Setup authentication info (credit to chatchavan ) Now, you should check what type of authentication your network use. Personal:  Typical home router require one password to connect. (Keywords: WPA, WPA2) Enterprise:  If you use the enterprise network, e.g.,  eduroam  at the university, you will have user name and password. (Keywords: PEAP, MSCHAPV2) For security reason, we will create a hash of your password. This hash will be used in the configuration file for the authentication info. This avoids saving your password in plain text. At the command prompt create a MD4 hash of one of your password by entering the following command, typing your password and pressing enter: (read -s PASS && echo -n $PASS | iconv -t utf16le | openssl md4 > hash.txt) This will create a file called hash.txt within this you will see something like: (stdin)= c612f89cd9678868a69e93beecfa10b6 You will need the bit after the equals sign. N...

After migrating to Windows 10 one of the many issues I came across was being unable to map windows 10 to one of my ubuntu samba shares with \\hostname or a \\fqdn ( it was returning system error 64 has occurred and specified network name no longer available) I found a fix by doing the following: Start -> Settings -> Control Panel -> Administrative Tools -> Local Security Policy Under Security Settings -> Local Policies -> Security Options Set "Microsoft network client: Digitally sign communications (always)" to "Disabled" Restart the computer For reference: https://lists.samba.org/archive/samba/2011-April/162201.html Unfortuantley whilst fixing one issue it highlighted another and that was not being able to communicate with one of my windows servers obviously requiring digital signing. The root of the issue is that I am running Samba version 3.6.25, so I will update this to at least 4.3.11 as I know this works as per another Ubunt...