Viewer stop after gray screen

[Rudi De Vos]

Many people reported that in some cases the viewer stops after you get the gray screen.
Using a tight or realvnc viewer it was working.

I was final ( after many weeks of debugging) able to repeat it.
Using a heavy debugger the viewer was 100x slower. It looks like when some part in
the viewer is slow some threads are in a start race.

Because it worked with other flavor viewers i was debugging the viewer... but the real cause is the server.
The server disable some parts that are ultravnc only...one on this is causing the crash.

Looks like it doesn't crash anymore ...
Update wil be only for testing in a few days.

[Rudi De Vos]

1.1.8 versions have been updated with new server.
Version server is now 1.1.8.2

http://www.uvnc.com/downloads/ultravnc/ ... -1100.html

Download versions 1180 have an updated exe or zip with the 1.1.8.2 server update.
To leazy to make a new page

[KB-IC]

Hi Rudi

Thanks for fixing this problem with the server. I'm having the same problem with the Single-Click used for support - if it's the same problem could you fix that as well please.

Thanks

[dcitelecom]

Unfortunately the problem still persists. I use a mix of windows 7 and windows XP machines and use ultravnc to remote control both machines from either windows version. Since 1.1.8 ultravnc constantly gets stuck on the gray screen after login and even if it can successfully control the other PC it will freeze after a couple of minutes. When looking at the server machine I can still see the remote cursor moving but on my remote machine the screen is frozen so it appears to be a screen driver issue. Removing the mirror driver does not fix the issue.

[dcitelecom]

I also noticed that the 32 bit server version is 1.1.8.5 (March 14) and the 64 bit version is still 1.1.8.4 (March 10)
Makes me wonder if the fix described in the previous post was also applied to the 64 bit server version.

[Rudi De Vos]

Changes are auto pushed to all versions.
We can run a version behind, but latest 32/64 versions are 1.1.8.7 while this was added with 1.1.8.2

I tried every trick to test server/viewer and can't repeat it anymore.
Without repeating i can not fix things.

To test:
Make sure both viewer and server use the latest version.

What's the network ( Wan/LAN Wifi..)
Try to set predefined encoders, possible it only happen with some
specific encoder or auto mode fail.
Just try to make all veriable factors as less as possible.

PS:
Before ,the lockup only happended on very slow networks, like 3G
en a server with a slow cpu. To repeat it i needed to run another app
that took almost 100% cpu.
Took me months to trace that one.

[dcitelecom]

I installed x64 server and viewer 1.1.8.7 on both machines. I tried LAN, WAN, etc... always same result. The viewer stops responding. Either I get the grey screen on login or after login the viewer stops responding. I can still see the remote control working LIVE on the other machine. It's just that the viewer stops sending screen updates. I tried the varieous different encoders all with same result. Do you have a debug version I can run and send you a log?

[Rudi De Vos]

You always can activate the logging ( server options) but the info you get is limited.

How do you connect
1) start server by clicking the exe
2) start winvnc and enter the ip of the viewer

Does it work in loopback, server and viewer on the same pc.

[Rudi De Vos]

Please test with the exe ( win32)
http://www.uvnc.eu/download/1180/winvnc_test1.zip

[Rudi De Vos]

Fuuny uploaded before checking...
Doesn't work, gray screen and only remote cursor.

Seems i now added the issue's you always have.
perhaps this give me some clue's

Do not test it, don't work

[Rudi De Vos]

This seems better, only don't know if it also fix your issue's.

http://www.uvnc.eu/download/1180/winvnc_test2.zip

[dcitelecom]

the server is registered as a service on the x64 machine. On the viewer side I click the exe file and enter the IP address.
I tested loopback and same result.
I started logging but don't see any error message.

Mon Mar 25 16:48:14 2013
vncservice.cpp : @@@@@@@@@@@@@ GetCurrentUser - UserNAme found: JohnDoe
vncservice.cpp : @@@@@@@@@@@@@
GetCurrentUser - UserNAme found: JohnDoe
vncmenu.cpp : ########### Shell_TrayWnd found 1
HideDesktop.cpp : Killwallpaper 1
vncmenu.cpp : DisableAero 0
vncservice.cpp : @@@@@@@@@@@@@ GetCurrentUser - UserNAme found: JohnDoe
vncmenu.cpp : ############### Usernames change: old="JohnDoe",
new="JohnDoe"

[dcitelecom]

I tried the new server file. I run win7 64 bit and it's a 32 bit file so it did not work with the dsm plugin but other than that it loaded fine. Unfortunately it produces the same error for me. Is it just me? Does no one else have this error?

[Rudi De Vos]

To avoid any settings issue's

1) copy the server/viewer to a temp folder
Just the 2 exe ( vncviewer.exe and winvnc.exe) no dll or config files.
2) make sure the uvnc_service isn't running
net stop uvnc_service

3) Start the server, this ask to set a passwd and create the default ultravnc.ini
4) start the viewer and connect to localhost

Development is also done on a X64 win7, and tested the tes2 on this pc.

Please mail the log.
There wil no errors in the file, but i want to compare it with a working version.

