This question has been asked before, but I haven't seen an answer that
solves my problem yet. And I have read the FAQ and searched the list for
similar postings.
I have installed WinVNC 3.3.3r7 on two Windows 2000 Servers. One of the
servers is a domain controller running Active Directory, the other is a
simple domain member.
Both servers run VNC as a service and I have set the default password for
the service. The app and service was installed under the Administrator
account and function fine when a user is logged into the system. If no one
is logged in, I get a "Connection Refused" message after attempting to
login via VNCViewer.
I need to leave the Servers logged out (they are in unsecured lab
locations) until such time as new accounts, upgrades, etc. need to be added
to the systems. It is possible that a security setting is causing this,
but I can't find it.
Does anyone have a way around this, or a fix? Any help would be greatly
appreciated!
--------------------------------------------------------------------------
Shawn Gimbert [EMAIL PROTECTED]
Info Tech Spec II tel: 804-924-0851
Department of Physics fax: 804-924-4576
382 McCormick Road
P.O. Box 400714
Charlottesville, VA 22904-4714
"Work is the price you pay for money!"
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------