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. Unable to login after Win7 remote update

Unable to login after Win7 remote update

Scheduled Pinned Locked Moved Help & Troubleshooting
3 Posts 2 Posters 279 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.
  • P Offline
    P Offline
    polourbani
    wrote on last edited by
    #1

    After a remote update of win7 inside my lab (25 pc) I'm no no more able to login to veyon master 4.0.3.0
    All the slave/client are connected using an admin account sharing the same user and pwd.
    A rollback to a windows recovery point before the update solve de problem: I tried only on the master PC but after the rollback I was able to login but the clients PC (also running win 7) that has been already updated to the new windows version are not reacheble (maybe for the same reason).

    Any suggegestions?
    Update to a new Veyon Version
    Some Windows configuration to check/modify
    Move to the key authentication?

    Thanks in advance
    Great job, this tool is really great!

    P 1 Reply Last reply
    0
    • P Offline
      P Offline
      polourbani
      replied to polourbani on last edited by
      #2

      @polourbani said in Unable to login after Win7 remote update:

      After a remote update of win7 inside my lab (25 pc) I'm no no more able to login to veyon master 4.0.3.0
      All the slave/client are connected using an admin account sharing the same user and pwd.
      A rollback to a windows recovery point before the update solve de problem: I tried only on the master PC but after the rollback I was able to login but the clients PC (also running win 7) that has been already updated to the new windows version are not reacheble (maybe for the same reason).

      Any suggegestions?
      Update to a new Veyon Version
      Some Windows configuration to check/modify
      Move to the key authentication?

      Thanks in advance
      Great job, this tool is really great!

      Below a part of the log that shows the error

      --Impossibile trovare il file specificato.
      2019-01-16T08:11:42.575: [INFO] DWORD vncDesktop::InitBitmap() : No driver used
      2019-01-16T08:11:42.575: [INFO] BOOL vncDesktop::SetPalette() : no palette data for truecolour display
      2019-01-16T08:11:42.580: [INFO] BOOL vncDesktop::InitWindow() : InitWindow called
      2019-01-16T08:11:42.580: [INFO] BOOL vncDesktop::InitWindow() : InitWindow:OpenInputdesktop OK
      2019-01-16T08:11:42.580: [INFO] BOOL vncDesktop::InitWindow() : InitWindow:SelectHDESK to Default (3ac) from 4c
      2019-01-16T08:11:42.581: [INFO] LRESULT DesktopWndProc(HWND, UINT, WPARAM, LPARAM) : wmcreate
      2019-01-16T08:11:42.581: [INFO] BOOL vncDesktop::InitWindow() : OOOOOOOOOOOO load hookdll's
      2019-01-16T08:11:42.582: [ERR] BOOL vncDesktop::InitWindow() : OOOOOOOOOOOO start dispatch
      --Impossibile trovare il modulo specificato.
      2019-01-16T08:11:42.588: [INFO] void vncDesktop::SethookMechanism(BOOL, BOOL) : Sethook_restart_wanted hook=1 driver=0
      2019-01-16T08:11:42.589: [INFO] void vncDesktop::SethookMechanism(BOOL, BOOL) : Hookdll status changed
      2019-01-16T08:11:42.696: [INFO] virtual void* vncDesktopThread::run_undetached(void*) : Wait for viewer init
      2019-01-16T08:11:43.743: [INFO] ---
      2019-01-16T08:11:43.743: [INFO] Last message repeated 10 times
      2019-01-16T08:11:43.743: [INFO] ---
      2019-01-16T08:11:43.743: [INFO] Authenticating user "controllo"
      2019-01-16T08:11:43.744: [WARN] ComputerControlServer: failed authenticating client "::ffff:127.0.0.1" "controllo"
      2019-01-16T08:11:43.744: [ERR] VncServerProtocol:::receiveAuthenticationMessage(): authentication failed - closing connection
      2019-01-16T08:11:43.744: [ERR] VBool VSocket::ReadExact(char*, VCard) : zero bytes read2
      2019-01-16T08:11:43.744: [INFO] static BOOL vncService::SelectHDESK(HDESK) : SelectHDESK to Default (4c) from 4c
      2019-01-16T08:11:43.744: [INFO] virtual void vncClientThread::run(void*) : client disconnected : 127.0.0.1 (1)
      2019-01-16T08:11:43.744: [ERR] void vncClientUpdateThread::Kill() : kill update thread

      1 Reply Last reply
      0
      • T Offline
        T Offline
        thomson67
        wrote on last edited by
        #3

        Same problem for me after updates on Windows 7.

        Remove this updates do the job but it's not a long term solution.

        Thanks in advance to fix it in a future version maybe 😉

        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