You are not the only one, some people reported the same...but i can not find why it does this on some systems.
Using a non ultravnc viewer solved it in some cases.
Is there any clipboard software installed ?

[Rudi De Vos]

I can't test the servers myself, no gray screen
Can you try this test.

http://www.uvnc.eu/download/1180/winvnc_test3.zip

This zip has the release and debug version

To see the debug info of the debug version
download dbgview
http://technet.microsoft.com/en-us/sysi ... 96647.aspx

Thye debug give a lot of info, i numbered all function locks to follow
what's going on.

Thanks for testing

[Rudi De Vos]

Updated to 1.1.8.8

Please test if this fix some initial connect gray screen issue's.

[Ryan138313]

Did the above version resolve the gray screen issue?

I am experiencing this issue also...



https://forum.ultravnc.net/viewtopic.ph ... 665#p94665

[nerdx86]

We are encountering this as well, but also other issues with the newer versions.. There seem to be problems in both viewer and server?? (1 and 2 below are not a new server, 3 fails with an old viewer)

We are also developers, and have tools to help if you can point us in the right direction.

1. We have older WinVNC servers that work with 1.0.9.6.1 viewer but give a hung gray screen with 1.1.8.9.
2. We have older servers that can reverse connect to a VNC listeners with 1.0.9.6.1 viewer but give a hung gray screen with 1.1.8.9.
3. We have a server that worked fine both via LAN and VPN/WAN on port 5900 with server version 1.02. (multiple viewer versions)
a. We upgraded the server to 1.1.8.8, and were then able to connect fine over the LAN, but not over the WAN/VPN. (The connection would connect and then disconnect immediately upon connection)
b. We tried several versions of Viewer, but encountered the same issue. (LAN ok, VPN not)
c. We upgraded the server to 1.1.8.9 and had the same issue (even with viewer 1.1.8.9) (LAN ok, VPN not)
d. We downgraded the server to 1.0.8.0 and everything worked normally (but 1.0.8.0+ has issues with the service locking up when we remotely shutdown our 16bit full screen software)
e. We re-upgraded the server to 1.1.8.9 and again same issue. (LAN ok, VPN not).
f. We changed the main port to an upper 16000+ port number and it began working normally.

[Rudi De Vos]

Lan and Wan was tested, not vpn.

I have spend hours >100 to try to get the gray screen or lock something without luck.
But as many people report it, there have to be something that goes wrong in a special case(s).

+To simplify the test, only 1189-1189. There is some old bug in 10961 that is triggered by the new viewers.

I just wonder if the following can be the cause.
People asked to add something that the server bind to a new or changed ip address, if the ip
is changed or some extra network card is added . The vpn change some ip addresses....
In that case starting winvnc after the vpn connection is made should work... If this works it would identify the ip detection
change as cause....

What vpn software are you using ? Possible i can setup something between my home and dedicated servers
to test.

[nerdx86]

Ok, Well. The version in issue 2 is 1.0.6.5.. So, the bug extends to other older versions.. I can try a survey of our servers in the field and see which will connect and which won't..

We aren't using any VPN software, we have a sonicwall to sonicwall VPN.. The PC has a single static IP. The gateway handles the VPN, and the tunnel is very transparent. Obviously there is a significant amount of additional delay. (ping is 63ms)

I am now 800 miles away from the server in issue 3, so I'll need to coordinate with the people onsite for any testing.. Maybe I can create a wireshark log for you along with a ultravnc.log? Do you think that might help?

[Rudi De Vos]

My own old WAN test server (216.55.178.47) is 8000km away ( europe-us), 168ms.
Using 1189 server and 1189 viewer on home pc it connect without any problem.

You can test it with your 1189 viewer.

ip: 216.55.178.47 ( old celeron with 524Mb)
View only passwd "ultravnc"

[nerdx86]

I should point out that all these machines are running XP.. (which it appears your test is too)

I will try to find a server that you can log in to that doesn't work..
I will also try to build a list of older servers that don't work with the new viewer..

[Rudi De Vos]

I'm testing with WAN 2003 server and use xp via virtualpc.

I don't think it's the viewer, it never is, he only show a gray screen because the server is locked or was crashed.

I can send a debug winvnc, using dbgview you get a lot debug info

[nerdx86]

Ok, please send debug version....
I can also send packet captures from wireshark if that helps?

The servers that lock with viewer 1.1.8.9 will connect with an older viewer simultaneously..?? Let me do more homework on this..

[Rudi De Vos]

http://www.uvnc.eu/download/1180/winvnc_debug.zip

[Rudi De Vos]

You say that the older viewer works with a older viewer
but the second connect to a new viewer stay gray ?

[Rudi De Vos]

reuploaded debug file, was already 9 days old and possible not more the same as the source.

[nerdx86]

New Viewer to old server stay's gray or freezes after a second or 2 and then throws an error and/or disconnects after a while..
Old viewer to same server from same pc at same time connects fine. (I just tried this again with a 1.0.6.5 Server and made a screen shot) I will private message you the screen shot..

[nerdx86]

Ok, sent email with results..