The solution to my problem with Connection Refused under Windows 2000: I was using Jeremy Peaks amended version of WinVNC 3.3.3r7, release 3. When I had the system set up and logged in (1024x768 with 16 bit color resolution, no wallpaper, WinVNC running as a service with default password set) all worked fine. I could log in and out of the remote system. When I closed my VNCViewer session, the remote computer would reset to 640x480 with 256 colors and I would get a "Connection Refused" message. Resetting the screen resolution and color on the remote system would instantly allow me to reconnect with the viewer, but again closing the viewer reset the video settings to default VGA. Apparently, there is a problem with WinVNC and the Windows 2000 VGA driver or settings according to the FAQ. Removing the registry entries for Disable Wallpaper, Disable Font Smoothing, Disable Pattern, and Resolution had no effect. But I reinstalled the WinVNC 3.3.3r7 original files and all worked fine. The viewer will now close without resetting the screen/video settings. I have not tested it with the registry entries added back yet, though, so the problem may have only been in the applications files. >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! --------------------------------------------------------------------- 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 ---------------------------------------------------------------------
