Hello, With version 3.3.6 for unknown reason I am not able to log in on a RealVNC server on random occasion(remotely, of course).
If I check the status of the service remotely, it shows that it's running. I stop the service remotely, then restart the service remotely, same result. Then I reboot the computer (remotely), still the same result. I actually have to log on with a username and password on the local area network, and then voila, I AM able to log in with Realvnc remotely. This happened to me several times in the past, so this is not an isolated incident. 1. question: Why the realVNC server stops responding to login request after a while like if it would be in a nowhere land? 2. If I stop the service and restart it remotely, it still won't help. Why? 3. After rebooting the computer it still won't accept remote logins. why? 4. Only after a phisical login will the RealVNC server function. Why? I experienced this on Windows NT 4.0 workstation but I got the same result with Windows 2000 Workstation as well. I don't have any clue why the service stops functioning after a while, but I do have a clue about why a reboot will not help: Because the "service helper" that runs at a network login, will get triggered form the "Run:" line of the registry can not "help" until someone locally will log on the computer. Does someone have a solution for these really annoying problems? I think, it would be nice to eliminate the (user login dependent) service helper all together, and rely on one complete, fully functioning one service. Geza _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
