Support For ZRLE Encoding In VNC · Issue #2603 - GitHub

Skip to content Dismiss alert {{ message }} / MeshCentral Public
  • Notifications You must be signed in to change notification settings
  • Fork 822
  • Star 6.2k
  • Code
  • Issues 91
  • Pull requests 18
  • Discussions
  • Actions
  • Projects
  • Wiki
  • Security 1
  • Insights
Additional navigation options Support for ZRLE encoding in VNC #2603New issueNew issueClosedClosedSupport for ZRLE encoding in VNC#2603Assignees YlianstLabelsFixed - Please Verify & Closeenhancement@AntonAndreevichMoroz

Description

@AntonAndreevichMorozAntonAndreevichMorozopened on May 8, 2021

There is such a product WtWare (OS for thin clients). They have a built-in VNC server. I use the new Local Devices feature and noVNC to connect. But I get an error on the current client side. Having tried the same thing in Guacamole, the connection was successful for me. I started looking for information by mistake and sorting out. Found a similar problem with noVNC (https://wtware.ru/forum/viewtopic.php?t=21514 unfortunately only in Russian). It indicates the need to have support for ZRLE encoding in VNC. Then I found discussions about noVNC and this type of encoding. Which brought me to github noVNC novnc/noVNC#545 and see that this issue has been resolved. I tried to compare what might be the differences between the original noVNC and what is built into MeshCentral. Found missing noVNC/core/deflator.js file. Unfortunately my knowledge is not enough to try to implement it.

I will give the connection logs through MeshCentral

10-19-31-932| [ gm] [ 820.963493] [VNC] Connection from 192.168.200.8. 10-19-31-979| [ gm] [ 821.005642] [VNC] Client VNC version 8 (RFB 003.008). 10-19-37-948| [ gm] [ 826.977682] [VNC] Password ok. 10-19-38-010| [ gm] [ 827.040134] [VNC] bits-per-pixel 32, depth 24, big-endian false, true-colour true. 10-19-38-057| [ gm] [ 827.040244] [VNC] red-max 0x00ff, green-max 0x00ff, blue-max 0x00ff. 10-19-38-072| [ gm] [ 827.040319] [VNC] red-shift 16, green-shift 8, blue-shift 0. 10-19-38-072| [ gm] [ 827.040385] [VNC] 32-bit server, 32-bit client. 10-19-38-072| [ gm] [ 827.069987] [VNC] 16 encodings: 1 7 -260 5 2 0 -26 -254 -223 -224 -258 -308 -309 -312 -313 -239.

I will give the connection logs through Guacamole

10-20-13-036| [ gm] [ 862.069148] [VNC] Connection from 10.10.1.201. 10-20-13-083| [ gm] [ 862.075333] [VNC] Client VNC version 8 (RFB 003.008). 10-20-13-083| [ gm] [ 862.087309] [VNC] Password ok. 10-20-13-083| [ gm] [ 862.097833] [VNC] bits-per-pixel 32, depth 24, big-endian false, true-colour true. 10-20-13-099| [ gm] [ 862.097885] [VNC] red-max 0x00ff, green-max 0x00ff, blue-max 0x00ff. 10-20-13-099| [ gm] [ 862.097924] [VNC] red-shift 16, green-shift 8, blue-shift 0. 10-20-13-099| [ gm] [ 862.097963] [VNC] 32-bit server, 32-bit client. 10-20-13-114| [ gm] [ 862.098625] [VNC] 19 encodings: 16 9 ffff0009 1 5 6 4 2 0 -253 -240 -239 -232 fffe0000 -223 fffe0001 fffe0002 fffe0003 -309.

Here we see differences only in encoding options. @Ylianst Could you check this issue?

Metadata

Metadata

Assignees

  • @YlianstYlianst

Labels

Fixed - Please Verify & Closeenhancement

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

You can’t perform that action at this time.

Từ khóa » Gm Vnc