TeamViewer in VM not connecting

[Pudding4Brains]

Howdy,

I've been using TeamViewer (TV) to provide support for family and friends for some time. On my side running on Windows and various Linuces - no problems so far.

This week I had to do a fresh install of my main system and decided to go with Qubes OS (nice!) which basically provides a set of virtualized and paravirtualized domains running under a modified Xen with a Fedora 20 GUI for managment and basic "Application VM"s (AppVM).

Tried installing the rpm for version 9 from:
http://www.teamviewer.com/en/download/linux.aspx

Installed that in my "untrusted" AppVM and installs seems to work fine.

However on starting teamviewer I get the normal window but I do not get a teamviewer ID ("Your ID") filled in and the error message "Not ready. Please check your connection."

To me this means teamviewer is not even able to connect to the teamviewer server(s) (or internet for that matter).

To be clear: I do not even get to the point where I might try connecting to a "partner" as I am unable to aquire my own ID from the TV-server.

Tried setting up an AppVM using a non-firewalled networking VM as a gateway to the internet but with the same result.

Both AppVMs (using firewallvm and netvm with TV installed) have no problem connecting to the inernet with FireFox et al.

Is there any reason you folks can think of that would prevent teamviewer from connecting to the internet when run from within a VM ?

Thanks for any ideas on this!

Cheers

[Pudding4Brains]

Update:  A few hours later I was able to try installing TV for Windoze in a Win7 VM running on the same Qubes OS. Installed fine and worked as supposed.

Searching this here forum I've found plenty of other people having the same or similar problems even on vanilla Linuces (non VM-ed) so I suppose the problem is not virtualisation related, nor Qubes OS or Fedora specific.

Tried a few of the solutions offered, such as running from the uninstalled TV offered as a tarbal download, but ran into other problems due to that one being 32-bit only and my system 64-bit (non multiarch). Could probably mess up a VM with extra 32-bit libs, tinker for a day or a week orso and maybe get it working at some point, but will settle for the version running in the Windoze VM for now.

Seems that quite a few people run into this problem on whatever-ix, so would assume that TV-techsupport would have found a reason/solution by now ... (?) Then again, TV runnign on wine as opposed to native kind of indicates enough about the seriousness (or lack thereof) of supporting TV on unices

Cheers!