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. Windows 10 clients wont connect

Windows 10 clients wont connect

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

    First of all I congratulate all the contributors for the work done.
    We are trying to deploy Veyon in a roundabout way to support a heterogeneous Windows and Linux computer pool. Veyon is the open source tool that seems to best fit our specifications.
    The software works very well on our Kubuntu 18.04 and Windows 7 platforms. We are currently migrating from our Windows 7 to Windows 10 computers. The connection to Windows 10 clients is not possible with the same configuration as the Windows 7 computers. We tried the latest version available 4.1.91.0 client side and computer master without more success.
    The problem is at the level of the access control because we use an authentification of type Logon authentication, ldap connection and with a rule which ask logged on user for permission. If we change this rule by checking Allow access, the connection works perfectly. Without this operational feature, Veyon no longer meets our specifications. Have you ever seen this problem with Windows 10. Is there a solution?
    Best regards

    1 Reply Last reply
    0
    • T Offline
      T Offline
      tobydox
      wrote on last edited by
      #2

      Hi,
      I was able to reproduce and fix this issue this morning. It will be fixed in the upcoming 4.1.8 and 4.1.92 releases.
      Best regards

      1 Reply Last reply
      0
      • J Offline
        J Offline
        joel.derthe
        wrote on last edited by
        #3

        Hi,
        thank you for this quick fix.
        I will download version 4.1.8 as soon as it becomes available.
        Best regards.

        1 Reply Last reply
        0
        • J Offline
          J Offline
          joel.derthe
          wrote on last edited by
          #4

          hi,
          after ten days of production with realease 4.1.8
          I confirm that the problem is well solved. I even see an improvement in the responsiveness of access control on all plateforms.
          Thank you so much.
          Regards.

          1 Reply Last reply
          0
          • T Offline
            T Offline
            tobydox
            wrote on last edited by
            #5

            Perfect! Thank you for your feedback!

            1 Reply Last reply
            0

            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