Correct me if I'm mistaken, I think when VNC isn't started as a service, it's 
"User setting" instead of "Default setting" which is being used.  Check your password 
in user setting.

> -----Message d'origine-----
> De : Jason Yates [mailto:[EMAIL PROTECTED]
> Envoyi : jeudi 5 fivrier 2004 02:46
> @ : [EMAIL PROTECTED]
> Objet : w2k vnc service
> 
> I just installed the VNC service on Windows 2000 Server edition box.  I
> made sure the service was started, and winvnc is showing up in the task
> manager.  Even though I see it running in the task manager,  I'm still
> getting an error saying "No existing instance of WinVNC could be contacted".
> 
> I also decided to start the VNC server logged in as Administrator over
> RDC; instead of as a service..  I start the server and I can access the
> properties fine now.  I set a password and everything looks fine. Now on
> the client side, I get an error saying no password has been set on the
> server.  When I just set the password.
> 
> I've installed VNC before and never had this problem.  The only
> difference now is I'm installing it remotely over RDC.  Could there be
> some confliction with Terminal Services maybe?  I'm stumped on this one.
> _______________________________________________
> VNC-List mailing list
> [EMAIL PROTECTED]
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to