Barracuda Networks SP4 User Manual download pdf (Page 6)

6 Migration Instructions - Bugfixes Included with Barracuda NG Network Access Client SP4

Bugfixes Included with

Barracuda NG Network Access Client SP4

Table 1–2 Bugfixes

Description

(13431) When using different interfaces, e.g. WLAN, UMTS and LAN, the Client did occasionally not work properly. This issue

was fixed.

(12701) While in reconnecting state, the Client did not react properly on the rvpn -d command issued through the CLI. This

issue was fixed.

(12832) An issue regarding the IsActiveDirectoryAccessibility setting of the Direct Access feature was fixed.

(12841) Occasionally, the Client was not properly recognizing whether currently an Active Directory server is accessible or not,

some times resulting in unwanted VPN reconnection attempts due to AD servers becoming accessible through a connected LAN.

This issue was fixed.

(12846) With enabled Direct Access, connections were erroneously initiated although no IP address was available locally. This

issue was fixed.

(12858) Clicking Connect within the tray window erroneously always brought the Client up with the default profile instead of using

the Current Profile as displayed within the tray window. This issue was fixed.

(12869) In very rare cases, the Client used to crash due to a problem with DNS.DLL. This issue was fixed.

(12873) In rare cases, the Client was not able to determine a virtual adapter’s IP address. This issue was fixed.

(12927) In rare cases, the Client’s system tray icon would stall. This issue was fixed.

(12936) In very are cases, the Client’s internal system check could not detect the correct IP address of a virtual adapter if, at the

same tim,e a WMI script assigned to it was active. This issue was fixed.

(12953) Under certain circumstances, Direct Access activity stopped although it should have been continuing to work. This issue

was fixed.

(13156) The Client did erroneously not re-route transports as intended on changing VPN profiles offering different routes. Instead,

it kept the old routes. This issue waa fixed.

(13394) The Client’s automatic update function did erroneously not test for file violation errors, resulting in failing update attempts

due to non-writeable or non-readable files. This issue was fixed.

(13289) Symantec and WinDefender were erroneously not recognized by the Health Agent. This issue was fixed.

(13290) Under certain circumstances, share mounts within virtual machines were erroneously blocked. This issue was fixed.

(12955) It was erroneously not possible to use the Client’s virtual keyboard for filling in the password field. This issue was fixed.

(13139) If a VPN connection had disabled the built-in Windows firewall in order to enable the NAC Firewall, the Windows firewall

was not automatically re-enabled as intended after terminating the connection. This issue was fixed.

(13137) The built-in Windows firewall was not properly fed with information by the Client and therefore did not recognize the NAC

Firewall even if the Client was active. This issue was fixed.

(12826) An issue regarding application lookup was fixed.

(13399) Occasionally, the firewall was erroneously activated on virtual adapters although it had been configured not to do so. This

issue was fixed.

(13423) VPN Probing did erroneously not use internal firewall rules for its purposes. This issue was fixed.

(12850) An issue regarding popups and notifications was fixed.

(13460) In rare cases, the Client’s host route protection tried to use the wrong interface IP address due to a missing internal

lookup function to recognize IP address changes. This issue was fixed.

1 2 3 4 5 6 7 8 9 10

No comments

Barracuda Networks SP4 User Manual Page 6