Rodney Almodovar | 1 May 01:12 2008
Picon

Rodney Almodovar/Austin/IBM is out of the office.

I will be out of the office starting 04/28/2008 and will not return until 05/05/2008.

Please contact David Birk v1dbirk <at> us.ibm.com, on any technical issues while I am out. Thanks!

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
___________________________________________________________
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
James Weatherall | 1 May 13:20 2008

RE: Cannot connect to VNC without monitor

Hi Midori,

In some configurations Windows avoids starting up the video hardware when it
thinks it's not in use, so that may be the problem you're hitting.  You can
test that by trying a trial installation of VNC Enterprise (or Personal)
Edition on that computer, which explicitly poke Windows to tell it the video
hardware is required.

Cheers,

--
Wez  <at>  RealVNC Ltd

> -----Original Message-----
> From: vnc-tight-list-bounces <at> lists.sourceforge.net 
> [mailto:vnc-tight-list-bounces <at> lists.sourceforge.net] On 
> Behalf Of Midori Kasugano
> Sent: 30 April 2008 07:52
> To: vnc-tight-list <at> lists.sourceforge.net
> Subject: Cannot connect to VNC without monitor
> 
> Hey all,
> 
> I've got a Pentium 200 with Windows Me running as a print and 
> scanner server.  I have TightVNC server running on it to 
> access the scanner.
> 
> The trouble is I'd like to not have the monitor and keyboard 
> connected to it.  However when I remove these and start the 
> machine up, I lose access to the VNC.
> 
> Is there anything I can do to stop this from happening?
> 
> Thanks
> 
> --
> Want an e-mail address like mine?
> Get a free e-mail account today at www.mail.com!
> 
> 
> --------------------------------------------------------------
> -----------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Don't miss this year's exciting event. There's still time to 
> save $100. 
> Use priority code J8TL2D2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java
.sun.com/javaone
> ___________________________________________________________
> 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
> 

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
___________________________________________________________
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

Jason Cowart | 1 May 17:52 2008
Picon

log out on exit

We are using vnc 1.3.9

 

On one computer, when I  access it remotely via VNC, when I close the VNC window on the viewer, the remote computer logs off.  It happens everytime.   Is there a setting causing the log off?  I need it to stop.

 

Jason

 

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
___________________________________________________________
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
Rohit Patil | 1 May 22:38 2008
Picon

Re: log out on exit

Yes, In the VNC Server Properties there is a radio button  that says
"Logoff workstation" under the section "When Last Client Disconnects".
You probably have that selected.

There are two other selections. Try one of those.
"Do Nothing"
"Lock Workstation"

-Rohit.

On Thu, May 1, 2008 at 8:52 AM, Jason Cowart <jcowart <at> mvhospital.net> wrote:
>
>
>
>
> We are using vnc 1.3.9
>
>
>
> On one computer, when I  access it remotely via VNC, when I close the VNC window on the viewer, the remote
computer logs off.  It happens everytime.   Is there a setting causing the log off?  I need it to stop.
>
>
>
> Jason
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> ___________________________________________________________
> 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
>
>

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
___________________________________________________________
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

Gerard | 2 May 13:51 2008
X-Face
Face
Picon

Error Message Then Lose Connection

I have TightVNC Version 1.3.9 installed on both a WinXP Pro machine and
a FreeBSD-6.3 computer. From time to time, much more often than I would
like, a warning message pops up on the WinXP machine and the connection
is terminated. About the only thing I can get from the log file on the
FreeBSD machine is this:

02/05/08 07:28:11 rfbSendUpdateBuf: write: Broken pipe
02/05/08 07:28:11 Client 192.168.1.104 gone

The error message on the WinXP machine:

	Unhandled SetColormap message type received

I have attached a screen capture of the error message.

What, if anything, can I do to alleviate this problem?

-- 
Gerard
gerard <at> seibercom.net

	   THE DAILY PLANET

	SUPERMAN SAVES DESSERT!
	Plans to "Eat it later"
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
___________________________________________________________
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
Lluis PARCET | 3 May 22:55 2008
Picon

VNCSERVER FAILS WHEN LAUNCHED VIA XINETD (GENTOO LINUX)

Hello:

I have problems launching vncserver via xinetd.


I use Gentoo Linux with kernel 2.6.24-gentoo-r4, tightvnc-1.3.9-r1, xinetd-2.3.14, xfce4-4.4.2 and xdm-1.1.6.


When launch the server via vncserver :1, everything works ok and I am able to connect from another computer in my home network.

It fails when trying the "automatic vncserver response" via xinetd. I launch

Code:

Vncviewer 192.168.1.34:62

and the login manager screen appears, but after typing the username and password the window is closed and the session ends.

This is my vncserver log:

Code:

