Simon Renshaw | 2 Mar 2006 17:02

Disable new clients problem

Hi,

Is there a way to automatically uncheck Disable New Clients when the
connection gets dropped?

I have a user that lost her connection last night and couldn't get back on
the computer since she checked Disable New Clients.

Would stopping and restarting the service work?

Running dev 1.37 on Win XP.

Thanks
Simon
Attachment (smime.p7s): application/x-pkcs7-signature, 3030 bytes
Michael Sharp | 4 Mar 2006 08:31

VNC over VPN

I use VNC over VPN when I am away from work. I use OpenVPN so I know my
VNC sessions are secured. If I run the VNC server and leave the account
logged in, everything is fine. But, if I do Start -> Log Off -> Switch
User then I cannot connect to the VNC server over the VPN.

The reason I am concerned about this is that there are three users on this
win box, and I want all to have a VNC server process on different ports
(diff passwords) and have it so when we are all away nobody can sit down
at the winbox and see what everyone is doing while they use their
respective VNC process.

So, in short, is there a way to run TightVNC server and log off and still
have the process usuable?

Michael

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___________________________________________________________
TightVNC mailing list, VNC-Tight-list <at> lists.sourceforge.net
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list

Rock | 4 Mar 2006 09:11
Picon
Favicon

When I connect to an XP box with TightVNC the 'Bliss' grass-sky goes to blue

Hi,

When I interact with a server box from the Internet via the TightVNC 
Viewer, the usual 'XP Bliss' Desktop screen changes to Dark Blue.  I 
have Dark Blue set as my screen colour but with the 'Bliss'  landscape 
the default.

For me to get it back, I have to reboot the server box when I get back 
to the office.

Why would this be?

Thanks

Rock

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
___________________________________________________________
TightVNC mailing list, VNC-Tight-list <at> lists.sourceforge.net
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list

Mark D. Brasche | 4 Mar 2006 17:22

RE: VNC over VPN

First, make sure WinVNC runs as a process.
Second, dev7 definitely does have a bug in it that prevents a smooth logoff/logon in any given session.
Regress to dev6 to see if that 'fixes' your problem.

-----Original Message-----
From: vnc-tight-list-admin <at> lists.sourceforge.net
[mailto:vnc-tight-list-admin <at> lists.sourceforge.net]On Behalf Of Michael
Sharp
Sent: Saturday, March 04, 2006 2:31 AM
To: vnc-tight-list <at> lists.sourceforge.net
Subject: VNC over VPN

I use VNC over VPN when I am away from work. I use OpenVPN so I know my
VNC sessions are secured. If I run the VNC server and leave the account
logged in, everything is fine. But, if I do Start -> Log Off -> Switch
User then I cannot connect to the VNC server over the VPN.

The reason I am concerned about this is that there are three users on this
win box, and I want all to have a VNC server process on different ports
(diff passwords) and have it so when we are all away nobody can sit down
at the winbox and see what everyone is doing while they use their
respective VNC process.

So, in short, is there a way to run TightVNC server and log off and still
have the process usuable?

Michael

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
(Continue reading)

Jacob Everist | 5 Mar 2006 11:15
Picon
Gravatar

server connection problems in FC4

Hello,

I've been trying to setup a tightvnc server on Fedora Core 4 linux, but I am having a connection problem.  When I setup VNC on the FC4 server, I get this:
---------
[jacob <at> localhost .vnc]$ vncserver

New 'localhost.localdomain:1 (jacob)' desktop is localhost.localdomain:1

Starting applications specified in /home/jacob/.vnc/xstartup
Log file is /home/jacob/.vnc/localhost.localdomain:1.log
---------

Wonderful.  Everything smooth so far.

When I try to connect to it remotely, I get this:
-----
[wildmage <at> localhost ~]$ vncviewer myserver.mydomain.com:1
vncviewer: ConnectToTcpAddr: connect: Connection timed out
Unable to connect to VNC server
-----

Originally I approached this as a VNC configuration problem, and I tried to address the SecurityPolicy and font errors that were found in the server log file, but that didn't accomplish anything.  I think those errors are warnings and don't really affect the server that much.

I can connect to the VNC server locally, so the server is actually working, but it's not accepting connections for some reason.

So then I thought that I might have a network problem.  I tried to open a telnet session the VNC port 5901 and got no response, no connection.  So I did a tcpdump to see if the connection attempt is filtered out by some firewall in the LAN, but tcpdump correctly reports a connection attempt on port 5901.  So, I am successfully able to contact port 5901, but it does not establish a vnc connection.

