Main list for questions, suggestions, bug reports etc about Tight VNC

Brendan Ratter | 2 Mar 2011 08:38

SSH Connection Issue: No configured security type

Hi All,

I have set up TightVNC Server on a Win7 64-bit platform. I can connect with no problems using TightVNC viewer through port 5900 directly.
I have also set up an SSH server on the same computer, which is working through PuTTY. I have also set up a tunnel in PuTTY to localhost:5900

When I try to connect with TightVNC Viewer to the server through the SSH (using localhost:0) as the server, I get the following error message: "No configured security type is supported by 3.3 viewer", and the connection fails

I have not been able to find a solution to this, but it looks like I am missing something fairly straightforward, so any help is appreciated.

Regards,
Brendan

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev

___________________________________________________________
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

headers

John Serink | 2 Mar 2011 14:52

Re: SSH Connection Issue: No configured security type

Hi brendan:

I assume you are using freesshd but even if you aren't the setup is the same.

You MUST instruct the ssh server to:
1. Enable tunneling,
2. Enable tunneling to local host.

You must also tell tvnc to accept connections from localhost since this is where the tunnel will come from, assuming the ssh server is also on the tvnc server.

Assuming you ssh/tvnc computer is 192.168.1.3, you need to tell putty that it must creat a tunnel from 192.168.1.3:5900 to say localhost:12000. Once you ssh is up, doing a netstat -a -p tcp -n -o should show you a service waiting for connection on 127.0.0.1:12000. Now, use the tvnc viewer and open. Session to locahost:12000.

That should work.

If you computer is behind a NAT wall with public IP 1.2.3.4, you need to put a PAT entry in from say 1.2.3.4:10022 to 192.168.1.3:22. Now, in putty create a new session to ssh to 1.2.3.4:10022 and also tell putting to open up a tunnel between 192.168.1.3:5900 to localhost:12000. You connect as above.

You might find that you NAT wall router support ssh tunneling on its own. If its unix based it should. Cisco IOS does not but many other routers do. You can the ssh tunnel via thius nat router to you windows box.

Give that a go and tell us how you get on.

Cheers,
John

From: Brendan Ratter
To: vnc-tight-list <at> lists.sourceforge.net
Sent: Wed Mar 02 20:38:10 2011
Subject: SSH Connection Issue: No configured security type
Hi All,

I have set up TightVNC Server on a Win7 64-bit platform. I can connect with no problems using TightVNC viewer through port 5900 directly.
I have also set up an SSH server on the same computer, which is working through PuTTY. I have also set up a tunnel in PuTTY to localhost:5900

When I try to connect with TightVNC Viewer to the server through the SSH (using localhost:0) as the server, I get the following error message: "No configured security type is supported by 3.3 viewer", and the connection fails

I have not been able to find a solution to this, but it looks like I am missing something fairly straightforward, so any help is appreciated.

Regards,
Brendan

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev

___________________________________________________________
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

headers

Brendan Ratter | 3 Mar 2011 15:11

Re: SSH Connection Issue: No configured security type

Hi John,

Thanks for your reply! Can I please clarify a few items:

I will assume my ssh/vnc server is at 192.168.1.3 and my client is at 192.168.1.6

1. I believe that my router firewall settings are correct - I have forward port 22 to 192.168.1.3 in the router and can successfully connect SSH, giving me a terminal window into 192.168.1.3. Does this sound right?

2. I have checked the 'allow loopback connections' box in tvnc GUI - I assume this is what you mean by telling tnv to acept connections from localhost?

3. I installed COPSSH out of the box and did not make any changes to the default settings other than adding a user. I'm not 100% sure what you mean by instructing the SSH server to enable tunneling. do I have to do something with sshd? I assumed from various articles I have read that this was all done in the putty settings, but am not really sure.

