Final solution for Vncviewer on Linux...

[Garret]

In some topics i see that many people have resolved the viewer problem on linux with this command:

Code: Select all

vncviewer -listen -encodings "hextile copyrect" 

But if i put this command in the terminal i obviously receive an error and vncviewer shows me an help...

So what's the right command?

I am on Ubuntu 7.10

P.S.: In ubuntu 8.04(the next coming) will have a new vnc viewer(vinagre). Do you know if it will support this listen feature?

[mod=494,1206553789]added sticky[/mod]

[terryvnc2]

Install TightVNC for Linux. It supports the additional encodings that might not be supported by the default installed Linux VNC client. To install under Ubuntu run:

apt-get install xtightvncviewer

Then run xtightvncviewer with the following settings to get it to work with UltraVNC SC:

xtightvncviewer -encodings "hextile copyrect" -listen

Note I did this without Encryption / RC4.key

Admin might want to bump this up as a sticky.

[Garret]

Ok it works but i have a little problem.

The command i use is:

xtightvncviewer -listen 12015 -encodings "hextile copyrect"

But the terminal gives me this:

xtightvncviewer -listen: Listening on port 17515 (flash port 17415)
xtightvncviewer -listen: Command line errors are not reported until a connection comes in.

So the port isn't right... why?

I need to set the port 12015. How i can do?

[senbani]

@Garret:
I have the same problem.
I found out that the standard port is 5500.
Now i'm working with substration from 5500 units.
In your case > -listen 6515
(you need 12015-5500=6515!)

I work also with Ubuntu, now 8.04, but i continues using the RealVNC viewer Version 3.3.7 that you can install if you add the radio button for the Ubuntu 7.1 universe packages. This don't need the -encodings option and is so much faster! But had the same problem with port number.

[JDaus]

yep, the tight vnc manual (http://www.tightvnc.com/vncviewer.1.html) explains it like this

-listen
Make the viewer listen on port 5500+display for reverse connections from a server.

hope this helps others ...

[mad__max]

Hi gui! I'ved fix all my VNC's problem using the default vnc clinet for XP.
Simply run it with wine!

I've downloaded the file SUPPORT.EXE from [ur=http://freehost04.websamba.com/duckware ... estsc.html]here [/url] then I run from shell caling wine:

wine support.exe

I see the client's icon in tray, the connection control panel over my desktop, it ask me the listening port at the boot and it's faster, REALLY faster than xtightvncviewer!!!

[ydrol]

I gave up on this. Sessions would keep crashing,

I install a VNC server at any potential clients
on a high port with a password and firewall rules.

Install a DDNS tracker.

Then I add an icon on their desktop to manually start the service.

A bit of a pain, but I get the impression that the developers are not really interested in fixing the interoperability issues between singleclick and Linux viewers. Which is a shame.
Esp as , people that manage or provide support are quite
likely to be running Linux (compared to end users)

I'll probably look around for other one-click solutions
(Or wrap the above steps into a big VBscript )


Is the WINE/Support.exe workaround stable (ie no dropped/frozen connections)? [edit - link has gone ]

[ddcometome]

Thanks, it is fine for me.
1 question.
¿How i could limit 1 conection simultaneously?

thanks

[cbraxton]

I tried the "wine support.exe" approach in Linux and it seems to work OK. Does support.exe work with the MSRC4 plugin? I tried putting the plugin and key files in the same directory with support.exe, and adding "-plugin MSRC4Plugin_NoReg.dsm" to the command line, but it does not seem to work.

[oxmosys]

Even better! SSVNC (or enhanced tight vnc viewer). This cross-platform vnc viewer is a side project of x11vnc and it now provides experimental support of ultravnc file transfert, chat window and some other features. These features are pretty new so don't expect them to work like the real uvnc (of course) but the code of this viewer can be improved at anytime if bugs are found. Since today, ssvnc works with SC without special arguments.

To UVNC Developers : You can answer linux users request without having to create a official new viewer, you can simply help to improve ssvnc. At least if you want to, your work is appreciated!

To download and use :
http://www.karlrunge.com/x11vnc/ssvnc.html

[ricky569]

Seem to be having trouble making ssvnc work with ultrvnc repeater and SSL.
The UltraVNC setup works great with the native ssl vncviewer from Ultravnc but when I try to use ssvnc to connect to the repeater I get this error:
SSL23 GET-CLIENT-HELLO: unknown protocol.

The setup

SingleClick UltraVNC SSL server
|
|
\/
UltraVNC SSL repeater
^
|
|
ssvnc (LISTEN)
repeater://192.168.250.4:5901+ID:1

This one works (obviously windows only)

SingleClick UltraVNC SSL server
|
|
\/
UltraVNC SSL repeater
^
|
|
UltrVNC SSL Viewer

[oxmosys]

You might want to try latest version of ssvnc. If you still have troubles, why not sending a mail to ssvnc developer with detailed informations? If you hit a bug, it will be useful to him, I guess.

[ricky569]

I got UVNC SC --> SSVNC to work just fine, so I'm not using the repeater anymore.