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.
Now you can add proper authentication info in the file /etc/wpa_supplicant/wpa_supplicant.conf. Use the following command to launch nano editor to edit this file.
sudo nano /etc/wpa_supplicant/wpa_supplicant.conf
Here're what you should add (depending on the authentication type). Replace YOUR_NETWORK_NAME, YOUR_USER_NAME, YOUR_PASSWORD_HASH below. (Keep the quotation marks if present.) If you have multiple network configurations, you can also add multiple entries.
For a thorough explanation about important keys in the settings, read [NetBeez's instruction].
Now, we have the authentication information ready.
Step 2. Ensure that the network interface use the authentication info
Here, you should edit /etc/network/interface. Find the section about wlan0 and replace it with one of the following configuration (again, depending on your authentication type).
Personal authentication (WPA, WPA2)
auto wlan0
allow-hotplug wlan0
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
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 Ubuntu server.