TightVNC 1.3.10 & TightVNC 2.0.2 released

[redge]

http://www.tightvnc.com/whatsnew.html
http://www.tightvnc.com/download.html#devel

support DFMirage
support multi monitors
improved properties dialog (user friendly help)
More accurate password handling
Fixed problems with restoring desktop wallpaper.
based RFB 3.8 and backward compatible with older RFB 3.3x


http://www.tightvnc.com/

[jremar]

Hi,

I'm using TightVNC 1.3.10 between two XP Pro PCs and is having file transfer problems.
The viewer is on an Administrator a/c and the remote PC is a Limited User a/c.
Both are on a LAN.

I can view and control the remote PC.

I tried to transfer files from the Admin to the remote PC but only get an empty file on the that PC.
I can however transfer a file INTO the Admin's PC.

Am I missing something?

Thanks

[jarvis]

This forum is about UltraVNC.

However, please confirm if either the viewer or the server is actually UltraVNC

[redge]

filetransfer between tightvnc and ultravnc is not compatible.

[jremar]

This forum is about UltraVNC.

However, please confirm if either the viewer or the server is actually UltraVNC

Oops!

I thought I was posting into the VNC-Related Products forum.
It's TightVNC for both viewer and server.

My bad.

Can the admin please move this thread to the correct forum?

Apologies and thanks.

[redge]

vnc related product is not intented for support help of third vnc but only for show known/news vnc related products
support help for tightvnc is by donation to tightvnc website .... but not via ultravnc forum.

[Rudi De Vos]

No problem posting tight vnc issue's, and it is always possible that
people use more vnc flavors.

We (devs) can't help with tightvnc, codebase differ and already
have a lot of work by making ultravnc stable.

[redge]

Hello everyone,

I am glad to inform you that TightVNC 2.0 Beta 1 is available for download. This is the first public preview of the upcoming TightVNC 2.0 release. The files can be downloaded here:

http://www.tightvnc.com/download-beta.php

This Beta version delivers completely new TightVNC Server for Windows. It was redesigned and reimplemented from scratch. It features new component-based architecture which is perfectly compatible with the latest operating systems, Windows 7 and Windows 2008 Server R2. Older versions of Windows are supported as well – the minimum requirement is Windows 2000.

The final release of TightVNC 2.0 for Windows is scheduled to April, 2010. There will be minimum changes between this Beta version and the final release – ideally, that should be bugfixes only.

Note: Beta versions of TightVNC 2.0 do not include components for Unix/Linux. These components will be worked on once TightVNC 2.0 for Windows goes out from Beta stage.

What's New?

Below is a list of major improvements in TightVNC 2.0 Beta 1:

• Introducing new file transfer subsystem based on new protocol extensions. Multiple files and directories can be copied at once, directories are processed recursively. Data compression is used to speed-up copying. Files can be renamed or removed, new directories can be created. File sizes are not limited by 4 Gb any more.
• Implemented new server architecture which separates service code from the user interface. This enables service-mode operation under Windows Vista and Windows 7. Also, this fixes all known problems with multi-user features of modern Windows systems like Fast User Switching and Terminal Services.
• Screen updates have become reliable. If something went wrong and the picture in the viewer is garbled, incomplete or outdated, it will be recovered in reasonable time. There should be no more hidden menus or destructive window movements. If fast update detection methods fail, full-screen polling will keep updates going.
• Featuring new secure administrative interface. What was called "TightVNC tray icon" in previous versions is now a separate process which acts as a control interface to the TightVNC service. Control interface can be optionally protected with a password to make sure users cannot reconfigure or shut down the service unless they know the password (or have administrator privileges).
• There should be no more confusion between "default settings" and "user settings". In TightVNC 2.0, there is only one service-mode configuration and it is not affected by any per-user settings. The "Configure..." menu item of the service always shows the effective configuration. From the other side, TightVNC Server can be started as an application, and in that case each user has his/her own configuration.
• Featuring IP-based access control for incoming connections. Previous versions of TightVNC did allow similar IP filtering, but now everything is easily configurable. You can even test the rules on specific IP addresses, prior to applying new rules.
• TightVNC 2.0 distribution has been packaged with new installer. It's smarter and more efficient. It tries to prevent reboots whenever possible. It invites to set passwords so that TightVNC Server would be ready to work right at the moment of finishing the installation. From the other side, it can operate silently (when run with /S option in the command line). Finally, the complete self-installing TightVNC package (both server and viewer parts, and the uninstall tool) is only 550 kilobytes in size.
• This list of changes is not full. TightVNC Server 2.0 for Windows has been completely rewritten by the TightVNC team. It does not include old TightVNC 1.3 code. So the right answer to the "What's New?" question must be "Everything!".

