For test you can try to run viewer on the same computer where the server installed.
Check the "Allow loopback" checkbox in configuration.
Also please write server log file with loglevel 9 and send it to support@tightvnc.com
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, I had the same issue.
Check the following key in the registry: HKEY_LOCAL_MACHINE --> "Software\Microsoft\Windows\CurrentVersion\Policies\System\"
There should be a entry (DWORD32) called "InactivityTimeoutSecs" with the value "0" if its not there --> create it, reboot the computer and the problem should be solved.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, I had the same issue.
Check the following key in the registry: HKEY_LOCAL_MACHINE -->
"Software\Microsoft\Windows\CurrentVersion\Policies\System\"
There should be a entry (DWORD32) called "InactivityTimeoutSecs" with the
value "0" if its not there --> create it, reboot the computer and the
problem should be solved.
Hi Team,
Can you help me for this issue.
Pravin Mori
Hello.
For test you can try to run viewer on the same computer where the server installed.
Check the "Allow loopback" checkbox in configuration.
Also please write server log file with loglevel 9 and send it to support@tightvnc.com
Hi Team,
I have try the same but still received same issue.
Enclosed the logs same.
Hi Team,
Can you please update the status ?
Pravin Mori
Hello, I had the same issue.
Check the following key in the registry: HKEY_LOCAL_MACHINE --> "Software\Microsoft\Windows\CurrentVersion\Policies\System\"
There should be a entry (DWORD32) called "InactivityTimeoutSecs" with the value "0" if its not there --> create it, reboot the computer and the problem should be solved.
Hi,
Thanks for the reply.
But I had formated system 1 week ago.
Pravin Mori
On Tue, Nov 26, 2019, 9:59 PM Jonathan Garcia jonel0311@users.sourceforge.net wrote:
Related
Bugs: #1470