24/04/08 19:07:35 Xvnc version TightVNC-1.3.9
24/04/08 19:07:35 Copyright (C) 2000-2007 TightVNC Group
24/04/08 19:07:35 Copyright (C) 1999 AT&T Laboratories Cambridge
24/04/08 19:07:35 All Rights Reserved.
24/04/08 19:07:35 See http://www.tightvnc.com/ for information on TightVNC
24/04/08 19:07:35 Desktop name 'x11' (PENTIUM3:1)
24/04/08 19:07:35 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
Font directory '/usr/X11R6/lib/X11/fonts/Speedo/' not found - ignoring
24/04/08 19:07:36 Using protocol version 3.8
24/04/08 19:07:36 Pixel format for client 192.168.1.37:
24/04/08 19:07:36   8 bpp, depth 6
24/04/08 19:07:36   true colour: max r 3 g 3 b 3, shift r 4 g 2 b 0
24/04/08 19:07:36 Enabling full-color cursor updates for client 192.168.1.37
24/04/08 19:07:36 rfbProcessClientNormalMessage: ignoring unknown encoding -223
24/04/08 19:07:36 rfbProcessClientNormalMessage: ignoring unknown encoding 16
24/04/08 19:07:36 Using hextile encoding for client 192.168.1.37
24/04/08 19:07:37 Pixel format for client 192.168.1.37:
24/04/08 19:07:37   16 bpp, depth 16, little endian
24/04/08 19:07:37   true colour: max r 31 g 63 b 31, shift r 11 g 5 b 0
24/04/08 19:07:37   no translation needed
AUDIT: Thu Apr 24 19:07:45 2008: 4806 Xvnc: client 2 rejected from IP 127.0.0.1 port 56666
  Auth name: MIT-MAGIC-COOKIE-1 ID: -1
AUDIT: Thu Apr 24 19:07:46 2008: 4806 Xvnc: client 2 rejected from IP 127.0.0.1 port 56667
  Auth name: MIT-MAGIC-COOKIE-1 ID: -1
AUDIT: Thu Apr 24 19:07:46 2008: 4806 Xvnc: client 2 rejected from IP 127.0.0.1 port 56668
  Auth name: MIT-MAGIC-COOKIE-1 ID: -1
AUDIT: Thu Apr 24 19:07:46 2008: 4806 Xvnc: client 2 rejected from IP 127.0.0.1 port 56669
  Auth name: MIT-MAGIC-COOKIE-1 ID: -1
AUDIT: Thu Apr 24 19:07:47 2008: 4806 Xvnc: client 2 rejected from IP 127.0.0.1 port 56670
  Auth name: MIT-MAGIC-COOKIE-1 ID: -1




Somebody knows what can be the problem?

My /etc/xinetd.conf:

Code:

#
# This is the master xinetd configuration file. Settings in the
# default section will be inherited by all service configurations
# unless explicitly overridden in the service configuration. See
# xinetd.conf in the man pages for a more detailed explanation of
# these attributes.

defaults
{
# The next two items are intended to be a quick access place to
# temporarily enable or disable services.
#
#   enabled      =
#   disabled   =

# Define general logging characteristics.
   log_type   = SYSLOG daemon info
   log_on_failure   = HOST
   log_on_success   = PID HOST DURATION EXIT

# Define access restriction defaults
#
#   no_access   =
#   only_from   = localhost
#   max_load   = 0
   cps      = 50 10
   instances   = 50
   per_source   = 10

# Address and networking defaults
#
#   bind      =
#   mdns      = yes
   v6only      = no

# setup environmental attributes
#
#   passenv      =
   groups      = yes
   umask      = 002

# Generally, banners are not used. This sets up their global defaults
#
#   banner      =
#   banner_fail   =
#   banner_success   =
}

includedir /etc/xinetd.d




My /etc/services:

Code:

#
# VNC Servers
#
vnc-640x480x8 5950/tcp
vnc-800x600x8 5951/tcp
vnc-1024x768x8 5952/tcp

vnc-640x480x16 5960/tcp
vnc-800x600x16 5961/tcp
vnc-1024x768x16 5962/tcp

vnc-640x480x24 5970/tcp
vnc-800x600x24 5971/tcp
vnc-1024x768x24 5972/tcp

vnc-640x480x32 5980/tcp
vnc-800x600x32 5981/tcp
vnc-1024x768x32 5982/tcp




My /etc/xinetd.d/xvncserver:

Code:

