Posts by aleho

    Everything is clear now.
    Thank's a lot for your irrefragable answer, but it isn't necessary, really.
    I've read topics around XU4 issues before wrote you.
    I wouldn't want to waste your time
    Appreciate your patience and good will.

    You won't loose support for HC1. It's only about XU4 and these Cloudshell toys.

    That's all I wanted to know )

    It looks some misunderstanding happen.
    I have read about the USB-to-SATA issues. (I was thinking to buy XU4, but changed my mind)
    Of course I know that XU4, HC1 and HC2 are identical and that is why I started to worry, after your decision to quit XU4 support.
    And yes, I'm using HC1 with OMV installed and I'm afraid to lose your support in close future.

    The same story.
    I have installed XFCE4, updated repo for TV, updated TV to last version. But I have no possibility to connect monitor to my Odroid-HC1
    Nothing changed.
    Teamviewer setup failed connection also.
    I add teamviewers servers into hosts manually - nothing helped.
    Searching for useful topics in teamviewer community...

    Teamviewer team declaring about headless instalation mode
    Installation via ssh (headless mode)
    After installing the package via ssh, on a machine with no monitor attached and no X server running, you have to find a way to connect.
    You could set a password and get your TeamViewer ID via command line, but the recommended way is to assign the device to your account. To do this, run setup.
    And System requirements nothing says about X server.
    But anything can happen...

    At my view, Teamviewer daemon have to initiate connection to Teamviewers servers (something like for handshake, ID assignment, tunnel establishment, etc., before teamviewer client will get possibility to connect to target system.
    Otherwise it will be impossible to connect remote system via internet thru NAT, routers, etc...
    On this netstat output:

    root@RDNS:~# netstat -ntap | grep teamviewer
    tcp 0 0* LISTEN 16170/teamviewerd

    we have only localhost listening for loopback purposes only.
    There is no any other connection necessary for tunnelling between remote an local systems via Teamviewers servers.
    That is the problem I guess.
    Other thing, I cannot connect my remote system directly in the same local network, but teamviewer software allowed direct connection in the same local network, for Windows version at list.
    I didn't check that you are the author of openmediavault-teamviewerhost plugin, I'm sorry for any possible inconvenience for you in case my issue opening on Github.
    And you are right - that's the question for teamviewer support mostly.

    I do have read this topic, and I spent few days searching the solution. But not successfully also.
    But I guess I found the possible core of that problem, because the netstat output on the system with operational teamviewer looks like this:

    user@home_machine:~$ sudo netstat -ntap | grep teamviewer
    tcp 0 0* LISTEN 20351/teamviewerd
    tcp 0 0 ESTABLISHED 20351/teamviewerd

    In my case I found there is no connection teamviewerd to Teamviewers servers:

    root@droid:~# netstat -ntap | grep teamviewer
    tcp 0 0* LISTEN 5507/teamviewerd

    Now I'm trying to find the reason of connection absence.
    May be somebody here has ideas about...

    I have installed the Teamviewer plugin and it doesn't work also.
    Actually the teamviewerd is running:

    But I can't connect remotely - Teamviewer client says that Teamviewer isn't active on the remote computer.
    I joined my OMV NAS to teamviwer account (using teamviewer setup via SSH), but it stays offline in teamviewer client.
    Than I trying to do teamviewer setup again, I've got message that my system is already registered. And it becomes online on the Teamviewer client list at that moment, but it's impossible to connect anyway.
    It looks that teamviewerd doesn't connect to teamviewers' servers:

    root@droid:~# netstat -ntap | grep teamviewer
    tcp 0 0* LISTEN 5507/teamviewerd

    No idea what to dig next.