Re: RedHat Enterprise 4, Gnome and SELinux security
On Sun, Jun 12, 2005 at 04:08:55AM -0400, Ken Winheim wrote: I've been asked by many clients for a simple detailed procedure for getting VNC to properly display gnome desktops on RedHat Enterprise Linux 4. I'm curious.. The final ~/.vnc/startup/ file should look like this: #!/bin/sh # Uncomment the following two lines for normal desktop: # unset SESSION_MANAGER # exec /etc/X11/xinit/xinitrc [ -x /etc/vnc/xstartup ] exec /etc/vnc/xstartup [ -r $HOME/.Xresources ] xrdb $HOME/.Xresources xsetroot -solid grey vncconfig -iconic xterm -geometry 80x24+10+10 -ls -title $VNCDESKTOP Desktop gnome-session --sm-disable gnome-session Why didn't just uncommenting the indicated lines do what you want? Tim. */ [demime 1.01d removed an attachment of type application/pgp-signature] ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
RE: reed: Connection reset by peer (10054)
Joel, What reason for disconnecting the viewer does the server give in its log file? (Look for a line starting Connections: closed). Regards, Wez @ RealVNC Ltd. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dr. Joel M. Hoffman Sent: 12 June 2005 15:07 To: vnc-list@realvnc.com Subject: reed: Connection reset by peer (10054) I am still plagues by the Connection reset by peer error message, which pops up almost whenever I connect to my Unix host (and I don't think I've ever seen it connecting to a Windows host). I get the message whichever viewer I'm using. I almost always get the error message if I leave the vnc connection idle for a while. If I'm using a slow connection, and I leave the connection idle for even 30 seconds, I'm likely to get the error message. The auto-reconnect feature is helpful in dealing with this, but isn't there some way to avoid it? Thanks. -Joel ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
RE: Adding servers
John, Error 10061 means that the machine who's IP address you specified does not have a VNC Server running on it. This might be because you're specifying the wrong IP address, or the wrong port/display number, or because there really is no server running. Regards, Wez @ RealVNC Ltd. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Griffiths Sent: 13 June 2005 03:08 To: VCN Subject: Adding servers I would like to know how to add servers to my list as a viewer. Also, I am attempting to connect to a server and I get the error message 10061. What is the meaning of this code? I checked and rechecked the IP address and it is OK. Perhaps the system is getting confused with #1 server and that is why I would like to know how to add extra servers. I thought maybe the server's firewall may have something to do with it. Thanks again, John. ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
RE: Mac talking to Windows Free VNC server problems
Robert, You need to upgrade the Java Virtual Machine on the Mac. This is a known behaviour with older versions of the VM that appears to have been fixed in more recent builds. Regards, Wez @ RealVNC Ltd. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dr Robert Young Sent: 13 June 2005 02:47 To: vnc-list@realvnc.com Subject: Mac talking to Windows Free VNC server problems When I use the Mac Firefox, IE, or Safari to go to a Windows Free VNC V4.1 server on port 5800, I get a java exception (java.lang.NullPointerException) after leaving the connection details screen on the Mac (running OS/X 10.3.9). When I go to the same system with a copy of Windows IE ( running on Win/ME) or Windows Netscape, it works perfectly. Ideas? ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
Re: Screen freezing in VNC4.1.1 over SSH
I have investigated further and have found a scenario where one change makes the problem appear. The test setup is as follows:- VNC viewer/PuTTY SSH tunnel | Linux firewall, ADSL router | internet | ADSL router - NAT 192.168.0.x | Linux Firewall, terminating SSH session external IP 192.168.0.254 internal IP 10.0.0.1 (separate physical ethernet card, same LAN segment) NAT - 10.0.0.x | VNC server machine IP 192.168.0.13 IP 10.0.0.23 (I have 2 separate cards in the machine, though the result is the same if I change the IP and only use 1) Result: If I port forward to the 192.168.0.13 IP address the VNC connection is stable. If I port forward to the 10.0.0.23 IP address, the VNC session hangs as before The only difference between these two sessions is that the Linux box terminating the SSH connection is forwarding to a 'public' address (from it's point of view) in one case and to a private address in the other. I suppose the next steps would be to try segmenting the LAN properly and swapping the ethernet cards on the SSH terminating linux server. I'll report back once I have done that. Any other suggestions on what could be going on here? Thanks mark. On 6/10/05, James Weatherall [EMAIL PROTECTED] wrote: Mark, The bad log indicates that VNC Viewer is seeing the connection close and is then exiting. The only obvious difference between the two logs is that the second session involves a change to the clipboard, which will result in data being transmitted to the server if the clipboard contents are text. If the contents were a large amount of text then this could conceivably cause the viewer to appear to hang while it was being transferred to the server. Regards, Wez @ RealVNC Ltd. -Original Message- From: Mark [mailto:[EMAIL PROTECTED] Sent: 10 June 2005 17:21 To: James Weatherall Cc: vnc-list@realvnc.com; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Screen freezing in VNC4.1.1 over SSH Here are the full logs of a good and a bad session. To make things as close as possible, I minimised and unminimised it after a few seconds - ie before anything froze. FYI, on the bad session I minimised vncviewer at 17:09:52 and unminimised it at 17:15:11. Thanks mark. ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
RE: Screen freezing in VNC4.1.1 over SSH
Mark, I don't understand your network configuration. Why does your VNC server machine have two IP addresses? Are both of its network cards connected to the linux firewall? Is anything on your network connected directly to the ADSL router? Wez @ RealVNC Ltd. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Sent: 13 June 2005 11:36 To: James Weatherall Cc: vnc-list@realvnc.com; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Screen freezing in VNC4.1.1 over SSH I have investigated further and have found a scenario where one change makes the problem appear. The test setup is as follows:- VNC viewer/PuTTY SSH tunnel | Linux firewall, ADSL router | internet | ADSL router - NAT 192.168.0.x | Linux Firewall, terminating SSH session external IP 192.168.0.254 internal IP 10.0.0.1 (separate physical ethernet card, same LAN segment) NAT - 10.0.0.x | VNC server machine IP 192.168.0.13 IP 10.0.0.23 (I have 2 separate cards in the machine, though the result is the same if I change the IP and only use 1) Result: If I port forward to the 192.168.0.13 IP address the VNC connection is stable. If I port forward to the 10.0.0.23 IP address, the VNC session hangs as before The only difference between these two sessions is that the Linux box terminating the SSH connection is forwarding to a 'public' address (from it's point of view) in one case and to a private address in the other. I suppose the next steps would be to try segmenting the LAN properly and swapping the ethernet cards on the SSH terminating linux server. I'll report back once I have done that. Any other suggestions on what could be going on here? Thanks mark. On 6/10/05, James Weatherall [EMAIL PROTECTED] wrote: Mark, The bad log indicates that VNC Viewer is seeing the connection close and is then exiting. The only obvious difference between the two logs is that the second session involves a change to the clipboard, which will result in data being transmitted to the server if the clipboard contents are text. If the contents were a large amount of text then this could conceivably cause the viewer to appear to hang while it was being transferred to the server. Regards, Wez @ RealVNC Ltd. -Original Message- From: Mark [mailto:[EMAIL PROTECTED] Sent: 10 June 2005 17:21 To: James Weatherall Cc: vnc-list@realvnc.com; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Screen freezing in VNC4.1.1 over SSH Here are the full logs of a good and a bad session. To make things as close as possible, I minimised and unminimised it after a few seconds - ie before anything froze. FYI, on the bad session I minimised vncviewer at 17:09:52 and unminimised it at 17:15:11. Thanks mark. ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
VNC Re-distribution
Am I allowed to distrbute VNC with my application? Thanks, Dave ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
RE: Question on accessing sound on viewer
No. VNC does not do sound. Only Video, mouse and keyboard. There have been rumors of other third-party network sound utils, but I don't know of any myself. -Original Message- From: Frank [mailto:[EMAIL PROTECTED] Sent: Sunday, June 12, 2005 8:25 AM To: vnc-list@realvnc.com Subject: Question on accessing sound on viewer I have two Win XP pcs - one I use for the server and the other for the viewer - both using VCN 4.0.0.6. The two pcs are connected via cable with a Netgear router. I notice that when my wife is playing music on the server pc and tells me to listen to the song, I cannot access the sound (music) with the viewer pc; the same is true when she is using MSN Messenger to chat with our relatives and I want to join in. Is there a way to configure the server and/or viewer settings to access sound on the viewer? Thanks for any assistance. Frank ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
RE: Mac talking to Windows Free VNC server problems
Make sure the VNC ports are permitted through the XP firewall and any other firewalls you may have. -Original Message- From: Dr Robert Young [mailto:[EMAIL PROTECTED] Sent: Sunday, June 12, 2005 9:47 PM To: vnc-list@realvnc.com Subject: Mac talking to Windows Free VNC server problems When I use the Mac Firefox, IE, or Safari to go to a Windows Free VNC V4.1 server on port 5800, I get a java exception (java.lang.NullPointerException) after leaving the connection details screen on the Mac (running OS/X 10.3.9). When I go to the same system with a copy of Windows IE ( running on Win/ME) or Windows Netscape, it works perfectly. Ideas? ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
RE: VNC Re-distribution
David, Assuming that you're referring to VNC Free Edition, you'll need to ensure that you comply with the requirements of the GPL, in particular with respect to applicability of the license to derived works. Regards, Wez @ RealVNC Ltd. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mock, David Sent: 13 June 2005 14:44 To: vnc-list@realvnc.com Subject: VNC Re-distribution Am I allowed to distrbute VNC with my application? Thanks, Dave ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
Re: Screen freezing in VNC4.1.1 over SSH
Wez, If everything was working fine, the VNC server would have only one IP address in th 10.0.0.x range and one NIC. I tried it on the 192.168.0.x (ie public as far as the linux SSH server is concerned, but still behind the ADSL router NAT) range just to see if it made any difference. As I had a machine with 2 network cards, I set it up so I could switch from one to the other with no other changes to make testing easier. In this test setup, both 192.168.0.x and 10.0.0.x interfaces of both the Linux firewall and the VNC server are plugged into the same hub (though I will try separating to see if that makes a difference). Normally the ADSL router acts as a hub for the local network (ie there is both 192.168.0.x traffic and 10.0.0.x traffic on the one hub), so yes there are potentially other things connected to the ADSL router, though I have reproduced the problem with nothing else connected. I realise running both ranges on one hub isn't perfect from a security point of view, but it's adequate for what I need security wise. Thanks, mark. On 6/13/05, James Weatherall [EMAIL PROTECTED] wrote: Mark, I don't understand your network configuration. Why does your VNC server machine have two IP addresses? Are both of its network cards connected to the linux firewall? Is anything on your network connected directly to the ADSL router? Wez @ RealVNC Ltd. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Sent: 13 June 2005 11:36 To: James Weatherall Cc: vnc-list@realvnc.com; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Screen freezing in VNC4.1.1 over SSH I have investigated further and have found a scenario where one change makes the problem appear. The test setup is as follows:- VNC viewer/PuTTY SSH tunnel | Linux firewall, ADSL router | internet | ADSL router - NAT 192.168.0.x | Linux Firewall, terminating SSH session external IP 192.168.0.254 internal IP 10.0.0.1 (separate physical ethernet card, same LAN segment) NAT - 10.0.0.x | VNC server machine IP 192.168.0.13 IP 10.0.0.23 (I have 2 separate cards in the machine, though the result is the same if I change the IP and only use 1) Result: If I port forward to the 192.168.0.13 IP address the VNC connection is stable. If I port forward to the 10.0.0.23 IP address, the VNC session hangs as before The only difference between these two sessions is that the Linux box terminating the SSH connection is forwarding to a 'public' address (from it's point of view) in one case and to a private address in the other. I suppose the next steps would be to try segmenting the LAN properly and swapping the ethernet cards on the SSH terminating linux server. I'll report back once I have done that. Any other suggestions on what could be going on here? Thanks mark. On 6/10/05, James Weatherall [EMAIL PROTECTED] wrote: Mark, The bad log indicates that VNC Viewer is seeing the connection close and is then exiting. The only obvious difference between the two logs is that the second session involves a change to the clipboard, which will result in data being transmitted to the server if the clipboard contents are text. If the contents were a large amount of text then this could conceivably cause the viewer to appear to hang while it was being transferred to the server. Regards, Wez @ RealVNC Ltd. -Original Message- From: Mark [mailto:[EMAIL PROTECTED] Sent: 10 June 2005 17:21 To: James Weatherall Cc: vnc-list@realvnc.com; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Screen freezing in VNC4.1.1 over SSH Here are the full logs of a good and a bad session. To make things as close as possible, I minimised and unminimised it after a few seconds - ie before anything froze. FYI, on the bad session I minimised vncviewer at 17:09:52 and unminimised it at 17:15:11. Thanks mark. ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
RE: Screen freezing in VNC4.1.1 over SSH
Mark, I'm afraid I really don't understand your network setup! You have a NAT router, so you don't need a separate firewall, but you do have a separate firewall, but the things connected to it see also to be connected directly to the router and so the firewall isn't actually firewalling. I'm also not sure what you mean by public as far as SSH is concerned since SSH doesn't have any concept of IP addresses being public or private and is not involved in firewalling. You originally stated that you had a problem with VNC Viewer, which you've since stated only occurs if you use a machine's direct-to-ADSL address rather than its via-Linux-PC address, but you've then said that you only added the direct-to-ADSL address because you had problems with VNC, so I'm not sure what setup it is that you're actually having problems with. I wondered whether when you said Linux firewall, you actually just mean Linux SSH server, but that wouldn't explain why you have two distinct sets of IP addresses. :( Wez @ RealVNC Ltd. -Original Message- From: Mark [mailto:[EMAIL PROTECTED] Sent: 13 June 2005 16:13 To: James Weatherall Cc: vnc-list@realvnc.com; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Screen freezing in VNC4.1.1 over SSH Wez, If everything was working fine, the VNC server would have only one IP address in th 10.0.0.x range and one NIC. I tried it on the 192.168.0.x (ie public as far as the linux SSH server is concerned, but still behind the ADSL router NAT) range just to see if it made any difference. As I had a machine with 2 network cards, I set it up so I could switch from one to the other with no other changes to make testing easier. In this test setup, both 192.168.0.x and 10.0.0.x interfaces of both the Linux firewall and the VNC server are plugged into the same hub (though I will try separating to see if that makes a difference). Normally the ADSL router acts as a hub for the local network (ie there is both 192.168.0.x traffic and 10.0.0.x traffic on the one hub), so yes there are potentially other things connected to the ADSL router, though I have reproduced the problem with nothing else connected. I realise running both ranges on one hub isn't perfect from a security point of view, but it's adequate for what I need security wise. Thanks, mark. On 6/13/05, James Weatherall [EMAIL PROTECTED] wrote: Mark, I don't understand your network configuration. Why does your VNC server machine have two IP addresses? Are both of its network cards connected to the linux firewall? Is anything on your network connected directly to the ADSL router? Wez @ RealVNC Ltd. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Sent: 13 June 2005 11:36 To: James Weatherall Cc: vnc-list@realvnc.com; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Screen freezing in VNC4.1.1 over SSH I have investigated further and have found a scenario where one change makes the problem appear. The test setup is as follows:- VNC viewer/PuTTY SSH tunnel | Linux firewall, ADSL router | internet | ADSL router - NAT 192.168.0.x | Linux Firewall, terminating SSH session external IP 192.168.0.254 internal IP 10.0.0.1 (separate physical ethernet card, same LAN segment) NAT - 10.0.0.x | VNC server machine IP 192.168.0.13 IP 10.0.0.23 (I have 2 separate cards in the machine, though the result is the same if I change the IP and only use 1) Result: If I port forward to the 192.168.0.13 IP address the VNC connection is stable. If I port forward to the 10.0.0.23 IP address, the VNC session hangs as before The only difference between these two sessions is that the Linux box terminating the SSH connection is forwarding to a 'public' address (from it's point of view) in one case and to a private address in the other. I suppose the next steps would be to try segmenting the LAN properly and swapping the ethernet cards on the SSH terminating linux server. I'll report back once I have done that. Any other suggestions on what could be going on here? Thanks mark. On 6/10/05, James Weatherall [EMAIL PROTECTED] wrote: Mark, The bad log indicates that VNC Viewer is seeing the connection close and is then exiting. The only obvious difference between the two logs is that the second session involves a change to the clipboard, which will result in data being transmitted to the server if the clipboard contents are text. If the contents were a large amount of text then this could conceivably cause the viewer to appear to hang while it was being transferred to the server. Regards, Wez @ RealVNC Ltd. -Original Message- From: Mark [mailto:[EMAIL PROTECTED] Sent: 10 June 2005
connect from Windows to Linux with VNC
Hello, I am a Linux novice and entirely new to Linux admin. I have installed Fedora core 3.0 onto a machine that I would like to connect to, via VNC, from my Windows (XP) platform, but have so far been unsuccessful. I have successfully installed and run vncserver on the Linux machine. Netstat -al shows that the vnc ports are open and listening when vncserver is running. I have changed the firewall settings to allow the vnc tcp ports, and I confirmed this in iptables: -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 5901 -j ACCEPT However, I am still unable to connect to the Linux machine. From Vnc viewer in XP, I recieve an error massage Unable to connect to host: connection timed out (10060). I also tried to connect the Linux machine to itself using vncviewer and I get a similar message: unable to connect to host: no route to host (113). I suspect that I need to do something with the network settings. For example, from the Linux computer I can ping other computers on the network, but this computer cannot be pinged by other computers or itself: Mon Jun 13 12:28:41 2005 main:unable to connect to host: No route to host (113) [EMAIL PROTECTED] ping ichabod PING ichabod.whrc.org (199.92.170.34) 56(84) bytes of data. From 199.92.170.121 icmp_seq=1 Destination Host Unreachable From 199.92.170.121 icmp_seq=2 Destination Host Unreachable [and so on] --- ichabod.whrc.org ping statistics --- 23 packets transmitted, 0 received, +15 errors, 100% packet loss, time 22001ms I don't know what to do, or even what to look for, to address this problem. Any help or advice will be appreciated. Thanks, Claire ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
RE: connect from Windows to Linux with VNC
Two things: 1) Either disable the XP firewall or allow VNC to pass through 2) Make sure the linux box doesn't have a firewall running to disallow connecting to it. You probably will be unable to connect your linux box to itself... This is to prevent the hall of mirrors effect. John -Original Message- From: Claire Jantz [mailto:[EMAIL PROTECTED] Sent: Monday, June 13, 2005 12:57 PM To: vnc-list@realvnc.com Subject: connect from Windows to Linux with VNC Hello, I am a Linux novice and entirely new to Linux admin. I have installed Fedora core 3.0 onto a machine that I would like to connect to, via VNC, from my Windows (XP) platform, but have so far been unsuccessful. I have successfully installed and run vncserver on the Linux machine. Netstat -al shows that the vnc ports are open and listening when vncserver is running. I have changed the firewall settings to allow the vnc tcp ports, and I confirmed this in iptables: -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 5901 -j ACCEPT However, I am still unable to connect to the Linux machine. From Vnc viewer in XP, I recieve an error massage Unable to connect to host: connection timed out (10060). I also tried to connect the Linux machine to itself using vncviewer and I get a similar message: unable to connect to host: no route to host (113). I suspect that I need to do something with the network settings. For example, from the Linux computer I can ping other computers on the network, but this computer cannot be pinged by other computers or itself: Mon Jun 13 12:28:41 2005 main:unable to connect to host: No route to host (113) [EMAIL PROTECTED] ping ichabod PING ichabod.whrc.org (199.92.170.34) 56(84) bytes of data. From 199.92.170.121 icmp_seq=1 Destination Host Unreachable From 199.92.170.121 icmp_seq=2 Destination Host Unreachable [and so on] --- ichabod.whrc.org ping statistics --- 23 packets transmitted, 0 received, +15 errors, 100% packet loss, time 22001ms I don't know what to do, or even what to look for, to address this problem. Any help or advice will be appreciated. Thanks, Claire ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
Re: connect from Windows to Linux with VNC
- Original Message - From: Claire Jantz [EMAIL PROTECTED] To: vnc-list@realvnc.com Sent: Monday, June 13, 2005 9:56 AM Subject: connect from Windows to Linux with VNC Hello, I am a Linux novice and entirely new to Linux admin. I have installed Fedora core 3.0 onto a machine that I would like to connect to, via VNC, from my Windows (XP) platform, but have so far been unsuccessful. [snip] Hi Claire, what is the ip address of this computer? It's looking that when you say ping ichabod, ichabod resolves to ichabod.whrc.org. is the ip 199.92.170.34 the real ip of your computer? Try pinging your own address. To find that address, type ifconfig and what is eth0 say your inet addr: is. Then use that ip and try to vnc from there. If you can connect from the FC3 desktop to itself, but not from your other computers on your LAN, it probably means you have a firewall issue in FC3. To add port 5901 to the allowed ports, in Fedora go to: Applications | System Settings | Security Level | enter your root password | under Firewall Options in the Other ports: field add a comma behind what's there if any, and add 5901:tcp | click OK and save settings, and then try again. You can also, disable your firewall altogether if this is just for fun and you're behind a router, but I think the preferred security method is using two NICs and adding one for the trusted interface that is only available on the LAN and the other NIC for the outside world which is how I have my FC3 box setup. Karen ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
Trying to compile Xvnc for OpenGL support on Linux
Hi, I'm trying to compile Xvnc with OpenGL support in Red Hat Enterprise Linux WS release 3 (Taroon Update 4). I've got the following RPM : vnc-4.0-0.beta4.1.4.src.rpm. The README has the following instructions : Once you have a copy of the X source tree, make sure it is unpacked at the top level of this distribution, so that the xc directory of the X source tree matches the xc of this distribution. Then you must apply a patch to some files in the X source tree: % patch -Np0 xc.patch If this works, you should be able to build the entire X tree, including Xvnc: % cd xc % make World This RPM contains the X source, so I copied the xc directory from X source over the xc directory in the vnc-4.0b4-unixsrc directory, applied the patch, set #define BuildGlxExt YES in vnc.def, compiled eveything with no complaints. However, Xvnc doesn't get built. Can anyone tell me what I'm missing? Thanks, Jason Mazzotta ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
Re: connect from Windows to Linux with VNC
- Original Message - From: [EMAIL PROTECTED] [snip] Hi Claire, what is the ip address of this computer? It's looking that when you say ping ichabod, ichabod resolves to ichabod.whrc.org. is the ip 199.92.170.34 the [snip] BTW, if you want to use the default FC3 desktop with vnc, you can copy my vnc/xstartup file: #!/bin/sh # Uncomment the following two lines for normal desktop: unset SESSION_MANAGER exec /etc/X11/xinit/xinitrc [ -x /etc/vnc/xstartup ] exec /etc/vnc/xstartup [ -r $HOME/.Xresources ] xrdb $HOME/.Xresources xsetroot -solid grey vncconfig -iconic #xterm -geometry 80x24+10+10 -ls -title $VNCDESKTOP Desktop #twm ..and then to make the clipboard transfers work, in FC3, run the command gnome-session-properties and click the Startup Programs tab and click Add and enter vncconfig (if you'd like vncconfig to hide itself at startup use the -nowin switch, click OK and then restart vnc. Unfortunately, the vncconfig -iconic option in the .vnc/xstartup file doesn't seem to run vncconfig when those 1st two uncommented out options are used, you I have to use gnome-session-properties to get it to work automatically. If you have any further issues, you can write me, and irc://irc.freenode.net/fedora (http://tinyurl.com/2xbnx ) is a great source for support too. Karen ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
vnc on solaris 8, can't get rid of grey x session
hello, I finally figured out how to make vnc work on solaris! (after lots of research and experimenting!) I installed the vnc from the companion CD (2/02) add the /opt/sfw/bin and /usr/openwin/bin to PATH, then modify vncserver script on /opt/sfw/bin; at the defaultXStartup section, change the last line 'twm' section to /usr/dt/bin/dtsession \n I did this on a fresh install and it works! I had another box where i left the twm and ran vncserver sessions. Then I tried changing the vncserver script to be like above, but it still gives me the old grey X session. I tried removing the .vnc directory and making new password, but it still gives me grey X session. I'm guessing there must be some temp files somewhere (or something like that) that keeps the initial grey X session and keeps running that even after I changed the vncserver script. What can I do to clear this out so it works with dtsession instead of grey X session? I also cleared out the /tmp directory but no luck. killed all vncserver sessions and restarted - no luck. even rebooted - no luck. I think I'm pretty close to getting dtsession to come up instead of grey X session but I'm at a dead end. HELP!! Thank you, Oskar ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