--
With Best Wishes,
Constantin Kaplinsky,
GlavSoft LLC.

--------------------------

TightVNC 2.0 Beta 1 for Windows

We are glad to present new Beta version of TightVNC for Windows which is a preview of the upcoming TightVNC 2.0 release.

This is a Beta version and may have bugs, use it at your own risk. Do not use it on mission critical computers. However, we kindly ask you to give it a chance. Please try it out and report problems if any.
System Requirements

TightVNC 2.0 Beta 1 supports all client and server versions of Microsoft Windows starting at Windows 2000. This includes:

• Windows 2000 Professional, Windows 2000 Server
• Windows XP, Windows 2003 Server
• Windows Vista, Windows 2008 Server
• Windows 7, Windows 2008 Server R2

It works in both 32-bit and 64-bit operating systems, although its performance may be lower in 64-bit versions of Windows.
Licensing and Support

TightVNC 2.0 Beta 1 is absolutely free for both personal and commercial usage. It is available under the terms of the GNU General Public License (GPL).

If you find the software useful, please consider purchasing a support contract.

http://www.tightvnc.com/download-beta.php

[redge]

TightVNC 2.0 beta 2 is available since 8 April 2010
http://www.tightvnc.com/download-beta.php

What's New?

Below you can find the list of changes in TightVNC 2.0 Beta 2, as compared to the previous Beta version.


Part 1. Changes in the Installer

• Valid digital signatures have been added to the installer and installed TightVNC executable files. That makes it easy to verify the integrity of the package. Make sure TightVNC has a valid signature of GlavSoft LLC., otherwise it's not the original distribution.
• Featuring new option to add exceptions for TightVNC Server and Viewer to Windows Firewall (supported in Windows XP SP2 or any later version of Windows). This makes TightVNC ready to accept connections right on finishing the installation.
• Featuring new option to enable system services simulate Ctrl-Alt-Del keyboard combination under Windows Vista and above. This allows TightVNC Server handle remote Ctrl-Alt-Del events in all supported operating systems from Windows 2000 to Windows 7 and Windows 2008 Server R2.
• The service configuration page (where initial passwords can be set) has become completely optional. And that page will not be auto-selected if the passwords have been set already.
• An issue with file sharing failure has been fixed – it could be experienced after trying to set both passwords via the service configuration page. Also, there were potential problems with not actually enabling authentication on setting passwords from the installer – they have been fixed as well.
• There was a number of other minor changes such as user interface enhancements and improvements to the installation logic.

Part 2. Changes in TightVNC Server for Windows

• Keyboard handling has been fixed. Previous Beta version could handle combinations like Ctrl-C or Ctrl-V incorrectly – it could insert literal C or V instead. New version fixes that – it should interpret keyboard modifiers properly. In addition, it fully supports Windows and Menu keys. Finally, sending Ctrl-Alt-Del remotely should work on all supported versions of Windows.
• Authentication subsystem has been improved – now it would prevent brute-force attacks on passwords by introducing delays after failed authentication attempts. This works for both RFB connections and for administrative passwords. Another authentication-related fix eliminates erroneous authentication requests on reverse connections.
• Tight encoder has been fixed – it could work incorrectly in previous Beta version. It did not preserve the state of its data stream in situations when it was disabled and then re-enabled by the viewer. As a result, the viewer could not decode compressed data and had to disconnect. Corrected code accurately preserves the state of each encoder to eliminate such protocol synchronization problems.
• Clipboard handling has been recovered. Clipboard transfers could fail in either direction due to text format translation problems – resolved now.
• Mouse position tracking over multiple monitors has been fixed. Previously, coordinates of the mouse cursor could be calculated incorrectly if the primary monitor was not the leftmost and topmost one within a composite desktop.
• New version sends viewers descriptive error messages if it must close their connections in the very beginning of the session. For example, if the server does not allow "loopback" connections, the viewer will report that fact. Similarly, the viewer should report other errors like protocol version mismatch or rejects caused by repetitive authentication failures.
• Several useful command-line options have been re-implemented: -connect, -disconnectall, -reload, -shutdown (they must be preceded with either -controlservice or -controlapp in the command line). Similar options (with slightly different names) were supported by TightVNC 1.x, but there were no counterparts available in TightVNC 2.0 Beta 1. You requested them, and here they are.
• Compatibility with other software has been improved. In particular, palette-based pixel formats are now properly supported. TightVNC Viewer never requests indexed colors, but other RFB-compliant software may do that. Previous version of the TightVNC Server could calculate palette colors incorrectly, effectively converting all colors to black. That issue has been resolved.
• In TightVNC file transfer protocol, file modification timestamps are represented in milliseconds. However, previous version erroneously decreased precision and actually operated with pure seconds. That has been fixed.
• There was a number of other improvements, including architectural adjustments, additional logging, fixes for real and potential memory leaks, code cleanups, and so on.