4. In the putty GUI on 192.168.1.6 I have set up a host at 192.168.1.3:22 and for this account added a tunnel with source port of 5900 and a destination of localhost:5900. On connecting with these settings, I am getting the "No configured security type is supported by 3.3 viewer" error

5. Doing netstat -a -p tcp -n -o (in the putty console SSH'd to 192.168.1.3) does not show a 127.0.0.1:5900, but does show 0.0.0.0:5900 as listening. Does this tell you anything, or would you need more detailed info?

your help is much appreciated.

Cheers,
Brendan

One of the 'how tos' that I was following is at http://members.shaw.ca/nicholas.fong/vnc/

On 3 March 2011 00:52, John Serink <John_Serink <at> trimble.com> wrote:

Hi brendan:

I assume you are using freesshd but even if you aren't the setup is the same.

You MUST instruct the ssh server to:
1. Enable tunneling,
2. Enable tunneling to local host.

You must also tell tvnc to accept connections from localhost since this is where the tunnel will come from, assuming the ssh server is also on the tvnc server.

Assuming you ssh/tvnc computer is 192.168.1.3, you need to tell putty that it must creat a tunnel from 192.168.1.3:5900 to say localhost:12000. Once you ssh is up, doing a netstat -a -p tcp -n -o should show you a service waiting for connection on 127.0.0.1:12000. Now, use the tvnc viewer and open. Session to locahost:12000.

That should work.

If you computer is behind a NAT wall with public IP 1.2.3.4, you need to put a PAT entry in from say 1.2.3.4:10022 to 192.168.1.3:22. Now, in putty create a new session to ssh to 1.2.3.4:10022 and also tell putting to open up a tunnel between 192.168.1.3:5900 to localhost:12000. You connect as above.

You might find that you NAT wall router support ssh tunneling on its own. If its unix based it should. Cisco IOS does not but many other routers do. You can the ssh tunnel via thius nat router to you windows box.

Give that a go and tell us how you get on.

Cheers,
John

From: Brendan Ratter
To: vnc-tight-list <at> lists.sourceforge.net
Sent: Wed Mar 02 20:38:10 2011
Subject: SSH Connection Issue: No configured security type

Hi All,

I have set up TightVNC Server on a Win7 64-bit platform. I can connect with no problems using TightVNC viewer through port 5900 directly.
I have also set up an SSH server on the same computer, which is working through PuTTY. I have also set up a tunnel in PuTTY to localhost:5900

When I try to connect with TightVNC Viewer to the server through the SSH (using localhost:0) as the server, I get the following error message: "No configured security type is supported by 3.3 viewer", and the connection fails

I have not been able to find a solution to this, but it looks like I am missing something fairly straightforward, so any help is appreciated.

Regards,
Brendan

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev

___________________________________________________________
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

headers

John Serink | 4 Mar 2011 06:06

RE: SSH Connection Issue: No configured security type

Hi Brendan:

Comments below:

Hi John,

Thanks for your reply! Can I please clarify a few items:

I will assume my ssh/vnc server is at 192.168.1.3 and my client is at 192.168.1.6

1. I believe that my router firewall settings are correct - I have forward port 22 to 192.168.1.3 in the router and can successfully connect SSH, giving me a terminal window into 192.168.1.3. Does this sound right?
[John Serink] Yup, working.

2. I have checked the 'allow loopback connections' box in tvnc GUI - I assume this is what you mean by telling tnv to acept connections from localhost?
[John Serink] Yup.

3. I installed COPSSH out of the box and did not make any changes to the default settings other than adding a user. I'm not 100% sure what you mean by instructing the SSH server to enable tunneling. do I have to do something with sshd? I assumed from various articles I have read that this was all done in the putty settings, but am not really sure.
[John Serink] No. You have to ensure that the sshd server supports tunneling and allows tunnling to localhost.

4. In the putty GUI on 192.168.1.6 I have set up a host at 192.168.1.3:22 and for this account added a tunnel with source port of 5900 and a destination of localhost:5900. On connecting with these settings, I am getting the "No configured security type is supported by 3.3 viewer" error
[John Serink] Yah, this is slitly wrong. localhost, in so far as putty is concerned, is the computer you are on. If you say destination localhost:5900 that mean YOUR computer, not the destination. Destination must be 192.168.1.3:5900, the same computer you ssh'd to, even if its behind a NAT wall. This will get mapped to 5900 localhost but putty leaves that out as its obvious, it only asks you for the port.

5. Doing netstat -a -p tcp -n -o (in the putty console SSH'd to 192.168.1.3) does not show a 127.0.0.1:5900, but does show 0.0.0.0:5900 as listening. Does this tell you anything, or would you need more detailed info?
[John Serink] 0.0.0.0:5900 means listening on all interfaces. That is not quite right but if you fix the above, you should be ok.

your help is much appreciated.

Cheers,
Brendan

One of the 'how tos' that I was following is at http://members.shaw.ca/nicholas.fong/vnc/

On 3 March 2011 00:52, John Serink <John_Serink <at> trimble.com> wrote:

Hi brendan:

I assume you are using freesshd but even if you aren't the setup is the same.

You MUST instruct the ssh server to:
1. Enable tunneling,
2. Enable tunneling to local host.

You must also tell tvnc to accept connections from localhost since this is where the tunnel will come from, assuming the ssh server is also on the tvnc server.

Assuming you ssh/tvnc computer is 192.168.1.3, you need to tell putty that it must creat a tunnel from 192.168.1.3:5900 to say localhost:12000. Once you ssh is up, doing a netstat -a -p tcp -n -o should show you a service waiting for connection on 127.0.0.1:12000. Now, use the tvnc viewer and open. Session to locahost:12000.

That should work.

If you computer is behind a NAT wall with public IP 1.2.3.4, you need to put a PAT entry in from say 1.2.3.4:10022 to 192.168.1.3:22. Now, in putty create a new session to ssh to 1.2.3.4:10022 and also tell putting to open up a tunnel between 192.168.1.3:5900 to localhost:12000. You connect as above.

You might find that you NAT wall router support ssh tunneling on its own. If its unix based it should. Cisco IOS does not but many other routers do. You can the ssh tunnel via thius nat router to you windows box.

Give that a go and tell us how you get on.

Cheers,
John

From: Brendan Ratter
To: vnc-tight-list <at> lists.sourceforge.net
Sent: Wed Mar 02 20:38:10 2011
Subject: SSH Connection Issue: No configured security type

Hi All,

I have set up TightVNC Server on a Win7 64-bit platform. I can connect with no problems using TightVNC viewer through port 5900 directly.
I have also set up an SSH server on the same computer, which is working through PuTTY. I have also set up a tunnel in PuTTY to localhost:5900

When I try to connect with TightVNC Viewer to the server through the SSH (using localhost:0) as the server, I get the following error message: "No configured security type is supported by 3.3 viewer", and the connection fails

I have not been able to find a solution to this, but it looks like I am missing something fairly straightforward, so any help is appreciated.

Regards,
Brendan

------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d

___________________________________________________________
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

headers

Brendan Ratter | 4 Mar 2011 08:50

Re: SSH Connection Issue: No configured security type

John,

Thanks for your continued assistance. I now have everything working.

The ssh server was configured correctly - the copssh frontend configures tunneling when setting up a user (but I believe that the openssh default is for tunneling yes anyway? But you have now taught me where to look for config issues!

The issue turned out to be that my work computer (that I was using for testing) was already listening on 5900 (I overlooked that we all have vnc servers on our work machines), so locahost:5900 was not going through the SSH. I have now tunneled a non-standard port, and it is working fine. I was obviously doing sometihng wrong when attempting your original instructions that used a non-standard port.

Thanks once again for the help, it is much appreciated.

Kind Regards,
Brendan

On 4 March 2011 16:06, John Serink <John_Serink <at> trimble.com> wrote:

Hi Brendan:

Comments below:

Hi John,

Thanks for your reply! Can I please clarify a few items:

I will assume my ssh/vnc server is at 192.168.1.3 and my client is at 192.168.1.6

1. I believe that my router firewall settings are correct - I have forward port 22 to 192.168.1.3 in the router and can successfully connect SSH, giving me a terminal window into 192.168.1.3. Does this sound right?

[John Serink] Yup, working.

2. I have checked the 'allow loopback connections' box in tvnc GUI - I assume this is what you mean by telling tnv to acept connections from localhost?

[John Serink] Yup.

3. I installed COPSSH out of the box and did not make any changes to the default settings other than adding a user. I'm not 100% sure what you mean by instructing the SSH server to enable tunneling. do I have to do something with sshd? I assumed from various articles I have read that this was all done in the putty settings, but am not really sure.

[John Serink] No. You have to ensure that the sshd server supports tunneling and allows tunnling to localhost.

4. In the putty GUI on 192.168.1.6 I have set up a host at 192.168.1.3:22 and for this account added a tunnel with source port of 5900 and a destination of localhost:5900. On connecting with these settings, I am getting the "No configured security type is supported by 3.3 viewer" error

[John Serink] Yah, this is slitly wrong. localhost, in so far as putty is concerned, is the computer you are on. If you say destination localhost:5900 that mean YOUR computer, not the destination. Destination must be 192.168.1.3:5900, the same computer you ssh'd to, even if its behind a NAT wall. This will get mapped to 5900 localhost but putty leaves that out as its obvious, it only asks you for the port.

5. Doing netstat -a -p tcp -n -o (in the putty console SSH'd to 192.168.1.3) does not show a 127.0.0.1:5900, but does show 0.0.0.0:5900 as listening. Does this tell you anything, or would you need more detailed info?

[John Serink] 0.0.0.0:5900 means listening on all interfaces. That is not quite right but if you fix the above, you should be ok.

your help is much appreciated.

Cheers,
Brendan

One of the 'how tos' that I was following is at http://members.shaw.ca/nicholas.fong/vnc/

On 3 March 2011 00:52, John Serink <John_Serink <at> trimble.com> wrote:

Hi brendan:

I assume you are using freesshd but even if you aren't the setup is the same.

You MUST instruct the ssh server to:
1. Enable tunneling,
2. Enable tunneling to local host.

You must also tell tvnc to accept connections from localhost since this is where the tunnel will come from, assuming the ssh server is also on the tvnc server.

Assuming you ssh/tvnc computer is 192.168.1.3, you need to tell putty that it must creat a tunnel from 192.168.1.3:5900 to say localhost:12000. Once you ssh is up, doing a netstat -a -p tcp -n -o should show you a service waiting for connection on 127.0.0.1:12000. Now, use the tvnc viewer and open. Session to locahost:12000.

That should work.

If you computer is behind a NAT wall with public IP 1.2.3.4, you need to put a PAT entry in from say 1.2.3.4:10022 to 192.168.1.3:22. Now, in putty create a new session to ssh to 1.2.3.4:10022 and also tell putting to open up a tunnel between 192.168.1.3:5900 to localhost:12000. You connect as above.

You might find that you NAT wall router support ssh tunneling on its own. If its unix based it should. Cisco IOS does not but many other routers do. You can the ssh tunnel via thius nat router to you windows box.

Give that a go and tell us how you get on.

Cheers,
John

From: Brendan Ratter
To: vnc-tight-list <at> lists.sourceforge.net
Sent: Wed Mar 02 20:38:10 2011
Subject: SSH Connection Issue: No configured security type

Hi All,

I have set up TightVNC Server on a Win7 64-bit platform. I can connect with no problems using TightVNC viewer through port 5900 directly.
I have also set up an SSH server on the same computer, which is working through PuTTY. I have also set up a tunnel in PuTTY to localhost:5900

When I try to connect with TightVNC Viewer to the server through the SSH (using localhost:0) as the server, I get the following error message: "No configured security type is supported by 3.3 viewer", and the connection fails

I have not been able to find a solution to this, but it looks like I am missing something fairly straightforward, so any help is appreciated.

Regards,
Brendan

------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d

___________________________________________________________
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

headers

John Serink | 4 Mar 2011 09:03

RE: SSH Connection Issue: No configured security type

Hi Brendon:

you could also tell putty to have you local machine to tunnel thetunneledIP:5900 to say 13000, then you TVNC to localhost::13000 and that will work as well.

Glad you got it working.

Cheers,

John

----Original Message-----
From: Brendan Ratter [mailto:brendan.ratter <at> gmail.com]
Sent: Friday, March 04, 2011 3:50 PM
To: John Serink
Cc: vnc-tight-list <at> lists.sourceforge.net
Subject: Re: SSH Connection Issue: No configured security type

John,

Thanks for your continued assistance. I now have everything working.

The ssh server was configured correctly - the copssh frontend configures tunneling when setting up a user (but I believe that the openssh default is for tunneling yes anyway? But you have now taught me where to look for config issues!

The issue turned out to be that my work computer (that I was using for testing) was already listening on 5900 (I overlooked that we all have vnc servers on our work machines), so locahost:5900 was not going through the SSH. I have now tunneled a non-standard port, and it is working fine. I was obviously doing sometihng wrong when attempting your original instructions that used a non-standard port.

Thanks once again for the help, it is much appreciated.

Kind Regards,
Brendan

On 4 March 2011 16:06, John Serink <John_Serink <at> trimble.com> wrote:

Hi Brendan:

Comments below:

Hi John,

Thanks for your reply! Can I please clarify a few items:

I will assume my ssh/vnc server is at 192.168.1.3 and my client is at 192.168.1.6

1. I believe that my router firewall settings are correct - I have forward port 22 to 192.168.1.3 in the router and can successfully connect SSH, giving me a terminal window into 192.168.1.3. Does this sound right?

[John Serink] Yup, working.

2. I have checked the 'allow loopback connections' box in tvnc GUI - I assume this is what you mean by telling tnv to acept connections from localhost?

[John Serink] Yup.

3. I installed COPSSH out of the box and did not make any changes to the default settings other than adding a user. I'm not 100% sure what you mean by instructing the SSH server to enable tunneling. do I have to do something with sshd? I assumed from various articles I have read that this was all done in the putty settings, but am not really sure.

[John Serink] No. You have to ensure that the sshd server supports tunneling and allows tunnling to localhost.

4. In the putty GUI on 192.168.1.6 I have set up a host at 192.168.1.3:22 and for this account added a tunnel with source port of 5900 and a destination of localhost:5900. On connecting with these settings, I am getting the "No configured security type is supported by 3.3 viewer" error

[John Serink] Yah, this is slitly wrong. localhost, in so far as putty is concerned, is the computer you are on. If you say destination localhost:5900 that mean YOUR computer, not the destination. Destination must be 192.168.1.3:5900, the same computer you ssh'd to, even if its behind a NAT wall. This will get mapped to 5900 localhost but putty leaves that out as its obvious, it only asks you for the port.

5. Doing netstat -a -p tcp -n -o (in the putty console SSH'd to 192.168.1.3) does not show a 127.0.0.1:5900, but does show 0.0.0.0:5900 as listening. Does this tell you anything, or would you need more detailed info?

[John Serink] 0.0.0.0:5900 means listening on all interfaces. That is not quite right but if you fix the above, you should be ok.

your help is much appreciated.

Cheers,
Brendan

One of the 'how tos' that I was following is at http://members.shaw.ca/nicholas.fong/vnc/

On 3 March 2011 00:52, John Serink <John_Serink <at> trimble.com> wrote:

Hi brendan:

I assume you are using freesshd but even if you aren't the setup is the same.

You MUST instruct the ssh server to:
1. Enable tunneling,
2. Enable tunneling to local host.

You must also tell tvnc to accept connections from localhost since this is where the tunnel will come from, assuming the ssh server is also on the tvnc server.

Assuming you ssh/tvnc computer is 192.168.1.3, you need to tell putty that it must creat a tunnel from 192.168.1.3:5900 to say localhost:12000. Once you ssh is up, doing a netstat -a -p tcp -n -o should show you a service waiting for connection on 127.0.0.1:12000. Now, use the tvnc viewer and open. Session to locahost:12000.

That should work.

If you computer is behind a NAT wall with public IP 1.2.3.4, you need to put a PAT entry in from say 1.2.3.4:10022 to 192.168.1.3:22. Now, in putty create a new session to ssh to 1.2.3.4:10022 and also tell putting to open up a tunnel between 192.168.1.3:5900 to localhost:12000. You connect as above.

You might find that you NAT wall router support ssh tunneling on its own. If its unix based it should. Cisco IOS does not but many other routers do. You can the ssh tunnel via thius nat router to you windows box.

Give that a go and tell us how you get on.

Cheers,
John

From: Brendan Ratter
To: vnc-tight-list <at> lists.sourceforge.net
Sent: Wed Mar 02 20:38:10 2011
Subject: SSH Connection Issue: No configured security type

Hi All,

I have set up TightVNC Server on a Win7 64-bit platform. I can connect with no problems using TightVNC viewer through port 5900 directly.
I have also set up an SSH server on the same computer, which is working through PuTTY. I have also set up a tunnel in PuTTY to localhost:5900

When I try to connect with TightVNC Viewer to the server through the SSH (using localhost:0) as the server, I get the following error message: "No configured security type is supported by 3.3 viewer", and the connection fails

I have not been able to find a solution to this, but it looks like I am missing something fairly straightforward, so any help is appreciated.

Regards,
Brendan

------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d

___________________________________________________________
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

headers

ArcFi | 4 Mar 2011 11:33

Re: Mouse cursor is blinking on server

Loek Verhees <loekverhees <at> gmail.com> writes:

> When a client is connected to the server (v2 beta 4)
> the mouse cursor on the server is blinking. How can I get rid of the blinking?

Confirm this bug.
Client, server: win-xp-sp3 + tightvnc-2.0.2

------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
___________________________________________________________
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

headers

jglong3 | 8 Mar 2011 20:50

Timeout related to IP change in GATEWAY.

Hello All,,,, :) :)

Been looking for a timeout period in the TightVNC Listener/Client that might be related to

the length of time the Listner/Client stops if no contact with the TightVNC SERVER for "X" number of Minutes or Milliseconds.

We are using a GATEWAY that is set for DYNAMIC IP allocation and the ISP will change the IP from time-to-time (about 3 times daily)......

Also, we use a service/application that allows us to use a URI/URL. That service/application only updates the URI/URL with the new GATEWAY IP once every 4 minutes.

We are using other applications (VOIP---XLITE) which does not terminate that uses the same URL/URI. It may take as long as 4 minutes to regain communication but this application continues to run and contact will continue when the new IP is updated to the URI/URL database.

Is there a timeout that can be set so that TightVNC Listener/Client will continue to listen for "X" number of minutes????

THANKS for your time, help, and advice!!! :) :)

Jerry

------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d

___________________________________________________________
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

headers

Su-Ping Cheng, Sharon | 14 Mar 2011 19:22

Question about install unix tightVNC 1.3.10

Hi,

I am installing the TightVNC 1.3.10 on my imac; but it is not successful. According to the instruction, I suppose to have "X" install. I saw X11 in my utility. I think that satisfied the requirement.

Now, it is expecting JPEG and zlib in /usr/bin. Although I cant find JPEG from the ftp site the instruction indicated, I googled and download a similar one. Is it ok, am I suppose to put it in /usr/bin/ or any other places?

Next is the zlib. I have it in /usr/bin/. I think I am ready to build everything.

I return to the vnc_unixsrc folder and type: xmkmf. The machine response: command not found. What did I do wrong?

Sharon

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d

___________________________________________________________
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

headers

Michael D. Setzer II | 15 Mar 2011 13:51

Any fixes to RANDR error?

I have 3 headless Ubuntu machines with 10.04 and 10.10, and 
have seen this error for some time, but it never seemed to cause 
an issue that I could see.

Xlib:  extension "RANDR" missing on display ":79.0".

But now I have a program that uses png graphics, and they don't 
display. The Xtightvnc server is running on these machines. I'm 
not clear on why this issue happens, or how exactly it only effects 
png images displayed in tool bars. 

The same program displays  fine on my Fedora machines that 
have the tigervnc that is the default? 

+----------------------------------------------------------+
  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                        
  G4L Disk Imaging Project maintainer 
  http://sourceforge.net/projects/g4l/
+----------------------------------------------------------+

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

BOINC <at> HOME CREDITS
SETI        10474090.320892   |   EINSTEIN     5577406.240851
ROSETTA      2910550.905419   |   ABC          4933478.318067

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___________________________________________________________
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

23	May 2013
16	April 2013
18	March 2013
17	February 2013
19	January 2013
33	December 2012
21	November 2012
30	October 2012
18	September 2012
49	August 2012
32	July 2012
38	June 2012
38	May 2012
12	April 2012
29	March 2012
12	February 2012
15	January 2012
33	December 2011
14	November 2011
16	October 2011
18	September 2011
27	August 2011
17	July 2011
26	June 2011
42	May 2011
42	April 2011
30	March 2011
56	February 2011
36	January 2011
48	December 2010
21	November 2010
17	October 2010
52	September 2010
73	August 2010
77	July 2010
27	June 2010
44	May 2010
23	April 2010
47	March 2010
54	February 2010
22	January 2010
57	December 2009
83	November 2009
81	October 2009
59	September 2009
24	August 2009
29	July 2009
28	June 2009
31	May 2009
37	April 2009
72	March 2009
71	February 2009
48	January 2009
31	December 2008
70	November 2008
49	October 2008
35	September 2008
59	August 2008
42	July 2008
85	June 2008
26	May 2008
32	April 2008
62	March 2008
80	February 2008
98	January 2008
27	December 2007
54	November 2007
71	October 2007
71	September 2007
41	August 2007
62	July 2007
63	June 2007
80	May 2007
69	April 2007
25	March 2007
40	February 2007
74	January 2007
66	December 2006
92	November 2006
56	October 2006
51	September 2006
66	August 2006
62	July 2006
61	June 2006
57	May 2006
104	April 2006
135	March 2006
89	February 2006
109	January 2006
83	December 2005
63	November 2005
67	October 2005
48	September 2005
128	August 2005
116	July 2005
69	June 2005
109	May 2005
98	April 2005
212	March 2005
136	February 2005
137	January 2005
151	December 2004
136	November 2004
186	October 2004
114	September 2004
125	August 2004
155	July 2004
165	June 2004
187	May 2004
84	April 2004
130	March 2004
73	February 2004
85	January 2004
112	December 2003
147	November 2003
114	October 2003
107	September 2003
96	August 2003
130	July 2003
103	June 2003
134	May 2003
127	April 2003
163	March 2003
219	February 2003
188	January 2003
215	December 2002
209	November 2002
186	October 2002
192	September 2002
187	August 2002
168	July 2002
84	June 2002
129	May 2002
80	April 2002
1	January 2002

Mon	Tue	Wed	Thu	Fri	Sat	Sun

	1	2	3	4	5	6
7	8	9	10	11	12	13
14	15	16	17	18	19	20
21	22	23	24	25	26	27
28	29	30	31