Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

Veyon Community Forum

  1. Home
  2. Help & Troubleshooting
  3. debian buster Computers can’t be accessed

debian buster Computers can’t be accessed

Scheduled Pinned Locked Moved Help & Troubleshooting
5 Posts 2 Posters 195 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Y Offline
    Y Offline
    yann972
    wrote on last edited by yann972
    #1

    Hi,

    On pcprof, I've installed veyon-master :

    root@pcprof:~# dpkg -l |grep veyon
    ii  libveyon-core:amd64                   4.5.3+repack1-1                 amd64        Computer Monitoring and Classroom Management Software - libraries
    ii  veyon-configurator                    4.5.3+repack1-1                 amd64        Computer Monitoring and Classroom Management Software - configurator
    ii  veyon-master                          4.5.3+repack1-1                 amd64        Computer Monitoring and Classroom Management Software - master
    ii  veyon-plugins:amd64                   4.5.3+repack1-1                 amd64        Computer Monitoring and Classroom Management Software - plugins
    ii  veyon-service                         4.5.3+repack1-1                 amd64        Computer Monitoring and Classroom Management Software - client service
    

    I use login identification, and add one pc in location and computer (pc2 with his IP).
    I've exported the VeyonMaster.json.

    On the client (pc2), I've installed veyon-service libveyon-core veyon-configurator veyon-plugins:

    root@pc2:~# dpkg -l |grep veyon
    ii  libveyon-core:amd64                   4.5.3+repack1-1                 amd64        Computer Monitoring and Classroom Management Software - libraries
    ii  veyon-configurator                    4.5.3+repack1-1                 amd64        Computer Monitoring and Classroom Management Software - configurator
    ii  veyon-plugins:amd64                   4.5.3+repack1-1                 amd64        Computer Monitoring and Classroom Management Software - plugins
    ii  veyon-service                         4.5.3+repack1-1                 amd64        Computer Monitoring and Classroom Management Software - client service
    

    I've imported VeyonMaster.json (not sure it's necessary).

    When I try to monitor from pcprof this PC (pc2) with veyon master , it's said: "access denied or authentification failed"

    On the client (pc2), I've this:

    # systemctl status veyon
    ● veyon.service - Veyon Service
         Loaded: loaded (/lib/systemd/system/veyon.service; enabled; vendor preset: enabled)
         Active: active (running) since Wed 2021-09-22 08:12:59 AST; 5min ago
           Docs: man:veyon-service(1)
       Main PID: 3703 (veyon-service)
          Tasks: 7 (limit: 14244)
         Memory: 18.0M
            CPU: 1min 9.207s
         CGroup: /system.slice/veyon.service
                 ├─3703 /usr/bin/veyon-service
                 ├─3707 /usr/bin/veyon-server
                 └─3710 /usr/bin/x11vnc -localhost -nosel -nosetclipboard -rfbport 11200 -rfbportv6 11200 -no6 -passwdfile rm:/tmp/Temp-139873bb-5fe3-4f17-8fef-89a27037fd99/Veyon.HiOJfe -foreve>
    
    sept. 22 08:18:12 pc2 veyon-auth-helper[4192]: pam_unix(login:auth): check pass; user unknown
    sept. 22 08:18:12 pc2 veyon-auth-helper[4192]: pam_unix(login:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=
    sept. 22 08:18:16 pc2 veyon-auth-helper[4194]: pam_unix(login:auth): check pass; user unknown
    sept. 22 08:18:16 pc2 veyon-auth-helper[4194]: pam_unix(login:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=
    sept. 22 08:18:22 pc2 veyon-auth-helper[4195]: pam_unix(login:auth): check pass; user unknown
    sept. 22 08:18:22 pc2 veyon-auth-helper[4195]: pam_unix(login:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=
    sept. 22 08:18:27 pc2 veyon-auth-helper[4196]: pam_unix(login:auth): check pass; user unknown
    sept. 22 08:18:27 pc2 veyon-auth-helper[4196]: pam_unix(login:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=
    sept. 22 08:18:33 pc2 veyon-auth-helper[4197]: pam_unix(login:auth): check pass; user unknown
    sept. 22 08:18:33 pc2 veyon-auth-helper[4197]: pam_unix(login:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=
    

    What is wrong with the authentification (authentification failure) ?

    More information:
    on pcprof:

    root@pcprof# netstat -lapute |grep veyon
    tcp        0      0 localhost:11300         0.0.0.0:*               LISTEN      root       178231     7254/veyon-server   
    tcp6       0      0 [::]:11100              [::]:*                  LISTEN      root       178234     7254/veyon-server
    

    on client (pc2):

    root@pc2:~# netstat -lapute |grep veyon
    tcp        0      0 localhost:11300         0.0.0.0:*               LISTEN      root       179890     5884/veyon-server  
    tcp6       0      0 [::]:11100              [::]:*                  LISTEN      root       179893     5884/veyon-server
    

    On pcprof and pc2, no firewall:

    # iptables -L
    Chain INPUT (policy ACCEPT)
    target     prot opt source               destination         
    
    Chain FORWARD (policy ACCEPT)
    target     prot opt source               destination         
    
    Chain OUTPUT (policy ACCEPT)
    target     prot opt source               destination
    

    And I can ping pc2 from pcprof
    Thanks for help.

    1 Reply Last reply
    0
    • Y Offline
      Y Offline
      yann972
      wrote on last edited by
      #2

      I've just read this on the doc:
      This method (logon authentication) requires identical user accounts to exist on all computers.

      So it means that the user on pcprof has to be the same than the user on pc2 ?
      In my my case, user on pcprof is prof and pc2 is eleve. Maybe that's the problem authentification reason ?

      Thanks for your help.

      Y 1 Reply Last reply
      0
      • Y yann972

        I've just read this on the doc:
        This method (logon authentication) requires identical user accounts to exist on all computers.

        So it means that the user on pcprof has to be the same than the user on pc2 ?
        In my my case, user on pcprof is prof and pc2 is eleve. Maybe that's the problem authentification reason ?

        Thanks for your help.

        Y Offline
        Y Offline
        yann972
        wrote on last edited by
        #3

        ok it works now.
        It's necessary to have the same user on pcprof (veyon master) and pc2 (client) if you use logon authentification, and then export the configuration (json file) from pcprof to pc2.

        I think I will use the key authentification in the future, not to have the same user on pcprof.

        T 1 Reply Last reply
        1
        • Y yann972

          ok it works now.
          It's necessary to have the same user on pcprof (veyon master) and pc2 (client) if you use logon authentification, and then export the configuration (json file) from pcprof to pc2.

          I think I will use the key authentification in the future, not to have the same user on pcprof.

          T Offline
          T Offline
          tobydox
          wrote on last edited by
          #4

          @yann972 I'm happy to hear you solved the issues. Key file authentication indeed is the way to go here. I also recommend to remove the packages from Debian/Ubuntu and install the official all-in-one package which can be downloaded from our website.

          Y 1 Reply Last reply
          0
          • T tobydox

            @yann972 I'm happy to hear you solved the issues. Key file authentication indeed is the way to go here. I also recommend to remove the packages from Debian/Ubuntu and install the official all-in-one package which can be downloaded from our website.

            Y Offline
            Y Offline
            yann972
            wrote on last edited by
            #5

            "install the official all-in-one package which can be downloaded from our website"
            Is it possible to have the adress of a repository that could be added in /etc/apt/source.list instead of download the package via the website ? (For debian)

            1 Reply Last reply
            0
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            Powered by NodeBB | Contributors
            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Users
            • Groups