Server connect to client in listening mode #4
Comments
|
did you try to capture packets with Wireshark on TCP port 5500 ? |
|
Attached wireshark logs and client configuration (tried hextile also). I tried connection client to server also but same error... hmmmm tightvnc_client_listening_from_server_on_5500.zip |
|
I'm adding tightvnc log also. Log of direct and reverse connection are equals: [38932/37076] 2021-09-07 10:19:19 - Init WinSock 2.1 |
|
Looks like a bug on RFB service side. You could try changing preferred encoding (eg. from tight to raw) and possibly other params. |
|
Sure! Asap i'll perform some tests as you requested.
do you prefer using other viewers than tightvnc? for example ultravnc or
remmina? or is tightvnc enough?
best regards
Il giorno mar 7 set 2021 alle ore 15:29 idelac ***@***.***>
ha scritto:
… Looks like a bug on RFB service side.
You could try changing preferred encoding (eg. from tight to raw) and
possibly other params.
I'll try to analyze and fix it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA26NBO53MWZDTHZQA2YBJDUAYHUJANCNFSM5DPGHZ5A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
try with other vnc clients. That would help to isolate the cause. I've tested with some versions, there is a table in README file. |
|
Attached a zip with various log by tightvnc and ultravnc and wireshark I hope this can help you. if i can help you let me know, ask anything. The only statement i use is the following: try { |
|
Perhaps solved... One problem hides another I had previously imported the project into mine but a conflict between ch.qos.logback and org.slf4j was causing problems. So from now on I just launch the original RFBService project and the RFBServiceExample class. For direct connection the problem appears to be due to a tightvnc 256 color support setting. With server listening i have that tightvnc at 256 colors it never works, in ultravnc yes. So the direct connection works avoiding tight256 :) With the server calling the listening client instead ultravnc works well in raw, hextile, tight even at 256. Tightvnc instead always gives as answer: "Error in tightvnc Viewer: Pseudo encoding -1 is not supported". I think it is a problem of the viewer as every time the client exits the listening mode I always see the 256 colors flag active. Infact during my test in tight I indicated hextile not 256 as the pixel model and in the rfb logs I see: 10: 34: 47.759 [ClientHandler- [localhost: 5500]] INFO com.scoreunit.rfb.service.ClientHandler - RFB protocol: 3.8 The encoder is different from what I had set in the client. I attach tightvnc log: [7336/18900] 2021-09-08 10:37:05 - Init WinSock 2.1 WIRESHARK tightvnc log hextile no 256 (in theory): vncviewer_listening_hextile.zip Could we consider closed (as wrong opened) this issue? Your vnc server is the first i see fully functional. Using it with novnc could be a real opensource-multiplatform-portable alternative to other closed-source commercial products. Sure vnc is an old protocol but is well defined and stable. Do you plan to extend it? Ex. To bypass the corporate proxy problem, add a vnc over http tunnel (ports 80,8080,443) would be usefull? |
|
Good that you have solved the problem. I had some plans and ideas to continue developing this project. However, it's not easy to find enough time for it. I've also tested with noVNC, I needed it in one of my Spring Boot MVC projects, where I had to provide clients ability to connect remotely to their desktops. |
|
I agree. The idea of using novnc and websocket is excellent and guarantees usability from a simple browser, cool. Spring boot is another great idea to have a self-contained and portable package of novnc. For now novnc only supports direct mode and therefore if the vnc server is under nat (99%) it cannot be reachable. It would be necessary to modify Novnc to add a Websockify independent listening websocket and rfbservice to add websocket support. I think... |
|
Between novnc and guacamole you can think of using the latter. Basically both should be put on a server. Guacamole is more restrictive, it uses a tomcat (java, and guacd which must be compiled on the server) while novnc directly uses websockify (which currently does not support reverse connection but does not need to be compiled) in python. In both cases the hosting must be at least one vps. I have read this comment: https://news.ycombinator.com/item?id=8168264 and I have to evaluate which one is actually more performing and complete. Before modifying rfbservice for websocket support I would think about it. It all depends on the product you are planning to make. |
Greetings
I am trying to use the server by connecting to a client in listen mode. The client is a tightvnc version 2.8.59.
I simply configured it to listen on port 5500 but when starting the service I have an error (screenshot attached).
Here is the code for connecting to my local network: service.connect ("192.168.178.21", 5500);
Server and client are in the same network and same pc.
I tried in direct mode (tightvnc client connect to server) and all works fine.
Am I doing something trivial wrong?
The text was updated successfully, but these errors were encountered: