I have the same problem. On both XP and NT40 machines. Gone back to previous versions of VNC, no luck. Searched through registry and deleted everything "vnc" before re-installing. Installed/uninstalled several times. Changed from ultravnc to realvnc. no luck Turned off Mcafee firewall software. no luck. Turned off Mcafee virus software. no luck. I have discovered that I do not need to stop/start a running VNC service in order to kick start it. I can "telnet localhost 5900" and that will work. The telnet window gets some junk characters. Just close it. Service will now be working properly and accepting connections. Unfortunately that means I have to log in to do that before service will work. So no remote reboots unless I eliminate windows login and put "telnet localhost 5900" in a bat file in the startup menu. I haven't tried that yet but i figure it will work. But i do not want to eliminate my login to windows. Hopefully, this telnet trick I discovered will be a clue that will reveal what the problem is. ToDo: Install a plain copy of Win XP. Install VNC before any other apps. If it works then test VNC service after each install of other apps. -joew
> Have you tried VNC4beta? > > During your uninstall / reinstall process, have you clear >registry keys > related to VNC? > > You didn't mention the presence of ZoneAlarm in your first post. >If they are > in the problem PC, you could desactivate it to see if the >problem disappears. > > Otherwise, no idea :( > > -----Message d'origine----- > De : Andy Hall [mailto:[EMAIL PROTECTED] > Envoyi : mardi 11 mai 2004 02:34 > @ : [EMAIL PROTECTED] > Objet : RE: can't connect to win2K server until service is stop/started > > Ah, it's been a few weeks since I installed; presumably I said yes to that dialog > and didn't > run the service installer. (If I had it would presumably give me the same error it > does now: > the service is already running). > > Either way, last night I tried un- and re-installing VNC, saying yes to the "install > as a > service" dialog, and rebooting, and my problem is unchanged. As I said, this issue > has > persisted through several rebuilds, so I don't think installation fragility is at > issue. The issue > was also present when I had a different network config (a simple modem, not an ADSL > router modem). > > Might VNC conflict with other running applications? Such as ZoneAlarm, for example, > or > AV programs? Might one of the various spyware checkers do something to it? Or any > other > ideas? > > thanks, > andy > > > -----Original Message----- > > From: "Seak, Teng-Fong" <tfseak "at" futurmaster.com> > > > > During VNC installation, there's a dialog asking if you want to > > create some icon and if you want to install VNC as a service > > and start it. If you had chosen these options but afterwards > > you run "Install as a service", I don't know what that would give. --------------------------------- Do you Yahoo!? SBC Yahoo! - Internet access at a great low price. _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