Part 3. Changes in TightVNC Viewer for Windows

• A bug with registering .vnc file extension has been fixed. The viewer wrote incorrect command line to the registry and then could not restore connections saved in .vnc files.
• Keyboard handling has been improved. New version is able to send Windows and Menu keys over the RFB protocol (and new TightVNC Server can handle that correctly).
• File modification time format has been corrected in file transfer panels. Timestamps were formatted in UTC for some reason, but now they should show up in local time zone, as we would normally expect that.
• "Local cursor shape" setting has been recovered. Now it should take immediate effect on pressing the Ok button in the Connection Options window. In addition, pressing that Ok button would not hide remote cursor – that was another bug fixed in this version.
• TightVNC Viewer could write repetitive entries to the connection history and it could create meaningless directories in the registry when parsing its command line. Both problems have been fixed.

Note that the above list does not pretend to be complete. Other minor improvements and fixes have been made as well.

[redge]

TightVNC 2.0 Beta 3 built 29 April 2010
http://www.tightvnc.com/download-beta.php

What's New?
Part 1. Improved Keyboard Handling

This Beta version is focused on keyboard handling. There have been a lot of problems in this area, so we've decided to put more effort into this. New version comes with a lot of keyboard-related enhancements in both server and viewer code. In particular, new version should provide better support for national keyboard layouts. What we are trying to achieve is to enable international characters to be passed via the RFB protocol correctly. Unfortunately, the protocol works with characters, not key codes, and that makes things very complicated.

In addition, we've fixed a number of bugs, including major ones causing TightVNC to crash under certain circumstances. Most important bugfixes are listed below.

Part 2. TightVNC Server

• A bug with clipboard handling has been fixed. When running as a service, TightVNC Server could crash if a user copied something to the clipboard.
• There was a bug which caused the control interface to crash if the server had a lot of IP addresses. This bug was experienced by users of software that uses to add a number of "virtual" network interfaces and addresses, such as VMWare. The problem has been resolved.
• File uploads could fail at changing file modification timestamps. Fixed now.
• Web access should be enabled by default. It was a bug that it defaulted to the disabled state.

Part 3. TightVNC Viewer

• When run with the -help command-line option, the viewer listed a lot of options it actually does not support. This has been fixed. Unsupported options have been removed, while supported options have received better documentation.
• Unsupported command-line options were treated as host names to connect to. Now the viewer will report error messages on discovering unknown options in the command line.
• The viewer used to connect to nowhere if it could not read the specified .vnc file. Now it should exit correctly after showing the error message.
• In connection options, the check box "Request shared session" should be disabled after the connection has been established, as it makes sense only on entering the session. Now its state should be set correctly.

[B]

Thanks for staying on top of this, redge. Looks good. (And the spammer in this thread should... never mind.)

[redge]

What's New in Beta 4 (since Beta 3)? (19 May 2010)

TightVNC Server

• The server should simulate pressing AltGr (Alt and Ctrl) to produce characters that would be entered with AltGr in current keyboard layout. Beta 3 failed to do that.
• Cursor shape updates were encoded and sent incorrectly if the cursor width was not a multiple of 16. That led to disconnects due to broken protocol synchronization. This issue has been fixed.
• Control interface erroneously tried to read configuration from the registry after it was already given that configuration by the service. That could cause IP access control rules to disappear from the configuration under certain circumstances. The problem has been fixed now.
• Registry entries could be created with wrong permissions while writing configuration or installing initial service-mode passwords. Fixed as well.
• Solved the problem of not shutting down the control interface if the tray menu was open at the moment of shutdown.
• More logging has been added to trace RFB initialization sequence for client connections.
• Fixed a problem with sending framebuffer updates for screen areas beyond the requested region.

