It can be done, you need to have the VNC server service, in services,
stopped and then run it in user mode. The server service, is sitting there
listening on port 5800/5900 and the user mode version can't listen on the
same default ports.
Try this, completely remove VNC, and reinstall. DO NOT select the defaults
and select custom, DO NOT install it as a service, and then finish. Then got
to vnc in the start menu and select user mode settings, set the password.
Then select run vnc server in user mode, and I am 90% sure this will work, I
don't have a 2008 VM handy to test but I will get one.
On Tue, Jun 17, 2008 at 9:24 PM, Eric <eshiau@...> wrote:
> I think you are right. It is related to windows server 2008 which is a
> variation of Vista.
> I tested VNC on both XP and 2008. For XP, it behaved just like document
> http://www.tightvnc.com/winst.html described. For 2008, I
> tried "Start->Programs->TightVNC->Administration->Run Service Helper" and it
> just was unable to display WinVNC on tray icon; not even I rebooted the
> machine. I concluded that VNC is not working for 2008 (I might be wrong)
> and gave up.
> I just tried you suggested that run it on user mode and got "Connection
> Closed" dialog box right after it sent password to server.
> Please let me know if anyone install VNC successfully on 2008.
> *From:* Morgan Storey <me@...>
> *Sent:* Tuesday, June 17, 2008 5:14 AM
> *To:* Claudio Coletta <c.coletta@...>
> *Cc:* Eric <eshiau@...> ; vnc-tight-list@...
> *Subject:* Re: Password is not set
> Could this be the same session 0 isolation that is experienced in Vista. I
> would think so.
> Vista gets this same issue (password not set) if you try and connect to the
> Tight VNC running in service mode. If you de-register, stop or don't install
> the service, then run the VNC user mode shortcut in the start menu, set the
> password on this it should work.
> It doesn't sound like a routing issue unless the route you are taking ends
> up at a different rfb/VNC server.
> My bet is that when you tested it internally the user mode one was running,
> testing it externally now is service mode.
> My advice, don't use VNC, or at most don't use it straight, VPN/ssh tunnel
> into the network then VNC, or RDP(which is faster and free for
> On Sat, Jun 14, 2008 at 11:55 PM, Claudio Coletta <c.coletta@...>
>> Hello Eric
>> *> Not quite sure what is " user password"? I only saw two passwords,
>> "Primary *
>> *> password" and "View-only password" on server tab of "TightVNC Server"
>> properties. I *
>> *> changed both passwords on both, server and client machines; still not
>> working. *
>> *> *
>> *1)* *From: Start Menu\TightVNC\Administration\Show Default Settings*
>> = Registry "Local Machine" configuration used for service mode (but I
>> don't know if can work with Windows 2008, with Vista the service mode cannot
>> work), used before that a user "log in";
>> *2)* *From: Start Menu\TightVNC\Show User Settings*
>> = Registry "Current User" configuration used when a user is "logged in".
>> *> Thanks. *
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> TightVNC mailing list, VNC-Tight-list@...
>> To change your subscription or to UNSUBSCRIBE, please visit
> Morgan Storey,A+, MCSE:Security.
> Senior Network and Security Consultant.
Morgan Storey,A+, MCSE:Security.
Senior Network and Security Consultant.