Teamviewer – NOT backwards compatible

In Short, requires a license to use an older version.

I have an old Mac OS X (OS 10.7.5 (Lion)) which I have on a shared Keyboard, Video and Monitor (KVM). I came across a software called Teamviewer, which lets a user access another computer remotely. WOW, perfect solution, as I wanted to remove the Mac from my KVM and use those resource for another device.

Down the rabbit hole…
After a few a few hours trying to find the version of Teamviewer that is compatible with the Mac, I finally found the version and downloaded the Host version, which allows the Teamviewer software to run in the background and to auto start on boot up. Great I thought to myself… that is done, now to install Teamviewer on my workstation and access the Mac. Man this is nice… Boy was I wrong!

After downloading the latest version of Teamviewer (15.18.5), installed and tried to access the Mac, I received a message that stated that the Teamviewer that I am trying to access is older that the Teamviewer I am using and to update the Teamviewer I am trying to access. Well since I would not update the Teamviewer on the Mac, as that is no longer supported, I thought, Hmmm… I will just downgrade the Teamviewer I installed. So uninstalled Teamviewer on my Ubuntu 20.04 workstation and installed the same version as the Mac, which is Teamviewer 11. I had compatibility issues with some modules missing, which I resolved after following this post: https://nezhar.com/blog/install-team-viewer-12-or-older-on-ubuntu-18-04/

Just as the article stated, I opened a command line, typed in ./teamviewer and Teamviewer launched as expected! GREAT I thought, that is until I tried to connect and only received the same message. So I searched why having the same versions I would still receive the same message… Came to licensing. With the “free” version, the software becomes obsolete, while if a license was purchased for that version, the software might continue to work. I say might, as I did my research on why Teamviewer was not working, some licensed users where posting in the Teamviewer forum why their licensed software is now no longer compatible. I came to the conclusion that Teamviewer uses something in the backend that prevents older unlicensed version from working.

