In this case, I made the end of stream happen by ctrl+c. 147::51545ĬConnection: Server supports RFB protocol version 3.16ĬConnection: Using RFB protocol version 3.8 TXImage: Using default colormap and visual, TrueColor, depth 24.ĬConn: Using pixel format depth 6 (8bpp) rgb222ĬConn: Throughput 20085 kbit/s - changing to hextile encodingĬConn: Throughput 20085 kbit/s - changing to full colourĬConn: Using pixel format depth 24 (32bpp) little-endian rgb888Īnd for the UltraVNC SC server (which worked in the old vncviewer in feisty), I get:ĬConn: Accepted connection from 72.54.229. ![]() ![]() ![]() After some further perusing into the problem, I have a hunch it may be related to the RFB version of the server? The feedback I get back at a terminal for a working connection is as follows:ĬConn: Accepted connection from 192.168.2.197::3707ĬConnection: Server supports RFB protocol version 3.6ĬConnection: Using RFB protocol version 3.3 Now, I can still listen for people who use other VNC servers such as the UltraVNC server full edition, but not from SC. Up until Gutsy and the new xvnc4viewer version, this worked wonderfully and I'd call this a regression. My regular motion is to run "vncviewer -listen" via terminal and then have the windows users connect to me. I've created a remote support application using their tool ( com/pchelpware/ creator/ index.html) and have used it for over a year to display Windows users desktops on my Ubuntu box. ![]() I use UltraVNC-based SingleClick to support windows users: com/pchelpware/ creator/ index.html
0 Comments
Leave a Reply. |