UltraVNC

no solutions?

This is cross-posted like crazy (3 forums). Please don't do that...

Have you tried the 32 bit download instead?

I did it to all 3 because it is the same for all 3 versions. perhaps someone knows of a fix that doesnt apply to all 3 versions. have tried 5 installers. hence the 1.0.6.5 x86 and x64 ...

I have tried installing all the above versions on a VM for windows 2003 x64. none of them will pass authentication. none of them are creating registry entries in HKCU or HKLM. I apply administrators group locally for authentication. does not even try for userID and password, only password as if I ...

this is my current problem.... I have tried about 29347298472398 reinstalls and Local_Machine\Software\Wow6432Node\ORL hives are completely empty...

just a headsup to anyone, this is still an issue so if anyone has any solution to this, please let me know.

also, since my last reinstall, now i cant even get it to recognize MS Login. authentication comes up with just password. it is also no longer creating the registry keys during installs. 1.0.6 ...

I have removed the system from the domain and am only trying login attempts with the local admin (Administrator) ID, similar to su on a *nix environment (all local, not domain oriented). this is all IBM Filenet's fault with their incompatibility with MS's RDP protocol. have caused me a major ...

appears that it accepts my connection but then says unauthorized user and closes socket, when reviewing the WinVNC.log file.


Wed May 05 11:17:08 2010
.\vsocket.cpp : VSocket() m_pDSMPlugin = NULL
.\vncsockconnect.cpp : accepted connection from MY_DESKTOP_IP
.\vncserver.cpp : AddClient() started ...

It is installed as a service. I am not currently logged on the server via MS RDP protocol and can make my initial connection, just after supplying local admin credentials, the client closes/crashes and never get to the C+A+D login screen.

I am attempting to authenticate with a user listed in the administrators group, which is listed as a group in the allowed sessions within the VNC admin properties. If this is not what you are referring to, if you could explain a little better, would be appreciated!

Running VNC Server 1.0.8.2 on a 2003 x64 Server on a VMware host. I get the first prompt to authenticate, which then advances usually to the windows C+A+D authentication screen. however, instead of advancing to that screen the "connecting" client just closes, experiencing no actual errors. I do not ...