performance
Did someone do any tests of performance to compare between vnc and other remote display programs? Does somebody know where can I find comparison like that? [demime 0.97b removed an attachment of type application/ms-tnef] - 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: icon at the rigth of the
-Original Message- From: Wouter Rikken [SMTP:[EMAIL PROTECTED]] Sent: Friday, January 05, 2001 11:27 PM To: [EMAIL PROTECTED] Subject:icon at the rigth of the I installed VNC on 3 pc's without any problems. But at the 4th (for me the most important) I don't see a VNC-server icon at the rigth of the taskbar. Did you download a version without icon; can you connect to the server ? I connect the 2 pc's directly (without using internet). How is it possible for me to get the IP-address of the PC. Normally, I'm hovering over the VNC-server icon. The 4th pc is running under windows 98 dutch version. You should give each pc an IP-adress. This can be done by choosing Network in the Control Panel. Use several adresses in the range 192.168.x.x Note: I've readed the FAQ's and other mailing, but I can't get the answer Thanks in advance for your answer. Wouter Rikken - 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 - Regards Dries Feys -- Software Engineer TVH forklift parts -- Thermote & Vanhalst NV Driemasten 120-126 -- B-8560 Gullegem - Belgium E-mail: [EMAIL PROTECTED] -- URL: http://www.tvh.be Tel: +32 (0)56 434745 -- Fax: +32 (0)56 434488 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. ** - 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 -
BUG: Unable to unlock workstation after locking it
After I lock an NT workstation (NT4/SP5 using domain login), I cannot unlock it a second time from vncviewer. The mouse functions properly and I can use the tab key to move around, but I can't enter any characters. It appears from the behavior that the ctrl or alt key is stuck, but repeatedly pressing these keys didn't fix anything. This problem happens with vncviewer on linux, hp-ux, and windows, so it appears to be a server problem. I am using the 3.3.3r7 server. After digging through the archives, I found someone mentioned that using the LEFT ctrl-alt sequence might avoid this problem, but since the server is two hours away, I'm not at liberty to test that at the moment. Is there a fix for this problem? Is this a problem with older versions of VNC? By the way, the 3.3.3r2 vncviewer program claims it is 3.3.3r1. Maybe the code didn't change between the two versions? A binary diff shows that they are different. -- Dan __ Get free e-mail at http://www.email.com Visit http://ecards.nbci.com to send exclusive NBCi electronic greeting cards. - 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: client-side printing
Ron Goldman wrote: > > Currently if someone wishes to print from an application running in a VNC > session, the printer must be visible to the computer running the VNC server > (and the server also probably needs to have a driver for that type of > printer). If the user is behind a firewall or does not want to make their > local printer visible to the entire net, then they are forced to print to a > file on the server, transfer that file to their local machine, and then > print it. > > There is no simple way to set things up so that applications on the server > can print to a printer on the client computer. The folks at WorkSpot want > to change this, so I'm exploring extending the current VNC protocol to > support local, client-side printing: a printing request on the server-side > would be redirected to the Xvnc server, sent over to the client (vncviewer) > and printed on a printer connected to the client computer. Initially only > plain text & PostScript would be supported. > > I welcome any comments about the issues involved in doing this or > suggestions on how to best proceed. How would the apps running on the remote machine see the printer? (this isn't intended to sound like a flame). In unix the printers are installed/maintained by root using printcap (or equivilant), so your vnc server can't install/unistall printers willy nilly. The applications are running in plain unix space, and just so happen to be talking to a GUI controller, which happens to also be a desktop controller. So to applications print to vnc, you would have to enable each app (recompile with a vnc print lib). For what it's worth I have a possible solution. Just like with a fax print driver, you can send meta info with the print job to the driver (in that case the fax #), you send some sort of session key. The vnc print daemon picks this up, redirects it to your own vnc server process, which then tunnels it to your client, which then prints it. Bear in mind that we can have lots of users & vnc servers running on the same machine, so inter-process security could be an issue. However every process belongs to another, so by looking back up the tree you could tell which vnc process printed the job. But even that can break, bum. The rest is left as an exercise for the reader :-). Having identified which vnc server asked for the print is not the end of it. With non-shared vnc servers, the vnc session can be snatched away from you at any moment. I think that you need a modification so that the print session belongs to the vnc client instanciation, not to the vnc server per se. Also what about protocol versions? Some clients will support the vnc-print, some wouln't, similarly with serrvers. This can be resolved with "masonic handshakes". But what sort of printer control protocol should we use? I have vnc on mac+win+linux, all of which control their printers in different ways. I would suggest that the vnc-server sees your printer in the way its OS would normally expect to see a spooler. Then the vnc-print protocol sorts the "shares". So far as print protocol is concered, I don't see too much a problem (ha ha). our vnc-print provides a spooler, so long as both ends know what is connected, then we should all be happy. So if you had say, a GDI printer, on your vnc-client m/c, you would want the vnc-server end to know this. The application on the vnc-server m/c would need to: a) know this is a GDI printer, and b) be able to print GDI. And the same for HPCL etc. So iff I can get my KOffice app to print GDI, then it's none of the spooler's business, just so long as the instructions come out OK at the actual printer. Clealy there should be some chat, based on the vnc-server's OS way of talking to printers+spoolers, to determine which kind of printer hangs of the back end. There is an existing model that you might like to play with: a Psion's remote printing. The Psion sits in its cradle with a spooler running on your desktop m/c. You select the PsionPrint printer in the Psion, and print your document to it. The PsionPrint forwards this down the link cable to your PC, where it gets spooled. This spooler is itself a native desktop app, that can send the printjobs onto any visible printer. So the vnc-print server module could be quite stupid, and just forward data to the vnc-client. It's up to the vnc-client to spool manage and worry about PS or HPCL errors or out-of-paper etc. Any good? -- Simon Dales, Publication Software Engineer "The impossible is easy" Nuffield Press Ltd., 21 Nuffield Way, Abingdon, Oxford, OX14 1RL,UK +44-1235-558637 - 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: client-side printing
> Currently if someone wishes to print from an application running in a VNC > session, the printer must be visible to the computer running the VNC server > (and the server also probably needs to have a driver for that type of > printer). If the user is behind a firewall or does not want to make their > local printer visible to the entire net, then they are forced to print to a > file on the server, transfer that file to their local machine, and then > print it. Perhaps you could configure the print output on the server to "print to file" (I assume this is an option under Unix, too), and have a process watching the directory such output was printed too. The process, on seeing a new file, would then transfer the data via the VNC connection and have it printed at the other end. Just a thought. Cheers, James "Wez" Weatherall -- "The path to enlightenment is /usr/bin/enlightenment" Laboratory for Communications Engineering, Cambridge - Tel : 766513 AT&T Labs Cambridge, UK - Tel : 343000 - 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: client-side printing
James ''Wez'' Weatherall wrote: > > > Currently if someone wishes to print from an application running in a VNC > > session, the printer must be visible to the computer running the VNC > server > > (and the server also probably needs to have a driver for that type of > > printer). If the user is behind a firewall or does not want to make their > > local printer visible to the entire net, then they are forced to print to > a > > file on the server, transfer that file to their local machine, and then > > print it. > > Perhaps you could configure the print output on the server to "print to > file" (I assume this is an option under Unix, too), and have a process > watching the directory such output was printed too. The process, on seeing > a new file, would then transfer the data via the VNC connection and have it > printed at the other end. What if you don't have write permission on that drive. Also some applications get a bit arsy and loose the working directory if you print to another folder. Also what about security? Just because user fred created this file, does not mean that this print file was intended for this instanciation of fred. Much better to have a print daemon that understands these things. On mac/Win the problem vanishes as there is only one user at any particular time. -- Simon Dales, Publication Software Engineer "The impossible is easy" Nuffield Press Ltd., 21 Nuffield Way, Abingdon, Oxford, OX14 1RL,UK +44-1235-558637 - 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: Port of VNC X server to Windows?
Does anyone know of any good translator web sites for this page? Matt Grab Akira Hatakeyama wrote: > Greetings. > > On Fri, Jan 05, 2001 at 07:36:47AM -0600, Richardson, Anthony M. wrote: > > How difficult would it be to port the VNC X server to Win9X/NT using > > the cygwin tools? > > Already exist. See > > http://www.netlaputa.ne.jp/~vmi/software/xtt-vnc/index.html > > Based on old package 3.3.2.r2, and page was written in japanese only. > > -- > Akira HatakeyamaE-Mail: [EMAIL PROTECTED] >http://www.sra.co.jp/people/akira/index.html > chigasaki-minami, tsuzuki ward, yokohama, japan > - > 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 > - - 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 and Firewalls, a story.
On Fri, 5 Jan 2001 20:36:09 -0600 (CST), William L. (Bill) Barth <[EMAIL PROTECTED]> wrote: > > home$ ssh -t work ssh work1 /pathtovncserver/vncserver :2 ; ssh -g -R >5902:work1:5902 home > > (The reverse connection is necessary since the firewalls don't allow > any ports but the SSH ports through.) I do not understand why you need the 2nd (reverse) ssh. You can forward the home to work and work to home on the initial ssh. Since I'm forwarding a lot of ports I have it on my ~/.ssh/config like this (I also connect to one computer at work and work on another): LocalForward 5910 bsw1:5910 # view LOAD VNC on bsw1 LocalForward 5944 linux:5944# work on X (VNC) Emacs RemoteForward 5901 ekc-5:5900# connect to 2nd Home computer I'm connecting from ekc-1 (at home ) to linux (at work). The net nnection is: ekc-1 |FW| ---(internet)--- |FW| linux ekc-5 __| |___bsw1___PC___(more) To work from home (ekc-1 or ekc-5) on my emacs session, I connect to ekc-1:44, to work on home PC (ekc-5) from my PC at work I connect to linux:1. So, single ssh should suffice (I also forward telnet and X). Ehud. -- @@ @@@ @@ @@ Ehud Karni Simon & Wiesel Insurance agency @@ @ @@ @ Tel: +972-3-6212-757Fax: +972-3-6292-544 @@ @@ @ @@(USA) Fax and voice mail: 1-815-5509341 @@ @@ @@Better Safe Than Sorry http://www.simonwiesel.co.ilmailto:[EMAIL PROTECTED] - 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 and Firewalls, a story.
In order to avoid the multiple nested ssh's, use a port redirector (eg. redir). On my firewall, I redirect port 24 to port 22 on my Solaris box, so from home I do: ssh -p 24 ... This should increase your performance, as well as simplify your command line. BJ. >> > Date: Fri, 5 Jan 2001 21:36:09 -0500 > From: "William L. (Bill) Barth" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: VNC and Firewalls, a story. > > I noticed that there were several questions regarding using VNC and > firewalls in the FAQ (50, directly and 51-54 indirectly) and a > write-up in the contrib section on the subject, so I thought I'd share > my experience with the community. > > My setup: (Apologies to the ASCII art impaired :) > > - -- -- > | Home |---| Firewall |---|Internet|---| Firewall |---| Work 1 | > - -- | -- > | -- > \-| Work 2 | > | -- > | -- > \-| Work n | >-- > > All the machines involved are linux boxen. > > The home firewall disallows all incoming connections except ssh. The > work firewall does the same. Incoming ssh connections on the work end > are routed randomly (for load balancing) to one of a list of machines on > the internal network all of which have the same host keys. Given all that: > > home$ ssh work > and > work1$ ssh home > > work as expected. To get to a particular machine, work1 for instance, > on the work internal network one would do: > > home$ ssh -t work ssh work1 > > That being said, in order to get Xvnc function from work to home, I do > the following: > > home$ ssh -t work ssh work1 /pathtovncserver/vncserver :2 ; ssh -g -R >5902:work1:5902 home > > then, in a separate xterm: > > home$ vncviewer localhost:2 > > (The reverse connection is necessary since the firewalls don't allow > any ports but the SSH ports through.) > > I'd like to hear from anyone in similar circumstances that's doing > something different. > > Bill. > > -- > Bill Barth | Home: (512) 797-3045 > [EMAIL PROTECTED] | Work: (512) 471-4069 > Office: WRW 111 | Fax: (512) 232-3357 - 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: FireWall problem
> The Questian: Ican't connect through browser because the fw restrict java so I > connect through vncviewer but then I get the loopback error. > my Questian is why do I get the loopback and how to resolve it. Look in the WinVNC docs for "AllowLoopback". Dan Fulbright - 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: Questions about VNC
--- Dimitry Andric <[EMAIL PROTECTED]> wrote: > >6. I've taken over another computer with a > >video card (VooDoo), > >but I have got a normal graphical card, but it is > >going slow. I > >thought that it was logical that a video card > >should work faster > >than a normal graphical card. But that is not true. > >Why is that? > > There is no difference between a "video card" and a > "graphical card". > These terms normally designate the same thing, > namely a card in your > PC which displays output on your monitor. What do > you mean exactly? I think she is talking about a Graphics Accelerator as opposed to a normal video card... Craig F. __ Do You Yahoo!? Yahoo! Photos - Share your holiday photos online! http://photos.yahoo.com/ - 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: vncserver configuration
RGB: Your RGB database is in /usr/openwin/lib, not bin. (Actually, there are probably links in lib to /usr/openwin/lib/X11.) The RGB database is a data file, not a program, so in every installation it will be in 'lib' or 'lib/X11'. Can't open display: Is the server still there; i.e. can you connect to it with the viewer? If so, did you disable the Unix domain connections to get around the problem described in FAQ #12? If so, you must use 'DISPLAY=myhost:2', not 'DISPLAY=:2' in your ~/.vnc/xstartup. (DISPLAY=:2 uses the file /tmp/.X11-unix/X2, which, by default, requires root privilege to create.) ['myhost' is, of course, your hostname.] According to Dale Westby: > Thanks for the tips that I've received so far. I have made progress but I'm > still getting problems which resemble Q13 of the FAQ so the issue appears to > be with ~/.vnc/xstartup > > When I launch the vncserver, the log file generates the messages shown > below. Incidentally, I did set the rgb path in the vncserver script to match > my system so I'm not sure why it indicates that it can't open RGB_DB. > /usr/openwin/bin is in my path so the messages at the bottom are equally > perplexing. Any suggestions or pointers to documentation are appreciated! > > Couldn't open RGB_DB '/usr/openwin/bin/rgb' > 08/01/01 09:44:08 Xvnc version 3.3.3r2 > 08/01/01 09:44:08 Copyright (C) AT&T Laboratories Cambridge. > 08/01/01 09:44:08 All Rights Reserved. > 08/01/01 09:44:08 See http://www.uk.research.att.com/vnc for information on > VNC > 08/01/01 09:44:08 Desktop name 'X' (myhost:2) > 08/01/01 09:44:08 Protocol version supported 3.3 > 08/01/01 09:44:08 Listening for VNC connections on TCP port 5902 > 08/01/01 09:44:08 Listening for HTTP connections on TCP port 5802 > 08/01/01 09:44:08 URL http://myhost:5802 > xrdb: No such file or directory > xrdb: Can't open display ':2' > xsetroot: unable to open display ':2' > xterm Xt error: Can't open display: :2 > twm: unable to open display ":2" > > thanks, > > Dale. > - > 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 > - -- -Grant "Kamisama" McDorman, Software Design Tipster[1], Advanced AppleCations [1] Consultant: A tipster disguised as an oracle, especially one who has learned to decamp at high speed in spite of the large briefcase and heavy wallet. - Stan Kelly-Bootle, _The Devil's DP Dictionary_ Fortune Cookie of the Moment: You're not drunk if you can lie on the floor without holding on. -- Dean Martin [demime 0.97b removed an attachment of type application/pgp-signature] - 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: vncserver configuration
Thanks for the tips that I've received so far. I have made progress but I'm still getting problems which resemble Q13 of the FAQ so the issue appears to be with ~/.vnc/xstartup When I launch the vncserver, the log file generates the messages shown below. Incidentally, I did set the rgb path in the vncserver script to match my system so I'm not sure why it indicates that it can't open RGB_DB. /usr/openwin/bin is in my path so the messages at the bottom are equally perplexing. Any suggestions or pointers to documentation are appreciated! Couldn't open RGB_DB '/usr/openwin/bin/rgb' 08/01/01 09:44:08 Xvnc version 3.3.3r2 08/01/01 09:44:08 Copyright (C) AT&T Laboratories Cambridge. 08/01/01 09:44:08 All Rights Reserved. 08/01/01 09:44:08 See http://www.uk.research.att.com/vnc for information on VNC 08/01/01 09:44:08 Desktop name 'X' (myhost:2) 08/01/01 09:44:08 Protocol version supported 3.3 08/01/01 09:44:08 Listening for VNC connections on TCP port 5902 08/01/01 09:44:08 Listening for HTTP connections on TCP port 5802 08/01/01 09:44:08 URL http://myhost:5802 xrdb: No such file or directory xrdb: Can't open display ':2' xsetroot: unable to open display ':2' xterm Xt error: Can't open display: :2 twm: unable to open display ":2" thanks, Dale. -Original Message- From: Dale Westby [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 21, 2000 11:29 AM To: [EMAIL PROTECTED] Subject: vncserver configuration I'm trying to get VNC working with a laptop (Win98) and two Solaris boxes. Basically I want to run vncviewer on one of the boxes (Solaris) to access the vncservers on both the Win98 box and the second Solaris box. Actually it doesn't matter if I'm running vncviewer or the Java viewer because the problem I'm running into is the same... I've had success getting vncviewer to display and access my Win98 desktop but not the Solaris vncserver. I don't really understand what the vncserver script is supposed to do, therefore, I may have the box (Solaris) running the vncserver set up incorrectly with respect to X. When I connect to the server via a browser or vncviewer, I only see a black screen where I expect to see the desktop. The Solaris server is running Openwindows (CDE version 1.2) and that is the part I don't understand. Is VNC basically for use with a headless server that isn't running a window manager or does it coexist with the window manager that is already in place. I only ask this because I think the vncserver script tries to launch a window manager. I've read the FAQ, etc. but still don't really know how to set this up. thanks, Dale ([EMAIL PROTECTED]) - 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 - - 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 -
Windows 2000 server & VCN
After VCN was installed some changes were made to the W2K server. The software locked up and someone did an uninstall. Now I cannot run Setup.Exe on this machine. Any ideas? Billie Vincent - 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 -
Mac Tight VNC?
Hi, Just wondering - are there any plans to add tight VNC capability to the Mac client? Thanks, Rami Levy - 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 Thing 2.2 observations
Dair, The version of CarbonLib I have is 1.0.4. Regards, Rami -- Date: Thu, 4 Jan 2001 10:16:40 + From: Dair Grant <[EMAIL PROTECTED]> Subject: Re: VNC Thing 2.2 observations Levy Rami-ERL005 wrote: >2. There seems to be a problem with the shift key sensing. In some >situations (most notably after a manual refresh) VNC Thing thinks >that the shift key is pressed, which causes all sorts of strange >behavior. Hmm, I'll take a look - haven't ever seen this myself. >3. I have noticed that when typing quickly, very often repeated >(double) characters only register as one character. For example, if >I'm typing the word "letter", I will see "leter". This was a >- - 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: BUG: Unable to unlock workstation after locking it
dgun wrote: > After I lock an NT workstation (NT4/SP5 using domain login), I cannot unlock > it a second time from vncviewer. The mouse functions properly and I can use > the tab key to move around, but I can't enter any characters. It appears from > the behavior that the ctrl or alt key is stuck, but repeatedly pressing these > keys didn't fix anything. This problem happens with vncviewer on linux, > hp-ux, and windows, so it appears to be a server problem. I am using the > 3.3.3r7 server. > > After digging through the archives, I found someone mentioned that using the > LEFT ctrl-alt sequence might avoid this problem, but since the server is two > hours away, I'm not at liberty to test that at the moment. Is there a fix for > this problem? Is this a problem with older versions of VNC? > > By the way, the 3.3.3r2 vncviewer program claims it is 3.3.3r1. Maybe the > code didn't change between the two versions? A binary diff shows that they > are different. > > -- > Dan OK, I discovered that windows vncviewer does NOT cause this problem. However, when the problem was caused by the linux vncviewer, the windows vncviewer also had the problem (since I tried linux first, then windows). So it definitely looks like a server problem. I'll try an older server and see if the problem goes away. Otherwise, anyone know of a fix? -- Dan __ Get free e-mail at http://www.email.com Visit http://ecards.nbci.com to send exclusive NBCi electronic greeting cards. - 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: [ANNOUNCEMENT] ChromiVNC Server...
>Your webpage links are invalid. Oops. I need to fix the 'release date' field, too. -- from: Jonathan "Chromatix" Morton mail: [EMAIL PROTECTED] (not for attachments) big-mail: [EMAIL PROTECTED] uni-mail: [EMAIL PROTECTED] The key to knowledge is not to rely on people to teach you it. Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/ -BEGIN GEEK CODE BLOCK- Version 3.12 GCS$/E/S dpu(!) s:- a19 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r- y+ -END GEEK CODE BLOCK- - 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 -