I ended up uninstalling Teamviewer on both workstations, enabled sharing on the Mac and using TightVNC (https://www.groovypost.com/howto/remote-access-mac-osx-windows-7/). Which works for what I wanted.

Teamviwer would have save me hours of frustration if they provided a notification that older versions will not work unless a license was purchased. But then again, the knowledge and experience that I gained would not have happened. There is always a positive side, just have to look! 😉

Samba

Install Samba

sudo apt update
sudo apt upgrade
sudo apt install samba samba-common-bin

Create shared directory

sudo mkdir /media/NameOfDirectory

Configure the directory rights, choose from one of the follwong:

This command sets the sticky bit (1) to help prevent the directory from being accidentally deleted and gives everyone read/write/execute (777) permissions on it.

sudo mkdir -m 1777 /media/NameOfDirectory

No sticky bit and directory can be deleted.

sudo mkdir 777 /media/NameOfDirectory

Configure Samba

Create a backup of the original file before editing

sudo cp /etc/samba/smb.conf /etc/samba/smb.conf.bak

Edit the Samba configuration file.

sudo nano /etc/samba/smb.conf


Open to everyone who can access the share.
Add the following to the bottom of the file.

[share]
Comment = Samba shared folder
Path = /media/NameOfDirectory
Browseable = yes
Writeable = Yes
only guest = no
create mask = 0777
directory mask = 0777
Public = yes
Guest ok = yes

Restart the Samba service.

sudo service smbd restart

Share that can only be accessed by user(s) who have been granted access.

User who already has an account in the system:

sudo smbpasswd -a NameOfUser
New SMB password:
Retype new SMB password:

User that does not have an account in the system, an account has to be created. Not creating a password for the user will only grant the user Samba access and not system access.

adduser NameofUser

Or explicitly state not to create a directory and password for the user.

sudo adduser --no-create-home --disabled-password --disabled-login NameOfUser

Create a Samba password for the user.

sudo smbpasswd -a NameOfUser
New SMB password:
Retype new SMB password:

Edit the Samba configuration file.

sudo nano /etc/samba/smb.conf

Add the following to the bottom of the file.

[share]
   comment = Samba Shared Directory
   path = /media/NameOfShare
   valid users = UserName1 UserName2
   public = no
   writable = yes

Restart the Samba service.

sudo service smbd restart

Removing Samba User

Delete Samba user.

sudo smbpasswd -x UserName

Delete user from the system.

sudo userdel -r UserName

LED Mouse Pad

Placed my order on May 17, 2020, and should be arriving soon!
Arrived July 28, 2020.

I ordered an LED large mouse pad.
Size: 35 x 60 cm
Thickness: 4 mm
Cost: $19.70



UPDATED: July 28, 2020
July 28, 2020, 1:22 pm
Delivered, In/At Mailbox

July 28, 2020, 7:10 am
Out for Delivery

July 28, 2020, 6:01 am
Arrived at Post Office

July 28, 2020, 4:46 am
Accepted at USPS Destination Facility


UPDATED: July 24, 2020
On Its Way to USPS
July 22, 2020 at 1:09 pm

Departed Shipping Partner Facility, USPS Awaiting Item
LOS ANGELES, CA 90045


UPDATED: July 18, 2020
July 17, 2020, 11:13 am
Arrived Shipping Partner Facility, USPS Awaiting Item
SAN BRUNO, CA 94066 
Shipping Partner:  INTERNATIONAL BRIDGE
Your item arrived at a shipping partner facility at 11:13 am on July 17, 2020 in SAN BRUNO, CA 94066. This does not indicate receipt by the USPS or the actual mailing date.


Tracking via USPS

United States Postal Service (USPS)
Tracking History

On Its Way to USPS
July 22, 2020 at 1:09 pm

Departed Shipping Partner Facility, USPS Awaiting Item
LOS ANGELES, CA 90045


July 17, 2020, 11:13 am
Arrived Shipping Partner Facility, USPS Awaiting Item
SAN BRUNO, CA 94066 
Shipping Partner:  INTERNATIONAL BRIDGE
Your item arrived at a shipping partner facility at 11:13 am on July 17, 2020 in SAN BRUNO, CA 94066. This does not indicate receipt by the USPS or the actual mailing date.

June 4, 2020, 9:27 pm
Departed Shipping Partner Facility, USPS Awaiting Item
Shipping Partner:  INTERNATIONAL BRIDGE
Your item departed a shipping partner facility at 9:27 pm on June 4, 2020. This does not indicate receipt by the USPS or the actual mailing date.


June 4, 2020, 3:35 pm
Arrived Shipping Partner Facility, USPS Awaiting Item
Shipping Partner:  INTERNATIONAL BRIDGE


June 3, 2020, 12:16 am
Arrived Shipping Partner Facility, USPS Awaiting Item
Shipping Partner:  INTERNATIONAL BRIDGE


May 20, 2020, 9:37 pm
Merchant Order Receipt Notification, USPS Awaiting Item

—————————————————————————————-

Tracking via International Bridge

International Bridge

2020-07-17 11:13:59
Received at warehouse
SAN BRUNO, CA, 94066, USA

2020-07-09 14:03:00
Arrived into the US
OAKLAND, CA, 94502, USA

2020-06-04 21:27:51
Departed warehouse
SHENZHEN, GUANGDONG, 518048, CHN

2020-06-04 15:35:54
Received at warehouse
SHENZHEN, GUANGDONG, 518048, CHN

2020-06-04 15:35:53
Scanned at:
SHENZHEN, GUANGDONG, 518048, CHN

2020-06-03 03:25:07
Received at warehouse
SHENZHEN, GUANGDONG, 518048, CHN

2020-06-03 00:16:17
Received at warehouse
SHENZHEN, GUANGDONG, 518048, CHN

2020-05-26 09:33:46.16
Departed Partner Warehouse
SHENZHEN, GUANGDONG, 518128, CHN

2020-05-20 21:37:48
Received data