VNC client just closes with no errors

[caveneyp]

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 believe it to be a VM issue since there is another 2003 VM I am running it on that is working without any issues.

I have also tried using 1.0.2.0 due to it being the same version we run on another server that has no issues. however, it works once and then begins getting that password not set bug this I did find a few reports on. Can get it resolved, but then after first disconnect, it does it again. So that solution appears as though it is not going to work.

VNC Client version 1.0.6.4
VNC Server versions tried: 1.0.2.0, 1.0.6.5, and 1.0.8.2
1.0.2.0 is the one that has the password related issue after first connection. the other 2 just close out immediately following the first authentication request.

Server OS: 2003 x64 EE on a VMware host.
Desktop OS: Windows XP Pro SP3.

[B]

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.

That sounds like something that happens when there's a disparity between the logon to the running WinVNC service versus the logon for the WinVNC app in someone's user session. In other words, it's connecting you but then dropping you right away as the "other" WinVNC takes over. I have that issue all the time.

But it could be something else entirely...

[caveneyp]

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!

[B]

What I was getting at is, just make sure that the VNC server is installed as a service, and that there is no instance of the WinVNC server that ever gets called in application mode (such as in a user's Startup folder).

But it sounds like you are also using the MSLogon / AD integration features, with which I'm not very familiar, so perhaps others can provide insight.

[caveneyp]

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.

[caveneyp]

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
.\vncclient.cpp : vncClient() executing...
.\vncclient.cpp : TEST 4
.\vncserver.cpp : AddClient() done
.\vncclient.cpp : client connected : MY_DESKTOP_IP
.\vncclient.cpp : DSMPlugin Pointer to socket OK
.\vncclient.cpp : m_ms_logon set to true.\vncclient.cpp : negotiated version
Entered InitAuthenticate
c:\data\ultravnc\ultravnc project root\ultravnc\winvnc\winvnc\vncPasswd.h : PASSWD : ToText called
.\vncserver.cpp : client MY_DESKTOP_IP verifiedHost 0 prior to adjustment
.\vncserver.cpp : client MY_DESKTOP_IP verifiedHost 0 after adjustment
.\vncservice.cpp : @@@@@@@@@@@@@ GetCurrentUser - Error: Usersize 0
MS-Logon (DH) authentication.\vncservice.cpp : @@@@@@@@@@@@@ GetCurrentUser - Error: Usersize 0
.\vncproperties.cpp : ***** DBG - Force USER SYSTEM 2
.\vncmenu.cpp : ########### vncMenu::TIMER TrayIcon 5s hack
.\vncservice.cpp : @@@@@@@@@@@@@ GetCurrentUser - Error: Usersize 0
.\vncmenu.cpp : ########### vncMenu::TIMER TrayIcon 5s hack call - Runningasservice
.\vncmenu.cpp : ########### vncMenu::AddTrayIcon - UserName =
.\vncservice.cpp : @@@@@@@@@@@@@ GetCurrentUser - Error: Usersize 0
.\vncmenu.cpp : ############### Usernames change: old="", new=""
Wed May 05 11:17:13 2010
After DH: g=671611049, m=1105360973, i=148589770, key=963044209
.\vncntlm.cpp : GetProcAddressCheckUserPasswordSDUni result=0 --Cannot create a file when that file already exists.
CheckUserGroupPasswordUni result=0
.\vncclient.cpp : authentication failed
.\vncserver.cpp : removing unauthorised client
.\vncmenu.cpp : Reset 0
.\vncserver.cpp : RemoveClient() done
.\vncclient.cpp : ~vncClient() executing...
.\vncclient.cpp : deleting socket
.\vsocket.cpp : closing socket

what could I be missing for the authentication piece? reviewing fields for authorization are Administrators and Power Users groups with local checked. nothing in field 3 for Read-Only. the local administrator is obviously in that group... at a loss.

[B]

Sorry if I'm misunderstanding, but are you using an AD account to authenticate to the running WinVNC service, but then trying to login as a "<b>local</b> admin", that is, one who's not on the domain at all? (That is, you're logging in as localmachinename/administrator rather than domainname/user?)

Might not trying to "log in locally" kill the domain relationship/connection? What happens if you log in as a regular domain admin?

But again, I'm not very familiar with the MSLogon architecture.

[caveneyp]

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 headache over last 3 days.

[B]

Uhh, so why don't you just uncheck "Require MSLogon" on that particular station, and just use password authentication and/or MSRC4 keys?

[caveneyp]

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.5 is really buggy I am beginning to think...

[caveneyp]