Release Notes

    Current version:
    Build 4.1.0.1994
    released on November 16, 2006

    Windows 2000/2003/XP

Usergate proxy release history


Build 4.1.0.1994 (16.11.2006)


What was fixed?
  • When installing over a previous build, Usergate server could not start due to an improperly converted database.
  • Exceeding a traffic limit could lead to an incorrect representation of traffic remaining in a users’ statistics.
  • The incorporated SMTP proxy would not work in non-transparent mode.
  • Under certain circumstances a “Buffer overrun detected” error occurred.

Build 4.1.0.1951 (13.11.2006)


What’s new?
  • A LAN adapter selector was added to the installation wizard.
  • POP3 and SMTP protocol support was built in at the top level, so Kaspersky antivirus can now check mail traffic. Both proxies can now work in transparent mode.
  • Usergate FTP proxy can operate in transparent mode now.
  • We have added a Usergate Cache Explorer module. Now you can examine Usergate Cache files.
  • Usergate Server was added to the Statistics & Administration module.
  • A special folder for suspicious and infected files was added to the Usergate folder. We also added a separate log file for antivirus.
  • Usergate HTTP proxy now supports FTP over HTTP.
What was fixed?
  • Some URL filters would lead to incorrect program behavior.
  • The action “Drop dial-up connection” in Usergate scheduler would not perform.
  • Under certain circumstances a pending user session would appear.
  • Incorrect DNS request caching could lead to URL substitution.
  • Several copies of Usergate authorization client could be started simultaneously.
  • Usergate authorization client could not find Usergate server if it was started as a service.

Build 4.1.0.1746 (06.07.2006)


What’s new?
  • The Usergate Administration module now contains a network and processor performance monitor.

Build 4.1.0.1711 (30.06.2006)


What’s new?
  • It is now possible to make several parent proxies in Usergate Administrator module.
  • The action “change connection speed” was added to Usergate traffic management rules.
  • A new authorization client was added.
  • The Usergate NAT driver can translate the ICMP protocol
What was fixed?
  • Resource publishing would not work in some cases.
  • Usergate Server would sometimes stop during simple HTTP browsing.
  • The Usergate NAT driver would not work if DHCP Server was used for IP address assignments.
  • The “Import URL filters” option did not work in the Traffic Management rules wizard.

Build 4.1.0.1640 (03.06.2006)


What’s new?
  • Using HTTP authorization Usergate proxy now supports users working from a terminal server.
  • A firewall log file was added
What was fixed?
  • Under certain circumstances Usergate FTP proxy could hang up.
  • Billing plans could not be changed for FTP connections.
  • Usergate Server would crash during multiple user connections if Usergate Administrator was used.
  • The connection speed limit doesn’t work for FTP connections in active mode.
  • Usergate cache could contain corrupted files

Build 4.0.0.1590 (26.04.2006)


What’s new?
  • The Usergate NAT driver can translate PPTP and L2TP/IPSec protocols
What was fixed?
  • In some cases the Usergate database could contain incorrect URLs.
  • High CPU loads would happen while downloading files through FTP Proxy.
  • Usergate Server would crash because of multiple threads in the download manager.
  • In some cases user’s personal statistics page can contain incorrect day and month traffic remaining.

Build 4.0.0.1492 (10.04.2006)


What’s new?
  • Ethernet headers now can be monitored for traffic accounting.
What was fixed?
  • In some cases the Usergate database could contain an empty destination host address.
  • Incorrect traffic accounting between Usergate and a parent proxy on 127.0.0.1.

Build 4.0.0.1486 (07.03.2006)


What was fixed?
  • The Usergate cache would not work properly with a transparent HTTP proxy.

Build 4.0.0.1457 (03.02.2006)


What was fixed?
  • Usergate Server could crash during an antivirus startup.
  • Usergate caused a high CPU load when a dial-up connection was used.
  • Usergate could crash using a parent proxy for Socks.

Build 4.0.0.1433 (28.12.2005)


What was fixed?
  • Some mistakes in the Usergate Administrator module.
  • The Usergate NAT driver was optimized for better performance.
  • The connection speed limit algorithm.

Twitter