From John_Roland_Elliott@Hotmail.com Sat Sep 1 00:14:03 2001 From: John_Roland_Elliott@Hotmail.com (John Roland Elliott) Date: Fri, 31 Aug 2001 23:14:03 +0000 Subject: Undocumented port in use by VNCviewer in Listen Mode? References: <2033C9E0A219D511914300508B44C0E511267D@CFJH> Message-ID: Roy, Pete, Zoran, Zalman, and all --- Thanks for considering my poorly posed question and thanks for your theories. Let me try my question again, a little more precisely and completely stated this time. The FAQ (http://www.uk.research.att.com/vnc/faq.html#q52) states, and I have observed, that the VNC server listens on port 5900+n (where n is the "display number") and that when the VNC viewer initiates a session with the server, it does so through that port. The FAQ (http://www.uk.research.att.com/vnc/faq.html#q52) states, and I have observed, that the VNC server listens on port 5800+n (where n is the "display number") and, on that port, answers as a minimalist web server which delivers the java implementation of the VNC viewer. Once the (java) VNC viewer is delivered to the machine that is to act as viewer, the java VNC viewer communicates with the VNC server through port 5900+n, just like the non-java VNC viewer. Ports 5900+n and 5800+n are open on machines running a VNC server (WinVNC, e.g.) and the (java or non-java) VNC viewer connects only to 5900+n. 5800+n is used only to fetch the java viewer (vncviewer.class in vncviewer.jar) from the machine running the VNC server. It is my understanding that the viewer, once it is loaded, regardless of how it is loaded, communicates with the server through the server's port 5900+n. I don't think that 5800+n is used as a control channel, or anything other than fetching the java client. I conclude this by configuring a firewall that defends the machine running the VNC server. When I configure it to drop inbound traffic on port 5800 I can successfully establish a VNC session from the other side of the firewall using the non-java VNC viewer. Further, I conducted the following experiment: 1) on the firewall between my viewer and server, I enabled 5800 (for loading the java VNC viewer) and disabled 5900 going from viewer to server 2) from my favorite java-capable web browser, I went to http://myVNCserver:5800 and got the VNC authentication page asking for a VNC password 3) at that point, I reconfigured my firewall to disable 5800 (the viewer is already loaded in the virtual machine of the machine that is to be viewer) and enable 5900 (so that the viewer could do something constructive) going from viewer to server 4) back at my web browser, which was still displaying the VNC authentication page, I entered the VNC password and established a session (without access to 5800 on the server but with 5900 on the server accessible) This experiment convinced me that a) 5800 is necessary and sufficient to load the java VNC viewer (i.e., 5900 is not needed for *loading* and *starting* the java VNC viewer) and b) 5900 is necessary and sufficient for the (java) VNC viewer (i.e., 5800 is not needed for *running* the VNC viewer, even the java one). I stress that 5800+n and 5900+n are VNC server ports. Those ports are not open on the VNC viewer machine (unless it is also running VNC server.) The FAQ (http://www.uk.research.att.com/vnc/faq.html#q52) states, and I have observed, that the VNC viewer (not server) listens on port 5500. When, from a VNC server, you "Add New Client", the server initiates a session with the viewer through the viewer's port 5500. In this mode of operation, the viewer does not use the server's 5900+n, which would have been used if the viewer had initiated the connection; I suspect, but I haven't confirmed, that the server continues to talk to the viewer's port 5500 and the viewer talks to the port that the server opened in order to call the viewer. So, I think I understand 5500, 5800+n, and 5900+n, but I'm still mystified by 5400. What I know is: 1) it is created on the viewer machine when I "Run VNCviewer (Listen Mode)" 2) it is destroyed on the viewer machine when I "Close listening daemon" 3) it is unused (or at least not required) during the conventional operation (viewer initiates the connection) 4) it is unused (or at least not required) by the java VNC viewer What I would like to know is does it serve any function whatsoever. In exchange for this knowledge I am prepared to offer my eternal gratitude and undying devotion. I really don't want to have to try to read the source (what is it? ... Object Oriented COBOL? ... "ADD-1-TO-COBOL-GIVING-COBOL"?) Regards, JRE P.S. One last clue: If, on the machine that has "Run VNCviewer (Listen Mode)", I go to http://localhost:5400, briefly, in maybe 36-point text, I see "plication/vnd.ms-excel, applica" at the top of the screen. ----- Original Message ----- From: "Zalman Margareten" To: Sent: Friday, August 31, 2001 12:39 PM Subject: RE: Undocumented port in use by VNCviewer in Listen Mode? > Are u trying to imply that it will establish the connection with port 5400 > and then hand it over to 5500? I can understand this with the "regular" > connection that is initiated from the viewer where it will send a sync to > 5800 and then establish a connection with 5900. But how do u explain it with > the "listener" method where it starts with 5500 according to my ( netstat -n > readings )? > > -----Original Message----- > From: Roy Long [mailto:roy@ncitech.com] > Sent: Friday, August 31, 2001 9:46 AM > To: vnc-list@uk.research.att.com > Subject: Re: Undocumented port in use by VNCviewer in Listen Mode? > > > >The documentation indicates that VNCviewer in Listen Mode uses port 5500. > It > >appears that when I start VNCviewer in Listen Mode, my machine also listens > >on port 5400, at least my Windows 2000 machine does. After stopping Listen > >Mode, both 5500 and 5400 are closed. I have set my firewall to block 5400 > >and allow 5500 and it seems to continue to work. > > > >As port 5400 is associated with the Blade Runner Trojan, I was a little > >alarmed to discover it open on one of my machines. > > > >Can anyone provide any illumination on the subject of VNC's use of port > >5400? > > I believe 5400 is the java web browser port for the viewer, just like > 5800 works for the java web browser port on the "normal" VNC server. > -- > Roy Long - KB3CZD > Computer Technician > NCI Technologies > 126 N. 2nd Street > Philipsburg PA 16866 > > roy@ncitech.com > > > > > -----BEGIN GEEK CODE BLOCK----- > Version: 3.12 > GO@ d-@ s: a- C++ C--- U+++ P+ L++>$ E--- W+ N+ w > M++$ PS PE+ PGP+ t+ 5 X R- tv b+ DI++ D G h--- r+++ y--(+++) > ------END GEEK CODE BLOCK------ > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From ccah@thegreen.co.uk Sat Sep 1 01:02:33 2001 From: ccah@thegreen.co.uk (Ceri Hankey) Date: Sat, 01 Sep 2001 00:02:33 +0000 Subject: SOCKS 5 support added to Win32 VNC Viewer References: <20010829203929.44975.qmail@web20303.mail.yahoo.com> <3B8D8BC1.11D52F86@Seanster.com> <000e01c131a6$a6294820$6764a8c0@ceri4> <7k1uotc5eispmh9b65ked80aij1ch3dl5a@4ax.com> Message-ID: <005001c13270$69c7c3f0$6764a8c0@ceri4> Sorry, but my proxy server tells me for the nth time ... Error : Can't connect to host www.google.com on port 80! Reason : Connect timeout. Error detected by WinProxy 1.4 If you can mail it to me at ceri_hankey@wanadoo.fr Thank you very much! Regards Ceri Hankey ----- Original Message ----- From: "Seanster" To: Sent: Friday, August 31, 2001 5:57 AM Subject: Re: SOCKS 5 support added to Win32 VNC Viewer > Just a brief net outage. I can mail it if anyone has trouble beyond that. > -Sean > > > On Fri, 31 Aug 2001 00:51:38 +0200, you wrote: > > >I cannot get thru to your site ... > >http://www.Seanster.com/vnc/ > > > >Can you give another source for your stuff? > > > >Thanks > > > >Ceri Hankey > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From spencer@silcom.com Sat Sep 1 02:24:03 2001 From: spencer@silcom.com (spencer) Date: Sat, 01 Sep 2001 01:24:03 +0000 Subject: VNC NTServer VPN Message-ID: <000001c1327b$4fbc9610$64c8690a@Carola> I am trying to use VNC to access a Windows NT Server (Backup Domain Controller, BDC). I am accessing the BDC via an all Microsoft VPN. I have RAS on the Server and use the PPTP protocol to connect. I can connect to the server (and have been doing this for some time now). Here is my setup. Corporate- NT Server, BDC running behind a Linksys BEFSR41 nat router. Public IP on the Wan side of the Linksys router. Forwarding ports 80, 25, 110, and 1723 (for Linksys to work with VPN) to the 192.168.xxx.xxx NT BDC. Remote- NT Workstation, running behind a Linksys BEFSR41 nat router, dynamic public IP (which has not changed in months). The Problem: I have loaded WinVNC onto that server and can use the Win 98 client viewer while on the local LAN. However, when on the remote NT Workstation I can successfully connect to Corporate, but I cannot successfully run the WinNT VNC client. I can enter the IP address of the remote machine, I get prompted for a password and the remote screen initiates, then turns all black, and then shuts down. Question: Has anyone successfully connected VNC via a VPN tunnel of any type, and specifically the type described above. Thank you in advance. --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From martin.sarter@web.de Sat Sep 1 18:36:45 2001 From: martin.sarter@web.de (Martin Sarter) Date: Sat, 01 Sep 2001 17:36:45 +0000 Subject: KDE again In-Reply-To: <001b01c12f87$4fa21fc0$0100000a@home.net> Message-ID: Hi, I searched the archive, watched the mailing list for several weeks, followed the usual hints (modifying xsetup, setting -depth to the appropriate) but KDE still isn't working with VNC. All I get is a vncviewer window with a konsole and the KDE background color but no icons, no background image, no task bar, no window elements to the konsole. I have SuSE 7.1 running. Any hints? Martin. Here's the log: --------------------------------- 01/09/01 17:02:51 Xvnc version 3.3.3r1 01/09/01 17:02:51 Copyright (C) AT&T Laboratories Cambridge. 01/09/01 17:02:51 All Rights Reserved. 01/09/01 17:02:51 See http://www.uk.research.att.com/vnc for information on VNC 01/09/01 17:02:51 Desktop name 'X' (linux:1) 01/09/01 17:02:51 Protocol version supported 3.3 01/09/01 17:02:51 Listening for VNC connections on TCP port 5901 01/09/01 17:02:51 Listening for HTTP connections on TCP port 5801 01/09/01 17:02:51 URL http://linux:5801 --------------------------------- It looks like dcopserver is already running. If you are sure that it is not already running, remove /root/.DCOPserver_linux and start dcopserver again. --------------------------------- kdesktop is already running! KDE Daemon (kded) already running. Could not load library! Trying exec.... Launched ok, pid = 1011 Server has no DPMS extension There are already artsd objects registered, looking if they are active... ERROR: kicker is already running! klipper is already running! Error: Can't add object reference (probably artsd is already running). If you are sure it is not already running, remove the relevant files: /tmp/mcop-root/Arts_SimpleSoundServer /tmp/mcop-root/Arts_PlayObjectFactory /tmp/mcop-root/Arts_AudioManager kwrited is already running.ERROR: KUniqueApplication: DCOP communication error! QSocketNotifier: Multiple socket notifiers for same socket 6 and type read 01/09/01 17:04:15 Got connection from client 127.0.0.1 01/09/01 17:04:16 Protocol version 3.3 01/09/01 17:04:22 Pixel format for client 127.0.0.1: 01/09/01 17:04:22 32 bpp, depth 24, little endian 01/09/01 17:04:22 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0 01/09/01 17:04:22 Using raw encoding for client 127.0.0.1 --------------------------------- --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From petasis@iit.demokritos.gr Sat Sep 1 18:53:04 2001 From: petasis@iit.demokritos.gr (Georgios Petasis) Date: Sat, 01 Sep 2001 17:53:04 +0000 Subject: KDE again References: Message-ID: <002701c13305$7ccf54a0$0103e98f@aias> That is very strange. I use both KDE 1.x and 2.x under VNC in both solaris and linux with no problems. I will suggest that you kill your VNC server, kill all KDE processes, start a new VNC server without loading anything in it, set the proper display variable and type "startkde". What is then happening? Make sure that nothing is run in the server before you run startkde, not even a window manager... George > Hi, > > I searched the archive, watched the mailing list for several weeks, followed > the usual hints (modifying xsetup, setting -depth to the appropriate) but > KDE still isn't working with VNC. All I get is a vncviewer window with a > konsole and the KDE background color but no icons, no background image, no > task bar, no window elements to the konsole. I have SuSE 7.1 running. > > Any hints? > > Martin. > > Here's the log: > --------------------------------- > 01/09/01 17:02:51 Xvnc version 3.3.3r1 > 01/09/01 17:02:51 Copyright (C) AT&T Laboratories Cambridge. > 01/09/01 17:02:51 All Rights Reserved. > 01/09/01 17:02:51 See http://www.uk.research.att.com/vnc for information on > VNC > 01/09/01 17:02:51 Desktop name 'X' (linux:1) > 01/09/01 17:02:51 Protocol version supported 3.3 > 01/09/01 17:02:51 Listening for VNC connections on TCP port 5901 > 01/09/01 17:02:51 Listening for HTTP connections on TCP port 5801 > 01/09/01 17:02:51 URL http://linux:5801 > --------------------------------- > It looks like dcopserver is already running. If you are sure > that it is not already running, remove /root/.DCOPserver_linux > and start dcopserver again. > --------------------------------- > > kdesktop is already running! > KDE Daemon (kded) already running. > Could not load library! Trying exec.... > Launched ok, pid = 1011 > Server has no DPMS extension > There are already artsd objects registered, looking if they are active... > ERROR: kicker is already running! > klipper is already running! > > Error: Can't add object reference (probably artsd is already running). > If you are sure it is not already running, remove the relevant files: > > /tmp/mcop-root/Arts_SimpleSoundServer > /tmp/mcop-root/Arts_PlayObjectFactory > /tmp/mcop-root/Arts_AudioManager > > kwrited is already running.ERROR: KUniqueApplication: DCOP communication > error! > QSocketNotifier: Multiple socket notifiers for same socket 6 and type read > > 01/09/01 17:04:15 Got connection from client 127.0.0.1 > 01/09/01 17:04:16 Protocol version 3.3 > 01/09/01 17:04:22 Pixel format for client 127.0.0.1: > 01/09/01 17:04:22 32 bpp, depth 24, little endian > 01/09/01 17:04:22 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0 > 01/09/01 17:04:22 Using raw encoding for client 127.0.0.1 > --------------------------------- > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From sczjd@yahoo.com Sat Sep 1 20:05:45 2001 From: sczjd@yahoo.com (SI Reasoning) Date: Sat, 01 Sep 2001 19:05:45 +0000 Subject: KDE again In-Reply-To: <002701c13305$7ccf54a0$0103e98f@aias> Message-ID: <20010901180055.13660.qmail@web9503.mail.yahoo.com> I had to set the default color to 24 instead of 8 to get kde programs to work properly. I did it by editing /usr/bin/vncserver. --- Georgios Petasis wrote: > That is very strange. I use both KDE 1.x and 2.x > under VNC in both > solaris and linux with no problems. > I will suggest that you kill your VNC server, > kill all KDE processes, start a new VNC server > without loading anything > in it, set the proper display variable and type > "startkde". > What is then happening? > Make sure that nothing is run in the server before > you run startkde, > not even a window manager... > > George > > > Hi, > > > > I searched the archive, watched the mailing list > for several weeks, > followed > > the usual hints (modifying xsetup, setting -depth > to the appropriate) but > > KDE still isn't working with VNC. All I get is a > vncviewer window with a > > konsole and the KDE background color but no icons, > no background image, no > > task bar, no window elements to the konsole. I > have SuSE 7.1 running. > > > > Any hints? > > > > Martin. > > > > Here's the log: > > --------------------------------- > > 01/09/01 17:02:51 Xvnc version 3.3.3r1 > > 01/09/01 17:02:51 Copyright (C) AT&T Laboratories > Cambridge. > > 01/09/01 17:02:51 All Rights Reserved. > > 01/09/01 17:02:51 See > http://www.uk.research.att.com/vnc for information > on > > VNC > > 01/09/01 17:02:51 Desktop name 'X' (linux:1) > > 01/09/01 17:02:51 Protocol version supported 3.3 > > 01/09/01 17:02:51 Listening for VNC connections on > TCP port 5901 > > 01/09/01 17:02:51 Listening for HTTP connections > on TCP port 5801 > > 01/09/01 17:02:51 URL http://linux:5801 > > --------------------------------- > > It looks like dcopserver is already running. If > you are sure > > that it is not already running, remove > /root/.DCOPserver_linux > > and start dcopserver again. > > --------------------------------- > > > > kdesktop is already running! > > KDE Daemon (kded) already running. > > Could not load library! Trying exec.... > > Launched ok, pid = 1011 > > Server has no DPMS extension > > There are already artsd objects registered, > looking if they are active... > > ERROR: kicker is already running! > > klipper is already running! > > > > Error: Can't add object reference (probably artsd > is already running). > > If you are sure it is not already running, > remove the relevant > files: > > > > /tmp/mcop-root/Arts_SimpleSoundServer > > /tmp/mcop-root/Arts_PlayObjectFactory > > /tmp/mcop-root/Arts_AudioManager > > > > kwrited is already running.ERROR: > KUniqueApplication: DCOP communication > > error! > > QSocketNotifier: Multiple socket notifiers for > same socket 6 and type read > > > > 01/09/01 17:04:15 Got connection from client > 127.0.0.1 > > 01/09/01 17:04:16 Protocol version 3.3 > > 01/09/01 17:04:22 Pixel format for client > 127.0.0.1: > > 01/09/01 17:04:22 32 bpp, depth 24, little > endian > > 01/09/01 17:04:22 true colour: max r 255 g 255 b > 255, shift r 16 g 8 b 0 > > 01/09/01 17:04:22 Using raw encoding for client > 127.0.0.1 > > --------------------------------- > > > --------------------------------------------------------------------- > > To unsubscribe, send a message with the line: > unsubscribe vnc-list > > to majordomo@uk.research.att.com > > See also: > http://www.uk.research.att.com/vnc/intouch.html > > > --------------------------------------------------------------------- > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: > unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: > http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- ===== SI Reasoning sczjd@yahoo.com gnupg/pgp key id 035213BC __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From sbest@best.com Sun Sep 2 04:33:14 2001 From: sbest@best.com (Scott C. Best) Date: Sun, 02 Sep 2001 03:33:14 +0000 Subject: New user In-Reply-To: Message-ID: David: Hello! I like these easy ones. :) You cannot connect to the LAN from *outside* of the LAN because of the security provided by the device which is connecting that LAN to the Internet. Sometimes called a firewall/router, sometimes called a gateway, sometimes it's part of the DSL/Cable modem itself. Those things do (amoung other things) something called Network Address Translation, a process specified by RFC-1918. That address range you mention, 192.168.x.y is called a "private address range". So, as a packet travels from a network device to the Internet, the gateway device tranlates it into a "real", world routable IP address assigned by your ISP. So to connect to a VNC server behind one of these gateways, you have to point to this "external IP address", not the 192.168.x.y one. Write back with what sorta gateway device you're using and we can help more! -Scott > I have got WinVNC 3.3.3R9 running on my home network, between my old > computer and my new one. It links fine through my network cards and a > coaxial cable. > > I have now taken my old computer to a friends house and connected it to his > phone line, but I cannot now dial into it from my new computer at home. Nor > can he dial into my computer from there. I seem to have got all the > settings right, but when it dials his number, and it answers, my old > computer does not pick up the signal. What am I doing wrong? I am > searching on the IP number, which is 192.168.0.2 for the old computer and > 192.168.0.1 for the new computer, which works fine on the home network > through the cable connection but I have never got it working through a modem > connection. How do I ping the old computer? How do I telnet, whatever that > is? > > Similarly, I have set up a network of 5 PCs for a client in Birmingham, > which happily use Winvnc to communicate with each other. But I cannot dial > into their system from here, even though I have set up their system to allow > me to do so. > > Any ideas? --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From spencer@silcom.com Sun Sep 2 17:00:30 2001 From: spencer@silcom.com (spencer) Date: Sun, 02 Sep 2001 16:00:30 +0000 Subject: New user References: Message-ID: <003c01c133bf$14edbf60$64c8690a@Carola> Scott, I have a similar issue as stated below. Do you have any suggestions? I am trying to use VNC to access a Windows NT Server (Backup Domain Controller, BDC). I am accessing the BDC via an all Microsoft VPN. I have RAS on the Server and use the PPTP protocol to connect. I can connect to the server (and have been doing this for some time now). Here is my setup. Corporate- NT Server, BDC running behind a Linksys BEFSR41 nat router. Public IP on the Wan side of the Linksys router. Forwarding ports 80, 25, 110, and 1723 (for Linksys to work with VPN) to the 192.168.xxx.xxx NT BDC. Remote- NT Workstation, running behind a Linksys BEFSR41 nat router, dynamic public IP (which has not changed in months). The Problem: I have loaded WinVNC onto that server and can use the Win 98 client viewer while on the local LAN. However, when on the remote NT Workstation I can successfully connect to Corporate, but I cannot successfully run the WinNT VNC client. I can enter the IP address of the remote machine, I get prompted for a password and the remote screen initiates, then turns all black, and then shuts down. Question: Has anyone successfully connected VNC via a VPN tunnel of any type, and specifically the type described above. ----- Original Message ----- From: "Scott C. Best" To: Cc: Sent: Saturday, September 01, 2001 7:24 PM Subject: Re: New user > David: > Hello! I like these easy ones. :) You cannot > connect to the LAN from *outside* of the LAN because > of the security provided by the device which is > connecting that LAN to the Internet. Sometimes called > a firewall/router, sometimes called a gateway, sometimes > it's part of the DSL/Cable modem itself. > Those things do (amoung other things) something > called Network Address Translation, a process specified > by RFC-1918. That address range you mention, 192.168.x.y > is called a "private address range". So, as a packet > travels from a network device to the Internet, the > gateway device tranlates it into a "real", world > routable IP address assigned by your ISP. > So to connect to a VNC server behind one of these > gateways, you have to point to this "external IP address", > not the 192.168.x.y one. Write back with what sorta gateway > device you're using and we can help more! > > -Scott > > > I have got WinVNC 3.3.3R9 running on my home network, between my old > > computer and my new one. It links fine through my network cards and a > > coaxial cable. > > > > I have now taken my old computer to a friends house and connected it to his > > phone line, but I cannot now dial into it from my new computer at home. Nor > > can he dial into my computer from there. I seem to have got all the > > settings right, but when it dials his number, and it answers, my old > > computer does not pick up the signal. What am I doing wrong? I am > > searching on the IP number, which is 192.168.0.2 for the old computer and > > 192.168.0.1 for the new computer, which works fine on the home network > > through the cable connection but I have never got it working through a modem > > connection. How do I ping the old computer? How do I telnet, whatever that > > is? > > > > Similarly, I have set up a network of 5 PCs for a client in Birmingham, > > which happily use Winvnc to communicate with each other. But I cannot dial > > into their system from here, even though I have set up their system to allow > > me to do so. > > > > Any ideas? > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From martin.sarter@web.de Sun Sep 2 19:54:14 2001 From: martin.sarter@web.de (Martin Sarter) Date: Sun, 02 Sep 2001 18:54:14 +0000 Subject: KDE again In-Reply-To: <20010901180055.13660.qmail@web9503.mail.yahoo.com> Message-ID: Hi, >I had to set the default color to 24 instead of 8 First modification I made. I can set -depth to 24 or 32, makes no difference. Martin. > -----Original Message----- > From: owner-vnc-list@uk.research.att.com > [mailto:owner-vnc-list@uk.research.att.com]On Behalf Of SI Reasoning > Sent: Saturday, September 01, 2001 8:01 PM > To: vnc-list@uk.research.att.com > Subject: Re: KDE again > > > I had to set the default color to 24 instead of 8 to > get kde programs to work properly. I did it by editing > /usr/bin/vncserver. > --- Georgios Petasis > wrote: > > That is very strange. I use both KDE 1.x and 2.x > > under VNC in both > > solaris and linux with no problems. > > I will suggest that you kill your VNC server, > > kill all KDE processes, start a new VNC server > > without loading anything > > in it, set the proper display variable and type > > "startkde". > > What is then happening? > > Make sure that nothing is run in the server before > > you run startkde, > > not even a window manager... > > > > George > > > > > Hi, > > > > > > I searched the archive, watched the mailing list > > for several weeks, > > followed > > > the usual hints (modifying xsetup, setting -depth > > to the appropriate) but > > > KDE still isn't working with VNC. All I get is a > > vncviewer window with a > > > konsole and the KDE background color but no icons, > > no background image, no > > > task bar, no window elements to the konsole. I > > have SuSE 7.1 running. > > > > > > Any hints? > > > > > > Martin. > > > > > > Here's the log: > > > --------------------------------- > > > 01/09/01 17:02:51 Xvnc version 3.3.3r1 > > > 01/09/01 17:02:51 Copyright (C) AT&T Laboratories > > Cambridge. > > > 01/09/01 17:02:51 All Rights Reserved. > > > 01/09/01 17:02:51 See > > http://www.uk.research.att.com/vnc for information > > on > > > VNC > > > 01/09/01 17:02:51 Desktop name 'X' (linux:1) > > > 01/09/01 17:02:51 Protocol version supported 3.3 > > > 01/09/01 17:02:51 Listening for VNC connections on > > TCP port 5901 > > > 01/09/01 17:02:51 Listening for HTTP connections > > on TCP port 5801 > > > 01/09/01 17:02:51 URL http://linux:5801 > > > --------------------------------- > > > It looks like dcopserver is already running. If > > you are sure > > > that it is not already running, remove > > /root/.DCOPserver_linux > > > and start dcopserver again. > > > --------------------------------- > > > > > > kdesktop is already running! > > > KDE Daemon (kded) already running. > > > Could not load library! Trying exec.... > > > Launched ok, pid = 1011 > > > Server has no DPMS extension > > > There are already artsd objects registered, > > looking if they are active... > > > ERROR: kicker is already running! > > > klipper is already running! > > > > > > Error: Can't add object reference (probably artsd > > is already running). > > > If you are sure it is not already running, > > remove the relevant > > files: > > > > > > /tmp/mcop-root/Arts_SimpleSoundServer > > > /tmp/mcop-root/Arts_PlayObjectFactory > > > /tmp/mcop-root/Arts_AudioManager > > > > > > kwrited is already running.ERROR: > > KUniqueApplication: DCOP communication > > > error! > > > QSocketNotifier: Multiple socket notifiers for > > same socket 6 and type read > > > > > > 01/09/01 17:04:15 Got connection from client > > 127.0.0.1 > > > 01/09/01 17:04:16 Protocol version 3.3 > > > 01/09/01 17:04:22 Pixel format for client > > 127.0.0.1: > > > 01/09/01 17:04:22 32 bpp, depth 24, little > > endian > > > 01/09/01 17:04:22 true colour: max r 255 g 255 b > > 255, shift r 16 g 8 b 0 > > > 01/09/01 17:04:22 Using raw encoding for client > > 127.0.0.1 > > > --------------------------------- > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, send a message with the line: > > unsubscribe vnc-list > > > to majordomo@uk.research.att.com > > > See also: > > http://www.uk.research.att.com/vnc/intouch.html > > > > > > --------------------------------------------------------------------- > > > --------------------------------------------------------------------- > > To unsubscribe, send a message with the line: > > unsubscribe vnc-list > > to majordomo@uk.research.att.com > > See also: > > http://www.uk.research.att.com/vnc/intouch.html > > --------------------------------------------------------------------- > > ===== > SI Reasoning > sczjd@yahoo.com > gnupg/pgp key id 035213BC > > __________________________________________________ > Do You Yahoo!? > Get email alerts & NEW webcam video instant messaging with Yahoo! > Messenger > http://im.yahoo.com > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From martin.sarter@web.de Sun Sep 2 19:54:17 2001 From: martin.sarter@web.de (Martin Sarter) Date: Sun, 02 Sep 2001 18:54:17 +0000 Subject: KDE again In-Reply-To: <002701c13305$7ccf54a0$0103e98f@aias> Message-ID: Hi, > kill all KDE processes Killing KDE is killing X but I can login with twm or whatever, okay. >start a new VNC server without loading anything in it You mean nothing but a window manager like twm? >type "startkde". What is then happening? KDE is starting up. But still I can run only one KDE. When I try to start another KDE in a new vncserver the same DCOP error shows up (DCOP server, kdesktop etc. already running! DCOP communication error!). Since I have to work on the linux machine where the vncserver is running I need a KDE on both the vncserver and the vncviewer machines. I know this is a KDE rather than a Xvnc problem but still I hope to find a solution within this mailing list. Martin. > -----Original Message----- > From: owner-vnc-list@uk.research.att.com > [mailto:owner-vnc-list@uk.research.att.com]On Behalf Of Georgios Petasis > Sent: Saturday, September 01, 2001 6:45 PM > To: vnc-list@uk.research.att.com > Subject: Re: KDE again > > > That is very strange. I use both KDE 1.x and 2.x under VNC in both > solaris and linux with no problems. > I will suggest that you kill your VNC server, > kill all KDE processes, start a new VNC server without loading anything > in it, set the proper display variable and type "startkde". > What is then happening? > Make sure that nothing is run in the server before you run startkde, > not even a window manager... > > George > > > Hi, > > > > I searched the archive, watched the mailing list for several weeks, > followed > > the usual hints (modifying xsetup, setting -depth to the > appropriate) but > > KDE still isn't working with VNC. All I get is a vncviewer window with a > > konsole and the KDE background color but no icons, no > background image, no > > task bar, no window elements to the konsole. I have SuSE 7.1 running. > > > > Any hints? > > > > Martin. > > > > Here's the log: > > --------------------------------- > > 01/09/01 17:02:51 Xvnc version 3.3.3r1 > > 01/09/01 17:02:51 Copyright (C) AT&T Laboratories Cambridge. > > 01/09/01 17:02:51 All Rights Reserved. > > 01/09/01 17:02:51 See http://www.uk.research.att.com/vnc for information > on > > VNC > > 01/09/01 17:02:51 Desktop name 'X' (linux:1) > > 01/09/01 17:02:51 Protocol version supported 3.3 > > 01/09/01 17:02:51 Listening for VNC connections on TCP port 5901 > > 01/09/01 17:02:51 Listening for HTTP connections on TCP port 5801 > > 01/09/01 17:02:51 URL http://linux:5801 > > --------------------------------- > > It looks like dcopserver is already running. If you are sure > > that it is not already running, remove /root/.DCOPserver_linux > > and start dcopserver again. > > --------------------------------- > > > > kdesktop is already running! > > KDE Daemon (kded) already running. > > Could not load library! Trying exec.... > > Launched ok, pid = 1011 > > Server has no DPMS extension > > There are already artsd objects registered, looking if they are > active... > > ERROR: kicker is already running! > > klipper is already running! > > > > Error: Can't add object reference (probably artsd is already running). > > If you are sure it is not already running, remove the relevant > files: > > > > /tmp/mcop-root/Arts_SimpleSoundServer > > /tmp/mcop-root/Arts_PlayObjectFactory > > /tmp/mcop-root/Arts_AudioManager > > > > kwrited is already running.ERROR: KUniqueApplication: DCOP communication > > error! > > QSocketNotifier: Multiple socket notifiers for same socket 6 > and type read > > > > 01/09/01 17:04:15 Got connection from client 127.0.0.1 > > 01/09/01 17:04:16 Protocol version 3.3 > > 01/09/01 17:04:22 Pixel format for client 127.0.0.1: > > 01/09/01 17:04:22 32 bpp, depth 24, little endian > > 01/09/01 17:04:22 true colour: max r 255 g 255 b 255, shift r > 16 g 8 b 0 > > 01/09/01 17:04:22 Using raw encoding for client 127.0.0.1 > > --------------------------------- > > --------------------------------------------------------------------- > > To unsubscribe, send a message with the line: unsubscribe vnc-list > > to majordomo@uk.research.att.com > > See also: http://www.uk.research.att.com/vnc/intouch.html > > --------------------------------------------------------------------- > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From maillist@devilsplayground.net Sun Sep 2 20:03:45 2001 From: maillist@devilsplayground.net (Dave Warren) Date: Sun, 02 Sep 2001 19:03:45 +0000 Subject: Undocumented port in use by VNCviewer in Listen Mode? References: <002301c13223$e2d8fcc0$1cbf4241@swbell.net> Message-ID: <003c01c133d9$20d60020$6b00a8c0@devilsplayground.net> But the original question was about running VNC *VIEWER* in listen mode, not running the server in listen mode. ----- Original Message ----- From: "Pete" To: Sent: Friday, August 31, 2001 7:50 AM Subject: Re: Undocumented port in use by VNCviewer in Listen Mode? > I've just run a VNC server on a system with a network monitor running and am > logged into it from a viewer over the network. > > I too see a second port open and listening, but in my case it's 5800. It > appears to simply be a control-connection. The only time I see any data > activity on that port is when a connection is established or disconnected. > > Hope that settles your fears. ======================================================== Dave Warren, devilsplayground.net administrator Email: dave.warren@devilsplayground.net ======================================================== --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From maillist@devilsplayground.net Sun Sep 2 20:03:50 2001 From: maillist@devilsplayground.net (Dave Warren) Date: Sun, 02 Sep 2001 19:03:50 +0000 Subject: Win2k Locked Workstation References: Message-ID: <003b01c133d9$208b3b80$6b00a8c0@devilsplayground.net> In the viewer, click on the system menu (The little icon at the top left hand corner), there's an option to send control-alt-del to the server from there. Does that work? ----- Original Message ----- From: "Roy Bosworth" To: Sent: Friday, August 31, 2001 12:21 PM Subject: Win2k Locked Workstation > I have a Win2k workstation at work and lock this station before I leave. At > home I have a Win98 system and using VNC 3.3r. I use the Web browser to > connect, but every time I enter my password, VNC automatically closes. If I > keep my workstation at work open and not locked, the connection gets through > no problem. Only when the Win2k system is locked does this problem arise. > I can connect through the normal Viewer but cannot send Ctl+Alt+Del through > this so it is useless to me. I need the browser.... ======================================================== Dave Warren, devilsplayground.net administrator Email: dave.warren@devilsplayground.net ======================================================== --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From sczjd@yahoo.com Sun Sep 2 22:59:57 2001 From: sczjd@yahoo.com (SI Reasoning) Date: Sun, 02 Sep 2001 21:59:57 +0000 Subject: KDE again In-Reply-To: Message-ID: <20010902205610.87355.qmail@web9503.mail.yahoo.com> from the server or the viewer? It has to be done by the server for KDE2 to work for me. --- Martin Sarter wrote: > Hi, > > >I had to set the default color to 24 instead of 8 > First modification I made. I can set -depth to 24 or > 32, makes no > difference. > > Martin. > > > > -----Original Message----- > > From: owner-vnc-list@uk.research.att.com > > [mailto:owner-vnc-list@uk.research.att.com]On > Behalf Of SI Reasoning > > Sent: Saturday, September 01, 2001 8:01 PM > > To: vnc-list@uk.research.att.com > > Subject: Re: KDE again > > > > > > I had to set the default color to 24 instead of 8 > to > > get kde programs to work properly. I did it by > editing > > /usr/bin/vncserver. > > --- Georgios Petasis > > wrote: > > > That is very strange. I use both KDE 1.x and 2.x > > > under VNC in both > > > solaris and linux with no problems. > > > I will suggest that you kill your VNC server, > > > kill all KDE processes, start a new VNC server > > > without loading anything > > > in it, set the proper display variable and type > > > "startkde". > > > What is then happening? > > > Make sure that nothing is run in the server > before > > > you run startkde, > > > not even a window manager... > > > > > > George > > > > > > > Hi, > > > > > > > > I searched the archive, watched the mailing > list > > > for several weeks, > > > followed > > > > the usual hints (modifying xsetup, setting > -depth > > > to the appropriate) but > > > > KDE still isn't working with VNC. All I get is > a > > > vncviewer window with a > > > > konsole and the KDE background color but no > icons, > > > no background image, no > > > > task bar, no window elements to the konsole. I > > > have SuSE 7.1 running. > > > > > > > > Any hints? > > > > > > > > Martin. > > > > > > > > Here's the log: > > > > --------------------------------- > > > > 01/09/01 17:02:51 Xvnc version 3.3.3r1 > > > > 01/09/01 17:02:51 Copyright (C) AT&T > Laboratories > > > Cambridge. > > > > 01/09/01 17:02:51 All Rights Reserved. > > > > 01/09/01 17:02:51 See > > > http://www.uk.research.att.com/vnc for > information > > > on > > > > VNC > > > > 01/09/01 17:02:51 Desktop name 'X' (linux:1) > > > > 01/09/01 17:02:51 Protocol version supported > 3.3 > > > > 01/09/01 17:02:51 Listening for VNC > connections on > > > TCP port 5901 > > > > 01/09/01 17:02:51 Listening for HTTP > connections > > > on TCP port 5801 > > > > 01/09/01 17:02:51 URL http://linux:5801 > > > > --------------------------------- > > > > It looks like dcopserver is already running. > If > > > you are sure > > > > that it is not already running, remove > > > /root/.DCOPserver_linux > > > > and start dcopserver again. > > > > --------------------------------- > > > > > > > > kdesktop is already running! > > > > KDE Daemon (kded) already running. > > > > Could not load library! Trying exec.... > > > > Launched ok, pid = 1011 > > > > Server has no DPMS extension > > > > There are already artsd objects registered, > > > looking if they are active... > > > > ERROR: kicker is already running! > > > > klipper is already running! > > > > > > > > Error: Can't add object reference (probably > artsd > > > is already running). > > > > If you are sure it is not already > running, > > > remove the relevant > > > files: > > > > > > > > /tmp/mcop-root/Arts_SimpleSoundServer > > > > /tmp/mcop-root/Arts_PlayObjectFactory > > > > /tmp/mcop-root/Arts_AudioManager > > > > > > > > kwrited is already running.ERROR: > > > KUniqueApplication: DCOP communication > > > > error! > > > > QSocketNotifier: Multiple socket notifiers for > > > same socket 6 and type read > > > > > > > > 01/09/01 17:04:15 Got connection from client > > > 127.0.0.1 > > > > 01/09/01 17:04:16 Protocol version 3.3 > > > > 01/09/01 17:04:22 Pixel format for client > > > 127.0.0.1: > > > > 01/09/01 17:04:22 32 bpp, depth 24, little > > > endian > > > > 01/09/01 17:04:22 true colour: max r 255 g > 255 b > > > 255, shift r 16 g 8 b 0 > > > > 01/09/01 17:04:22 Using raw encoding for > client > > > 127.0.0.1 > > > > --------------------------------- > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, send a message with the line: > > > unsubscribe vnc-list > > > > to majordomo@uk.research.att.com > > > > See also: > > > http://www.uk.research.att.com/vnc/intouch.html > > > > > > > > > > --------------------------------------------------------------------- > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, send a message with the line: > > > unsubscribe vnc-list > > > to majordomo@uk.research.att.com > > > See also: > > > http://www.uk.research.att.com/vnc/intouch.html > > > > --------------------------------------------------------------------- > > > > ===== > > SI Reasoning > > sczjd@yahoo.com > > gnupg/pgp key id 035213BC > > > > __________________________________________________ > > Do You Yahoo!? > > Get email alerts & NEW webcam video instant > messaging with Yahoo! > > Messenger > > http://im.yahoo.com > > > --------------------------------------------------------------------- > > To unsubscribe, send a message with the line: > unsubscribe vnc-list > > to majordomo@uk.research.att.com > > See also: > http://www.uk.research.att.com/vnc/intouch.html > > > --------------------------------------------------------------------- > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: > unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: > http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- ===== SI Reasoning sczjd@yahoo.com gnupg/pgp key id 035213BC __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From karlheinz@khschulz.com Mon Sep 3 00:59:49 2001 From: karlheinz@khschulz.com (Karl-Heinz Schulz) Date: Sun, 02 Sep 2001 23:59:49 +0000 Subject: Problem with VNC Viewer Message-ID: <000b01c13402$59fa0120$0b515d18@CHARLIELABTOP> Viewer is installed on Windows 2000 (with all patches installed) VNC Server is installed on Mandrake 8 (latest version available) Problem number 1 - kvm is not available on Mandrake when running Xfree 4.XX I have the following Windows Manager installed KDE Gnome Fvwm When starting the viewer I see only the grey start up screen The output of my xstartup file is as following bash-2.05$ more xstartup #!/bin/sh xrdb $HOME/.Xresources xsetroot -solid grey xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" & fvwm & What am I missing? Thank you --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From const@ce.cctpu.edu.ru Mon Sep 3 01:21:23 2001 From: const@ce.cctpu.edu.ru (Const Kaplinsky) Date: Mon, 03 Sep 2001 00:21:23 +0000 Subject: TightVNC crash on 6 of 16 NT servers In-Reply-To: <3B8FAB27.1F01E02@InvisibleRobot.com> References: <3B8FAB27.1F01E02@InvisibleRobot.com> Message-ID: Hello, >>>>> "EC" == Eric Carlson writes: EC> Two days ago I installed TightVNC 1.20 on 16 Windows NT 4.0/SP6a EC> servers in place of plain VNC 3.3.3r9. On 6 of the servers, when I EC> try to connect, TightVNC server gives a Dr. Watson error, and EC> stops working (I've tried both clients, with the same results). So EC> far, the other 10 servers are okay. EC> All of the servers will let me connect within a few minutes after EC> I boot them, but within the next hour or the next day, TightVNC EC> stops working. EC> I didn't have problems with the 3.3.3r9 server. EC> The servers each have different combinations of hardware, so the EC> problem doesn't appear to be caused by a specific piece of EC> hardware. EC> To install TightVNC, I replaced the old VNC files, and then EC> uninstalled and reinstalled the VNC service, and rebooted the EC> servers. EC> Should I switch all the servers back to 3.3.3r9, or is there EC> another solution? Did I install TightVNC incorrectly? I originally EC> installed VNC 3.3.3r9 with the install program. I have not seen crashes with latest TightVNC version yet, and if I could re-produce the problem, or to clarify conditions causing the server to crash, that could help me to locate and fix bugs that might cause the problem. What color mode do you use on servers and does changing screen mode (e.g. 24bit -> 16bit) change anything? Do these crashes depend on encoding or cursor pointer mode used? Maybe there is something where machines differ (e.g. video drivers)? Also, I'd like to know, does anybody else experience similar problems? -- With Best Wishes, Constantin --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From sczjd@yahoo.com Mon Sep 3 01:35:30 2001 From: sczjd@yahoo.com (SI Reasoning) Date: Mon, 03 Sep 2001 00:35:30 +0000 Subject: Problem with VNC Viewer In-Reply-To: <000b01c13402$59fa0120$0b515d18@CHARLIELABTOP> Message-ID: <20010902233236.63326.qmail@web9501.mail.yahoo.com> Have you tried the fvwm on your desktop to make sure it works? Are you sure it is installed? --- Karl-Heinz Schulz wrote: > Viewer is installed on Windows 2000 (with all > patches installed) > VNC Server is installed on Mandrake 8 (latest > version available) > > Problem number 1 - kvm is not available on Mandrake > when running Xfree 4.XX > I have the following Windows Manager installed > > KDE > Gnome > Fvwm > > When starting the viewer I see only the grey start > up screen > > The output of my xstartup file is as following > > bash-2.05$ more xstartup > #!/bin/sh > > xrdb $HOME/.Xresources > xsetroot -solid grey > xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP > Desktop" & > fvwm & > > What am I missing? > > Thank you > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: > unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: > http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- ===== SI Reasoning sczjd@yahoo.com gnupg/pgp key id 035213BC __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From karlheinz@khschulz.com Mon Sep 3 01:49:12 2001 From: karlheinz@khschulz.com (Karl-Heinz Schulz) Date: Mon, 03 Sep 2001 00:49:12 +0000 Subject: Problem with VNC Viewer In-Reply-To: <20010902233236.63326.qmail@web9501.mail.yahoo.com> Message-ID: <000c01c13409$67415750$0b515d18@CHARLIELABTOP> I didn't try fvwm because it was installed it remotely be me. I tried it also with KDE and Gnome - both are installed and work. The problem is that the server is in Montreal and I'm in North Carolina and log in via OpenSSH. -----Original Message----- From: owner-vnc-list@uk.research.att.com [mailto:owner-vnc-list@uk.research.att.com] On Behalf Of SI Reasoning Sent: Sunday, September 02, 2001 7:33 PM To: vnc-list@uk.research.att.com Subject: Re: Problem with VNC Viewer Have you tried the fvwm on your desktop to make sure it works? Are you sure it is installed? --- Karl-Heinz Schulz wrote: > Viewer is installed on Windows 2000 (with all > patches installed) > VNC Server is installed on Mandrake 8 (latest > version available) > > Problem number 1 - kvm is not available on Mandrake > when running Xfree 4.XX > I have the following Windows Manager installed > > KDE > Gnome > Fvwm > > When starting the viewer I see only the grey start > up screen > > The output of my xstartup file is as following > > bash-2.05$ more xstartup > #!/bin/sh > > xrdb $HOME/.Xresources > xsetroot -solid grey > xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP > Desktop" & > fvwm & > > What am I missing? > > Thank you > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: > unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: > http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- ===== SI Reasoning sczjd@yahoo.com gnupg/pgp key id 035213BC __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From yan@cardinalengineering.com Mon Sep 3 02:10:56 2001 From: yan@cardinalengineering.com (Yan Seiner) Date: Mon, 03 Sep 2001 01:10:56 +0000 Subject: New user References: <003c01c133bf$14edbf60$64c8690a@Carola> Message-ID: <3B92C9E7.3963ADE3@cardinalengineering.com> VNC over VPN? Yes. Do it all the time. There should not be anything special about it. I run VNC over a network built with vtund (lightweight linux-based vpn). I have also run VNC over pptp from a win 9x client to a linux-based pptp server. No problem either way. I have, however, run into a similar problem trying to run various connections through a winNT based firewall. I suspect some sort of stateful packet inspection, but since the attempts were unauthorized, I can't provide any additional data. Can you get firewall/access logs from the NT server? --Yan spencer wrote: > > Scott, > I have a similar issue as stated below. Do you have any suggestions? > > I am trying to use VNC to access a Windows NT Server (Backup Domain > Controller, BDC). I am accessing the BDC via an all Microsoft VPN. I have > RAS on the Server and use the PPTP protocol to connect. I can connect to the > server (and have been doing this for some time now). > > Here is my setup. > Corporate- NT Server, BDC running behind a Linksys BEFSR41 nat router. > Public IP on the Wan side of the Linksys router. Forwarding ports 80, 25, > 110, and 1723 (for Linksys to work with VPN) to the 192.168.xxx.xxx NT BDC. > > Remote- NT Workstation, running behind a Linksys BEFSR41 nat router, dynamic > public IP (which has not changed in months). > > The Problem: > I have loaded WinVNC onto that server and can use the Win 98 client viewer > while on the local LAN. However, when on the remote NT Workstation I can > successfully connect to Corporate, but I cannot successfully run the WinNT > VNC client. I can enter the IP address of the remote machine, I get prompted > for a password and the remote screen initiates, then turns all black, and > then shuts down. > > Question: > Has anyone successfully connected VNC via a VPN tunnel of any type, and > specifically the type described above. --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From sczjd@yahoo.com Mon Sep 3 07:24:33 2001 From: sczjd@yahoo.com (SI Reasoning) Date: Mon, 03 Sep 2001 06:24:33 +0000 Subject: Problem with VNC Viewer In-Reply-To: <000c01c13409$67415750$0b515d18@CHARLIELABTOP> Message-ID: <20010903051745.11142.qmail@web9504.mail.yahoo.com> try this: ------------------ #!/bin/sh xrdb $HOME/.Xresources exec fvwm #exec gnome-session #exec startkde ---------------------- you can unmark gnome or kde and re-mark fvwm if you want to try the others. --- Karl-Heinz Schulz wrote: > I didn't try fvwm because it was installed it > remotely be me. > I tried it also with KDE and Gnome - both are > installed and work. > > The problem is that the server is in Montreal and > I'm in North Carolina and > log in via OpenSSH. > > -----Original Message----- > From: owner-vnc-list@uk.research.att.com > [mailto:owner-vnc-list@uk.research.att.com] On > Behalf Of SI Reasoning > Sent: Sunday, September 02, 2001 7:33 PM > To: vnc-list@uk.research.att.com > Subject: Re: Problem with VNC Viewer > > Have you tried the fvwm on your desktop to make sure > it works? > Are you sure it is installed? > > --- Karl-Heinz Schulz > wrote: > > Viewer is installed on Windows 2000 (with all > > patches installed) > > VNC Server is installed on Mandrake 8 (latest > > version available) > > > > Problem number 1 - kvm is not available on > Mandrake > > when running Xfree 4.XX > > I have the following Windows Manager installed > > > > KDE > > Gnome > > Fvwm > > > > When starting the viewer I see only the grey start > > up screen > > > > The output of my xstartup file is as following > > > > bash-2.05$ more xstartup > > #!/bin/sh > > > > xrdb $HOME/.Xresources > > xsetroot -solid grey > > xterm -geometry 80x24+10+10 -ls -title > "$VNCDESKTOP > > Desktop" & > > fvwm & > > > > What am I missing? > > > > Thank you > > > --------------------------------------------------------------------- > > To unsubscribe, send a message with the line: > > unsubscribe vnc-list > > to majordomo@uk.research.att.com > > See also: > > http://www.uk.research.att.com/vnc/intouch.html > > > --------------------------------------------------------------------- > > ===== > SI Reasoning > sczjd@yahoo.com > gnupg/pgp key id 035213BC > > __________________________________________________ > Do You Yahoo!? > Get email alerts & NEW webcam video instant > messaging with Yahoo! Messenger > http://im.yahoo.com > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: > unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: > http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: > unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: > http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- ===== SI Reasoning sczjd@yahoo.com gnupg/pgp key id 035213BC __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From petasis@iit.demokritos.gr Mon Sep 3 08:23:53 2001 From: petasis@iit.demokritos.gr (Georgios Petasis) Date: Mon, 03 Sep 2001 07:23:53 +0000 Subject: KDE again In-Reply-To: References: Message-ID: <01090309120600.29666@atlas> On ??? 02 ??? 2001 20:47, you wrote: > Hi, > > > kill all KDE processes > > Killing KDE is killing X but I can login with twm or whatever, okay. No, killing KDE is *not* killing X. KDE utilises many services that do not require X, like the DCOP server. > > >start a new VNC server without loading anything in it > > You mean nothing but a window manager like twm? No, not even a window manager like twm > > >type "startkde". What is then happening? > > KDE is starting up. But still I can run only one KDE. When I try to start > another KDE in a new vncserver the same DCOP error shows up (DCOP server, > kdesktop etc. already running! DCOP communication error!). Note that the *same* user can start up only *one* kde session. Loggin as a different user to start another session... George --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From richard.harris@nottscc.gov.uk Mon Sep 3 10:30:00 2001 From: richard.harris@nottscc.gov.uk (Richard Harris) Date: Mon, 03 Sep 2001 09:30:00 +0000 Subject: Push to Windows Millenium In-Reply-To: Message-ID: <3B934CB2.16317.F7611@localhost> > I did a search of the archives and wasnt able to find any info on > this. Is there a specific way to push VNC to a Windows ME machine > from an NT 4.0 Server? I can map drives as normal to the machine (its > a domain member), but what about the service install, et cetera? Is > the install any different from a remote install on an NT/Win2k > machine? I don't have any experience with VNC on ME. If ME is just a jazzed up 95 that takes NT drivers, then you'll have to go down the route of an install package. If ME has NT-like services then you should be able to use the SC command to install VNC as a service. You only need a push script if the local OS has it's own security system (nt/2000). Windows 9x doesn't have any of this, so if ME is like 9x, you could just use your own custom installer. Check out http://www.darkage.co.uk/vnc/owndistro.htm for a more in-depth discussion. HTH, Rich --------------------------------- Richard Harris Environment IT Tel: 0115 977 4509 --------------------------------- --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From david@jdavidj.freeserve.co.uk Mon Sep 3 11:51:36 2001 From: david@jdavidj.freeserve.co.uk (David Jackson) Date: Mon, 03 Sep 2001 10:51:36 +0000 Subject: New user In-Reply-To: <002001c132a5$05bab7c0$1cbf4241@swbell.net> Message-ID: Thanks Pete No, I am not trying to dial up via the Internet, I am trying to do it direct via the telephone line. This is what I cannot understand. If I can connect two machines through a coaxial cable, why can I not connect the same two machines through a modem and phone line? On the Server machine, the IP address is 10.1.0.11, or at least that is what comes up when I hover the mouse over the vnc icon on the desktop toolbar. Having said that, I have just hovered over the icon on this PC and I now get 62.137.158.158.192.168.0.1 Is the first part of this the dynamic IP? Cheers David -----Original Message----- From: Pete [mailto:pete@atdt911.com] Sent: 01 September 2001 06:15 To: David Jackson Subject: Re: New user > OK. So I dial up through my usual ISP, and use whatever IP I am given for > each computer? Right. It can be tedious figuring out what a dynamic IP is; you might want to look into a dynamic DNS server. http://www.cjb.net/ http://www.dns2go.com/ http://www.dynip.com/ > The network of 5 dials up to the Internet via the Server, each workstation > using Winvnc to get the Server screen and then using that screen for dial up > via the Server modem to the Internet. OK, so they've only got 1 public IP -- on the server machine. Run WINIPCFG.EXE on that machine and that'll tell you what its IP is. > > Thanks for taking the time to help me with this. > > Cheers > David > > -----Original Message----- > From: Pete [mailto:pete@atdt911.com] > Sent: 31 August 2001 13:43 > To: David Jackson > Subject: Re: New user > > Well, on your old- and new-computer, you'll need to set the IPs to whatever > the internet service provider gives as an IP on each end. On dial-up, the IP > usually changes on each connection. > > On the 5 client PCs you describe, same thing, but they would hopefully have > static IPs. Do you know if they're using a proxy or have their own DNS > server and are using DHCP? How do they connect those 5 machines to the > internet? > > ----- Original Message ----- > From: "David Jackson" > To: "Pete" > Sent: Friday, August 31, 2001 6:37 AM > Subject: RE: New user > > > > Thanks Pete. That's very helpful. I shall certainly try that. > > How do I find out what the public IP is? > > Cheers > > David > > > > -----Original Message----- > > From: Pete [mailto:pete@atdt911.com] > > Sent: 31 August 2001 12:08 > > To: david@jdavidj.freeserve.co.uk > > Subject: Re: New user > > > > Everything you're describing is the correct behavior, since those are > > private IPs. They will not pass through any router. > > > > To address the machines from an outside-network, you need to use the > public > > IPs. You must fix that before worrying about using telnet or anything > else. > > > > Once you've found that the public IP is, let's say 12.34.56.78, just make > > sure that either telnet.exe or hyperterminal (better) are installed on the > > box you're telnet'ing from, then enter from the RUN prompt or any address > > bar: > > telnet 12.34.56.78 > > > > ----- Original Message ----- > > From: "David Jackson" > > To: > > Sent: Friday, August 31, 2001 2:45 AM > > Subject: New user > > > > > > > I have got WinVNC 3.3.3R9 running on my home network, between my old > > > computer and my new one. It links fine through my network cards and a > > > coaxial cable. > > > > > > I have now taken my old computer to a friends house and connected it to > > his > > > phone line, but I cannot now dial into it from my new computer at home. > > Nor > > > can he dial into my computer from there. I seem to have got all the > > > settings right, but when it dials his number, and it answers, my old > > > computer does not pick up the signal. What am I doing wrong? I am > > > searching on the IP number, which is 192.168.0.2 for the old computer > and > > > 192.168.0.1 for the new computer, which works fine on the home network > > > through the cable connection but I have never got it working through a > > modem > > > connection. How do I ping the old computer? How do I telnet, whatever > > that > > > is? > > > > > > Similarly, I have set up a network of 5 PCs for a client in Birmingham, > > > which happily use Winvnc to communicate with each other. But I cannot > > dial > > > into their system from here, even though I have set up their system to > > allow > > > me to do so. > > > > > > Any ideas? > > > --------------------------------------------------------------------- > > > To unsubscribe, send a message with the line: unsubscribe vnc-list > > > to majordomo@uk.research.att.com > > > See also: http://www.uk.research.att.com/vnc/intouch.html > > > --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From karlheinz@khschulz.com Mon Sep 3 13:51:31 2001 From: karlheinz@khschulz.com (Karl-Heinz Schulz) Date: Mon, 03 Sep 2001 12:51:31 +0000 Subject: Problem with VNC Viewer In-Reply-To: <20010903051745.11142.qmail@web9504.mail.yahoo.com> Message-ID: <000501c1346e$0952e900$0b515d18@CHARLIELABTOP> No, no difference - I see just the gray X start up page - no Windows manager. -----Original Message----- From: owner-vnc-list@uk.research.att.com [mailto:owner-vnc-list@uk.research.att.com] On Behalf Of SI Reasoning Sent: Monday, September 03, 2001 1:18 AM To: vnc-list@uk.research.att.com Subject: RE: Problem with VNC Viewer try this: ------------------ #!/bin/sh xrdb $HOME/.Xresources exec fvwm #exec gnome-session #exec startkde ---------------------- you can unmark gnome or kde and re-mark fvwm if you want to try the others. --- Karl-Heinz Schulz wrote: > I didn't try fvwm because it was installed it > remotely be me. > I tried it also with KDE and Gnome - both are > installed and work. > > The problem is that the server is in Montreal and > I'm in North Carolina and > log in via OpenSSH. > > -----Original Message----- > From: owner-vnc-list@uk.research.att.com > [mailto:owner-vnc-list@uk.research.att.com] On > Behalf Of SI Reasoning > Sent: Sunday, September 02, 2001 7:33 PM > To: vnc-list@uk.research.att.com > Subject: Re: Problem with VNC Viewer > > Have you tried the fvwm on your desktop to make sure > it works? > Are you sure it is installed? > > --- Karl-Heinz Schulz > wrote: > > Viewer is installed on Windows 2000 (with all > > patches installed) > > VNC Server is installed on Mandrake 8 (latest > > version available) > > > > Problem number 1 - kvm is not available on > Mandrake > > when running Xfree 4.XX > > I have the following Windows Manager installed > > > > KDE > > Gnome > > Fvwm > > > > When starting the viewer I see only the grey start > > up screen > > > > The output of my xstartup file is as following > > > > bash-2.05$ more xstartup > > #!/bin/sh > > > > xrdb $HOME/.Xresources > > xsetroot -solid grey > > xterm -geometry 80x24+10+10 -ls -title > "$VNCDESKTOP > > Desktop" & > > fvwm & > > > > What am I missing? > > > > Thank you > > > --------------------------------------------------------------------- > > To unsubscribe, send a message with the line: > > unsubscribe vnc-list > > to majordomo@uk.research.att.com > > See also: > > http://www.uk.research.att.com/vnc/intouch.html > > > --------------------------------------------------------------------- > > ===== > SI Reasoning > sczjd@yahoo.com > gnupg/pgp key id 035213BC > > __________________________________________________ > Do You Yahoo!? > Get email alerts & NEW webcam video instant > messaging with Yahoo! Messenger > http://im.yahoo.com > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: > unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: > http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: > unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: > http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- ===== SI Reasoning sczjd@yahoo.com gnupg/pgp key id 035213BC __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From jason9x19@sunflower.com Mon Sep 3 15:12:21 2001 From: jason9x19@sunflower.com (Jason Holbert) Date: Mon, 03 Sep 2001 14:12:21 +0000 Subject: No subject Message-ID: I'm having the same problem, and I'm running it on Windows NT 4.0 SP5 --J --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From spencer@silcom.com Mon Sep 3 15:31:24 2001 From: spencer@silcom.com (spencer) Date: Mon, 03 Sep 2001 14:31:24 +0000 Subject: References: Message-ID: <000c01c1347b$f075ac70$64c8690a@Carola> I think the problem might be that the appropriate switch on the VNC Service for trapping Ctrl-Alt-Del is not turned on. I will have to verify this on Tuesday when the corporate office is open again. ----- Original Message ----- From: "Jason Holbert" To: Sent: Friday, August 31, 2001 11:53 PM > I'm having the same problem, and I'm running it on Windows NT 4.0 SP5 > > --J > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From tritium2010@home.com Mon Sep 3 17:04:24 2001 From: tritium2010@home.com (test) Date: Mon, 03 Sep 2001 16:04:24 +0000 Subject: References: Message-ID: <007501c13488$f3b88f80$f8180018@CORPNT.NET> Funny that this should come up... I just installed VNC on a machine with X-Windows... and I typed password, and this gray screen came up. I thought.. damn... something is incompatible.... Well.. close.. but no cigar. I left clicked on the background, holding the mouse button down... some little invisible windows popped up. All you have to do.. is Click-Hold and drag a little to the right .. it should pop up with something... may not look exactly like your desktop, but it is. Hope that's all! Mike ----- Original Message ----- From: "Jason Holbert" To: Sent: Friday, August 31, 2001 11:53 PM > I'm having the same problem, and I'm running it on Windows NT 4.0 SP5 > > --J > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From OAnkert@t-online.de Mon Sep 3 17:05:09 2001 From: OAnkert@t-online.de (OAnkert@t-online.de) Date: Mon, 03 Sep 2001 16:05:09 +0000 Subject: ip forwarding win98 Message-ID: <999528982.3b939a168ebe3@webmail.t-online.de> Hello, i have one pc running win98 with two network cards, each attached to a different network. I need to forwarding ip from one network to the other to access the vncservers running on that network. I can not change this pc to winNT or 2000. Can anybody help? Oliver --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From tage@cs.uit.no Mon Sep 3 17:28:42 2001 From: tage@cs.uit.no (Tage Stabell-Kulo) Date: Mon, 03 Sep 2001 16:28:42 +0000 Subject: WinVNC and vncwiever (on NetBSD): Closed connection Message-ID: I am running WinVNC on Win2K (3.3.3 R9). The client is version 3.3.3r1, on NetBSD. When I connect the window opens, I get a glimpse of my desktop; the colours seem to be right, and the size seems to be OK. If I stop the viewer (by sending it SUSP at the right moment) I can see that the desktop has been drawn perfectly. However, the window closes after a split second. Below is logging from the client, and then on thw WinVNC side. Any assistance is very welcome. [TaSK] -- //// Tage Stabell-Kulx | email : Tage@cs.uit.no //// ///Department of Computer Science| Phone : +47 7764 4032 /// // 9037 University of Tromsx | Fax : +47 7764 4580 // / Norway | http://www.cs.uit.no/~tage/ ============================= IPv6to4gw:~>vncviewer host VNC server supports protocol version 3.3 (viewer 3.3) Password: VNC authentication succeeded Desktop name "host" Connected to VNC server, using protocol version 3.3 VNC server default format: 32 bits per pixel. Least significant byte first in each pixel. True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0 Using default colormap which is TrueColor. Pixel format: 16 bits per pixel. Least significant byte first in each pixel. True colour: max red 31 green 63 blue 31, shift red 11 green 5 blue 0 vncviewer: read: Connection reset by peer IPv6to4gw:~> ================================= D:\ORL\vss\winvnc\vncSockConnect.cpp : accepted connection from 129.242.16.153 D:\ORL\vss\winvnc\vncClient.cpp : vncClient() executing... D:\ORL\vss\winvnc\vncServer.cpp : AddClient() done D:\ORL\vss\winvnc\WinVNC.cpp : message 1026 recieved D:\ORL\vss\winvnc\vncClient.cpp : client connected : 129.242.16.153 (1) D:\ORL\vss\winvnc\vncClient.cpp : negotiated version D:\ORL\vss\winvnc\vncPasswd.h : PASSWD : ToText called D:\ORL\vss\winvnc\WinVNC.cpp : message 275 recieved D:\ORL\vss\winvnc\vncMenu.cpp : tray icon added ok Mon Sep 03 13:49:00 2001 D:\ORL\vss\winvnc\vncClient.cpp : non-shared connection - disconnecting old clie nts D:\ORL\vss\winvnc\vncServer.cpp : KillAuthClients() done D:\ORL\vss\winvnc\vncDesktop.cpp : initialising desktop handler D:\ORL\vss\winvnc\vncDesktop.cpp : KillScreenSaver... D:\ORL\vss\winvnc\vncDesktop.cpp : bitmap dimensions are 1024 x 768 D:\ORL\vss\winvnc\vncDesktop.cpp : created memory bitmap D:\ORL\vss\winvnc\vncDesktop.cpp : got bitmap format D:\ORL\vss\winvnc\vncDesktop.cpp : DBG:display context has 1 planes! D:\ORL\vss\winvnc\vncDesktop.cpp : DBG:memory context has 1 planes! D:\ORL\vss\winvnc\vncDesktop.cpp : attempting to enable DIBsection blits D:\ORL\vss\winvnc\vncDesktop.cpp : unable to enable fast blits D:\ORL\vss\winvnc\vncDesktop.cpp : no palette data for truecolour display D:\ORL\vss\winvnc\vncBuffer.cpp : raw encoder requested D:\ORL\vss\winvnc\vncEncoder.cpp : settranslatefunction called D:\ORL\vss\winvnc\vncEncoder.cpp : only 8, 16 or 32 bits supported remotely - 0 requested D:\ORL\vss\winvnc\vncEncoder.cpp : settranslatefunction called D:\ORL\vss\winvnc\vncEncoder.cpp : no translation required D:\ORL\vss\winvnc\vncBuffer.cpp : local buffer=3145728, remote buffer=3145740 D:\ORL\vss\winvnc\vncBuffer.cpp : local buffer=3145728, remote buffer=3145740 D:\ORL\vss\winvnc\WinVNC.cpp : message 1027 recieved D:\ORL\vss\winvnc\vncServer.cpp : Authenticated() done D:\ORL\vss\winvnc\vncClient.cpp : authenticated connection D:\ORL\vss\winvnc\vncClient.cpp : sent pixel format to client D:\ORL\vss\winvnc\vncMenu.cpp : tray icon added ok D:\ORL\vss\winvnc\vncBuffer.cpp : SetClientFormat called D:\ORL\vss\winvnc\vncEncoder.cpp : settranslatefunction called D:\ORL\vss\winvnc\vncEncoder.cpp : triple LUT used D:\ORL\vss\winvnc\vncBuffer.cpp : local buffer=3145728, remote buffer=1572876 D:\ORL\vss\winvnc\vncBuffer.cpp : Hextile encoder requested D:\ORL\vss\winvnc\vncEncoder.cpp : settranslatefunction called D:\ORL\vss\winvnc\vncEncoder.cpp : only 8, 16 or 32 bits supported remotely - 0 requested D:\ORL\vss\winvnc\vncEncoder.cpp : settranslatefunction called D:\ORL\vss\winvnc\vncEncoder.cpp : triple LUT used D:\ORL\vss\winvnc\vncBuffer.cpp : local buffer=3145728, remote buffer=1576061 D:\ORL\vss\winvnc\vncEncoder.cpp : remote palette data requested Mon Sep 03 13:49:01 2001 D:\ORL\vss\winvnc\vncBuffer.cpp : clearing rectangle (0, 0)-(507, 768) D:\ORL\vss\winvnc\VSocket.cpp : socket error 0 D:\ORL\vss\winvnc\vncBuffer.cpp : clearing rectangle (507, 0)-(1024, 768) Mon Sep 03 13:49:02 2001 D:\ORL\vss\winvnc\vncService.cpp : SelectHDESK to Default (40) from 40D:\ORL\vss \winvnc\vncService.cpp : SelectHDESK failed to close old desktop 40 (Err=170) D:\ORL\vss\winvnc\vncClient.cpp : client disconnected : 129.242.16.153 (1) D:\ORL\vss\winvnc\vncServer.cpp : removing authorised client D:\ORL\vss\winvnc\vncServer.cpp : deleting desktop server D:\ORL\vss\winvnc\vncDesktop.cpp : killing screen server D:\ORL\vss\winvnc\vncDesktop.cpp : quitting desktop server thread D:\ORL\vss\winvnc\vncService.cpp : SelectHDESK to Default (40) from 40D:\ORL\vss\winvnc\vncService.cpp : SelectHDESK failed to close old desktop 40 (Err=170) D:\ORL\vss\winvnc\vncServer.cpp : RemoveClient() done D:\ORL\vss\winvnc\vncClient.cpp : ~vncClient() executing... D:\ORL\vss\winvnc\vncClient.cpp : deleting socket D:\ORL\vss\winvnc\VSocket.cpp : closing socket D:\ORL\vss\winvnc\vncClient.cpp : deleting buffer --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From IanF@src.co.uk Mon Sep 3 17:41:18 2001 From: IanF@src.co.uk (Ian Ferguson) Date: Mon, 03 Sep 2001 16:41:18 +0000 Subject: ip forwarding win98 Message-ID: I think you should be able to use VNCproxy. someone please correct me if this is not the case. Ian -----Original Message----- From: OAnkert@t-online.de [mailto:OAnkert@t-online.de] Sent: 03 September 2001 15:59 To: VNC Liste Subject: ip forwarding win98 Hello, i have one pc running win98 with two network cards, each attached to a different network. I need to forwarding ip from one network to the other to access the vncservers running on that network. I can not change this pc to winNT or 2000. Can anybody help? Oliver --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From bebsworthy@entreview.com Mon Sep 3 19:01:49 2001 From: bebsworthy@entreview.com (Boyd Ebsworthy) Date: Mon, 03 Sep 2001 18:01:49 +0000 Subject: VNC and CORBA Message-ID: <002c01c13497$64a36360$2c30fac2@entreview.com> hi everyone, I'm looking for a way to remotely control a vncserver, i also understand that the internal (corba enabled) version will not be released, so i was wondering if anyone here has done some work to implement some corba control to the windows version of the server. Anyway i'll do my best to come up with something but since i currently know very little about corba any hints or examples will be welcomed :) thanks boyd. --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From zmer@weddingchannel.com Mon Sep 3 19:11:56 2001 From: zmer@weddingchannel.com (Zmer Andranigian) Date: Mon, 03 Sep 2001 18:11:56 +0000 Subject: ip forwarding win98 Message-ID: <7D380B2F4B3BD411B748009027855234015814E7@laxchange.weddingc hannel.com> why not just vnc to the machine with two nics and then open another vnc session and vnc over to the other network? -----Original Message----- From: OAnkert@t-online.de [mailto:OAnkert@t-online.de] Sent: Monday, September 03, 2001 6:59 AM To: VNC Liste Subject: ip forwarding win98 Hello, i have one pc running win98 with two network cards, each attached to a different network. I need to forwarding ip from one network to the other to access the vncservers running on that network. I can not change this pc to winNT or 2000. Can anybody help? Oliver --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From Eric@InvisibleRobot.com Mon Sep 3 19:27:21 2001 From: Eric@InvisibleRobot.com (Eric Carlson) Date: Mon, 03 Sep 2001 18:27:21 +0000 Subject: TightVNC crash on 6 of 16 NT servers References: Message-ID: <3B93B093.CB0294F6@InvisibleRobot.com> Constantin: I think all the servers are running at 800x600x16-bit. The same problem happens no matter which VNC client is used. I'll have to get the Dr.Watson error to send to you, as soon as I can get back into the servers. All the servers should have the same VNC settings. I'll have to find out what video drivers each server is running. - Eric, http://www.InvisibleRobot.com/ > Date: 03 Sep 2001 07:18:31 +0800 > From: Const Kaplinsky > Subject: Re: TightVNC crash on 6 of 16 NT servers > > I have not seen crashes with latest TightVNC version yet, and if I > could re-produce the problem, or to clarify conditions causing the > server to crash, that could help me to locate and fix bugs that might > cause the problem. What color mode do you use on servers and does > changing screen mode (e.g. 24bit -> 16bit) change anything? Do these > crashes depend on encoding or cursor pointer mode used? Maybe there is > something where machines differ (e.g. video drivers)? > > Also, I'd like to know, does anybody else experience similar problems? > > - -- > With Best Wishes, > Constantin --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From sczjd@yahoo.com Mon Sep 3 19:31:23 2001 From: sczjd@yahoo.com (SI Reasoning) Date: Mon, 03 Sep 2001 18:31:23 +0000 Subject: Problem with VNC Viewer In-Reply-To: <000501c1346e$0952e900$0b515d18@CHARLIELABTOP> Message-ID: <20010903172556.46558.qmail@web9501.mail.yahoo.com> Did you try all 3 (only one at a time though!) You know this has to be set on the server computer...not the computer you are typing from. You have to set it up in your user account on the server. --- Karl-Heinz Schulz wrote: > No, no difference - I see just the gray X start up > page - no Windows > manager. > > -----Original Message----- > From: owner-vnc-list@uk.research.att.com > [mailto:owner-vnc-list@uk.research.att.com] On > Behalf Of SI Reasoning > Sent: Monday, September 03, 2001 1:18 AM > To: vnc-list@uk.research.att.com > Subject: RE: Problem with VNC Viewer > > try this: > ------------------ > #!/bin/sh > > xrdb $HOME/.Xresources > exec fvwm > #exec gnome-session > #exec startkde > ---------------------- > you can unmark gnome or kde and re-mark fvwm if you > want to try the others. > > > --- Karl-Heinz Schulz > wrote: > > I didn't try fvwm because it was installed it > > remotely be me. > > I tried it also with KDE and Gnome - both are > > installed and work. > > > > The problem is that the server is in Montreal and > > I'm in North Carolina and > > log in via OpenSSH. > > > > -----Original Message----- > > From: owner-vnc-list@uk.research.att.com > > [mailto:owner-vnc-list@uk.research.att.com] On > > Behalf Of SI Reasoning > > Sent: Sunday, September 02, 2001 7:33 PM > > To: vnc-list@uk.research.att.com > > Subject: Re: Problem with VNC Viewer > > > > Have you tried the fvwm on your desktop to make > sure > > it works? > > Are you sure it is installed? > > > > --- Karl-Heinz Schulz > > wrote: > > > Viewer is installed on Windows 2000 (with all > > > patches installed) > > > VNC Server is installed on Mandrake 8 (latest > > > version available) > > > > > > Problem number 1 - kvm is not available on > > Mandrake > > > when running Xfree 4.XX > > > I have the following Windows Manager installed > > > > > > KDE > > > Gnome > > > Fvwm > > > > > > When starting the viewer I see only the grey > start > > > up screen > > > > > > The output of my xstartup file is as following > > > > > > bash-2.05$ more xstartup > > > #!/bin/sh > > > > > > xrdb $HOME/.Xresources > > > xsetroot -solid grey > > > xterm -geometry 80x24+10+10 -ls -title > > "$VNCDESKTOP > > > Desktop" & > > > fvwm & > > > > > > What am I missing? > > > > > > Thank you > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, send a message with the line: > > > unsubscribe vnc-list > > > to majordomo@uk.research.att.com > > > See also: > > > http://www.uk.research.att.com/vnc/intouch.html > > > > > > --------------------------------------------------------------------- > > > > ===== > > SI Reasoning > > sczjd@yahoo.com > > gnupg/pgp key id 035213BC > > > > __________________________________________________ > > Do You Yahoo!? > > Get email alerts & NEW webcam video instant > > messaging with Yahoo! Messenger > > http://im.yahoo.com > > > --------------------------------------------------------------------- > > To unsubscribe, send a message with the line: > > unsubscribe vnc-list > > to majordomo@uk.research.att.com > > See also: > > http://www.uk.research.att.com/vnc/intouch.html > > > --------------------------------------------------------------------- > > > --------------------------------------------------------------------- > > To unsubscribe, send a message with the line: > > unsubscribe vnc-list > > to majordomo@uk.research.att.com > > See also: > > http://www.uk.research.att.com/vnc/intouch.html > > > --------------------------------------------------------------------- > > ===== > SI Reasoning > sczjd@yahoo.com > gnupg/pgp key id 035213BC > > __________________________________________________ > Do You Yahoo!? > Get email alerts & NEW webcam video instant > messaging with Yahoo! Messenger > http://im.yahoo.com > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: > unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: > http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: > unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: > http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- ===== SI Reasoning sczjd@yahoo.com gnupg/pgp key id 035213BC __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From twaugh@redhat.com Mon Sep 3 19:41:31 2001 From: twaugh@redhat.com (Tim Waugh) Date: Mon, 03 Sep 2001 18:41:31 +0000 Subject: [patch] make vncpasswd create ~/.vnc if it doesn't exist Message-ID: <20010903183607.F20060@redhat.com> Here is a patch that makes vncpasswd create ~/.vnc if it doesn't exist, rather than failing with a less than obvious error message. Tim. */ --- vnc_unixsrc/vncpasswd/vncpasswd.c.vncuserdir Tue Aug 17 12:31:42 1999 +++ vnc_unixsrc/vncpasswd/vncpasswd.c Mon Sep 3 18:09:06 2001 @@ -24,9 +24,12 @@ * anyway. */ +#include #include #include #include +#include +#include #include #include "vncauth.h" @@ -38,6 +41,7 @@ int main(int argc, char *argv[]) { char *passwd; char *passwd1; + char passwdDir[256]; char passwdFile[256]; int i; @@ -46,7 +50,8 @@ fprintf(stderr,"Error: no HOME environment variable\n"); exit(1); } - sprintf(passwdFile,"%s/.vnc/passwd",getenv("HOME")); + sprintf(passwdDir,"%s/.vnc",getenv("HOME")); + sprintf(passwdFile,"%s/passwd",passwdDir); } else if (argc == 2) { @@ -78,6 +83,12 @@ } if (strcmp(passwd1, passwd) == 0) { + if (mkdir (passwdDir, (S_IRWXU | S_IRGRP | S_IXGRP | + S_IROTH | S_IXOTH)) == -1 && + errno != EEXIST) { + perror ("~/.vnc"); + exit (1); + } if (vncEncryptAndStorePasswd(passwd, passwdFile) != 0) { fprintf(stderr,"Cannot write password file %s\n",passwdFile); exit(1); --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From twaugh@redhat.com Mon Sep 3 19:43:17 2001 From: twaugh@redhat.com (Tim Waugh) Date: Mon, 03 Sep 2001 18:43:17 +0000 Subject: Problem with VNC Viewer In-Reply-To: <20010903172556.46558.qmail@web9501.mail.yahoo.com>; from sczjd@yahoo.com on Mon, Sep 03, 2001 at 10:25:56AM -0700 References: <000501c1346e$0952e900$0b515d18@CHARLIELABTOP> <20010903172556.46558.qmail@web9501.mail.yahoo.com> Message-ID: <20010903183827.G20060@redhat.com> Here is the patch that I'll be putting into the Red Hat Linux VNC RPMs to make this kind of thing easier. Tim. */ --- vnc_unixsrc/vncserver.xclients Mon Sep 3 17:45:51 2001 +++ vnc_unixsrc/vncserver Mon Sep 3 17:48:16 2001 @@ -43,10 +43,8 @@ $defaultXStartup = ("#!/bin/sh\n\n". - "xrdb \$HOME/.Xresources\n". - "xsetroot -solid grey\n". - "xterm -geometry 80x24+10+10 -ls -title \"\$VNCDESKTOP Desktop\" &\n". - "twm &\n"); + "# Red Hat Linux VNC session startup script\n". + "exec /etc/X11/xinit/Xclients\n"); chop($host = `uname -n`); Tim. */ --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From karlheinz@khschulz.com Mon Sep 3 20:21:40 2001 From: karlheinz@khschulz.com (Karl-Heinz Schulz) Date: Mon, 03 Sep 2001 19:21:40 +0000 Subject: Problem with VNC Viewer In-Reply-To: <20010903172556.46558.qmail@web9501.mail.yahoo.com> Message-ID: <001401c134a3$942c4f50$0b515d18@CHARLIELABTOP> Yes ;) Yes of course - the viewer is used on a Windows 2000 machine. -----Original Message----- From: owner-vnc-list@uk.research.att.com [mailto:owner-vnc-list@uk.research.att.com] On Behalf Of SI Reasoning Sent: Monday, September 03, 2001 1:26 PM To: vnc-list@uk.research.att.com Subject: RE: Problem with VNC Viewer Did you try all 3 (only one at a time though!) You know this has to be set on the server computer...not the computer you are typing from. You have to set it up in your user account on the server. --- Karl-Heinz Schulz wrote: > No, no difference - I see just the gray X start up > page - no Windows > manager. > > -----Original Message----- > From: owner-vnc-list@uk.research.att.com > [mailto:owner-vnc-list@uk.research.att.com] On > Behalf Of SI Reasoning > Sent: Monday, September 03, 2001 1:18 AM > To: vnc-list@uk.research.att.com > Subject: RE: Problem with VNC Viewer > > try this: > ------------------ > #!/bin/sh > > xrdb $HOME/.Xresources > exec fvwm > #exec gnome-session > #exec startkde > ---------------------- > you can unmark gnome or kde and re-mark fvwm if you > want to try the others. > > > --- Karl-Heinz Schulz > wrote: > > I didn't try fvwm because it was installed it > > remotely be me. > > I tried it also with KDE and Gnome - both are > > installed and work. > > > > The problem is that the server is in Montreal and > > I'm in North Carolina and > > log in via OpenSSH. > > > > -----Original Message----- > > From: owner-vnc-list@uk.research.att.com > > [mailto:owner-vnc-list@uk.research.att.com] On > > Behalf Of SI Reasoning > > Sent: Sunday, September 02, 2001 7:33 PM > > To: vnc-list@uk.research.att.com > > Subject: Re: Problem with VNC Viewer > > > > Have you tried the fvwm on your desktop to make > sure > > it works? > > Are you sure it is installed? > > > > --- Karl-Heinz Schulz > > wrote: > > > Viewer is installed on Windows 2000 (with all > > > patches installed) > > > VNC Server is installed on Mandrake 8 (latest > > > version available) > > > > > > Problem number 1 - kvm is not available on > > Mandrake > > > when running Xfree 4.XX > > > I have the following Windows Manager installed > > > > > > KDE > > > Gnome > > > Fvwm > > > > > > When starting the viewer I see only the grey > start > > > up screen > > > > > > The output of my xstartup file is as following > > > > > > bash-2.05$ more xstartup > > > #!/bin/sh > > > > > > xrdb $HOME/.Xresources > > > xsetroot -solid grey > > > xterm -geometry 80x24+10+10 -ls -title > > "$VNCDESKTOP > > > Desktop" & > > > fvwm & > > > > > > What am I missing? > > > > > > Thank you > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, send a message with the line: > > > unsubscribe vnc-list > > > to majordomo@uk.research.att.com > > > See also: > > > http://www.uk.research.att.com/vnc/intouch.html > > > > > > --------------------------------------------------------------------- > > > > ===== > > SI Reasoning > > sczjd@yahoo.com > > gnupg/pgp key id 035213BC > > > > __________________________________________________ > > Do You Yahoo!? > > Get email alerts & NEW webcam video instant > > messaging with Yahoo! Messenger > > http://im.yahoo.com > > > --------------------------------------------------------------------- > > To unsubscribe, send a message with the line: > > unsubscribe vnc-list > > to majordomo@uk.research.att.com > > See also: > > http://www.uk.research.att.com/vnc/intouch.html > > > --------------------------------------------------------------------- > > > --------------------------------------------------------------------- > > To unsubscribe, send a message with the line: > > unsubscribe vnc-list > > to majordomo@uk.research.att.com > > See also: > > http://www.uk.research.att.com/vnc/intouch.html > > > --------------------------------------------------------------------- > > ===== > SI Reasoning > sczjd@yahoo.com > gnupg/pgp key id 035213BC > > __________________________________________________ > Do You Yahoo!? > Get email alerts & NEW webcam video instant > messaging with Yahoo! Messenger > http://im.yahoo.com > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: > unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: > http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: > unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: > http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- ===== SI Reasoning sczjd@yahoo.com gnupg/pgp key id 035213BC __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From steedra@earthlink.net Mon Sep 3 20:59:39 2001 From: steedra@earthlink.net (Robert A. Steed) Date: Mon, 03 Sep 2001 19:59:39 +0000 Subject: Systray Icon Message-ID: <000001c134a9$670c6ef0$010000c0@steedra> I am currently running VNC 3.3.3r9 and looking for a way to hide the SysTray Icon. Does anyone have a registry edit that will do this or can point me in the right direction. Thanks in advance. Robert A. Steed mailto:steedra@yahoo.com http://www.afn.org/~afn52478 --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From gmabbutt@quartetservice.com Mon Sep 3 21:16:27 2001 From: gmabbutt@quartetservice.com (Glenn Mabbutt) Date: Mon, 03 Sep 2001 20:16:27 +0000 Subject: Systray Icon Message-ID: <11AAD83F4149D4118C840008C7CF4686D04D7A@QMAIL> -----Original Message----- From: Robert A. Steed [mailto:steedra@earthlink.net] Sent: Monday, September 03, 2001 2:51 PM To: vnc-list@uk.research.att.com Subject: Systray Icon I am currently running VNC 3.3.3r9 and looking for a way to hide the SysTray Icon. Does anyone have a registry edit that will do this or can point me in the right direction. Thanks in advance. Robert A. Steed mailto:steedra@yahoo.com http://www.afn.org/~afn52478 --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From pdy1969@yahoo.com Mon Sep 3 21:16:31 2001 From: pdy1969@yahoo.com (Philip Ygnacio) Date: Mon, 03 Sep 2001 20:16:31 +0000 Subject: Systray Icon In-Reply-To: <000001c134a9$670c6ef0$010000c0@steedra> Message-ID: <20010903191409.84004.qmail@web11201.mail.yahoo.com> the way to solve this is to install the VNC a s a "Service". You will find the instructions for doing this in the instruction packet that you can down load at the VNC website. --- "Robert A. Steed" wrote: > I am currently running VNC 3.3.3r9 and looking for a way to hide the SysTray > Icon. Does anyone have a registry edit that will do this or can point me in > the right direction. > > > Thanks in advance. > > Robert A. Steed > mailto:steedra@yahoo.com > http://www.afn.org/~afn52478 > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- ===== Have you ever noticed that the people that say something can't be done .... are the ones that are always successfull at not doing anything? >> pdy << Some see the world as it is ...and.. ask... " WHY" ? Others see the world as it could be and ask... "Why Not" ? << Robert Kennedy >> __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From gmabbutt@quartetservice.com Mon Sep 3 21:16:39 2001 From: gmabbutt@quartetservice.com (Glenn Mabbutt) Date: Mon, 03 Sep 2001 20:16:39 +0000 Subject: Systray Icon Message-ID: <11AAD83F4149D4118C840008C7CF4686D04D7B@QMAIL> Yes, look at the TridiaVNC distro - they have this registry hack included. See http://www.tridiavnc.com. -----Original Message----- From: Robert A. Steed [mailto:steedra@earthlink.net] Sent: Monday, September 03, 2001 2:51 PM To: vnc-list@uk.research.att.com Subject: Systray Icon I am currently running VNC 3.3.3r9 and looking for a way to hide the SysTray Icon. Does anyone have a registry edit that will do this or can point me in the right direction. Thanks in advance. Robert A. Steed mailto:steedra@yahoo.com http://www.afn.org/~afn52478 --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From steedra@earthlink.net Mon Sep 3 22:56:52 2001 From: steedra@earthlink.net (Robert A. Steed) Date: Mon, 03 Sep 2001 21:56:52 +0000 Subject: Systray Icon In-Reply-To: <20010903191409.84004.qmail@web11201.mail.yahoo.com> Message-ID: <000001c134ba$857085f0$010000c0@steedra> I have set it up as a service, but did watch my registry a little closer this time. It was placing a hook in the registry for service helper. This is what kept is showing in the systray. Removing that service helper from the run once part of the registry corrected. Thanks for the pointer. -----Original Message----- From: owner-vnc-list@uk.research.att.com [mailto:owner-vnc-list@uk.research.att.com]On Behalf Of Philip Ygnacio Sent: Monday, September 03, 2001 3:14 PM To: vnc-list@uk.research.att.com Subject: Re: Systray Icon the way to solve this is to install the VNC a s a "Service". You will find the instructions for doing this in the instruction packet that you can down load at the VNC website. --- "Robert A. Steed" wrote: > I am currently running VNC 3.3.3r9 and looking for a way to hide the SysTray > Icon. Does anyone have a registry edit that will do this or can point me in > the right direction. > > > Thanks in advance. > > Robert A. Steed > mailto:steedra@yahoo.com > http://www.afn.org/~afn52478 > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- ===== Have you ever noticed that the people that say something can't be done .... are the ones that are always successfull at not doing anything? >> pdy << Some see the world as it is ...and.. ask... " WHY" ? Others see the world as it could be and ask... "Why Not" ? << Robert Kennedy >> __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From sczjd@yahoo.com Mon Sep 3 23:51:14 2001 From: sczjd@yahoo.com (SI Reasoning) Date: Mon, 03 Sep 2001 22:51:14 +0000 Subject: Problem with VNC Viewer In-Reply-To: <001401c134a3$942c4f50$0b515d18@CHARLIELABTOP> Message-ID: <20010903214739.44134.qmail@web9502.mail.yahoo.com> have you killed the process and then restarted the server after you make the change? If not, type vncserver -kill :1 replace the number (1) with the number for your server then type vncserver :1 (again replacing your number for the 1. --- Karl-Heinz Schulz wrote: > Yes ;) > Yes of course - the viewer is used on a Windows 2000 > machine. > > -----Original Message----- > From: owner-vnc-list@uk.research.att.com > [mailto:owner-vnc-list@uk.research.att.com] On > Behalf Of SI Reasoning > Sent: Monday, September 03, 2001 1:26 PM > To: vnc-list@uk.research.att.com > Subject: RE: Problem with VNC Viewer > > Did you try all 3 (only one at a time though!) > You know this has to be set on the server > computer...not the computer you are typing from. You > have to set it up in your user account on the > server. > > --- Karl-Heinz Schulz > wrote: > > No, no difference - I see just the gray X start up > > page - no Windows > > manager. > > > > -----Original Message----- > > From: owner-vnc-list@uk.research.att.com > > [mailto:owner-vnc-list@uk.research.att.com] On > > Behalf Of SI Reasoning > > Sent: Monday, September 03, 2001 1:18 AM > > To: vnc-list@uk.research.att.com > > Subject: RE: Problem with VNC Viewer > > > > try this: > > ------------------ > > #!/bin/sh > > > > xrdb $HOME/.Xresources > > exec fvwm > > #exec gnome-session > > #exec startkde > > ---------------------- > > you can unmark gnome or kde and re-mark fvwm if > you > > want to try the others. > > > > > > --- Karl-Heinz Schulz > > wrote: > > > I didn't try fvwm because it was installed it > > > remotely be me. > > > I tried it also with KDE and Gnome - both are > > > installed and work. > > > > > > The problem is that the server is in Montreal > and > > > I'm in North Carolina and > > > log in via OpenSSH. > > > > > > -----Original Message----- > > > From: owner-vnc-list@uk.research.att.com > > > [mailto:owner-vnc-list@uk.research.att.com] On > > > Behalf Of SI Reasoning > > > Sent: Sunday, September 02, 2001 7:33 PM > > > To: vnc-list@uk.research.att.com > > > Subject: Re: Problem with VNC Viewer > > > > > > Have you tried the fvwm on your desktop to make > > sure > > > it works? > > > Are you sure it is installed? > > > > > > --- Karl-Heinz Schulz > > > wrote: > > > > Viewer is installed on Windows 2000 (with all > > > > patches installed) > > > > VNC Server is installed on Mandrake 8 (latest > > > > version available) > > > > > > > > Problem number 1 - kvm is not available on > > > Mandrake > > > > when running Xfree 4.XX > > > > I have the following Windows Manager installed > > > > > > > > KDE > > > > Gnome > > > > Fvwm > > > > > > > > When starting the viewer I see only the grey > > start > > > > up screen > > > > > > > > The output of my xstartup file is as following > > > > > > > > bash-2.05$ more xstartup > > > > #!/bin/sh > > > > > > > > xrdb $HOME/.Xresources > > > > xsetroot -solid grey > > > > xterm -geometry 80x24+10+10 -ls -title > > > "$VNCDESKTOP > > > > Desktop" & > > > > fvwm & > > > > > > > > What am I missing? > > > > > > > > Thank you > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, send a message with the line: > > > > unsubscribe vnc-list > > > > to majordomo@uk.research.att.com > > > > See also: > > > > > http://www.uk.research.att.com/vnc/intouch.html > > > > > > > > > > --------------------------------------------------------------------- > > > > > > ===== > > > SI Reasoning > > > sczjd@yahoo.com > > > gnupg/pgp key id 035213BC > > > > > > > __________________________________________________ > > > Do You Yahoo!? > > > Get email alerts & NEW webcam video instant > > > messaging with Yahoo! Messenger > > > http://im.yahoo.com > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, send a message with the line: > > > unsubscribe vnc-list > > > to majordomo@uk.research.att.com > > > See also: > > > http://www.uk.research.att.com/vnc/intouch.html > > > > > > --------------------------------------------------------------------- > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, send a message with the line: > > > unsubscribe vnc-list > > > to majordomo@uk.research.att.com > > > See also: > > > http://www.uk.research.att.com/vnc/intouch.html > > > > > > --------------------------------------------------------------------- > > > > ===== > > SI Reasoning > > sczjd@yahoo.com > > gnupg/pgp key id 035213BC > > > > __________________________________________________ > > Do You Yahoo!? > > Get email alerts & NEW webcam video instant > > messaging with Yahoo! Messenger > > http://im.yahoo.com > > > --------------------------------------------------------------------- > > To unsubscribe, send a message with the line: > > unsubscribe vnc-list > > to majordomo@uk.research.att.com > > See also: > > http://www.uk.research.att.com/vnc/intouch.html > > > --------------------------------------------------------------------- > > > --------------------------------------------------------------------- > > To unsubscribe, send a message with the line: > > unsubscribe vnc-list > > to majordomo@uk.research.att.com > > See also: > > http://www.uk.research.att.com/vnc/intouch.html > > > --------------------------------------------------------------------- > > ===== > SI Reasoning > sczjd@yahoo.com > gnupg/pgp key id 035213BC > > __________________________________________________ > Do You Yahoo!? > Get email alerts & NEW webcam video instant > messaging with Yahoo! Messenger > http://im.yahoo.com > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: > unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: > http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: > unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: > http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- ===== SI Reasoning sczjd@yahoo.com gnupg/pgp key id 035213BC __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From sczjd@yahoo.com Mon Sep 3 23:53:07 2001 From: sczjd@yahoo.com (SI Reasoning) Date: Mon, 03 Sep 2001 22:53:07 +0000 Subject: Problem with VNC Viewer In-Reply-To: <20010903183827.G20060@redhat.com> Message-ID: <20010903215100.49971.qmail@web9507.mail.yahoo.com> You might want to leave in "xrdb \$HOME/.Xresources\n". since that will allow for individual changes (helps clue in sophisticated newbies) --- Tim Waugh wrote: > Here is the patch that I'll be putting into the Red > Hat Linux VNC RPMs > to make this kind of thing easier. > > Tim. > */ > > --- vnc_unixsrc/vncserver.xclients Mon Sep 3 > 17:45:51 2001 > +++ vnc_unixsrc/vncserver Mon Sep 3 17:48:16 2001 > @@ -43,10 +43,8 @@ > > $defaultXStartup > = ("#!/bin/sh\n\n". > - "xrdb \$HOME/.Xresources\n". > - "xsetroot -solid grey\n". > - "xterm -geometry 80x24+10+10 -ls -title > \"\$VNCDESKTOP Desktop\" &\n". > - "twm &\n"); > + "# Red Hat Linux VNC session startup > script\n". > + "exec /etc/X11/xinit/Xclients\n"); > > chop($host = `uname -n`); > > Tim. > */ > --------------------------------------------------------------------- > To unsubscribe, send a message with the line: > unsubscribe vnc-list > to majordomo@uk.research.att.com > See also: > http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- ===== SI Reasoning sczjd@yahoo.com gnupg/pgp key id 035213BC __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From ajv@greebo.net Tue Sep 4 04:39:07 2001 From: ajv@greebo.net (Andrew van der Stock) Date: Tue, 04 Sep 2001 03:39:07 +0000 Subject: [patch] make vncpasswd create ~/.vnc if it doesn't exist In-Reply-To: <20010903183607.F20060@redhat.com> Message-ID: NO! NO! NO! NO!* Do not EVER trust the environment, particularly when using sprintf() with bounded arrays! This is how we got into all that locale, xmcd, kerberos, dtmail (and so on... the list is endless) bother. Create the directory securely, and test for its existance before you go out and create it. This is how symlink attacks occur. The mode of the .vnc directory should be 700 not, 755. There is no reason to create this directory as 755, as this allows any user to discover the user's VNC password. Test the error result, don't just ignore it! Andrew * :-) in case you feel that I'm being too harsh. But this is about security, so I'm being harsh. -----Original Message----- From: owner-vnc-list@uk.research.att.com [mailto:owner-vnc-list@uk.research.att.com]On Behalf Of Tim Waugh Sent: Tuesday, 4 September 2001 03:36 To: vnc-list@uk.research.att.com Subject: [patch] make vncpasswd create ~/.vnc if it doesn't exist Here is a patch that makes vncpasswd create ~/.vnc if it doesn't exist, rather than failing with a less than obvious error message. Tim. */ --- vnc_unixsrc/vncpasswd/vncpasswd.c.vncuserdir Tue Aug 17 12:31:42 1999 +++ vnc_unixsrc/vncpasswd/vncpasswd.c Mon Sep 3 18:09:06 2001 @@ -24,9 +24,12 @@ * anyway. */ +#include #include #include #include +#include +#include #include #include "vncauth.h" @@ -38,6 +41,7 @@ int main(int argc, char *argv[]) { char *passwd; char *passwd1; + char passwdDir[256]; char passwdFile[256]; int i; @@ -46,7 +50,8 @@ fprintf(stderr,"Error: no HOME environment variable\n"); exit(1); } - sprintf(passwdFile,"%s/.vnc/passwd",getenv("HOME")); + sprintf(passwdDir,"%s/.vnc",getenv("HOME")); + sprintf(passwdFile,"%s/passwd",passwdDir); } else if (argc == 2) { @@ -78,6 +83,12 @@ } if (strcmp(passwd1, passwd) == 0) { + if (mkdir (passwdDir, (S_IRWXU | S_IRGRP | S_IXGRP | + S_IROTH | S_IXOTH)) == -1 && + errno != EEXIST) { + perror ("~/.vnc"); + exit (1); + } if (vncEncryptAndStorePasswd(passwd, passwdFile) != 0) { fprintf(stderr,"Cannot write password file %s\n",passwdFile); exit(1); --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From Asael_Degany@amat.com Tue Sep 4 07:33:40 2001 From: Asael_Degany@amat.com (Asael_Degany@amat.com) Date: Tue, 04 Sep 2001 06:33:40 +0000 Subject: Refresh problem using Internet Explorer to view VNC server that run on Unix station Message-ID: Hi, I have a refresh problem using Internet Explorer 4.0 ( on my P.C. with window NT 4.) to connect to VNC server on my Unix station: When I'm working on any P.C. and drag an application window inside the Explorer window (that display the VNC server) it is not refreshed, therefore the dragged window is spread all over the browser window. I don't experience that problem at all when I'm using VNCviwer that is installed on any P.C. Any solution ? Thanks Asael --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From twaugh@redhat.com Tue Sep 4 10:39:20 2001 From: twaugh@redhat.com (Tim Waugh) Date: Tue, 04 Sep 2001 09:39:20 +0000 Subject: [patch] make vncpasswd create ~/.vnc if it doesn't exist In-Reply-To: ; from ajv@greebo.net on Tue, Sep 04, 2001 at 12:31:13PM +1000 References: <20010903183607.F20060@redhat.com> Message-ID: <20010904093418.K20060@redhat.com> On Tue, Sep 04, 2001 at 12:31:13PM +1000, Andrew van der Stock wrote: > NO! NO! NO! NO!* I know what you mean; I was horified myself to learn that the user's .vnc directory has world execute permission. But the passwd file has mode 600 (see the code that creates it in the library). I was just extending the existing convention: take a look at how the vncserver script creates the .vnc directory. > Do not EVER trust the environment, particularly when using sprintf() with > bounded arrays! This is how we got into all that locale, xmcd, kerberos, > dtmail (and so on... the list is endless) bother. Well, to be honest, the risk here is hard to see: * If the user's HOME environment variable is somehow changed by an attacker, they are in trouble anyhow since the VNC library is about to fopen(...,"w") the passwd file. * Otherwise the HOME environment variable is sane, so we should worry about symlink attacks. Wait---a symlink attack on a user, in their own home directory? How? > The mode of the .vnc directory should be 700 not, 755. There is no reason to > create this directory as 755, as this allows any user to discover the user's > VNC password. Although the 'allows any user to discover the user's VNC password' bit is incorrect (see above), I agree that this directory ought to be more secure. That requires a change to the vncserver script as well. > Test the error result, don't just ignore it! Where do I ignore an error result? Thanks for the feedback. Tim. */ [demime 0.97b removed an attachment of type application/pgp-signature] --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to majordomo@uk.research.att.com See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- From christian@i-a.co.uk Tue Sep 4 10:39:26 2001 From: christian@i-a.co.uk (Christian D'Amico) Date: Tue, 04 Sep 2001 09:39:26 +0000 Subject: Problem connecting to VNC Server Message-ID: <002701c1351c$d25d4990$1f00a8c0@ia.co.uk> Hi all, wondering if someone can help me. I've tried us