Because we are in a governmental network (called KDN), our SG. Since then, systemd has arrived in force and is normally used for constructing services that start upon boot. What I forgot to mention is, that our firewall does not connect to the internet directly. If you don't feel like rebooting, you can start the service manually with: sudo service teamviewerd.sysv startĢ019 EDIT: This answer was written in 2013. The service will now start automatically with each boot.

Then run sudo update-rc.d teamviewerd.sysv defaults Making sure of this is relatively simple, just copy it to /etc/init.d like so: cd /opt/teamviewer/tv_bin/scriptĭon't forget to make the script non-writable to anyone but the owner! sudo chmod 755 /etc/init.d/teamviewerd.sysv # Description: TeamViewer remote control daemonĪll you need to do is make sure this script runs on startup. # Short-Description: TeamViewer remote control daemon # Required-Stop: $local_fs $network $named The solution: Have the end user download the TeamViewer app to the computer. I had them run the TeamViewer program and I remoted in, but of course the administrative login prompt does not get sent to my end of the connection and so I was stuck. Provided the device is already paired to the computer youre accessing you should be able to transfer files via Bluetooth without a problem (provided the.

TeamViewer provides a script called teamviewerd.sysv available in /opt/teamviewer/tv_bin/script. End user is running as a non-admin, and they needed to install something.

Teamviewer does not connect