I know I don't set both passwords. Never have. I have always used just one password, regardless of whether someone is logged in to the machine or not.
Of course, I don't get the "failed to connect" message either. Well, I have received it, but not because of a password problem. Off hand, it sounds like your problem is unrelated to the password issue. -----Original Message----- From: Chris Dillon [mailto:[EMAIL PROTECTED]] Sent: Friday, August 30, 2002 10:36 AM To: [EMAIL PROTECTED] Subject: Re: NT5 / Windows 2000 Server Problem -- session gets hung On Fri, 30 Aug 2002, Bruce Lilly wrote: > >>>>Twice now, I have been in a session. I have inadvertently closed > >>>>the VNC client. > >>>> > >>>>Then, the client can no longer establish a connection. > >>>> > >>>>We check. VNC is STILL running as a Service. If we stop and then > >>>>start VNC, then it works again. You need to set BOTH the default and user-specific passwords. When you are running outside the context of a user logged in, it uses the default password. Once you have connected and then logged in as a user, the next authentication (such as when you get disconnected and have to try to reconnect again) will use the user-specific password. Restarting the VNC server remotely from another NT server would let me connect again, probably because VNC no longer knew what user context it should be in and reverted to the default password. I scratched my head on this one for a while, too, and it finally dawned on me that was my problem. Simple operator error. :-) -- Chris Dillon - cdillon(at)wolves.k12.mo.us FreeBSD: The fastest and most stable server OS on the planet - Available for IA32 (Intel x86) and Alpha architectures - IA64, PowerPC, UltraSPARC, ARM, and S/390 under development - http://www.freebsd.org _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
