HELP
-----Mensaje original-----
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
nombre de [EMAIL PROTECTED]
Enviado el: Thursday, March 09, 2006 1:00 PM
Para: [email protected]
Asunto: VNC-List digest, Vol 1 #1698 - 19 msgs
Send VNC-List mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://www.realvnc.com/mailman/listinfo/vnc-list
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of VNC-List digest..."
Today's Topics:
1. Recording VNC Session (Cea)
2. RE: How to terminate VNC sessions immediately at network
connection drop (Kolev, Nik)
3. VNCviewer Applet opens new window (Charles Levasseur)
4. Re: How to terminate VNC sessions immediately at network
connection drop (B. Scott Smith)
5. RE: How to terminate VNC sessions immediately at network
connection drop (Kolev, Nik)
6. RE: VNCviewer Applet opens new window (James Weatherall)
7. RE: How to terminate VNC sessions immediately at network
connection drop (James Weatherall)
8. Re: How to terminate VNC sessions immediately at network
connection drop (B. Scott Smith)
9. Re: First timer - Common VNC Error 10066 (Scott C. Best)
10. Re: How to terminate VNC sessions immediately at network
connection drop (Adrian Phillips)
11. RE: How to terminate VNC sessions immediately at network
connection drop (James Weatherall)
12. Connecting via dial up connection (Dr. Jiri Dohnalek)
--__--__--
Message: 1
From: "Cea" <[EMAIL PROTECTED]>
To: <[email protected]>
Subject: Recording VNC Session
Date: Wed, 8 Mar 2006 15:01:43 +0100
Hallo,
I'm looking for a tool which allows to record VNC session
to file. It should work in background as a simple passive VNC client
(server will be configured as view only) without an interaction.
A tool will be used instead of camera, which independently records and
registers actual state of some 'network maps' - for evidence purposes.
Vncrec and rfbproxy don't satisfy, because they need to open an extra
display
and don't run in background.
Maybe someone help me?
Best regards.
Tom CeaL.
Poland
--__--__--
Message: 2
Subject: RE: How to terminate VNC sessions immediately at network
connection drop
Date: Wed, 8 Mar 2006 11:06:03 -0500
From: "Kolev, Nik" <[EMAIL PROTECTED]>
To: "James Weatherall" <[EMAIL PROTECTED]>, <[email protected]>
Thanks Wez,
Let me rephrase my question then. Assume the viewer and server
communicate over a low quality (and low bandwidth) network. What are the
scenarios (other than unplugging the network cable) where the client
"goes fishing" with an info/error message but the server continues
running the session until the idle timeout tells it to dispose it? And
how can one guard (terminate the session earlier than the idle timeout)
against them happening?
-nik
-----Original Message-----
From: James Weatherall [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 08, 2006 5:51 AM
To: Kolev, Nik; [email protected]
Subject: RE: How to terminate VNC sessions immediately at network
connection drop
Nik,
The only reason your viewer detects the connection drop is that your
computer has had the cable physically removed - it sees this and removes
the routing information for that network connection from the TCP stack,
then notices that there is now no way to reach your server, and so
returns the (wrong, as it happens) error code to VNC Viewer.
The server doesn't notice that the viewer computer has been physically
disconnected, because no-one tells it - the viewer can't tell it,
because it's been disconnected from the network. The only part of the
system that
*could* tell it is the switch to which the viewer computer was
connected, assuming it knows that the viewer computer does not have
other network connections. The only practical way to implement this
sort of functionality is with a regular "ping" and timeout combination,
but this still won't give you instantaneous disconnect, and may lead to
disconnects in the event of network delays, etc.
Regards,
Wez @ RealVNC Ltd.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Kolev, Nik
> Sent: 07 March 2006 21:19
> To: [email protected]
> Subject: How to terminate VNC sessions immediately at network
> connection drop
>
> Hi,
>
> I've set up a non-persistent vnc (v. 4.1.1) session through inetd (on
> Solaris and Linux) and using vncviewer (v 4.1.1.) to connect from
> Windows workstations.
>
> The vncviewer is configured to not "Offer To Automatically Reconnect".
> When I unplug the network cable of the windows workstation I expect
> and get a vncviewer info prompt saying "read: Connection reset by peer
> (10054)". What I also expect to happen is that the corresponding
> server
> (Xvnc) detects this and terminates the session running on the server
> side immediately. Unfortunately this does not happen. The session only
> gets terminated after the idle timeout (default: 3600 secs).
> Is there a
> way to enforce this to happen?
>
> Here's how I start Xvnc on Solaris through inetd:
> /usr/local/bin/Xvnc -inetd -securitytypes=none -desktop remote-user
> -depth 16 -geometry 1024x768 -nolisten named -query localhost -once
> 3>/dev/null
>
> Thanks,
> -nik
>
>
> Confidentiality Notice
> This e-mail (including any attachments) is intended only for the
> recipients named above. It may contain confidential or privileged
> information and should not be read, copied or otherwise used by any
> other person. If you are not a named recipient, please notify the
> sender of that fact and delete the e-mail from your system.
> _______________________________________________
> VNC-List mailing list
> [email protected]
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
>
Confidentiality Notice
This e-mail (including any attachments) is intended only for the recipients
named above. It may contain confidential or privileged information and
should not be read, copied or otherwise used by any other person. If you are
not a named recipient, please notify the sender of that fact and delete the
e-mail from your system.
--__--__--
Message: 3
Subject: VNCviewer Applet opens new window
Date: Wed, 8 Mar 2006 09:07:46 -0800
From: "Charles Levasseur" <[EMAIL PROTECTED]>
To: <[email protected]>
Hello
With VNC 3.3.7, I was able to open the Java VNC applet in a web page that
was
contained inside of a frame.
For example, from a link on a webpage on my left frame, I would click on
which
VNC server I wanted to connect to and the VNC viewer Java applet would
appear
in the right side frame. My link was setup like this one: <a
href='http://192.168.0.45:5845' target='right_frame'>Server 1</a>
Since I upgraded to VNC 4.0 and 4.1, this no longer works. The applet now
opens a new window.
Is there a work around for this?
Thanks
--
NEIL SQUIRE SOCIETY - http://www.neilsquire.ca <http://www.neilsquire.ca/>
We use technology, knowledge and passion to empower Canadians with physical
disabilities.
Charles Levasseur | Acting Program Coordinator / Lead Computer Instructor /
IT
Specialist
Voice 506.856.9101 | Fax 506.854.7509 | [EMAIL PROTECTED]
236 St-George Street Suite 305, Moncton, NB E1C 1W1
This message and any attachments are directed in confidence to those named,
and must not be reviewed, retained or disclosed without the consent of the
sender or the named recipient(s). If you have received it in error, please
delete it and notify us immediately.
Le prisent courriel y compris toute pihce jointe sont destinis exclusivement
aux personnes mentionnies. Il est interdit de revoir ou de conserver ce
courriel ou d'en divulguer le contenu sans le consentement de l'expiditeur
ou
des destinataires visis. Si vous avez regu le prisent courriel par erreur,
veuillez le supprimer et nous en aviser immidiatement.
--__--__--
Message: 4
Date: Wed, 08 Mar 2006 12:22:17 -0500
From: "B. Scott Smith" <[EMAIL PROTECTED]>
To: "Kolev, Nik" <[EMAIL PROTECTED]>
CC: [email protected]
Subject: Re: How to terminate VNC sessions immediately at network
connection drop
You can tweak your "ndd" settings in Solaris to a more reasonable
timeout for these types of client disconnects. Just be careful, while
setting it to a minute may seem very reasonable in this case, the ndd
setting will effect the whole system, and all it's network connections.
Kolev, Nik wrote:
> Thanks Wez,
>
> Let me rephrase my question then. Assume the viewer and server
> communicate over a low quality (and low bandwidth) network. What are the
> scenarios (other than unplugging the network cable) where the client
> "goes fishing" with an info/error message but the server continues
> running the session until the idle timeout tells it to dispose it? And
> how can one guard (terminate the session earlier than the idle timeout)
> against them happening?
>
> -nik
>
>
> -----Original Message-----
> From: James Weatherall [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 08, 2006 5:51 AM
> To: Kolev, Nik; [email protected]
> Subject: RE: How to terminate VNC sessions immediately at network
> connection drop
>
> Nik,
>
> The only reason your viewer detects the connection drop is that your
> computer has had the cable physically removed - it sees this and removes
> the routing information for that network connection from the TCP stack,
> then notices that there is now no way to reach your server, and so
> returns the (wrong, as it happens) error code to VNC Viewer.
>
> The server doesn't notice that the viewer computer has been physically
> disconnected, because no-one tells it - the viewer can't tell it,
> because it's been disconnected from the network. The only part of the
> system that
> *could* tell it is the switch to which the viewer computer was
> connected, assuming it knows that the viewer computer does not have
> other network connections. The only practical way to implement this
> sort of functionality is with a regular "ping" and timeout combination,
> but this still won't give you instantaneous disconnect, and may lead to
> disconnects in the event of network delays, etc.
>
> Regards,
>
> Wez @ RealVNC Ltd.
>
>
>
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On Behalf Of Kolev, Nik
>> Sent: 07 March 2006 21:19
>> To: [email protected]
>> Subject: How to terminate VNC sessions immediately at network
>> connection drop
>>
>> Hi,
>>
>> I've set up a non-persistent vnc (v. 4.1.1) session through inetd (on
>> Solaris and Linux) and using vncviewer (v 4.1.1.) to connect from
>> Windows workstations.
>>
>> The vncviewer is configured to not "Offer To Automatically Reconnect".
>> When I unplug the network cable of the windows workstation I expect
>> and get a vncviewer info prompt saying "read: Connection reset by peer
>>
>
>
>> (10054)". What I also expect to happen is that the corresponding
>> server
>> (Xvnc) detects this and terminates the session running on the server
>> side immediately. Unfortunately this does not happen. The session only
>>
>
>
>> gets terminated after the idle timeout (default: 3600 secs).
>> Is there a
>> way to enforce this to happen?
>>
>> Here's how I start Xvnc on Solaris through inetd:
>> /usr/local/bin/Xvnc -inetd -securitytypes=none -desktop remote-user
>> -depth 16 -geometry 1024x768 -nolisten named -query localhost -once
>> 3>/dev/null
>>
>> Thanks,
>> -nik
>>
>>
>> Confidentiality Notice
>> This e-mail (including any attachments) is intended only for the
>> recipients named above. It may contain confidential or privileged
>> information and should not be read, copied or otherwise used by any
>> other person. If you are not a named recipient, please notify the
>> sender of that fact and delete the e-mail from your system.
>> _______________________________________________
>> VNC-List mailing list
>> [email protected]
>> To remove yourself from the list visit:
>> http://www.realvnc.com/mailman/listinfo/vnc-list
>>
>>
>
>
>
> Confidentiality Notice
> This e-mail (including any attachments) is intended only for the
recipients named above. It may contain confidential or privileged
information and should not be read, copied or otherwise used by any other
person. If you are not a named recipient, please notify the sender of that
fact and delete the e-mail from your system.
> _______________________________________________
> VNC-List mailing list
> [email protected]
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
--__--__--
Message: 5
Subject: RE: How to terminate VNC sessions immediately at network
connection drop
Date: Wed, 8 Mar 2006 12:37:13 -0500
From: "Kolev, Nik" <[EMAIL PROTECTED]>
To: "B. Scott Smith" <[EMAIL PROTECTED]>
Cc: <[email protected]>
Sorry I may have confused you...
To do what you suggest I'll use the -IdleTimeout argument when starting
Xvnc -- this way I won't tweak any other connection's behaviour to match
what I expect from vnc.
The solution I'd like, however, is that Xvnc terminates as soon as the
other endpoint (the machine that runs vncviewer) goes away (as in -
network cable is unplugged). I am surprised that this does not happen,
especially if the vncviewer-Xvnc is a TCP connection.
-nik
-----Original Message-----
From: B. Scott Smith [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 08, 2006 12:22 PM
To: Kolev, Nik
Cc: [email protected]
Subject: Re: How to terminate VNC sessions immediately at network
connection drop
You can tweak your "ndd" settings in Solaris to a more reasonable
timeout for these types of client disconnects. Just be careful, while
setting it to a minute may seem very reasonable in this case, the ndd
setting will effect the whole system, and all it's network connections.
Kolev, Nik wrote:
> Thanks Wez,
>
> Let me rephrase my question then. Assume the viewer and server
> communicate over a low quality (and low bandwidth) network. What are
> the scenarios (other than unplugging the network cable) where the
> client "goes fishing" with an info/error message but the server
> continues running the session until the idle timeout tells it to
> dispose it? And how can one guard (terminate the session earlier than
> the idle timeout) against them happening?
>
> -nik
>
>
> -----Original Message-----
> From: James Weatherall [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 08, 2006 5:51 AM
> To: Kolev, Nik; [email protected]
> Subject: RE: How to terminate VNC sessions immediately at network
> connection drop
>
> Nik,
>
> The only reason your viewer detects the connection drop is that your
> computer has had the cable physically removed - it sees this and
> removes the routing information for that network connection from the
> TCP stack, then notices that there is now no way to reach your server,
> and so returns the (wrong, as it happens) error code to VNC Viewer.
>
> The server doesn't notice that the viewer computer has been physically
> disconnected, because no-one tells it - the viewer can't tell it,
> because it's been disconnected from the network. The only part of the
> system that
> *could* tell it is the switch to which the viewer computer was
> connected, assuming it knows that the viewer computer does not have
> other network connections. The only practical way to implement this
> sort of functionality is with a regular "ping" and timeout
> combination, but this still won't give you instantaneous disconnect,
> and may lead to disconnects in the event of network delays, etc.
>
> Regards,
>
> Wez @ RealVNC Ltd.
>
>
>
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On Behalf Of Kolev, Nik
>> Sent: 07 March 2006 21:19
>> To: [email protected]
>> Subject: How to terminate VNC sessions immediately at network
>> connection drop
>>
>> Hi,
>>
>> I've set up a non-persistent vnc (v. 4.1.1) session through inetd (on
>> Solaris and Linux) and using vncviewer (v 4.1.1.) to connect from
>> Windows workstations.
>>
>> The vncviewer is configured to not "Offer To Automatically
Reconnect".
>> When I unplug the network cable of the windows workstation I expect
>> and get a vncviewer info prompt saying "read: Connection reset by
>> peer
>>
>
>
>> (10054)". What I also expect to happen is that the corresponding
>> server
>> (Xvnc) detects this and terminates the session running on the server
>> side immediately. Unfortunately this does not happen. The session
>> only
>>
>
>
>> gets terminated after the idle timeout (default: 3600 secs).
>> Is there a
>> way to enforce this to happen?
>>
>> Here's how I start Xvnc on Solaris through inetd:
>> /usr/local/bin/Xvnc -inetd -securitytypes=none -desktop remote-user
>> -depth 16 -geometry 1024x768 -nolisten named -query localhost -once
>> 3>/dev/null
>>
>> Thanks,
>> -nik
>>
>>
>> Confidentiality Notice
>> This e-mail (including any attachments) is intended only for the
>> recipients named above. It may contain confidential or privileged
>> information and should not be read, copied or otherwise used by any
>> other person. If you are not a named recipient, please notify the
>> sender of that fact and delete the e-mail from your system.
>> _______________________________________________
>> VNC-List mailing list
>> [email protected]
>> To remove yourself from the list visit:
>> http://www.realvnc.com/mailman/listinfo/vnc-list
>>
>>
>
>
>
> Confidentiality Notice
> This e-mail (including any attachments) is intended only for the
recipients named above. It may contain confidential or privileged
information and should not be read, copied or otherwise used by any
other person. If you are not a named recipient, please notify the sender
of that fact and delete the e-mail from your system.
> _______________________________________________
> VNC-List mailing list
> [email protected]
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
>
>
>
>
Confidentiality Notice
This e-mail (including any attachments) is intended only for the recipients
named above. It may contain confidential or privileged information and
should not be read, copied or otherwise used by any other person. If you are
not a named recipient, please notify the sender of that fact and delete the
e-mail from your system.
--__--__--
Message: 6
From: "James Weatherall" <[EMAIL PROTECTED]>
To: "'Charles Levasseur'" <[EMAIL PROTECTED]>,
<[email protected]>
Subject: RE: VNCviewer Applet opens new window
Date: Wed, 8 Mar 2006 17:57:14 -0000
Organization: RealVNC Ltd.
Charles,
Opening VNC Viewer in a new window is the intended behaviour for the VNC 4.x
series VNC Viewer for Java.
Regards,
Wez @ RealVNC Ltd.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Charles Levasseur
> Sent: 08 March 2006 17:08
> To: [email protected]
> Subject: VNCviewer Applet opens new window
>
> Hello
>
> With VNC 3.3.7, I was able to open the Java VNC applet in a
> web page that was
> contained inside of a frame.
>
> For example, from a link on a webpage on my left frame, I
> would click on which
> VNC server I wanted to connect to and the VNC viewer Java
> applet would appear
> in the right side frame. My link was setup like this one: <a
> href='http://192.168.0.45:5845' target='right_frame'>Server 1</a>
>
> Since I upgraded to VNC 4.0 and 4.1, this no longer works.
> The applet now
> opens a new window.
>
> Is there a work around for this?
>
> Thanks
> --
> NEIL SQUIRE SOCIETY - http://www.neilsquire.ca
> <http://www.neilsquire.ca/>
> We use technology, knowledge and passion to empower Canadians
> with physical
> disabilities.
>
> Charles Levasseur | Acting Program Coordinator / Lead
> Computer Instructor / IT
> Specialist
> Voice 506.856.9101 | Fax 506.854.7509 | [EMAIL PROTECTED]
> 236 St-George Street Suite 305, Moncton, NB E1C 1W1
>
> This message and any attachments are directed in confidence
> to those named,
> and must not be reviewed, retained or disclosed without the
> consent of the
> sender or the named recipient(s). If you have received it in
> error, please
> delete it and notify us immediately.
>
> Le prisent courriel y compris toute pihce jointe sont
> destinis exclusivement
> aux personnes mentionnies. Il est interdit de revoir ou de
> conserver ce
> courriel ou d'en divulguer le contenu sans le consentement de
> l'expiditeur ou
> des destinataires visis. Si vous avez regu le prisent
> courriel par erreur,
> veuillez le supprimer et nous en aviser immidiatement.
> _______________________________________________
> VNC-List mailing list
> [email protected]
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
--__--__--
Message: 7
From: "James Weatherall" <[EMAIL PROTECTED]>
To: "'Kolev, Nik'" <[EMAIL PROTECTED]>, "'B. Scott Smith'"
<[EMAIL PROTECTED]>
Cc: <[email protected]>
Subject: RE: How to terminate VNC sessions immediately at network
connection drop
Date: Wed, 8 Mar 2006 18:20:55 -0000
Organization: RealVNC Ltd.
Nik,
> The solution I'd like, however, is that Xvnc terminates as soon as the
> other endpoint (the machine that runs vncviewer) goes away (as in -
> network cable is unplugged). I am surprised that this does not happen,
> especially if the vncviewer-Xvnc is a TCP connection.
Why are you surprised? Is there some feature of TCP that we're not aware of
that would allow it to detect that the computer running the computer was no
longer accessible?
Wez @ RealVNC Ltd.
--__--__--
Message: 8
Date: Wed, 08 Mar 2006 14:15:06 -0500
From: "B. Scott Smith" <[EMAIL PROTECTED]>
To: "'Kolev, Nik'" <[EMAIL PROTECTED]>
CC: [email protected]
Subject: Re: How to terminate VNC sessions immediately at network
connection drop
James Weatherall wrote:
> Why are you surprised? Is there some feature of TCP that we're not aware
of
> that would allow it to detect that the computer running the computer was
no
> longer accessible?
>
> Wez @ RealVNC Ltd.
>
>
Like Wez is saying, this is not VNC specific. If you had a telnet
session going, and simply disconnected the cable, the telnet server
would be totally unaware of a disconnected client for upwards of 2 hours
(the Solaris default). When you remove the cable, there is no way for
the remote network to tell your server he is gone, and the NDD settings
on Solaris instruct the TCP layer to hang around for quite a while in
case the client comes back, and will therefore attempt to "recover" the
TCP session.
I typically tweak my NDD settings in Solaris to set a keepalive down in
the 1 minute range.
--__--__--
Message: 9
Date: Wed, 8 Mar 2006 19:21:12 +0000 (GMT)
From: "Scott C. Best" <[EMAIL PROTECTED]>
To: [email protected]
cc: [EMAIL PROTECTED]
Subject: Re: First timer - Common VNC Error 10066
Eddie:
Heya. Have a look here for some advice in getting VNC to
run across the Internet:
http://faq.gotomyvnc.com/fom-serve/cache/63.html
The 10061 error I think you're seeing is explained here:
http://faq.gotomyvnc.com/fom-serve/cache/66.html
cheers,
Scott
> Hi all,
>
> Please be patient with me. I have done as much research as I could and
from what I understand, there probably is a simple fix here that I am not
seeing and or understanding how to fix.
>
> What I am trying to accomplish: Tech my parents/grandparents computer with
their common problems, keep them up to date and clean their systems up.
>
> I have the common set up:
>
> My computer XP Media Center. DSL with an Infinilink router. This will
be the only viewer.
>
> My parents computer in another city: XP using Comcast Cable Modem
Motorola model not listed on the router port forwarding section on the
RealVNC site. Running Zone Alarm firewall and I have VNC authorized across
the board.
>
> I have not set up any exceptions as I am not running the Window's
firewall on their systems.
>
> I clicked on the test page for the IP address from the REALVNC page and
it confirms the email address and says there is no connection to port 5900.
This happens to both systems when I do the test.
>
> I sort of understand ports, but not how to open one if that is my
problem. I get the same error trying to connect to both systems.
>
> Any help would be greatly appreciated.
--__--__--
Message: 10
To: [email protected]
Subject: Re: How to terminate VNC sessions immediately at network
connection drop
From: Adrian Phillips <[EMAIL PROTECTED]>
Date: Thu, 09 Mar 2006 10:12:13 +0100
>>>>> "James" == James Weatherall <[EMAIL PROTECTED]> writes:
James> Nik,
>> The solution I'd like, however, is that Xvnc terminates as soon
>> as the other endpoint (the machine that runs vncviewer) goes
>> away (as in - network cable is unplugged). I am surprised that
>> this does not happen, especially if the vncviewer-Xvnc is a TCP
>> connection.
James> Why are you surprised? Is there some feature of TCP that
James> we're not aware of that would allow it to detect that the
James> computer running the computer was no longer accessible?
Well, ssh implements timeouts (ServerAliveInterval amongst others)
above the normal TCP mechanism so it is technically feasible to do
it. The standard TCP timeouts (at least a few years ago the default
timeout was 2 hours) are way too long for many applications.
Sincerely,
Adrian
--
Who really wrote the works of William Shakespeare ?
http://www.pbs.org/wgbh/pages/frontline/shakespeare/
--__--__--
Message: 11
From: "James Weatherall" <[EMAIL PROTECTED]>
To: "'Adrian Phillips'" <[EMAIL PROTECTED]>, <[email protected]>
Subject: RE: How to terminate VNC sessions immediately at network
connection drop
Date: Thu, 9 Mar 2006 10:36:21 -0000
Organization: RealVNC Ltd.
Adrian,
That's not what Nik was describing - I'd already covered the use of a
keep-alive & timeout mechanism in an earlier mail. :)
TCP connections won't shutdown in the absence of traffic at all, on most
systems, unless the program is actively trying to send data, in which case
there's normally a timeout of about four minutes or thereabouts. The
two-hour timeout you refer to sounds like an inactivity-timer (equivalent to
VNC Server's IdleTimeout) built-in either to the software you're using or
possibly even to the system.
Regards,
Wez @ RealVNC Ltd.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Phillips
> Sent: 09 March 2006 09:12
> To: [email protected]
> Subject: Re: How to terminate VNC sessions immediately at
> network connection drop
>
> >>>>> "James" == James Weatherall <[EMAIL PROTECTED]> writes:
>
> James> Nik,
> >> The solution I'd like, however, is that Xvnc terminates as soon
> >> as the other endpoint (the machine that runs vncviewer) goes
> >> away (as in - network cable is unplugged). I am surprised that
> >> this does not happen, especially if the vncviewer-Xvnc is a TCP
> >> connection.
>
> James> Why are you surprised? Is there some feature of TCP that
> James> we're not aware of that would allow it to detect that the
> James> computer running the computer was no longer accessible?
>
> Well, ssh implements timeouts (ServerAliveInterval amongst others)
> above the normal TCP mechanism so it is technically feasible to do
> it. The standard TCP timeouts (at least a few years ago the default
> timeout was 2 hours) are way too long for many applications.
>
> Sincerely,
>
> Adrian
>
> --
> Who really wrote the works of William Shakespeare ?
> http://www.pbs.org/wgbh/pages/frontline/shakespeare/
> _______________________________________________
> VNC-List mailing list
> [email protected]
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
--__--__--
Message: 12
From: "Dr. Jiri Dohnalek" <[EMAIL PROTECTED]>
To: <[email protected]>
Subject: Connecting via dial up connection
Date: Thu, 9 Mar 2006 21:36:15 +1000
I have a pc that connects to the internet via dial up or when I am at
home via a broadband connection via a wireless network. I can connect
from my pc to my home server via my wireless network and use vnc but
when away from home I can't connect to my server using my dial up
connection. I can't even establish 'ping'. What am I doing wrong. Can
some one please tell me how I use vnc via dial up from my pc to my home
server which is on broadband.
Thankyou
Email: [EMAIL PROTECTED]
--__--__--
_______________________________________________
VNC-List mailing list
[email protected]
http://www.realvnc.com/mailman/listinfo/vnc-list
End of VNC-List Digest
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
