< Junos Pulse Release Notes >
© Juniper Networks, Inc.
10
logging in via the Junos Pulse client. This is only applicable to browser based initial deployments. (504952)
•
Firewalls like Kaspersky software that are known to block Pulse Application Acceleration control packets. UDP
port 3578 will have to be provisioned to open ports at the endpoint. (505817)
•
If Junos Pulse software requires the Application Acceleration capability to be deployed from an SA Series
device, ‘All’ components should be selected at the SA Series device. (505944)
•
Pulse may disrupt Internet Connection Sharing via Windows Virtual Wifi on Windows 7 Endpoints when
Application Acceleration is installed. (507628)
•
Application Acceleration may not get enabled correctly when changing the configured community string after
deploying Pulse via Host Checker. (527411)
•
An Application Acceleration adjacency can still be established between Pulse and WXC server when the
community string that was deployed to the Pulse client from an SA or IC device is removed from the
Administrator UI of the SA or IC device. (527660)
•
When creating a WX Connection in the SA Series or IC Series device Administrator UI, do not use a blank
value for the Community String property. (527732)
Communicating Issues
To open a case or to obtain support information, please visit the Juniper Networks Support Site:
http://www.juniper.net/support
.