This seems like a network configuration problem in the default install of Fedora Core 4.  However, I have no idea on what it might be or how to go about tracking it down.  Has anyone had similar problems with FC4 or other linux distros?  Does anyone have any suggestions on how to address this issue?

Thanks,
--

Jacob Everist

Michael D. Setzer II | 6 Mar 2006 04:16

Re: server connection problems in FC4


Probable a selinux problem.
Run system-config-securitylevel
At the bottome, it shows other ports.
Enter 5901:tcp for port 01.

I generally also modify vncservers file
/etc/sysconfig/vncservers

You can modify the line VNCSERVERS to
VNCSERVERS="1:user1 20:user2 50:user3"
Then you activate the vncserver service, and it will start these sessions at 
boot time. You must set the session up manually once to create the 
password.

I like to use specific ports for users, and you would need to open each port 
for the selinux to allow it to connect.

On 5 Mar 2006 at 2:15, Jacob Everist wrote:

> 
> Hello,
> 
> I've been trying to setup a tightvnc server on Fedora Core 4 linux, but I am having a connection 
> problem. When I setup VNC on the FC4 server, I get this:
> ---------
> [jacob <at> localhost .vnc]$ vncserver
> 
> New 'localhost.localdomain:1 (jacob)' desktop is localhost.localdomain:1
> 
> Starting applications specified in /home/jacob/.vnc/xstartup
> Log file is /home/jacob/.vnc/localhost.localdomain:1.log
> ---------
> 
> Wonderful. Everything smooth so far.
> 
> When I try to connect to it remotely, I get this:
> -----
> [wildmage <at> localhost ~]$ vncviewer myserver.mydomain.com:1
> vncviewer: ConnectToTcpAddr: connect: Connection timed out
> Unable to connect to VNC server
> -----
> 
> Originally I approached this as a VNC configuration problem, and I tried to address the 
> SecurityPolicy and font errors that were found in the server log file, but that didn't accomplish 
> anything. I think those errors are warnings and don't really affect the server that much.
> 
> I can connect to the VNC server locally, so the server is actually working, but it's not accepting 
> connections for some reason.
> 
> So then I thought that I might have a network problem. I tried to open a telnet session the VNC 
> port 5901 and got no response, no connection. So I did a tcpdump to see if the connection 
> attempt is filtered out by some firewall in the LAN, but tcpdump correctly reports a connection 
> attempt on port 5901. So, I am successfully able to contact port 5901, but it does not establish a 
> vnc connection.
> 
> This seems like a network configuration problem in the default install of Fedora Core 4. However, 
> I have no idea on what it might be or how to go about tracking it down. Has anyone had similar 
> problems with FC4 or other linux distros? Does anyone have any suggestions on how to address 
> this issue?
> 
> Thanks,
> -- 
> 
> Jacob Everist

+----------------------------------------------------------+
  Michael D. Setzer II -  Computer Science Instructor      
  Guam Community College  Computer Center                  
  mailto:mikes <at> kuentos.guam.net                            
  mailto:msetzerii <at> gmail.com
  http://www.guam.net/home/mikes
  Guam - Where America's Day Begins                        
+----------------------------------------------------------+

http://setiathome.berkeley.edu
Number of Seti Units Returned:  19,471
Processing time:  32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)

BOINC Seti <at> Home Total Credits 501569.663057 

Jeff Schallenberg | 7 Mar 2006 00:15
Picon

VNC viewer can't "see" alpha-blended apps?

I am running TightVNC 1.3dev7 on my desktop PC, and viewing with vncviewer on my laptop. Both machines are using xp sp2. Some of my applications on the desktop PC use alpha-blending, meaning that the application window appears translucent. Very cool - except those windows don't show in the viewer :-(

Is this a known limitation? Is there a fix or a work-around?

--
Jeff Schallenberg
Saint Lambert, Québec

James Weatherall | 7 Mar 2006 00:24
Favicon

RE: VNC viewer can't "see" alpha-blended apps?

Jeff,

