[opensuse] vnc on dial-up and why 5800 is open?!
Hi, My mom's stock/boxed SUSE 8.2 is on dial-up. Sometimes I teach her to do tasks via vnc, being located in another country. I'm new to vnc, but the desktop sharing we do from her KDE session is simple and the thing works quite well... The only thing I would change is to avoid seeing her desktop image when connecting, which would surely accelerate the speed of the connection a lot. I use SUSE 9.1 with KDE 3.3.x, where there was an option to hide desktop background when connecting, but on her earlier KDE's Control Center there was no option like this and disableBackground=true in her respective config file was also without any effect:( Any idea/work-around please to achieve the needed effect or acce- lerate on another way the vnc connection's speed?! The second related question is that on her computer I saw TCP 5800 listening. I didn't see it before she activated the desktop sharing and would be interested, how it could get opened. I didn't activate vnc through xinetd and chkconfig reports it (as supposed) to be deactivated. The only thing is that via KDE's Control Panel we acti- vated the above desktop sharing and immediately moved it to a higher port number. TCP 5800 I just saw accidentally and is anyway firewal- led; the particular port needed by me has been opened under the SuSEfirewall2. Thank you for any thoughts, comments. Pelibali -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 11 Feb 2007, pelibali wrote:
Hi,
My mom's stock/boxed SUSE 8.2 is on dial-up. Sometimes I teach her to do tasks via vnc, being located in another country. I'm new to vnc, but the desktop sharing we do from her KDE session is simple and the thing works quite well...
The only thing I would change is to avoid seeing her desktop image when connecting, which would surely accelerate the speed of the connection a lot. I use SUSE 9.1 with KDE 3.3.x, where there was an option to hide desktop background when connecting, but on her earlier KDE's Control Center there was no option like this and disableBackground=true in her respective config file was also without any effect:(
Any idea/work-around please to achieve the needed effect or acce- lerate on another way the vnc connection's speed?!
The second related question is that on her computer I saw TCP 5800 listening. I didn't see it before she activated the desktop sharing and would be interested, how it could get opened. I didn't activate vnc through xinetd and chkconfig reports it (as supposed) to be deactivated. The only thing is that via KDE's Control Panel we acti- vated the above desktop sharing and immediately moved it to a higher port number. TCP 5800 I just saw accidentally and is anyway firewal- led; the particular port needed by me has been opened under the SuSEfirewall2.
Thank you for any thoughts, comments.
Pelibali
I've not used VNC but I first tried NX If you are both on Linux, have a look at www.nomachine.com. Their free NX Client/server is excellent. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 11 February 2007 06:45, pelibali wrote:
My mom's stock/boxed SUSE 8.2 is on dial-up. Sometimes I teach her to do tasks via vnc, being located in another country. I'm new to vnc, but the desktop sharing we do from her KDE session is simple and the thing works quite well...
The second related question is that on her computer I saw TCP 5800 listening. I didn't see it before she activated the desktop sharing and would be interested, how it could get opened. I didn't activate vnc through xinetd and chkconfig reports it (as supposed) to be deactivated. The only thing is that via KDE's Control Panel we acti- vated the above desktop sharing and immediately moved it to a higher port number. TCP 5800 I just saw accidentally and is anyway firewal- led; the particular port needed by me has been opened under the SuSEfirewall2.
Pelibali
VNC uses port 5800 for the java based server, i.e. the client runs in a web browser. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi, On Sun, 11 Feb 2007 15:19:34 -0600 Wade Jones <.> wrote:
On Sunday 11 February 2007 06:45, pelibali wrote: ... The second related question is that on her computer I saw TCP 5800 listening. I didn't see it before she activated the desktop sharing and would be interested, how it could get opened. I didn't activate vnc through xinetd and chkconfig reports it (as supposed) to be deactivated. The only thing is that via KDE's Control Panel we acti- vated the above desktop sharing and immediately moved it to a higher port number. TCP 5800 I just saw accidentally and is anyway firewal- led; the particular port needed by me has been opened under the SuSEfirewall2.
Pelibali
VNC uses port 5800 for the java based server, i.e. the client runs in a web browser.
I moved from KDE's default vnc server port (5900) to a higher one, so in fact no need for 5800! Any chance to deactivate that 5800 and keep only my custom port? As I mentioned earlier, I firewall 5800 anyway, but would be surely better to avoid listening on that particular java based server port. Thanks, Pelibali -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 12 February 2007 12:36:25 pm pelibali wrote:
I moved from KDE's default vnc server port (5900) to a higher one, so in fact no need for 5800! Any chance to deactivate that 5800 and keep only my custom port? As I mentioned earlier, I firewall 5800 anyway, but would be surely better to avoid listening on that particular java based server port.
Thanks, Pelibali
YaST, Network Services, Network Service (xinetd) and make sure that the services vnc1, vnc2 and vnc3 are all disabled/off. Those are the 5801, 5802 and 5803 ports used by web browsers to VNC. Stan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon February 12 2007 14:20, S Glasoe wrote:
YaST, Network Services, Network Service (xinetd) and make sure that the services vnc1, vnc2 and vnc3 are all disabled/off. Those are the 5801, 5802 and 5803 ports used by web browsers to VNC.
This is interesting... out of curiosity, I logged into a shell as superuser and did a 'chkconfig vnc1 status'... it reports "illegal runlevel specified for vnc1: t", likewise vnc2 and vnc3. What's up? Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 12 February 2007 07:14:49 pm Carl Hartung wrote:
On Mon February 12 2007 14:20, S Glasoe wrote:
YaST, Network Services, Network Service (xinetd) and make sure that the services vnc1, vnc2 and vnc3 are all disabled/off. Those are the 5801, 5802 and 5803 ports used by web browsers to VNC.
This is interesting... out of curiosity, I logged into a shell as superuser and did a 'chkconfig vnc1 status'... it reports "illegal runlevel specified for vnc1: t", likewise vnc2 and vnc3. What's up?
Carl
Wait a minute. Who said to disable the vnc1, vnc2, vnc3? Some noob. The correct thing to disable to stop web browsing through a java client in a vnc manner are the vnchttpd1, vnchttpd2 and vnchttpd3 services. Some people just answer with the first thing out of their tiny little brains... So to disable the web browser vnc capabilities disable the vnchttpd1, vnchttpd2 and vnchttpd3 services. To be unable to use the regular vnc services please disable vnc1, vnc2 and vnc3. Sheesh, some people... You'd think they'd double check their answers occasionally... Stan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Carl Hartung -
ianseeks -
pelibali -
S Glasoe -
Wade Jones