[opensuse-amd64] VNC on OpenSuse 10.2
Afternoon all, Open Suse 10.2 is now installed. I have a question about VNC sessions onto the Suse Box using RealVNC viewer. I cannot connect to the same session after disconnecting it like using Windows RealVNC server. This question has popped up a lot in my google searches and there are no answers for these guys! Is it because it is not possible? I use VNC for all my other boxes on my network and this is my first linux machine so it would be good if I could use the same stuff for RAS. How do you set the VNC server in linux to accept reconnection to old sessions? I have tried IPAddress:SessionNo ie: 192.168.0.x:1 and that always starts a new session where you have to log in. Same with ComputerName:SessionNo or just the computername or IPAddress. I'm guessing there are settings to change - but alas, my skills are poo. :) Thanks for any help. Ben _________________________________________________________________ Windows Live Messenger has arrived. Click here to download it for free! http://imagine-msn.com/messenger/launch80/?locale=en-gb --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
Ben Ladd wrote:
Afternoon all,
Open Suse 10.2 is now installed. I have a question about VNC sessions onto the Suse Box using RealVNC viewer. I cannot connect to the same session after disconnecting it like using Windows RealVNC server.
This question has popped up a lot in my google searches and there are no answers for these guys! Is it because it is not possible? I use VNC for all my other boxes on my network and this is my first linux machine so it would be good if I could use the same stuff for RAS.
How do you set the VNC server in linux to accept reconnection to old sessions? I have tried IPAddress:SessionNo ie: 192.168.0.x:1 and that always starts a new session where you have to log in. Same with ComputerName:SessionNo or just the computername or IPAddress.
I'm guessing there are settings to change - but alas, my skills are poo. :)
I'm assuming the session that you're connecting to was created by something like: vncserver --geometry 1024x768 --depth 24 - standard output tells you the screen number that it's using (s >= 2) If you're not doing the above explicitly, what do you think is? Does ps aux | grep -i vnc show anything? If not, try netstat to see if ports 590x are open. Given that the service *is* running, and you still can't connect, it sounds like a firewall issue to me - assuming SuSEfirewall2, you need to open ports 5900:5909 (*) for TCP (use YaST -> Security -> Firewall -> advanced) (unfortunately VNC isn't in the selection menu, not sure why not, so you have to select the ports manually) I use VNC both into and out of my AMD64 box with no problems. (*) the last digit corresponds to the screen number as s in command vncviewer host:s - opening 0 to 9 allows all likely screens. As you saw, s=1 connects to xdm (IIUIC) and allows a new session. This session closes when you exit... -- HTH Richard. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
Thanks for that, but I fear I am not communicating my problem correctly. I have the ability to VNC onto my linux box from my XP box no problem. The problem is that once I connect, I cannot reconnect to the same session again after closing the RealVNC window. What I want to be able to do is: 1. VNC onto the linux box from my windows box. - I can do this! 2. Close the VNC window, but not kill my session - I'm not sure what is happening to the session once I kill the VNC session on my windows box. 3. Reconnect to the Session that I opened in step 1, not just create a new session. I keep on closing my vnc window when I am in the middle of something on my linux box and I cant get it back! How does that sit? Cheers Ben
Afternoon all,
Open Suse 10.2 is now installed. I have a question about VNC sessions onto the Suse Box using RealVNC viewer. I cannot connect to the same session after disconnecting it like using Windows RealVNC server.
This question has popped up a lot in my google searches and there are no answers for these guys! Is it because it is not possible? I use VNC for all my other boxes on my network and this is my first linux machine so it would be good if I could use the same stuff for RAS.
How do you set the VNC server in linux to accept reconnection to old sessions? I have tried IPAddress:SessionNo ie: 192.168.0.x:1 and that always starts a new session where you have to log in. Same with ComputerName:SessionNo or just the computername or IPAddress.
I'm guessing there are settings to change - but alas, my skills are poo. :)
I'm assuming the session that you're connecting to was created by something like: vncserver --geometry 1024x768 --depth 24 - standard output tells you the screen number that it's using (s >= 2) If you're not doing the above explicitly, what do you think is? Does ps aux | grep -i vnc show anything? If not, try netstat to see if ports 590x are open. Given that the service *is* running, and you still can't connect, it sounds like a firewall issue to me - assuming SuSEfirewall2, you need to open ports 5900:5909 (*) for TCP (use YaST -> Security -> Firewall -> advanced) (unfortunately VNC isn't in the selection menu, not sure why not, so you have to select the ports manually) I use VNC both into and out of my AMD64 box with no problems. (*) the last digit corresponds to the screen number as s in command vncviewer host:s - opening 0 to 9 allows all likely screens. As you saw, s=1 connects to xdm (IIUIC) and allows a new session. This session closes when you exit... -- HTH Richard. _________________________________________________________________ Think you're a film buff? Play the Movie Mogul quiz and win fantastic prizes! http://www.msnmoviemogul.com --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
Okay, the method you are using to connect to the server automatically creates a new session. The port that the session is using is "random". Therefore it would not be easy to connect back to the session if the seesion still existed (which it doesn't). In Unix there are diferent ways to use vnc. The one you got is the "Inetd" method. This is more like a "Windows terminal session" than the VNC on windows session you are used to. It allows any number of simultaneously open connections to the linux machine. But closes the session when vnc disconnects. Another method of using vnc, is for you to start a "private" vnc session. This is the method another reader was talking about. In this scheeme, you start a session manually. You receive a port to connect to, and you can connect, and reconnect as many time as you wish. There is a third method. Here you tell your private X-Windows instance to allow remote controll via vnc. Of course you need to be logged in to X-Windows for the option to take effect, so I doubt its what you want either... The forth method is similar to windows. Here you tell the X-Windows system itself to allow remote access to the console so you can remote control the physical screen/keyboard/mouse of linux box. Just like windows this then allows you to "VNC-IN" and continue what ever you where doing on the console. I think this is what you want. It is configured under yast2->Hardware->Display (or something like that, I don't happen to have a linux handy at the moment). That starts the Graphic card configuration program. In there look for "Allow Remote acess" and/or VNC. Hope this helps Jerry Ben Ladd wrote:
Thanks for that, but I fear I am not communicating my problem correctly.
I have the ability to VNC onto my linux box from my XP box no problem.
The problem is that once I connect, I cannot reconnect to the same session again after closing the RealVNC window.
What I want to be able to do is:
1. VNC onto the linux box from my windows box. - I can do this! 2. Close the VNC window, but not kill my session - I'm not sure what is happening to the session once I kill the VNC session on my windows box. 3. Reconnect to the Session that I opened in step 1, not just create a new session.
I keep on closing my vnc window when I am in the middle of something on my linux box and I cant get it back!
How does that sit?
Cheers
Ben
Afternoon all,
Open Suse 10.2 is now installed. I have a question about VNC sessions onto the Suse Box using RealVNC viewer. I cannot connect to the same session after disconnecting it like using Windows RealVNC server.
This question has popped up a lot in my google searches and there are no answers for these guys! Is it because it is not possible? I use VNC for all my other boxes on my network and this is my first linux machine so it would be good if I could use the same stuff for RAS.
How do you set the VNC server in linux to accept reconnection to old sessions? I have tried IPAddress:SessionNo ie: 192.168.0.x:1 and that always starts a new session where you have to log in. Same with ComputerName:SessionNo or just the computername or IPAddress.
I'm guessing there are settings to change - but alas, my skills are poo. :)
I'm assuming the session that you're connecting to was created by something like:
vncserver --geometry 1024x768 --depth 24
- standard output tells you the screen number that it's using (s >= 2)
If you're not doing the above explicitly, what do you think is? Does
ps aux | grep -i vnc
show anything? If not, try netstat to see if ports 590x are open.
Given that the service *is* running, and you still can't connect, it sounds like a firewall issue to me - assuming SuSEfirewall2, you need to open ports 5900:5909 (*) for TCP (use YaST -> Security -> Firewall -> advanced) (unfortunately VNC isn't in the selection menu, not sure why not, so you have to select the ports manually)
I use VNC both into and out of my AMD64 box with no problems.
(*) the last digit corresponds to the screen number as s in command vncviewer host:s - opening 0 to 9 allows all likely screens. As you saw, s=1 connects to xdm (IIUIC) and allows a new session. This session closes when you exit... -- HTH Richard.
_________________________________________________________________ Think you're a film buff? Play the Movie Mogul quiz and win fantastic prizes! http://www.msnmoviemogul.com
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
Afternoon all,
Open Suse 10.2 is now installed. I have a question about VNC sessions onto the Suse Box using RealVNC viewer. I cannot connect to the same session after disconnecting it like using Windows RealVNC server.
This question has popped up a lot in my google searches and there are no answers for these guys! Is it because it is not possible? I use VNC for all my other boxes on my network and this is my first linux machine so it would be good if I could use the same stuff for RAS.
How do you set the VNC server in linux to accept reconnection to old sessions? I have tried IPAddress:SessionNo ie: 192.168.0.x:1 and that always starts a new session where you have to log in. Same with ComputerName:SessionNo or just the computername or IPAddress.
I'm guessing there are settings to change - but alas, my skills are poo. :)
I'm assuming the session that you're connecting to was created by something like:
vncserver --geometry 1024x768 --depth 24
- standard output tells you the screen number that it's using (s >= 2)
If you're not doing the above explicitly, what do you think is? Does
ps aux | grep -i vnc
show anything? If not, try netstat to see if ports 590x are open.
Given that the service *is* running, and you still can't connect, it sounds like a firewall issue to me - assuming SuSEfirewall2, you need to open ports 5900:5909 (*) for TCP (use YaST -> Security -> Firewall -> advanced) (unfortunately VNC isn't in the selection menu, not sure why not, so you have to select the ports manually)
I use VNC both into and out of my AMD64 box with no problems.
(*) the last digit corresponds to the screen number as s in command vncviewer host:s - opening 0 to 9 allows all likely screens. As you saw, s=1 connects to xdm (IIUIC) and allows a new session. This session closes when you exit... -- HTH Richard.
Ben Ladd wrote:
Thanks for that, but I fear I am not communicating my problem correctly.
I have the ability to VNC onto my linux box from my XP box no problem.
The problem is that once I connect, I cannot reconnect to the same session again after closing the RealVNC window.
What I want to be able to do is:
1. VNC onto the linux box from my windows box. - I can do this! 2. Close the VNC window, but not kill my session - I'm not sure what is happening to the session once I kill the VNC session on my windows box. 3. Reconnect to the Session that I opened in step 1, not just create a new session.
I keep on closing my vnc window when I am in the middle of something on my linux box and I cant get it back!
How does that sit?
Cheers
Ben
Okay, the method you are using to connect to the server automatically creates a new session. The port that the session is using is "random". Therefore it would not be easy to connect back to the session if the seesion still existed (which it doesn't).
In Unix there are diferent ways to use vnc.
The one you got is the "Inetd" method. This is more like a "Windows terminal session" than the VNC on windows session you are used to. It allows any number of simultaneously open connections to the linux machine. But closes the session when vnc disconnects.
Another method of using vnc, is for you to start a "private" vnc session. This is the method another reader was talking about. In this scheeme, you start a session manually. You receive a port to connect to, and you can connect, and reconnect as many time as you wish.
There is a third method. Here you tell your private X-Windows instance to allow remote controll via vnc. Of course you need to be logged in to X-Windows for the option to take effect, so I doubt its what you want either...
The forth method is similar to windows. Here you tell the X-Windows system itself to allow remote access to the console so you can remote control the physical screen/keyboard/mouse of linux box. Just like windows this then allows you to "VNC-IN" and continue what ever you where doing on the console. I think this is what you want. It is configured under yast2->Hardware->Display (or something like that, I don't happen to have a linux handy at the moment). That starts the Graphic card configuration program. In there look for "Allow Remote acess" and/or VNC.
Hope this helps Jerry
Problem solved. Jerry's fixed worked and I am now working fine. Sorry for stepping on peoples' toes - I have reformatted the message so that people do not get confused and can follow the question and fix. Newbie out. Thanks! Ben _________________________________________________________________ Windows Live Messenger has arrived. Click here to download it for free! http://imagine-msn.com/messenger/launch80/?locale=en-gb --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
participants (3)
-
Ben Ladd -
Jerry Westrick -
richard (MQ)