(·Tightly integrated with ISAServer and support remote management; ·Support real-time bandwidth limit and total traffic limit; ·Support limit on IP and user account; ·Support limit group total or limit individual IP/user in group; ·Can Limit the number of concurrent connection requests of users, which is a good complement to the ISAServer connection limit defect (there are only two types of connection limits); Support no bandwidth limit for Web cache access; Ability to monitor the running status of each rule in real time and details; ·Highly functional, extremely low impact on system functions; ·Transparent to end users, no need for users to install any client software; ·Support HTTP acceleration function; ·Strictly integrated with ISAServer (of course, this is also its disadvantage, It can only be used together with ISAServer); Supports bandwidth control for user accounts; Supports limiting the number of concurrent connection requests for users; Cache access is not limited by bandwidth; the tight integration of BS and ISAServer is mainly in the following four aspects: The configuration data of BS and ISAServer are stored together; The management console of BS is integrated with the management console of ISAServer ; BS runs as the application selector of ISAServer; BS uses the policy element in ISAServer as its own policy element; BS only runs as the application selector of ISAServer, it will not affect the original rules and configuration of ISAServer , it only provides bandwidth management functions on the basis of ISAServer, but it has a lower priority than the firewall policy of ISAServer, so if you want to implement bandwidth management for users, you must first allow the user's firewall policy in the ISAServer access. In addition, the BS cannot manage non-TCP/UDP protocols such as ICMP protocols, etc., and the BS will not manage the connection between the local host and other non-external networks (such as internal networks, DMZ networks).)
收藏
