Teamviewer and Third Party Product co-existence

jbarnett12 · 2023-10-15T20:50:35+00:00

There was an error rendering this rich post.

I am using a free version of Teamviewer on Linux but thinking of moving to **Third Party Product** . I have both installed on one machine but weirdly every time I try to grant access to the linux machine it stops working after I reboot. I assign the linuxbox but I then have to migrate the machine but once it is migrated and I reboot the access has been removed. This does not happen when I remove Teamviewer - is there some reason that they cannot coexist?

Find more posts tagged with

Accepted answers

All comments

misterm3140

I have used a Third Party Product while using TeamViewer as well, and experiencing an issue where the TeamViewer IDs changed. However, please elaborate on "stops working." Is it an issue with connecting to TeamViewer? What error messages are being produced from your end?

jbarnett12

I have installed Nomachine but what happens is that I have had a fully functioning teamviewer session working on a Linux box. When I installed nomachine is caused Teamviewer to remove the machine that is assigned to an account. I can't add the machine back because every time I do it wants me to go though the migration process and then it says I have duplicates which I need to remove - when I run the migration it removes the device assignment and I cannot logon to the machine. I can't try to assign again unless I remove Nomachine

misterm3140

Yes, I had a similar issue like this as well. I would recommend saving the two IDs in your list of computers. When the machine is dropped, a new ID is created. In my case, the remote computer had two TeamViewer IDs that swapped every so often when connecting to the other remote desktop application. This is the only solution that worked for me when I used to have two remote desktop clients in the event that one of them was not working.

jbarnett12

Thanks for the suggestion but that may nbot work for me as I noticed that the remote did in fact get two Teamviewer id's but in my case they were identical so when I tried to migrate one, it said I had duplicate and then dropped one but when I tried to connect I got the message that one was not ready to connect

misterm3140

Interesting, I think one way is to write a Shell Script that regularly resets the TeamViewer daemon after each logout, but even so, it will reset your TeamViewer ID and machine. Perhaps, switch to another remote desktop application if that is possible or create an SSH server so that you can reset your TeamViewer daemon remotely if your machine breaks. The OpenSSH Server is reliable for a last case scenario.

jbarnett12

Thanks for your help on this , sadly I am getting tired of the problems I am having with Teamviewer and am transtioning to **Third Party Product** as the support is much better