I have the RealVNC personal edition server configured as a service under Win XP Pro/SP2. When I reboot
my PC, RealVNC will not accept connections until after I logon. You may wonder why
this is in the ZA forum. It's here because the problem dissapears if I change ZA
so that it does not start with windows. I.e., if ZA does not start after a reboot
I can connect to RealVNC immediately after a reboot without having to logon first.

I am running ZoneAlarm Pro, latest and greatest.
I am running the latest version of RealVNC personal edition.

I apologize if this has been covered elsewhere. I searched the forum and didn't find it.

Operating System: Windows XP Pro
Product Name: ZoneAlarm Pro
Software Version: 6.0

[Updated 9/27/05]
Well, the problem isn't related to the order of which vsmon and WinVNC4 are started. I've made the WinVNC4 service a dependency of the vsmon service, and the vsmon service a dependency of the WinVNC4 service (not at the same time of course). This had no effect on my problem.

I'm a bit frustrated here. I've been buying and using ZoneAlarm for over 3 years now. The first time I need support I find that they charge for it. Not a lot of loyalty to their customer base.

Message Edited by lcsherwin on 09-27-2005 11:19 AM