TightVNC Viewer

• New version fixes problems with sending key combinations like Ctrl+A, Ctrl+[ or Ctrl+Shift+^ that should produce control characters with ASCII codes below 32.
• Various other key combinations with Ctrl and AltGr have been fixed.
• CapsLock functionality has been recovered. It was broken in Beta 3.
• Key codes have been corrected for a number of keys: F1, F2, F3, F4, "=".
• New viewer will reset keyboard modifiers to their actual state on restoring keyboard focus. That was a long-term problem of the viewer. After leaving the viewer window with Alt+Tab and returning to the viewer again, Alt could get "stuck" and one would need to press Alt once again to restore correct keyboard handling. We've eliminated that problem at last.
• "Win" key presses will not be propagated to the server any more. Otherwise, combinations like Win+R would have both local effect (e.g. open the "Run" prompt) and also open the Start menu remotely.
• Special ScrollLock functionality has been restored. When ScrollLock is on, the viewer will send Meta on pressing Alt. This may be handy when working on Unix servers.
• Fixed a problem with adjusting the listening port number using arrow buttons near the text field. It could add thousands separator and produce invalid numbers in the text field.

Installer and Uninstaller

• Uninstaller did not remove TightVNC entries from Add/Remove Programs list. Beta 4 not only fixes the uninstaller itself but also its installer removes invalid entries left by previous Beta versions
• Installer tries to recover registry entries created with wrong permissions by previous Beta versions. Correct permissions to the service-mode configuration should give access only to SYSTEM and to the Administrators group.

[redge]

who interesting for open source.
cost 10'000 $ US for improve speed up of tightvnc for 2 month of developers full time.

[supercoe]

I don't understand redge, can you explain more?

[averkiev]

Hi,
we have just published the property reference for our TightVNC 2.0 MSI deployment package. The package is included in the VNC Manager 5.5.16.0 or newer builds.

DISCLAMER You may use TightVNC 2.0 (Repackaged by SmartCode Solutions) MSI package only if you have a license for SmartCode VNC Manager (Enterprise Edition) purchased.

The reference can be found here:
http://www.s-code.com/kayako/index.php? ... &nav=0,1,5

[mod=494,1297025950]merged to tightvnc[/mod]

[redge]

supercoe

if you need to improve the core for speedup of tightvnc 2.0
you need to spend 10000 $

[averkiev]

Our TightVNC MSI installer has been updated to install TightVNC 2.0 RTM binaries. The updated installer is included in the VNC Manager 5.5.17.0 build.

[redge]

July 1, 2010 – GlavSoft LLC. has released TightVNC version 2.0.

TightVNC is a free software package that shows the desktop of a remote computer and allows to control it with local mouse and keyboard, just like it was a local computer. TightVNC comes with full source code which is GPL-licensed. It's free even for commercial usage (technical support and customization services can be ordered separately).

TightVNC 2.0 delivers completely new TightVNC Server for Windows. It was redesigned and reimplemented from scratch. It features new component-based architecture compatible with the latest operating systems, Windows 7 and Windows 2008 Server R2. Older versions of Windows are supported as well – the minimum requirement is Windows 2000.

New TightVNC Server demonstrates improved user interface and offers better administrative functions such as IP-based access control and password protection for administrative actions. It implements new file transfer protocol, adds better support for national keyboard layouts, features new installer, and includes a lot of other major and minor enhancements.

TightVNC 2.0 can be downloaded from the TightVNC Web site:

http://www.tightvnc.com/download.php


About the company

GlavSoft LLC. was founded by Constantin Kaplinsky, originator and lead developer of the TightVNC project. The company maintains TightVNC and customizes it for corporate customers, develops commercial software and offers technical support services.

[redge]

July 8, 2010 – TightVNC 2.0.2 is available

TightVNC 2.0.2 fixes a packaging issue with previous version and includes the fix for Windows DPI scaling feature (that fix was announced in 2.0.1 but was not actually included there). Also, this version adds another small fix for clipboard transfers. Download Now!

[jj]

Do you guys face problem in File Transfer? I am able to connect to VNC server but the file transfer just could not. It say Error folder at the bottom. Do you guys got any idea what's wrong?