How to install TeamViewer 14 on CentOS 6.5
I have successfully upgraded TeamViewer on CentOS 6.5. This is how I did it:
From a terminal window:
uname -m # tells you if the system is 32bit or 64 bit. You need the matching TV version.
strings /lib64/libc.so.6 | grep GLIBC # will show you the GLIBC versions on your system, which needs to include 2.17
Assuming you need to upgrade GLIBC on a 64-bit machine, do this:
su # To get Super User access
wget http://copr-be.cloud.fedoraproject.org/results/mosquito/myrepo-el6/epel-6-x86_64/glibc-2.17-55.fc20/glibc-2.17-55.el6.x86_64.rpm
wget http://copr-be.cloud.fedoraproject.org/results/mosquito/myrepo-el6/epel-6-x86_64/glibc-2.17-55.fc20/glibc-common-2.17-55.el6.x86_64.rpm
wget http://copr-be.cloud.fedoraproject.org/results/mosquito/myrepo-el6/epel-6-x86_64/glibc-2.17-55.fc20/glibc-devel-2.17-55.el6.x86_64.rpm
wget http://copr-be.cloud.fedoraproject.org/results/mosquito/myrepo-el6/epel-6-x86_64/glibc-2.17-55.fc20/glibc-headers-2.17-55.el6.x86_64.rpm
rpm –Uvh glibc-2.17-55.el6.x86_64.rpm --force --nodeps
rpm –Uvh glibc-common-2.17-55.el6.x86_64.rpm --force --nodeps
rpm –Uvh glibc-devel-2.17-55.el6.x86_64.rpm --force --nodeps
rpm –Uvh glibc-headers-2.17-55.el6.x86_64.rpm --force --nodeps
strings /lib64/libc.so.6 | grep GLIBC # should now show GLIBC 2.17
If that succeeded download teamviewer-host (for only remote access to this machine), or full teamviewer (to access other machines from this machine) from TeamViewer.com for Linux/CentOS x86_64
Now uninstall your old teamviewer:
yum remove teamviewer
From a file-explorer, open the download folder and double-click on the teamviewer .rpm
Or you can install with yum, by navigating your CD to the download folder and:
yum install teamviewer-host_14.4.2669.x86_64.rpm
There is one final step.
On the machine you want to access this server from, open TeamViewer and go to:
Extras -> Options -> Advanced -> Advanced settings for connections to other computers -> Access Control
and set to "Full Access".
Best Answer
-
Thanks for sharing this! I've confirmed I got it working as well in CentOS 6 following these steps!
5
Answers
-
Thanks for sharing this! I've confirmed I got it working as well in CentOS 6 following these steps!
5