AfterDawn | Programas | Soporte técnico | Foros
AfterDawn.com

Historial de versiones para Hamachi

<<Regresar a la descripción del programa

Cambios para v2.2.0.279 - v2.2.0.291

  • User experience enhancements



Cambios para v2.2.0.266 - v2.2.0.279

  • Enhancements (Windows & Mac)
  • When launching an unattached Hamachi Client without signing in with a LogMeIn ID, users can start a limited version of Hamachi in order to attach the client to an account.
  • Improvements (Windows 8, 8.1 and 2012)
  • Fixed an issue that reset the bridge IP address to static instead of DHCP after a system reboot
  • Resolved an issue that caused the Windows default gateway IP address to be empty on a Hamachi Gateway Client
  • Hamachi bridge settings are now removed on uninstall
  • Other
  • Improved stability for new installations (fixed a crash caused by the login/registration window)
  • Various bug fixes



Cambios para v2.2.0.258 - v2.2.0.266

  • Windows
  • Fixed an issue where a client was created without an empty nickname
  • Other stability improvements



Cambios para v2.2.0.255 - v2.2.0.258

  • Various stability improvements



Cambios para v2.2.0.232 - v2.2.0.255

  • Various stability improvements



Cambios para v2.2.0.227 - v2.2.0.232

  • Improved LogMeIn Guardian error reporting
  • Fixed an issue with the Windows 8 driver that caused the client to crash
  • Resolved an issue in gateway networks where pending Hamachi mobile clients attempting to go online caused the client to crash



Cambios para v2.2.0.222 - v2.2.0.227

  • Various stability improvements



Cambios para v2.2.0.214 - v2.2.0.222

  • Resolved an issue where some computers did not connect after coming back from sleep state.



Cambios para v2.2.0.193 - v2.2.0.214

  • This release fixes a bug that caused system instability on high-load servers with multiple CPUs



Cambios para v2.2.0.188 - v2.2.0.193

  • Improvement: Enhanced error reporting



Cambios para v2.2.0.173 - v2.2.0.188

  • This release resolves an issue that caused the client to crash during uPNP discovery



Cambios para v2.2.0.130 - v2.2.0.170

  • - When installing Hamachi, some users will be given the option to install Google Chrome together with Hamachi.



Cambios para v2.2.0.114 - v2.2.0.130

  • This release fixes a bug that caused system instability on Window 8 and Windows 2012



Cambios para v2.2.0.109 - v2.2.0.114

  • This release fixes a bug that caused system instability and sleep-related service problems on Window 8 and Windows 2012.



Cambios para v2.2.0.100 - v2.2.0.109

  • This release fixes a bug that caused a network driver crash on Windows 8.1/2012 R2.



Cambios para v2.1.0.374 - v2.2.0.100

  • # Bug fixes
  • * When installing to Windows XP, the engine configuration directory path is set correctly
  • * LMIGuardian now installs properly to 64-bit devices



Cambios para v2.1.0.262 - v2.1.0.362

  • This release of the Hamachi client for Windows fixes a number of bugs, including the following:
  • • Hamachi ui.exe will no longer use excessive CPU resources when the Hamachi service is set to start manually
  • • The notification dialog no longer hides other dialogs
  • • The link in the notification regarding network capacity now properly communicates the ID of the network that needs to be upgraded



Cambios para v2.1.0.159 - v2.1.0.262

  • New Features
  • Online status for unattended clients
  • Until now the Hamachi client started automatically as a service and the client went online when you started or restarted your computer. As of this release, the Hamachi client for Free users only goes online in Hamachi networks if you log in to the computer that runs the Hamachi client. This feature only affects Windows and Mac users whose computers require them to log in with their user credentials.
  • System notifications
  • The client now displays system notifications in a popup window whenever there are important changes in Hamachi that LogMeIn wants to communicate.
  • Copy and ping peers by Client ID
  • You can now use mDNS or LLMNR to address your peers by their client ID rather than their dynamic virtual IP address. To do so, the following context menu options have been added to the Hamachi client:
  • •Ping [ClientID]
  • •Copy [ClientID]
  • [ClientID] stands for the Hamachi client ID of the peer. For example, you can ping a peer by right-clicking your peer’s name and clicking Ping 123-456-789.
  • Enhancements
  • Hamachi clients move to the 25.x.x.x IP range
  • As of November 19, 2012, Hamachi clients will have their virtual IP addresses changed from 5.x.x.x to 25.x.x.x. This change will have no effect on your Hamachi networks.
  • IPv6 address for the default gateway of the Hamachi adapter
  • As of this release, an IPv6 default gateway is set for the Hamachi network adapter when the IP protocol is configured to IPv6-only or Both mode. You can set the IP protocol mode in System > Preferences > Settings > Advanced Settings > Peer Connections.
  • Fixes
  • Unsuccessful client update on Fedora Linux
  • In some rare cases, the downloaded client update was not installed successfully and, as a result, the Hamachi client did not start on Fedora Linux computers.
  • Menu available in offline mode on Mac clients
  • When a client was installed for the first time, the System > Attach to LogMeIn account menu was available on Mac clients even if the client was offline.
  • Client user interface issues on Windows
  • In some cases, when an unexpected error occurred and the LogMeIn Hamachi service restarted the client interface, the client was resized, opened at a different location in the screen, and certain user interface configurations were not taken into account.
  • Hamachi Client Failing to Connect to the Hamachi Engine
  • In some cases, the Hamachi client was not able go online and displayed the following error:
  • Failed to connect to engine
  • By improving the client connection method it is now less likely to get this error.
  • Hamachi engine and client interface issues on Macs
  • In some cases, the Hamachi engine and the client stopped working due to an unexpected error.



Cambios para v1.0.1.2 - v1.0.1.3



Cambios para v1.0.1.1 - v1.0.1.2



Cambios para v1.0.0.62 Beta - v1.0.1.0



<<Regresar a la descripción del programa