Server Closed Connection at logon screen

[scorp]

I am getting that Server Closed Connection instantly upon connecting now. I am connecting from one machine to three others, one running 1.0.8.2, one with 1.0.5.6 and one 1.0.2.

If I connect using the 1.0.8.2 viewer I get the that server disconnected immediately on all versions. But it allows me to connect using the 1.0.5.6 or 1.02 viewer to any of them. What I am figuring out though is that if I use 1.0.5.6 or 1.0.2 to connect and then log into windows sign on then I can disconnect and reconnect with 1.0.8.2 and it seems to run fine.

Is there something about the windows Logon page that could make the new viewer crash like that? I am running the MSRC4Plugin_1.2.2_NoReg on all of them but haven't tested it without yet, although I am hoping it isn't a problem to run a plugin.

The servers are running on one windows XP machine and the other two are Windows Server 2003.

Any ideas?
Scorp

[redge]

i think is incompatibility of msrc4plugin between different version of winvnc/vncviewer

securevncplugin allow multi connections but require all ultravnc servers update to 1.0.8.2 without uprade (uninstall old uvnc ...reboot.... delete old ultravnc folder, install new uvnc)

[scorp]

OK.. I will give that a try.. Thanks..
P.S. Love the new screen option for seeing dual screens at once.. Awesome stuff, keep it up!!

[scorp]

I swapped plugins and I still am getting disconnected.
I am on Vista with 1.0.8.2 and connect to XP with 1.0.8.2 and as soon as I see the login screen it goes grey and I get the message that VNCViewer has stopped working. All I can do is close. Is there any kind of debug or log file I can look at to see if it gives a better explanation for the crash?

Also if I use the 1.0.2 veiwer with the new plugin it connects fine and I can login like normal.

[scorp]

When I check the event viewer I see this...

Faulting application vncviewer.exe, version 1.0.8.2, time stamp 0x4b1c3bb0, faulting module ntdll.dll, version 6.0.6002.18005, time stamp 0x49e03821, exception code 0xc0000005, fault offset 0x000675ff, process id 0x1a3c, application start time 0x01ca844094386d38.

Details:
- System
- Provider

[ Name] Application Error
- EventID 1000
[ Qualifiers] 0
Level 2
Task 100
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2009-12-24T02:27:15.000Z
EventRecordID 11114
Channel Application
Computer MyPC
Security

- EventData

vncviewer.exe
1.0.8.2
4b1c3bb0
ntdll.dll
6.0.6002.18005
49e03821
c0000005
000675ff
1a3c
01ca844094386d38

I am going to try other things and see what happens.

[redge]

I am on Vista with 1.0.8.2 and connect to XP with 1.0.8.2 and as soon as I see the login screen it goes grey and I get the message that VNCViewer has stopped working.

what the vncviewer quick option used ?
what the type of connection of both side ? LAN or WLAN or both
inhouse test or via internet ?

[scorp]

what the vncviewer quick option used ?
what the type of connection of both side ? LAN or WLAN or both
inhouse test or via internet ?

I have only tried the Auto option.

The connection has been tested from Home LAN to Work LAN (internet) and internally at work from the same switch.

I stopped locking my PC and have been using it now for two weeks with no crashing when I connect. Not sure what the windows logon screen could be doing to me.

[redge]

until winvnc care screen saver/locked screen by default
you need to add winvnc.exe -sc_exit
this make winvnc waiting for security input UAC (User Account Control)

[scorp]

I also noticed that when I connect to Windows Server 2003 running v1.02 still that with the 1.082 viewer I would get the same stop message but could connect again and sometimes I could make it in OK.. but if I use the 1.056 viewer it worked perfectly every time.

I will give it a try.. but how do I do that exactly? Do I need to modify the service with that command? like this.. "winvnc.exe -service -sc_exit" ?

Thanks

[tmoore]

I am getting the same problems here. Windows 7 pro 64 on the client and server end. UltraVNC 1.0.8.2 on both the client and server.

When I try to connect when the server is at the login screen it briefly connects (I see the login screen) and then instantly on the client I get an error dialog saying that "VNCViewer has stopped working".

The event viewer viewer records the following information:
Faulting application name: vncviewer.exe, version: 1.0.8.2, time stamp: 0x4b1c3c7e
Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b802
Exception code: 0xc0000005
Fault offset: 0x000000000005252b
Faulting process id: 0x1918
Faulting application start time: 0x01cb859d0118a9ae
Faulting application path: C:\Program Files\UltraVNC\vncviewer.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 4598f49e-f190-11df-a8ff-e0cb4e060089

This looks like a null pointer problem, so it looks like a bug in the client code.

I can use the java viewer to log in to the server, and then switch to the vncviewer app and it seems to be ok from there.

[sfhub]

You might be seeing this problem:
[topic=17917][/topic]

Which was fixed in build 1.0.9.2 and above. You can get 1.0.9.3.3 here:
[topic=26860][/topic]

Give it a try and see if it resolves your problem.