Is SC Viewer the same at WinVNC?

[kens]

I'm trying to get SC to operate. This is my setup

SC on a remote Windows PC with the helpdesk.txt set to send the connection out to a Linux machine with a public IP.

I can set port forwarding on the Linux box to get to either a WinVNC viewer on a Windows PC or one on a Linux machine.

When I initiate the connection I can see that the forwarding is established and the viewer acknowledges that the connection has arrived but no display is produced.

As a test, I used the winvnc server from realvnc.com in user mode to manually initiate a connection to the remote viewer. That works.

Is the protocol for the SC server different? Should I use the UltraVNC viewer rather than the one that comes with Linux?

Thanks

Ken

[kens]

Bump

I tested the regular UltraVNC server today using the "Add new client" option and pointing it at the my Internet accessible Linux Box, which has port 5500 forwarded to a Linux VNCViewer inside my firewall.

It works.

So there is something about my configuration of SC that is hozed.

Here's my helpdesk.txt

Code: Select all

[TITLE]
           Remote Support

[HOST]
Double click HERE to start the connection
-connect linuxboxip:5500 -noregistry


[TEXTTOP]
Double Click to make a connection

[TEXTMIDDLE]
Before making a connection

[TEXTBOTTOM]
Please Call ***

[TEXTRBOTTOM]


[TEXTRMIDDLE]
UK

[TEXTRTOP]
PC support

[TEXTBUTTON]
More Info

[WEBPAGE]
http://www

[TEXTCLOSEBUTTON]
STOP test


[BALLOON1TITLE]
Establishing connection ...

[BALLOON1A]
5 min try period

[BALLOON1B]
If it fails, the software will remove himself

[BALLOON1C]
from your system. 

[BALLOON2TITLE]
Connection active.

[BALLOON2A]
Warning, your desktop is remote visable

[BALLOON2B]
You can break the connection any time

[BALLOON2C]
by using the close button

[WEBPAGE]
http://www

I've tried every version SC offers.

Any suggestions

Thanks

Ken

[supercoe]

-connect linuxboxip:5500 -noregistry

5500 is the server port, should be 5900 viewer port.

[kens]

Have I misunderstood.

I was under the impression that SC worked in the same way, leaving out for the moment the issues of NAT/Firewalls/relays and so on, as where a VNCServer connects to a VNCViewer that is listening on port 5500. After all the example configuration in helpdesk.txt has port 5500 in it.

My understanding is that SC is a packaged VNCServer that simply loads a VNCServer and then, using its pre-configured settings, it initiates a reverse VNC connection to a listening VNCViewer.

I understand that the common way for VNC to work is for a VNCViewer to connect to a VNCServer that is listening on port 5900. But isn't the whole point of SC to do a 'reverse' connection in a simple pre-packaged way.

But maybe I misunderstand how SC is meant to work. Clearly, my non-working configuration shows that something is wrong. Is there an in depth 'how to' out there somewhere.

Thanks

Ken

[supercoe]

Sorry, I could be wrong.... I don't use SC as I prefer the functionality of the main server. Hopefully redge can give you some insight as to what is wrong.

[jeanh]

It took me a while to realize that when using the "SC" VNC server, the viewer must be in listening mode. I have not been able to put my usual Linux VNC viewers (gtkvncviewer, KRDC, etc...) in "listening" mode. Thus the only solution that has worked (quite well actually) is the UltraVNCviewer in listening mode (either plain or encrypted, both work well)
Of what I could see your helpdesk.txt looks fine, assuming your SC VNC server has direct connection to your viewer.

[supercoe]

Enhanced TightVNC Viewer (SSVNC: SSL/SSH VNC viewer)

Linux, Windows, Mac viewer that supports listen mode.

http://www.karlrunge.com/x11vnc/ssvnc.html

[kens]

Not a problem on FC8 see below

Code: Select all

$ cat /etc/fedora-release 
Fedora release 8 (Werewolf)
$ rpm -qa | grep vnc
vnc-libs-4.1.2-24.fc8
vnc-4.1.2-24.fc8
vnc-server-4.1.2-24.fc8
$ vncviewer -listen &
[1] 5425
VNC Viewer Free Edition 4.1.2 for X - built Mar 19 2008 08:01:45
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Fri Jan 22 22:02:18 2010
 main:        Listening on port 5500

$ netstat -nlp | grep vncviewer
tcp        0      0 0.0.0.0:5500                0.0.0.0:*                   LISTEN      5425/vncviewer  

Of what I could see your helpdesk.txt looks fine, assuming your SC VNC server has direct connection to your viewer.

That's the point. If I do the various port forwarding required to allow access to port 5500 on the viewer a 'normal' VNC server connects without any problem when I tell it to connect using the "Add new client" option. But for some reason the SC version of the VNCServer does not appear to do the same thing. When I initiate the connection from SC the Viewer acknowledges that the connection has arrived but does not produce a display of the remote desktop. So that suggests that the port forwarding is working fine but that there is something else wrong.

Hence my seemingly daft question as to whether the protocol that SC is using is non standard and different from regular VNC.

Maybe I should break out wireshark and analyse the packets on the wire.

Thanks

Ken

[redge]

kens

solution of supercoe is correct
others vnc don't know SC except ssvnc

Enhanced TightVNC Viewer (SSVNC: SSL/SSH VNC viewer)
can let connect SC from windows to linux ssvnc viewer
http://www.karlrunge.com/x11vnc/ssvnc.html

one feature of SSVNC viewer
Reverse (viewer listening) VNC connections can show a Popup dialog asking whether to accept the connection or not (-acceptpopup.) The extra info provided by UltraVNC Single Click reverse connections is also supported (-acceptpopupsc)

[kens]

Thanks Redge, You are quite right. The protocol that SC uses is different from the one that, for example, would run between a RealVnc Server connecting to a listening Real VNC listener.

I just set up a test from my SC build to an UltraVNC viewer in listen mode and it worked.

That makes sense of all this now.

Thanks

Ken

[redge]

terryvnc2 wrote:
xtightvncviewer -encodings "hextile copyrect" -listen

----------
vncviewer -encodings "hextile copyrect" -listen

you use too old vncviewer from real vnc 2008 on your linux
replace with most recent available and faster vncviewer for fedora
https://fedoraproject.org/wiki/Features/TigerVNC