Current VNC Server releases (http://www.realvnc.com/download.html) support
capture of alpha-blended windows. 

Cheers,

Wez  <at>  RealVNC Ltd.

> -----Original Message-----
> From: vnc-tight-list-admin <at> lists.sourceforge.net 
> [mailto:vnc-tight-list-admin <at> lists.sourceforge.net] On Behalf 
> Of Jeff Schallenberg
> Sent: 06 March 2006 23:15
> To: vnc-tight-list <at> lists.sourceforge.net
> Subject: VNC viewer can't "see" alpha-blended apps?
> 
> I am running TightVNC 1.3dev7 on my desktop PC, and viewing 
> with vncviewer on my laptop. Both machines are using xp sp2. 
> Some of my applications on the desktop PC use alpha-blending, 
> meaning that the application window appears translucent. Very 
> cool - except those windows don't show in the viewer :-( 
> 
> Is this a known limitation? Is there a fix or a work-around?
> 
> -- 
> Jeff Schallenberg
> Saint Lambert, Québec
> 
> 

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___________________________________________________________
TightVNC mailing list, VNC-Tight-list <at> lists.sourceforge.net
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list

Jacob Everist | 7 Mar 2006 06:40
Picon
Gravatar

Re: server connection problems in FC4

The problem why vncserver wouldn't accept connections on Fedora Core 4 out of the box was becayse FC4 starts with a pretty restrictive firewall set up.  Depending on what you selected on install, it will only accept connections for ftp, ssh, and http.  Any further connection ports you want to setup, you need to modify the iptables configuration file.

The config file is /etc/sysconfig/iptables

There will be 3 lines that allow ftp, http, and ssh:
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 21 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT

You need to add an extra line for vncserver:
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 5901 -j ACCEPT

After this, restart the iptables by running as root:
/sbin/service iptables restart

Hope this is helpful for future Fedora Core 4 users.

Jacob Everist



On 3/5/06, Michael D. Setzer II <mikes <at> kuentos.guam.net> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Probable a selinux problem.
Run system-config-securitylevel
At the bottome, it shows other ports.
Enter 5901:tcp for port 01.

I generally also modify vncservers file
/etc/sysconfig/vncservers

You can modify the line VNCSERVERS to
VNCSERVERS="1:user1 20:user2 50:user3"
Then you activate the vncserver service, and it will start these sessions at
boot time. You must set the session up manually once to create the
password.

I like to use specific ports for users, and you would need to open each port
for the selinux to allow it to connect.


On 5 Mar 2006 at 2:15, Jacob Everist wrote:

>
> Hello,
>
> I've been trying to setup a tightvnc server on Fedora Core 4 linux, but I am having a connection
> problem. When I setup VNC on the FC4 server, I get this:
> ---------
> [jacob <at> localhost .vnc]$ vncserver
>
> New 'localhost.localdomain:1 (jacob)' desktop is localhost.localdomain:1
>
> Starting applications specified in /home/jacob/.vnc/xstartup
> Log file is /home/jacob/.vnc/localhost.localdomain: 1.log
> ---------
>
> Wonderful. Everything smooth so far.
>
> When I try to connect to it remotely, I get this:
> -----
> [wildmage <at> localhost ~]$ vncviewer myserver.mydomain.com:1
> vncviewer: ConnectToTcpAddr: connect: Connection timed out
> Unable to connect to VNC server
> -----
>
> Originally I approached this as a VNC configuration problem, and I tried to address the
> SecurityPolicy and font errors that were found in the server log file, but that didn't accomplish
> anything. I think those errors are warnings and don't really affect the server that much.
>
> I can connect to the VNC server locally, so the server is actually working, but it's not accepting
> connections for some reason.
>
> So then I thought that I might have a network problem. I tried to open a telnet session the VNC
> port 5901 and got no response, no connection. So I did a tcpdump to see if the connection
> attempt is filtered out by some firewall in the LAN, but tcpdump correctly reports a connection
> attempt on port 5901. So, I am successfully able to contact port 5901, but it does not establish a
> vnc connection.
>
> This seems like a network configuration problem in the default install of Fedora Core 4. However,
> I have no idea on what it might be or how to go about tracking it down. Has anyone had similar
> problems with FC4 or other linux distros? Does anyone have any suggestions on how to address
> this issue?
>
> Thanks,
> --
>
> Jacob Everist


+----------------------------------------------------------+
  Michael D. Setzer II -  Computer Science Instructor
  Guam Community College  Computer Center
  mailto:mikes <at> kuentos.guam.net
  mailto: msetzerii <at> gmail.com
  http://www.guam.net/home/mikes
  Guam - Where America's Day Begins
+----------------------------------------------------------+

http://setiathome.berkeley.edu
Number of Seti Units Returned:  19,471
Processing time:  32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)


BOINC Seti <at> Home Total Credits 501569.663057


-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8 -- QDPGP 2.61c
Comment: http://community.wow.net/grt/qdpgp.html

iQA/AwUBRAsc8izGQcr/2AKZEQL8RwCfdid40E6S8U/PkbnlwWLba6IDBrwAoKX8
HX4N1y84f4XHVq46pIp+oBsU
=NENV
-----END PGP SIGNATURE-----



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
___________________________________________________________
TightVNC mailing list, VNC-Tight-list <at> lists.sourceforge.net
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list



--

Jacob Everist

Gmane