You can use Niresoft Task Manager (Freeware: http://www.niresoft.com/tm.asp ) It works great and shows all processes, incl. The hidden ones
Marc Beck Dallas TX, USA [EMAIL PROTECTED] SMS Email: [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Saturday, January 19, 2002 12:00 AM To: [EMAIL PROTECTED] Subject: vnc-list-digest V1 #1416 vnc-list-digest Saturday, January 19 2002 Volume 01 : Number 1416 ............................ VNC-LIST-DIGEST is a daily collection of the messages sent to the VNC mailing list. For more information about VNC see the home page http://www.uk.research.att.com/vnc . In this issue: RE : WinVNC and CTRL+ALT+DEL can't view active remote process ? RE : WinVNC and CTRL+ALT+DEL can't view active remote process ? Updated. Was Re: Success was Re: VNC Server setup on Linux Re: how do I get VNC to recognize Alt-Tab? RE: Problems connecting through internet RE: Error while waiting for server message RE: WinVNC and CTRL+ALT+DEL can't view active remote process ? Re: Updated. Was Re: Success was Re: VNC Server setup on Linux RE: how do I get VNC to recognize Alt-Tab? Re: Problems connecting through internet Re: Success was Re: VNC Server setup on Linux Re: Success was Re: VNC Server setup on Linux Re: Success was Re: VNC Server setup on Linux Re: Success was Re: VNC Server setup on Linux Re: Success was Re: VNC Server setup on Linux Re: Success was Re: VNC Server setup on Linux RE: Providing (Windows) VNC support to clients that have strict... RE: Providing (Windows) VNC support to clients that have strict corporate firewalls RE: Providing (Windows) VNC support to clients that have strict corporate firewalls Re: Updated. Was Re: Success was Re: VNC Server setup on Linux RE: How do I know if I have it? Re: How do I know if I have it? Re: Success was Re: VNC Server setup on Linux Re: Success was Re: VNC Server setup on Linux ............................ ---------------------------------------------------------------------- Date: Fri, 18 Jan 2002 10:14:50 +0100 From: <[EMAIL PROTECTED]> Subject: RE : WinVNC and CTRL+ALT+DEL can't view active remote process ? Sorry but it is a win98 pc - -----Message d'origine----- De : Ian Simcock [mailto:[EMAIL PROTECTED]] Envoyi : vendredi 18 janvier 2002 03:38 @ : [EMAIL PROTECTED] Objet : Re: WinVNC and CTRL+ALT+DEL can't view active remote process ? If you right click on the remote computers task bar you'll get the windows menu that includes the Task Manager option. - ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 17, 2002 11:26 PM Subject: RE : WinVNC and CTRL+ALT+DEL can't view active remote process ? > Thank you i tried this but unfortunately it doesn't display anything > on remote vnc server and on vnc viewer client. Have you another idea ? > > > -----Message d'origine----- > De : Alex Angelopoulos [mailto:[EMAIL PROTECTED]] > Envoyi : jeudi 17 janvier 2002 13:18 > @ : [EMAIL PROTECTED] > Objet : Re: WinVNC and CTRL+ALT+DEL can't view active remote process ? > > > Use SHIFT+CTRL+ALT+DEL > > Took me a while to figure that one out first time. It works with the > VNCViewer, the Java web interface, and the ActiveX control. > > ----- Original Message ----- > From: <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday/2002 January 17 03:17 > Subject: WinVNC and CTRL+ALT+DEL can't view active remote process ? > > > : Hi, > : > : Does anyone has a solution to view active process on remote server winvnc > ? > : When the remote user use ctrl+alt+del key the active process are displayed > : on the remote pc but not on the winvnc viewer pc. > : So have you a solution to do this even with anther way or another windows > : command or another freeware ? > : > : Thanks, > : > : JPV > : > --------------------------------------------------------------------- > : To unsubscribe, mail [EMAIL PROTECTED] with the line: > : 'unsubscribe vnc-list' in the message BODY > : See also: http://www.uk.research.att.com/vnc/intouch.html > : --------------------------------------------------------------------- > --------------------------------------------------------------------- > To unsubscribe, mail [EMAIL PROTECTED] with the line: > 'unsubscribe vnc-list' in the message BODY See also: > http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- > --------------------------------------------------------------------- > To unsubscribe, mail [EMAIL PROTECTED] with the line: > 'unsubscribe vnc-list' in the message BODY > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- - --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html - --------------------------------------------------------------------- ------------------------------ Date: Fri, 18 Jan 2002 10:21:03 +0100 From: <[EMAIL PROTECTED]> Subject: RE : WinVNC and CTRL+ALT+DEL can't view active remote process ? If i use the ctrl+alt+del on the vncviewer client the effect is not on the remote vnc server but on the local pc with vncviewer and if the remote user use the ctrl+alt+del the windows appear on his screen but not on the pc who view his screen with vncviewer so it's a bug because during that the viewer lost the remote cursor and only the local cursor is moving. So now i have to tried the rkit tools to do that, i think it is a good idea Thanks, JPV - -----Message d'origine----- De : Alex Angelopoulos [mailto:[EMAIL PROTECTED]] Envoyi : jeudi 17 janvier 2002 17:26 @ : [EMAIL PROTECTED] Objet : Re: WinVNC and CTRL+ALT+DEL can't view active remote process ? Let me ask another question since you say that. Is the system running Windows 95/98/Me? If yes, you simply can't use Ctl-Alt-Del - it halts all system processes on that architecture. The alternative is to use some "alternate" tools as you thought. One possibility if youhave access to the WIn98 Resource Kit from Microsoft is to use "tlist" and "kill". You can also get similar tools (with similar names) in Unix clone tools available for Windows. The first one which comes to mind is "Cygwin" which is now available from Red Hat http://sources.redhat.com/cygwin/ That is probably overkill for what you need. look for Win9x "clones" of the following and you will find what you need I think: tlist ps pslist kill - ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday/2002 January 17 07:56 Subject: RE : WinVNC and CTRL+ALT+DEL can't view active remote process ? : Thank you i tried this but unfortunately it doesn't display anything on : remote vnc server and on vnc viewer client. : Have you another idea ? : : : -----Message d'origine----- : De : Alex Angelopoulos [mailto:[EMAIL PROTECTED]] : Envoyi : jeudi 17 janvier 2002 13:18 : @ : [EMAIL PROTECTED] : Objet : Re: WinVNC and CTRL+ALT+DEL can't view active remote process ? : : : Use SHIFT+CTRL+ALT+DEL : : Took me a while to figure that one out first time. It works with the : VNCViewer, the Java web interface, and the ActiveX control. : : ----- Original Message ----- : From: <[EMAIL PROTECTED]> : To: <[EMAIL PROTECTED]> : Sent: Thursday/2002 January 17 03:17 : Subject: WinVNC and CTRL+ALT+DEL can't view active remote process ? : : : : Hi, : : : : Does anyone has a solution to view active process on remote server winvnc : ? : : When the remote user use ctrl+alt+del key the active process are displayed : : on the remote pc but not on the winvnc viewer pc. : : So have you a solution to do this even with anther way or another windows : : command or another freeware ? : : : : Thanks, : : : : JPV : : --------------------------------------------------------------------- : : To unsubscribe, mail [EMAIL PROTECTED] with the line: : : 'unsubscribe vnc-list' in the message BODY : : See also: http://www.uk.research.att.com/vnc/intouch.html : : --------------------------------------------------------------------- : --------------------------------------------------------------------- : To unsubscribe, mail [EMAIL PROTECTED] with the line: : 'unsubscribe vnc-list' in the message BODY See also: : http://www.uk.research.att.com/vnc/intouch.html : --------------------------------------------------------------------- : --------------------------------------------------------------------- : To unsubscribe, mail [EMAIL PROTECTED] with the line: : 'unsubscribe vnc-list' in the message BODY : See also: http://www.uk.research.att.com/vnc/intouch.html : --------------------------------------------------------------------- - --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html - --------------------------------------------------------------------- ------------------------------ Date: Fri, 18 Jan 2002 11:20:41 -0000 From: "David Colliver" <[EMAIL PROTECTED]> Subject: Updated. Was Re: Success was Re: VNC Server setup on Linux The page has now been updated with the gdmconfig and more importantly, some debugging information. If anyone has any more information, or can find problems with the document, please let me know. The file is at http://www.sourcecodecorner.com/articles/vnc/linux.asp Regards. Dave Colliver. ~~ All I ask is a chance to prove that money can't make me happy. Collectible dolls from http://www.collectorsdolls.com Web design? Web hosting? http://www.revilloc.com is the answer. Tips, tricks and articles for programmers of all languages on http://www.sourcecodecorner.com Planning a wedding? http://www.bmcweddings.com Advertise your car for free on http://www.drivingseat.com ------------------------------ Date: Fri, 18 Jan 2002 13:52:13 +0000 From: Illtud Daniel <[EMAIL PROTECTED]> Subject: Re: how do I get VNC to recognize Alt-Tab? "Frank S. Kim" wrote: > > I am guessing this is impossible but is there anyway to get my VNC session to > recognize when I am doing an Alt-Tab for switching windows. What platform(s) are your client & server on? - -- Illtud Daniel [EMAIL PROTECTED] Uwch Ddadansoddwr Systemau Senior Systems Analyst Llyfrgell Genedlaethol Cymru National Library of Wales Yn siarad drosof fy hun, nid LlGC - Speaking personally, not for NLW ------------------------------ Date: Fri, 18 Jan 2002 08:35:06 -0600 From: Hotel Puesta del Sol <[EMAIL PROTECTED]> Subject: RE: Problems connecting through internet Thank you for your assistance. We are using the same Internet provider for both machines and verified with the ISP that they are not blocking any ports. Since we can reverse the setup (ie have the client become the server and the server become the client) this suggests that this is not an issue with the ISP. There is no firewall or security software running on the server machine and no other programs are trying to claim port 5900. A netstat -a reveals that port 5900 is unused before winvnc is running and that it is open and listening after winvnc is launched. So I can4t telnet to that port and I cannot figure out why. Any help or suggestions would be greatly appreciated! In the meanwhile, I will install a new telnet client and hopefully it will give me a more informative error message. Harald - ----- Original Message ----- From: Michael Ossmann <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 17, 2002 6:35 PM Subject: Re: Problems connecting through internet > On Thu, Jan 17, 2002 at 04:49:58PM -0600, Hotel Puesta del Sol wrote: > > > > At this point, I think that the problem is linked to my inablity to telnet to > > the machine and I would appreciate it if anyone had suggestions as to what > > might be causing this. > > Yes, it sounds like you are correct. This is most likely due to some > sort of firewall configuration either on your part or your Internet > provider's at either the client side or the server side. You can > probably determine whether it is on the client side or the server side > by testing a telnet to port 5900 from a third Internet location. > > -- > Mike Ossmann, Tarantella/UNIX Engineer/Instructor > Alternative Technology, Inc. http://www.alttech.com/ > --------------------------------------------------------------------- > To unsubscribe, mail [EMAIL PROTECTED] with the line: > 'unsubscribe vnc-list' in the message BODY > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- ------------------------------ Date: Fri, 18 Jan 2002 09:35:51 -0500 From: "Christopher Tesla" <[EMAIL PROTECTED]> Subject: RE: Error while waiting for server message Do you have a static IP address through the cable company? Since the cable modems have the external NAT IP set via DHCP by the ISP you may be seeing your IP address changed. So you are able to connect, but in between a request by the viewer and a response from the server the IP address is changing and you cannot receive the server response. From what I understand there is a very small pool of addresses available for a specific user group, so eventually your original address will be re-leased to you...hence you are able to re-connect to the server after a period of time. How long do you have to wait before you are able to re-connect to the remote PCs? Just a thought. I have been trying to document how frequently my ISP changes my cable modem's address (using AT scheduled IPCONFIG commands piped to a text document) and it seems to be pretty infrequent. But who knows...yours may have a much more brief lease period. Good luck! C-ya Chris Tesla > -----Original Message----- > From: Steve Holmes [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 18, 2002 12:03 AM > To: [EMAIL PROTECTED] > Subject: Error while waiting for server message > > > Hello group! > > I am hoping someone can provide guidance with this problem. > > I have two remote PCs running WinVNC as a service behind a Linksys NAT > (ports redirected) and a cable modem. When I try to connect > to either one, > it accepts the password and displays the screen as it should. > > However, the connection is somehow lost within a range of 5 > to 15 seconds. > During this period I am able to control the remote PC. After > another 20 > seconds or so VNC Viewer closes. (TightVNC viewer generates > a dialog box > with this message "Error while waiting for server message".) After a > certain timeout the remote PC will start accepting > connections again, but I > still can't get a connection for longer than 5-15 seconds. > > I can use VNC internally on the LAN without any trouble, so I > suspect either > the Linksys firewall or the cable modem. I don't know how to go about > testing though. I have other Linksys boxes in place and they > all work fine. > > Any suggestions will be greatly appreciated. > > Thanks > Steve > > from Steve Holmes > --------------------------------------------------------------------- > To unsubscribe, mail [EMAIL PROTECTED] with the line: > 'unsubscribe vnc-list' in the message BODY > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- ------------------------------ Date: Fri, 18 Jan 2002 10:02:34 -0500 From: "Chuck Renner" <[EMAIL PROTECTED]> Subject: RE: WinVNC and CTRL+ALT+DEL can't view active remote process ? This is a Windows problem. If you are using an NT kernel (NT 3.5, 4, Win2000, or WinXP), you just need to make sure you are running WinVNC as a service. If you are using a personal OS (Win 95, 98, 98SE, ME), you are out of luck. CTRL+ALT+DEL stops ALL processes, and you cannot remote control the machine. I hope this helps. - - Chuck Renner Director of Technical Serices ICT/Data On CD www.dataoncd.com - -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Thursday, January 17, 2002 3:17 AM To: [EMAIL PROTECTED] Subject: WinVNC and CTRL+ALT+DEL can't view active remote process ? Hi, Does anyone has a solution to view active process on remote server winvnc ? When the remote user use ctrl+alt+del key the active process are displayed on the remote pc but not on the winvnc viewer pc. So have you a solution to do this even with anther way or another windows command or another freeware ? Thanks, JPV - --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html - --------------------------------------------------------------------- ------------------------------ Date: Fri, 18 Jan 2002 17:14:29 +0100 From: Dumas Patrice <[EMAIL PROTECTED]> Subject: Re: Updated. Was Re: Success was Re: VNC Server setup on Linux Hi, On Fri, Jan 18, 2002 at 11:20:41AM -0000, David Colliver wrote: > The page has now been updated with the gdmconfig and more importantly, some > debugging information. If anyone has any more information, or can find > problems with the document, please let me know. There are some confusions which aren't that bad, but which should, IMHO be avoided In the section about gdmconfig 3) b) If running Gnome as your desktop, ... It doesn't matter whether your desktop is gnome, kde, icewm or whatever. What matters is whether you use xdm, kdm or gdm as display manager. Thus this should be changed in "If running gdm as your display manager, ...". (nb: in fact in the redhat, in the basic configuration the display manager and the desktop are the same, as they are both set up by /etc/sysconfig/desktop or something like that). - - some settings seems to be valid for all the configurations, but it isn't true. For example, 2) edit 'xdm-config' and comment out the line '! DisplayManager.requestPort: 0' (should be the last line) hasn't any impact on the gdm settings. I think it should be made more clear. I put here a summary of what is needed for the display managers I know: xdm: 2) and 4) 2) edit 'xdm-config' and comment out the line '! DisplayManager.requestPort: 0' (should be the last line) a) RedHat 6.2, 7.1, 7.2 - '/etc/X11/xdm/xdm-config' 4) edit Xaccess and uncomment the line '* #any host can get a login window' a) RedHat 6.2, 7.1, 7.2 -' /etc/X11/xdm/Xaccess' gdm: 3) b) I have never used kdm, but I have heard on another mailing list that for old versions of kdm, the config files used are the same than for xdm (point 2) and 4)) and that for new kdm there is a kdmrc file, as stated in 3) a). Changing config for applications you don't use isn't such a big deal, but I think it may confuse things. Last, I think it should be fine if, in addition to explaining how to set up gdm to accept xdmcp with gdmconfig, there was also a explaination on how to do it manualy, like "edit /etc/X11/gdm/gdm.conf and in the [xdmcp] section, put "Enable=true" and "Port=177"" It is only suggestions, now, do what you want ! Pat ------------------------------ Date: Fri, 18 Jan 2002 11:28:53 -0500 From: "Fisher, Dave" <[EMAIL PROTECTED]> Subject: RE: how do I get VNC to recognize Alt-Tab? go to the VNC Search page and search the VNC Mailing List for Alt Tab http://www.uk.research.att.com/search.html - -----Original Message----- From: Frank S. Kim [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 17, 2002 9:34 AM To: [EMAIL PROTECTED] Subject: how do I get VNC to recognize Alt-Tab? I am guessing this is impossible but is there anyway to get my VNC session to recognize when I am doing an Alt-Tab for switching windows. Thanks, Frank - --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html - --------------------------------------------------------------------- ------------------------------ Date: Fri, 18 Jan 2002 10:20:25 -0700 From: Michael Ossmann <[EMAIL PROTECTED]> Subject: Re: Problems connecting through internet On Fri, Jan 18, 2002 at 08:35:06AM -0600, Hotel Puesta del Sol wrote: > > We are using the same Internet provider for both machines and verified with > the ISP that they are not blocking any ports. Since we can reverse the setup > (ie have the client become the server and the server become the client) this > suggests that this is not an issue with the ISP. There is no firewall or > security software running on the server machine and no other programs are > trying to claim port 5900. A netstat -a reveals that port 5900 is unused > before winvnc is running and that it is open and listening after winvnc is > launched. Very puzzling. Perhaps you could ask your ISP to try the telnet test to both sides from within their network. If you are just taking their word that they are not blocking anything, it might still be a good idea to verify for yourself from a third location. If you don't have a shell account somewhere that you can use, feel free to send me the IP addresses by private email and I'd be happy to test from here. Have you tried any other services (such as a web server)? Are you able to ping in both directions? Are you using IP addresses or DNS names? If DNS, have you verified name service from both sides? - -- Mike Ossmann, Tarantella/UNIX Engineer/Instructor Alternative Technology, Inc. http://www.alttech.com/ ------------------------------ Date: Fri, 18 Jan 2002 09:31:32 -0800 From: "Scott J. Sherratt" <[EMAIL PROTECTED]> Subject: Re: Success was Re: VNC Server setup on Linux Sorry for the newbie questions, but I am having trouble with your VNC setup procedure & need some clarification: http://www.sourcecodecorner.com/articles/vnc/linux.asp#vncserver.inetd I am running Red Hat 7.2, gdm ########## Step 6: 6) Update inetd configuration for the services to enable (based on /etc/services) a) inetd - append contents of 'vncserver.inetd' to '/etc/inetd.conf' b) xinetd - copy 'vncserver.xinetd' to '/etc/xinetd.d' (RH 7.2 (not available in my RH6.2) and The file below is vncserver.inetd. This should be added to the end of /etc/inetd.conf. Please note the path. In this document the path is /usr/local/bin/Xvnc. This will need to be modified based on your own system. ########## - - Do I need to do both (a) and (b) ? I have no /etc/inetd.conf file to append anything to... Step "Our last file is for Redhat 7.2" (almost missed this one) ########## This should be copied to the end of /etc/xinet.d. Again, modify the paths to suit your system. This is the vncserver.xinetd. ########## /etc/xinet.d is a directory, not a file. Do I place this as a file /etc/xinet.d/vncserver.xinetd ? Scott J. Sherratt -- Morgan Hill, California [EMAIL PROTECTED] Fax: (208)246-5250 ------------------------------ Date: Fri, 18 Jan 2002 11:55:31 -0600 From: Joel Sherrill <[EMAIL PROTECTED]> Subject: Re: Success was Re: VNC Server setup on Linux "Scott J. Sherratt" wrote: > > Sorry for the newbie questions, but I am having trouble with your VNC setup > procedure & need some clarification: > > http://www.sourcecodecorner.com/articles/vnc/linux.asp#vncserver.inetd > > I am running Red Hat 7.2, gdm > > ########## > Step 6: > 6) Update inetd configuration for the services to enable (based on > /etc/services) > a) inetd - append contents of > 'vncserver.inetd' to '/etc/inetd.conf' > b) xinetd - copy 'vncserver.xinetd' to > '/etc/xinetd.d' (RH 7.2 (not available in my RH6.2) > and > The file below is vncserver.inetd. This should be added to the end of > /etc/inetd.conf. Please note the path. In this > document the path is /usr/local/bin/Xvnc. This will > need to be modified based on your own system. > ########## > > - Do I need to do both (a) and (b) ? I have no /etc/inetd.conf file to > append anything to... Right. RH 7.2 uses xinetd so you do "b" and then restart the xinetd service (/etc/rc.d/init.d/xinetd restart). It writes to /var/log/messages so you should be able to see if it had a problem with the vnc file or any others. (another debugging hint :) > Step "Our last file is for Redhat 7.2" (almost missed this one) > > ########## > This should be copied to the end of /etc/xinet.d. Again, modify the paths > to suit your > system. This is the vncserver.xinetd. > ########## > > /etc/xinet.d is a directory, not a file. Do I place this as a file > /etc/xinet.d/vncserver.xinetd ? I installed it as "vnc" in that directory. If you are running gdm, then you will have to use gdmconfig to turn on port 177. I think the instructions have been updated to reflect this. > Scott J. Sherratt -- Morgan Hill, California > [EMAIL PROTECTED] Fax: (208)246-5250 > --------------------------------------------------------------------- > To unsubscribe, mail [EMAIL PROTECTED] with the line: > 'unsubscribe vnc-list' in the message BODY > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- - -- Joel Sherrill, Ph.D. Director of Research & Development [EMAIL PROTECTED] On-Line Applications Research Ask me about RTEMS: a free RTOS Huntsville AL 35805 Support Available (256) 722-9985 ------------------------------ Date: Fri, 18 Jan 2002 19:02:53 +0100 From: Dumas Patrice <[EMAIL PROTECTED]> Subject: Re: Success was Re: VNC Server setup on Linux > need to be modified based on your own system. > ########## > > - Do I need to do both (a) and (b) ? I have no /etc/inetd.conf file to > append anything to... You just need the xinetd stuff. > > Step "Our last file is for Redhat 7.2" (almost missed this one) > > ########## > This should be copied to the end of /etc/xinet.d. Again, modify the paths > to suit your > system. This is the vncserver.xinetd. > ########## > > /etc/xinet.d is a directory, not a file. Do I place this as a file > /etc/xinet.d/vncserver.xinetd ? Yes Pat ------------------------------ Date: Fri, 18 Jan 2002 18:22:33 -0000 From: "David Colliver" <[EMAIL PROTECTED]> Subject: Re: Success was Re: VNC Server setup on Linux Joel or Jeff, Can you clarify if this works, as the way it currently stands, the instructions are not that clear. Not having RH7.2, I wouldn't know. The way I understood from the instructions is that xinet.d is a file, and that vncserver.xinetd was just the sample text to put into that file. I will then make the instructions a bit clearer. Regards Dave. ~~ All I ask is a chance to prove that money can't make me happy. Collectible dolls from http://www.collectorsdolls.com Web design? Web hosting? http://www.revilloc.com is the answer. Tips, tricks and articles for programmers of all languages on http://www.sourcecodecorner.com Planning a wedding? http://www.bmcweddings.com Advertise your car for free on http://www.drivingseat.com - ----- Original Message ----- From: "Dumas Patrice" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 18, 2002 6:02 PM Subject: Re: Success was Re: VNC Server setup on Linux > > need to be modified based on your own system. > > ########## > > > > - Do I need to do both (a) and (b) ? I have no /etc/inetd.conf file to > > append anything to... > > You just need the xinetd stuff. > > > > > Step "Our last file is for Redhat 7.2" (almost missed this one) > > > > ########## > > This should be copied to the end of /etc/xinet.d. Again, modify the paths > > to suit your > > system. This is the vncserver.xinetd. > > ########## > > > > /etc/xinet.d is a directory, not a file. Do I place this as a file > > /etc/xinet.d/vncserver.xinetd ? > > Yes > > Pat > --------------------------------------------------------------------- > To unsubscribe, mail [EMAIL PROTECTED] with the line: > 'unsubscribe vnc-list' in the message BODY > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To download your own free RevilloC mailserver, visit http://www.revilloc.com/mailserver ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ------------------------------ Date: Fri, 18 Jan 2002 19:35:44 +0100 From: Dumas Patrice <[EMAIL PROTECTED]> Subject: Re: Success was Re: VNC Server setup on Linux On Fri, Jan 18, 2002 at 06:22:33PM -0000, David Colliver wrote: > Joel or Jeff, > > Can you clarify if this works, as the way it currently stands, the > instructions are not that clear. Not having RH7.2, I wouldn't know. The way > I understood from the instructions is that xinet.d is a file, and that No, no, it is a directory. All the files in that directory are sourced by xinetd. > vncserver.xinetd was just the sample text to put into that file. I will then > make the instructions a bit clearer. vncserver.xinetd should be considered as a file. Pat ------------------------------ Date: Fri, 18 Jan 2002 12:35:20 -0600 From: Joel Sherrill <[EMAIL PROTECTED]> Subject: Re: Success was Re: VNC Server setup on Linux David Colliver wrote: > > Joel or Jeff, > > Can you clarify if this works, as the way it currently stands, the > instructions are not that clear. Not having RH7.2, I wouldn't know. The way > I understood from the instructions is that xinet.d is a file, and that > vncserver.xinetd was just the sample text to put into that file. I will then > make the instructions a bit clearer. /etc/xinet.d is a directory which contains one file per service. I put your file named vncserver.xinetd in there with the name "vnc". Then I restarted xinetd using "/etc/rc.d/init.d/xinetd restart" and watched /var/log/messages for complaints. > Regards > Dave. > ~~ > All I ask is a chance to prove that money can't make me happy. > > Collectible dolls from http://www.collectorsdolls.com > Web design? Web hosting? http://www.revilloc.com is the answer. > Tips, tricks and articles for programmers of all languages on > http://www.sourcecodecorner.com > Planning a wedding? http://www.bmcweddings.com > Advertise your car for free on http://www.drivingseat.com > > ----- Original Message ----- > From: "Dumas Patrice" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, January 18, 2002 6:02 PM > Subject: Re: Success was Re: VNC Server setup on Linux > > > > need to be modified based on your own system. > > > ########## > > > > > > - Do I need to do both (a) and (b) ? I have no /etc/inetd.conf file to > > > append anything to... > > > > You just need the xinetd stuff. > > > > > > > > Step "Our last file is for Redhat 7.2" (almost missed this one) > > > > > > ########## > > > This should be copied to the end of /etc/xinet.d. Again, modify the > paths > > > to suit your > > > system. This is the vncserver.xinetd. > > > ########## > > > > > > /etc/xinet.d is a directory, not a file. Do I place this as a file > > > /etc/xinet.d/vncserver.xinetd ? > > > > Yes > > > > Pat > > --------------------------------------------------------------------- > > To unsubscribe, mail [EMAIL PROTECTED] with the line: > > 'unsubscribe vnc-list' in the message BODY > > See also: http://www.uk.research.att.com/vnc/intouch.html > > --------------------------------------------------------------------- > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > To download your own free RevilloC mailserver, visit http://www.revilloc.com/mailserver > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > --------------------------------------------------------------------- > To unsubscribe, mail [EMAIL PROTECTED] with the line: > 'unsubscribe vnc-list' in the message BODY > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- - -- Joel Sherrill, Ph.D. Director of Research & Development [EMAIL PROTECTED] On-Line Applications Research Ask me about RTEMS: a free RTOS Huntsville AL 35805 Support Available (256) 722-9985 ------------------------------ Date: Fri, 18 Jan 2002 15:52:13 -0500 From: "Chuck Renner" <[EMAIL PROTECTED]> Subject: RE: Providing (Windows) VNC support to clients that have strict... OK. The registry setting AllowLoopback does not work when connecting WinVNC to a VNCviewer. Thanks. Darn! I might still have to have a custom compile. - -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Scott C. Best Sent: Thursday, January 17, 2002 4:26 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Providing (Windows) VNC support to clients that have strict... Chuck: Heya. You've probably already discovered this, but there's a registry setting you need to make to your VNC server machine to allow loopback: http://www.uk.research.att.com/vnc/winvnc.html Down at the bottom, AllowLoopback. Or, even more aggressive, try LoopbackOnly (which appears to be specific to working well with SSH tunneling). Hope one of them is what you're looking for! - -Scott > Ok. I have tested this scenario. The tunneling works fine, but the total > picture does not. > > When you make the connection from WinVNC to VNCviewer using the tunnel > through SSH, the VNCviewer on the other end thinks it is an "internal > loopback connection", and disconnects you. This happens regardless of which > IP address you use on the WinVNC machine. > > Since VNCviewer states, "Internal loopback connections are not allowed", the > implication is that there is a setting that WILL allow them, either in the > source, or in the GUI settings. Is this the case? > > So the solution just got more complicated. > > To avoid the VNCviewer thinking the connection is a loopback, you have to > run the SSH client on a completely separate machine on the same LAN, and > have to allow it to receive connections on its local port from other hosts, > like so: > > WinVNC on ClientWS1 ---> SSH on ClientWS2 port 5500 --> Internet --> sshd on > MYFirewall port 443 --> VNCviewer on MyWS1 port 5500 > > This I have tested, and it works, but presents the following major two > problems: > > 1. This is too complicated for the client. > 2. Opening the SSH connection from the client to the SSHD your Linux > firewall is effectively like creating a VPN connection from the client to > your network. This opens a huge security hole in your network, and gives > someone on the client's network the ability to snoop around your network > when the connection is made. > > I am concerned about tunneling VNC through SSH, because it gives the client > the ability to create more tunnels. Is it really wise to secure the client > VNC connection, at the cost of exposing your own network to the client? > > Feedback is greatly appreciated. - --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html - --------------------------------------------------------------------- ------------------------------ Date: Fri, 18 Jan 2002 15:52:13 -0500 From: "Chuck Renner" <[EMAIL PROTECTED]> Subject: RE: Providing (Windows) VNC support to clients that have strict corporate firewalls Thanks. The "permitopen" option works really well on the sshd. The only way I seem to be able to get around the loopback restriction is by running the ssh client on an intermediate machine. The "AllowLoopback" registry setting changes nothing. - - Chuck Renner - -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Michael Ossmann Sent: Wednesday, January 16, 2002 3:26 PM To: [EMAIL PROTECTED] Subject: Re: Providing (Windows) VNC support to clients that have strict corporate firewalls On Wed, Jan 16, 2002 at 02:40:16PM -0500, Chuck Renner wrote: > > Since VNCviewer states, "Internal loopback connections are not allowed", the > implication is that there is a setting that WILL allow them, either in the > source, or in the GUI settings. Is this the case? I wasn't expecting this. I have no idea why loopback connections wouldn't be allowed, and I suspect a source code change would be required to change it. Anyone? > 2. Opening the SSH connection from the client to the SSHD your Linux > firewall is effectively like creating a VPN connection from the client to > your network. This opens a huge security hole in your network, and gives > someone on the client's network the ability to snoop around your network > when the connection is made. One of the advantages of using public key authentication is that OpenSSH can limit port forwarding to particular host:port combinations specified by the permitonly option in the authorized_keys file. - -- Mike Ossmann, Tarantella/UNIX Engineer/Instructor Alternative Technology, Inc. http://www.alttech.com/ - --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html - --------------------------------------------------------------------- ------------------------------ Date: Fri, 18 Jan 2002 16:21:56 -0500 From: "Steve Palocz" <[EMAIL PROTECTED]> Subject: RE: Providing (Windows) VNC support to clients that have strict corporate firewalls Please go to the vnc website and read the documentation. As we have told you the answer that works for us and it is documented there. - -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Chuck Renner Sent: Friday, January 18, 2002 3:52 PM To: [EMAIL PROTECTED] Subject: RE: Providing (Windows) VNC support to clients that have strict corporate firewalls Thanks. The "permitopen" option works really well on the sshd. The only way I seem to be able to get around the loopback restriction is by running the ssh client on an intermediate machine. The "AllowLoopback" registry setting changes nothing. - - Chuck Renner - -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Michael Ossmann Sent: Wednesday, January 16, 2002 3:26 PM To: [EMAIL PROTECTED] Subject: Re: Providing (Windows) VNC support to clients that have strict corporate firewalls On Wed, Jan 16, 2002 at 02:40:16PM -0500, Chuck Renner wrote: > > Since VNCviewer states, "Internal loopback connections are not allowed", the > implication is that there is a setting that WILL allow them, either in the > source, or in the GUI settings. Is this the case? I wasn't expecting this. I have no idea why loopback connections wouldn't be allowed, and I suspect a source code change would be required to change it. Anyone? > 2. Opening the SSH connection from the client to the SSHD your Linux > firewall is effectively like creating a VPN connection from the client to > your network. This opens a huge security hole in your network, and gives > someone on the client's network the ability to snoop around your network > when the connection is made. One of the advantages of using public key authentication is that OpenSSH can limit port forwarding to particular host:port combinations specified by the permitonly option in the authorized_keys file. - -- Mike Ossmann, Tarantella/UNIX Engineer/Instructor Alternative Technology, Inc. http://www.alttech.com/ - --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html - --------------------------------------------------------------------- - --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html - --------------------------------------------------------------------- ------------------------------ Date: Fri, 18 Jan 2002 15:38:47 -0700 From: "Jeff Vincent" <[EMAIL PROTECTED]> Subject: Re: Updated. Was Re: Success was Re: VNC Server setup on Linux The problems I had when I started writing the initial draft that David has now adapted is that older versions of gdm and kdm both did seem to use the xdm-config files from what I remember. My old SuSe box did (I believe anyway). It is all sort of blurring together. If you know which configuration files each version of each dm uses, let us/me know. It will definitely simplify things. I started doing it by distribution/OS version but it may need to be based on dm/version to show what configuration files each uses. Then each dm/version section could just reference the files that it uses. The file section could then just explain what needs to change for that file alone. I didn't (and still don't) have all knowledge and just started throwing it together as I got it working. Now as xinetd comes into play with more of the distributions, it adds one more twist to an already tangled mess. Also, as the dm's progress, they seem to be going to their own set of config files. For example, the kdmrc file for kdm in the Debian (woody-testing) version I could NOT get to work at all with Xvnc (grey screen only). My guess is that the version of kdm it was using at the time was still trying to reference the xdm-config or other xdm files and because they weren't there, it didn't work right. That is my take. I got gdm working the first time. All suggestions are welcomed and appreciated and thanks for the other corrections. That is what this was intended to do, get input and refinements to make it start to crystalize into a really helpful document. It sure beats trying to muck through a search of the list archives. Jeff >>> [EMAIL PROTECTED] 01/18/02 09:14AM >>> Hi, On Fri, Jan 18, 2002 at 11:20:41AM -0000, David Colliver wrote: > The page has now been updated with the gdmconfig and more importantly, some > debugging information. If anyone has any more information, or can find > problems with the document, please let me know. There are some confusions which aren't that bad, but which should, IMHO be avoided In the section about gdmconfig 3) b) If running Gnome as your desktop, ... It doesn't matter whether your desktop is gnome, kde, icewm or whatever. What matters is whether you use xdm, kdm or gdm as display manager. Thus this should be changed in "If running gdm as your display manager, ...". (nb: in fact in the redhat, in the basic configuration the display manager and the desktop are the same, as they are both set up by /etc/sysconfig/desktop or something like that). - - some settings seems to be valid for all the configurations, but it isn't true. For example, 2) edit 'xdm-config' and comment out the line '! DisplayManager.requestPort: 0' (should be the last line) hasn't any impact on the gdm settings. I think it should be made more clear. I put here a summary of what is needed for the display managers I know: xdm: 2) and 4) 2) edit 'xdm-config' and comment out the line '! DisplayManager.requestPort: 0' (should be the last line) a) RedHat 6.2, 7.1, 7.2 - '/etc/X11/xdm/xdm-config' 4) edit Xaccess and uncomment the line '* #any host can get a login window' a) RedHat 6.2, 7.1, 7.2 -' /etc/X11/xdm/Xaccess' gdm: 3) b) I have never used kdm, but I have heard on another mailing list that for old versions of kdm, the config files used are the same than for xdm (point 2) and 4)) and that for new kdm there is a kdmrc file, as stated in 3) a). Changing config for applications you don't use isn't such a big deal, but I think it may confuse things. Last, I think it should be fine if, in addition to explaining how to set up gdm to accept xdmcp with gdmconfig, there was also a explaination on how to do it manualy, like "edit /etc/X11/gdm/gdm.conf and in the [xdmcp] section, put "Enable=true" and "Port=177"" It is only suggestions, now, do what you want ! Pat - --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html - --------------------------------------------------------------------- ------------------------------ Date: 18 Jan 2002 19:51:39 -0600 From: ScanMan <[EMAIL PROTECTED]> Subject: RE: How do I know if I have it? What's the only OS that doesn't even pretend to be secure? Duh. On Mon, 2002-01-14 at 11:12, Andrew Cornish wrote: > what o/s do you have ?? > > > Dork Monical wrote > Dear All, > > How do I know if someone has placed a copy of VNC on my computer to help > them hack it? I suspect someone is getting access to my computer and have > messed with it some. > > Thanks in advance, > Dork Monical ------------------------------ Date: Fri, 18 Jan 2002 19:52:34 -0700 From: Dave Warren <[EMAIL PROTECTED]> Subject: Re: How do I know if I have it? Palm OS ScanMan wrote: > What's the only OS that doesn't even pretend to be secure? Duh. - -- The nice thing about standards, there is enough for everyone to have their own. ------------------------------ Date: Sat, 19 Jan 2002 10:59:23 +0800 From: "Daniel Tan" <[EMAIL PROTECTED]> Subject: Re: Success was Re: VNC Server setup on Linux my xinetd doesn't support restart..i am using RH 7.0...anyone have any idea of an alternate way? - ----- Original Message ----- From: "Joel Sherrill" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, January 19, 2002 2:35 AM Subject: Re: Success was Re: VNC Server setup on Linux > David Colliver wrote: > > > > Joel or Jeff, > > > > Can you clarify if this works, as the way it currently stands, the > > instructions are not that clear. Not having RH7.2, I wouldn't know. The way > > I understood from the instructions is that xinet.d is a file, and that > > vncserver.xinetd was just the sample text to put into that file. I will then > > make the instructions a bit clearer. > > /etc/xinet.d is a directory which contains one file per service. > I put your file named vncserver.xinetd in there with the name "vnc". > Then I restarted xinetd using "/etc/rc.d/init.d/xinetd restart" > and watched /var/log/messages for complaints. > > > Regards > > Dave. > > ~~ > > All I ask is a chance to prove that money can't make me happy. > > > > Collectible dolls from http://www.collectorsdolls.com > > Web design? Web hosting? http://www.revilloc.com is the answer. > > Tips, tricks and articles for programmers of all languages on > > http://www.sourcecodecorner.com > > Planning a wedding? http://www.bmcweddings.com > > Advertise your car for free on http://www.drivingseat.com > > > > ----- Original Message ----- > > From: "Dumas Patrice" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Friday, January 18, 2002 6:02 PM > > Subject: Re: Success was Re: VNC Server setup on Linux > > > > > > need to be modified based on your own system. > > > > ########## > > > > > > > > - Do I need to do both (a) and (b) ? I have no /etc/inetd.conf file to > > > > append anything to... > > > > > > You just need the xinetd stuff. > > > > > > > > > > > Step "Our last file is for Redhat 7.2" (almost missed this one) > > > > > > > > ########## > > > > This should be copied to the end of /etc/xinet.d. Again, modify the > > paths > > > > to suit your > > > > system. This is the vncserver.xinetd. > > > > ########## > > > > > > > > /etc/xinet.d is a directory, not a file. Do I place this as a file > > > > /etc/xinet.d/vncserver.xinetd ? > > > > > > Yes > > > > > > Pat > > > --------------------------------------------------------------------- > > > To unsubscribe, mail [EMAIL PROTECTED] with the line: > > > 'unsubscribe vnc-list' in the message BODY > > > See also: http://www.uk.research.att.com/vnc/intouch.html > > > --------------------------------------------------------------------- > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > To download your own free RevilloC mailserver, visit http://www.revilloc.com/mailserver > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > --------------------------------------------------------------------- > > To unsubscribe, mail [EMAIL PROTECTED] with the line: > > 'unsubscribe vnc-list' in the message BODY > > See also: http://www.uk.research.att.com/vnc/intouch.html > > --------------------------------------------------------------------- > > -- > Joel Sherrill, Ph.D. Director of Research & Development > [EMAIL PROTECTED] On-Line Applications Research > Ask me about RTEMS: a free RTOS Huntsville AL 35805 > Support Available (256) 722-9985 > --------------------------------------------------------------------- > To unsubscribe, mail [EMAIL PROTECTED] with the line: > 'unsubscribe vnc-list' in the message BODY > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- ------------------------------ Date: Sat, 19 Jan 2002 11:18:00 +0800 From: "Daniel Tan" <[EMAIL PROTECTED]> Subject: Re: Success was Re: VNC Server setup on Linux i tried typing Xvnc and i got this error message. i typed this while using Xmanager to log in... Fatal Server Error: Couldn't add screen - ----- Original Message ----- From: "Joel Sherrill" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, January 19, 2002 2:35 AM Subject: Re: Success was Re: VNC Server setup on Linux > David Colliver wrote: > > > > Joel or Jeff, > > > > Can you clarify if this works, as the way it currently stands, the > > instructions are not that clear. Not having RH7.2, I wouldn't know. The way > > I understood from the instructions is that xinet.d is a file, and that > > vncserver.xinetd was just the sample text to put into that file. I will then > > make the instructions a bit clearer. > > /etc/xinet.d is a directory which contains one file per service. > I put your file named vncserver.xinetd in there with the name "vnc". > Then I restarted xinetd using "/etc/rc.d/init.d/xinetd restart" > and watched /var/log/messages for complaints. > > > Regards > > Dave. > > ~~ > > All I ask is a chance to prove that money can't make me happy. > > > > Collectible dolls from http://www.collectorsdolls.com > > Web design? Web hosting? http://www.revilloc.com is the answer. > > Tips, tricks and articles for programmers of all languages on > > http://www.sourcecodecorner.com > > Planning a wedding? http://www.bmcweddings.com > > Advertise your car for free on http://www.drivingseat.com > > > > ----- Original Message ----- > > From: "Dumas Patrice" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Friday, January 18, 2002 6:02 PM > > Subject: Re: Success was Re: VNC Server setup on Linux > > > > > > need to be modified based on your own system. > > > > ########## > > > > > > > > - Do I need to do both (a) and (b) ? I have no /etc/inetd.conf file to > > > > append anything to... > > > > > > You just need the xinetd stuff. > > > > > > > > > > > Step "Our last file is for Redhat 7.2" (almost missed this one) > > > > > > > > ########## > > > > This should be copied to the end of /etc/xinet.d. Again, modify the > > paths > > > > to suit your > > > > system. This is the vncserver.xinetd. > > > > ########## > > > > > > > > /etc/xinet.d is a directory, not a file. Do I place this as a file > > > > /etc/xinet.d/vncserver.xinetd ? > > > > > > Yes > > > > > > Pat > > > --------------------------------------------------------------------- > > > To unsubscribe, mail [EMAIL PROTECTED] with the line: > > > 'unsubscribe vnc-list' in the message BODY > > > See also: http://www.uk.research.att.com/vnc/intouch.html > > > --------------------------------------------------------------------- > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > To download your own free RevilloC mailserver, visit http://www.revilloc.com/mailserver > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > --------------------------------------------------------------------- > > To unsubscribe, mail [EMAIL PROTECTED] with the line: > > 'unsubscribe vnc-list' in the message BODY > > See also: http://www.uk.research.att.com/vnc/intouch.html > > --------------------------------------------------------------------- > > -- > Joel Sherrill, Ph.D. Director of Research & Development > [EMAIL PROTECTED] On-Line Applications Research > Ask me about RTEMS: a free RTOS Huntsville AL 35805 > Support Available (256) 722-9985 > --------------------------------------------------------------------- > To unsubscribe, mail [EMAIL PROTECTED] with the line: > 'unsubscribe vnc-list' in the message BODY > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- ------------------------------ End of vnc-list-digest V1 #1416 ******************************* To stop receiving this digest, mail [EMAIL PROTECTED] with the line 'unsubscribe vnc-list-digest' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
