My company is using RealVNC 4.3.2 on Windows XP SP2 in a Windows 2003 domain and we are unable to connect to a workstation when the workstation first boots up. If someone physically goes to the computer and logs in, VNC will then connect even if you immediately log back out. Someone just has to log in one time and then everything is fine. The error we are getting is "Failed to connect: connection timed out (10060)". It isn't a matter of the service not having time to start because you can wait a while and if no one has ever logged in you won't connect. Also, I can remotely connect to the services on the computer and see that the VNC service is running and even restart it, but it has no affect and I can also connect using Remote Desktop, but even that isn't enough to allow RealVNC to connect. Only having someone physically log into the machine resolves the connection problem. We are using NT Logon Authentication if that matters. We didn't have this problem with earlier versions, but we also have some Vista and 64bit machines and needed the new version for full support. Lastly, we are using Symantec Firewall, but I wouldn't think that would matter since we can connect after someone logs in and then logs back out. Has anyone else encountered this and is there a way to resolve the problem?
Thanks, Paul _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
