Another option for securing VNC communication
I just discovered http://www.cs.berkeley.edu/~smcpeak/SafeTP/ It's a free, secure, and completely transparent FTP proxy. The method is similar to SSH tunneling, but easier to set up. The same methods could be used to build a transparent VNC proxy which would encrypt all VNC traffic. - To unsubscribe, send a message with the line: unsubscribe vnc-list to [EMAIL PROTECTED] See also: http://www.uk.research.att.com/vnc/intouch.html -
RE: vnc Solaris 2.6 CDE (strange error message)
Thanks a lot. It helped. !
Of course I've run into other problems, but I think
it's better to post it in a separate thread, after I've
searched the mailing lists for similar problem solutions.
regards
Tor
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 31. marts 2001 17:13
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; Tor Andersen
Subject: Re: vnc Solaris 2.6 CDE (strange error message)
>From: "Tor Bye Andersen" <[EMAIL PROTECTED]>
>Date: Sat Mar 31 2001 4:49am
>To: <[EMAIL PROTECTED]>
>Cc: "Tor Andersen" <[EMAIL PROTECTED]>
>Subj: vnc Solaris 2.6 CDE (strange error message)
>
>I am currently trying to make VNC work under Solaris 2.6, using CDE. I've
>searched the mailing lists for clues,
>but haven't found anything directly related to my particular problem.
>
>Having performed
>the basic tasks mentioned in the README file of the installation tar-file, I
>start the server
>without arguments. (vncserver) on the machine ypch12.
>This yields lines on standard out : (omitting the password part)
>
>Nex 'X' desktop is ypch12:1
>Starting applications specified in /export/home/tba/7.55/.vnc/xstartup
>Log file is /export/home/tba/7.55/.vnc/ypch12:1.log
>
>So far so good.
>But the log file is not so happy :
>
>31/03/01 09:08:21 Xvnc version 3.3.3r2
>31/03/01 09:08:21 Copyright (C) AT&T Laboratories Cambridge.
>31/03/01 09:08:21 All righs reserved
>31/03/01 09:08:21 See http:/www.uk...
>31/03/01 09:08:21 Desktop name 'X' (ypch12:1)
>31/03/01 09:08:21 Protocol version supported 3.3
>31:03:01 09:08:21 Listening for VNC connections on TCP port 5901
>31:03:01 09:08:21 Listening for HTTP connections on TCP port 5801
>31:03:01 09:08:21 URL http://ypch12:5801
>xrdb: No such file or directory
>xrdb: can't open display ':1'
>xsetroot: unable to open display "1"
>xterm Xt error : Can't open display: ":1"
>twm: unable to open display ":1"
>
===
Known Problems in version 3.3.3R2
There is a known bug with this release, which fortunately has an
easy workaround: Before you start the VNC server you need to insert
these two lines in your startup file ($HOME/.vnc/xstartup), right
after the first line in the file:
DISPLAY=unix${DISPLAY}
export DISPLAY
===
Freddy
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-
Connecting two Win98SE computer
I have succesfully used VNC to view my work computer from home, and now wish to view one home computer from another. But The setup: two home computers running Windows 98SE connected with Intel's Wireless Anypoint system. One of the computers, I'll call it server, is connected to the Internet through a dialup modem, and acts as the server in the Anypoint setup. The other computer is the client. I have fixed the IP numbers for both of these machines as suggested buried in Intel's support help: XXX10.1 for the server, and XXX10.2 for the client. This wireless LAN is working fine as far as I can tell. I run the WinVNC server from the server machine. When the mouse is placed over its icon in the system tray it displays the IP number: XXX10.1 (If it is connected to the DUN, it also displays the IP number assigned by the ISP). Now: when I run the VNC server from the client machine, it displays the same IP number: XXX10.1, even though I can check that it is indeed set to 10.2 for the wireless adapter. And when I try to run the VNC viewer from the client to view the server, it complains about a loopback connection, thinking I am trying to view itself. Any suggestions as to what I have setup wrong? Thanks! - To unsubscribe, send a message with the line: unsubscribe vnc-list to [EMAIL PROTECTED] See also: http://www.uk.research.att.com/vnc/intouch.html -
