Hi,

I've put Windows 7 on a machine that I will temporarily use for my computer used to assist users in my company.  When I use VNC Manager to connect to the remote computers, the VNC server crashes on their systems.  I'm using UltraVNC as the distribution for those computers.  I've tried both the current release and the beta release of VNC Manager.  When I use UVNC's viewer, there are no problems.  In fact, at this time I've replaced the default connection from the built in VNC viewer in VNC Manager, to the external UVNC viewer.  Which of course is somewhat of a pain to use.

I can't seem to find any solid scenario where it happens every time.  Sometimes changing between monitor views, all remotes use dual monitors, or using aspect view or normal view and changing it can cause a crash.  It seems to crash on connect mostly with the aspect view active.

I use a large number of different UVNC versions on the remote computers (over 100 in all that I manage) and there appears to be no difference in how they act with what version I connect to.

I'll be glad to assist by sending any information about this issue to you guys if that would help any.  I'm still testing settings and changes to see if I can find some sort of common action.  But, so far the problem is very random in actions.  Other than it crashes the server 99% of the time during a session within the first minute or two, if not on the initial connect which is the most common.

Scott

Scott

This is my sig...

Scott,
since this VNC server which is crashes and not the VNC Manager I don't think we would want to investigate why UltraVNC crashes. I could simply be not very well compatible with Windows 7.

Please note that screen scaling command implemented on the client side, so there is no way they could have any effect on the server. Encoding used by VNC client very well could cause UltraVNC server to crash. I remember that v1.0.2 used to crash on a regular basis when Ultra encoding was used. Just to let you know, the VNC Manager's VNC viewer uses Tight encoding by default, so you my try to change to some other encoding and see if it helps.

PS: By the way, the VNC Manager should receive Certified for Windows 7 logo approval within next 2-3 weeks.


Regards,

I follow what you are saying 100%, and also thought it very odd in what was occuring.  All the remote machines are XP or Vista, Win 7 is only on my management machine where VNC Manager is installed.  UVNC on the remotes varies in version, so there just didn't seem to be any common variable to report for this.

Now though, since the latest VNC Manager beta release (the one right after my original post here) the crashing problem has almost gone away.  Now the connection to the remotes is just a bit slow, sometimes taking 60 seconds or more just to show the full desktop of the remote.  After connection, the speed is good.  How's that for another odd issue?

Keep up the great work, I'm sure these issues will work themselves out.  If there is any info I can provide, let me know.

This is my sig...

The latest stable build v4.5 and the v5.0.3.0 use exactly the same build of VNC viewer ActiveX, so the connection speed should be exactly the same using both VM builds. There was a bug in the UltraVNC 1.0.5 builds under Vista when initial connection was taking too long, altrough not 60 seconds long, more like 10-15 seconds, but still... So it could be that UVNC 1.0.5 running under Windows 7 produces similar kind of problem...

Thanks


Regards,

I've got a new connectivity issue that seems similar to this thread.

Now, I can't fully connect to remote VNC machines outside my local LAN, but can connect to local LAN machines just fine.

I do get an initial connection, but the screens never draw in.  I can connect with UVNC's 1.0.5 viewer just fine, but the VNC Manager veiwer will never complete the first screen draw.  The end user states that it seems like I'm connected, mouse cursor moving and all, but I can't see what's going on.  I've waiting up to 120 seconds for anything, tried screen refreshes and nothing seems to make the screen draw complete the initial draw.

These remote machines are on a VPN tunnel, and never had this problem before.  It's odd that this showed up now, and only in the VNC Manager viewer.

This is my sig...

Could you please configure both UltraVNC viewer and VNC Manager's viewer to use the same encoding (any encoding except Ultra will do) and see if the problem is still reproducible.


Regards,

Bingo!

The default settings for the VNC viewer were "Raw".  I changed it to "Tight" and wow what a difference.  Makes a faster connection within my local LAN too.

Thanks!

Scott

This is my sig...

"raw"?! wow it was a bit extreme The "raw" encoding transfers uncompressed bitmaps between two computers. So the amount of data that has to be transfered in case if the "raw" encoding is used is by the order of magnitude is large when in case of other encodings.


Regards,

I thought the same thing too, why "raw"???  I will have to say though that I never set it up that way.  It was installed that way as default.  hmmmm....

This is my sig...

The default encoding that the VNC Manager uses is "Tight". Could it be that you changed it to "raw" by accident and didn't notice it.


Regards,