#17 UAC often causes "Unknown message type" messages & disconnec

open
nobody
2015-03-29
2012-07-04
medeis
No

Under Windows Vista SP2 running UltraVNC 1.0.9.6.2 (and earlier), when a user access control permissions dialog comes up, it often (but not always) causes Chicken 2.2b2 to drop the connection and present an "Unknown message type N" message, where for N I've seen -1, 4, 6 and 107. After responding to the dialog, the same thing happens (dropped connection, "Unknown message type" message from Chicken), though the number may be different. The screen is sometimes updated to display the UAC dialog before the connection is dropped, sometimes not. "Unknown message type 4" and "Unknown message type 6" are the most common.

No UltraVNC server options are set (right-click system tray icon, "Properties"). In particular, the polling, "System HookDLL" and "Video Hook Driver" aren't enabled. As for admin properties, UltraVNC is set to remove Aero and the wallpaper on connection, and "Blank Monitor on Viewer Request" is enabled. Most other options are unchecked.

Tested with:
OS X 10.6.8 (client)
Chicken 2.2b2
Vista SP2 (server)
UltraVNC 1.0.8.2, 1.0.9.6.2

Discussion

  • dustinac
    dustinac
    2012-07-14

    Thanks for the bug report. The level of detail is very useful for debugging incompatibility bugs. I'm a bit busy with other things right now, but I'll try to fix this as soon as I can.

     
  • medeis
    medeis
    2012-07-14

    Hopefully it's enough to reproduce the issue. Fortunately, it's not a big deal, as Chicken can reconnect at the click of a button.

     
  • Brian Long
    Brian Long
    2012-10-19

    I'm experiencing "Unknown message type 6" running 2.2b2 on OS X. I'm not sure what causes it since I can be connected fine for a couple of hours. I'm unable to reconnect (I get the same error again). If I completely quit Chicken, I'm able to connect to the VNC server (Linux running TigerVNC) and authenticate, but when it tries to draw the screen I get this same message. If I quit Chicken and use OS X native screen sharing to connect to smb://host:display, it works fine (but Chicken is a much nicer client). Any ideas on how to diagnose?

     
  • dustinac
    dustinac
    2015-03-29

    • labels: --> compatibility