service vnc-640x480x8
{
          protocol = tcp
          socket_type = stream
          wait = no
          user = nobody
          server = /usr/bin/Xvnc
          server_args = :50 -inetd -query localhost -once -geometry 640x480 -depth 8
}
service vnc-800x600x8
{
          protocol = tcp
          socket_type = stream
          wait = no
          user = nobody
          server = /usr/bin/Xvnc
          server_args = :51 -inetd -query localhost -once -geometry 800x600 -depth 8
}
service vnc-1024x768x8
{
          protocol = tcp
          socket_type = stream
          wait = no
          user = nobody
          server = /usr/bin/Xvnc
          server_args = :52 -inetd -query localhost -once -geometry 1024x768 -depth 8
}
service vnc-640x480x16
{
          protocol = tcp
          socket_type = stream
          wait = no
          user = nobody
          server = /usr/bin/Xvnc
          server_args = :60 -inetd -query localhost -once -geometry 640x480 -depth 16
}
service vnc-800x600x16
{
          protocol = tcp
          socket_type = stream
          wait = no
          user = nobody
          server = /usr/bin/Xvnc
          server_args = :61 -inetd -query localhost -once -geometry 800x600 -depth 16
}
service vnc-1024x768x16
{
          protocol = tcp
          socket_type = stream
          wait = no
          user = nobody
          server = /usr/bin/Xvnc
          server_args = :62 -inetd -query localhost -once -geometry 1024x768 -depth 16
}
service vnc-640x480x24
{
          protocol = tcp
          socket_type = stream
          wait = no
          user = nobody
          server = /usr/bin/Xvnc
          server_args = :70 -inetd -query localhost -once -geometry 640x480 -depth 24
}
service vnc-800x600x24
{
          protocol = tcp
          socket_type = stream
          wait = no
          user = nobody
          server = /usr/bin/Xvnc
          server_args = :71 -inetd -query localhost -once -geometry 800x600 -depth 24
}
service vnc-1024x768x24
{
          protocol = tcp
          socket_type = stream
          wait = no
          user = nobody
          server = /usr/bin/Xvnc
          server_args = :72 -inetd -query localhost -once -geometry 1024x768 -depth 24
}
service vnc-640x480x32
{
          protocol = tcp
          socket_type = stream
          wait = no
          user = nobody
          server = /usr/bin/Xvnc
          server_args = :80 -inetd -query localhost -once -geometry 640x480 -depth 32
}
service vnc-800x600x32
{
          protocol = tcp
          socket_type = stream
          wait = no
          user = nobody
          server = /usr/bin/Xvnc
          server_args = :81 -inetd -query localhost -once -geometry 800x600 -depth 32
}
service vnc-1024x768x32
{
          protocol = tcp
          socket_type = stream
          wait = no
          user = nobody
          server = /usr/bin/Xvnc
          server_args = :82 -inetd -query localhost -once -geometry 1024x768 -depth 32
}


Thank you in advance.

Regards.

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
___________________________________________________________
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
Tomasz Chmielewski | 6 May 12:31 2008

locking settings doesn't work in 1.3.9?

Previously I was running TightVNC 1.2.7 on Windows clients, and I could 
lock settings so that normal users could not see nor manipulate them.

However, with 1.3.9 it doesn't seem to work - setting "AllowProperties", 
"AllowShutdown" to 0 in the registry doesn't seem to have any effect, as 
normal users can see and change the properties and can shutdown the VNC 
server. I rebooted the machine after changing these settings to make 
sure they're applied - but apparently, they are not.

Am I missing anything here?

--

-- 
Tomasz Chmielewski
http://wpkg.org

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
___________________________________________________________
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

Constantin Kaplinsky | 11 May 12:09 2008

Re: TightProjector Question

Hello Hugh,

>>>>> Hugh Rowley wrote:

> This seemed to be the only list to use for a TightProjector question,
> hope it is okay...
> 
> Has anyone tried running TightProjector on Windows Vista (Business or
> Ultimate)?

Yes, TightProjector runs fine on Vista. To make sure, give it a try:

  http://www.tightvnc.com/projector/

--

-- 
With Best Wishes,
Constantin

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
___________________________________________________________
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

Per Gunnar Hansø | 13 May 12:29 2008
Picon

Re: port forwarding

Lathe Craft wrote:
> Is there a way to get around port forwarding with tightvnc? if so 
> could someone please explain it to me or help me out with this?
>  
> v/r
> Lathe Craft II
If you make VPN connections between the VNC Viewer and the VNC server
machine or network, that would take care of safety - both against
breakins and eavesdropping. Hamachi is a simple solution if you have no
clue.

Apart from that you have proxying, but then, that's not simple if you
want to make it secure.

Good luck.

Best regards,
Per Gunnar Hansø

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
___________________________________________________________
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

Andrew Thompson | 16 May 17:58 2008

Problem connecting to remote maching through Browser

I have recently installed tightvnc on my home file server, and can connect to it fine using the VNC viewer.
 
The problem I am having is when I try to connect through a web browser, I am entering my server address as normal, an all I am getting is an empty box with a cross in the top left corner.
 
All the port forwarding is set up correctly and firwalls configured to allow connections on required ports.
 
Any help to get this working would be appreciated.
 
Andy
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
___________________________________________________________
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

Gmane