Critical Impact


Internet Security And Acceleration Server The Firewall Service Cannot Initialize WinSock, Registry Corruption Or Out Of Memory

AIS Monitoring Platform has discovered that the ISA firewall Service failure because the system is probably out of memory, or the registry might be corrupted. Check the Firewall service configuration. Try to stop, and then restart the Firewall service. To do this, click Start, point to All Programs, point to Administrative Tools, and then click Services. Select Microsoft Firewall and click Restart the service. If this does not work, restart the computer.

ISA Server Control Not In Running State

This alert condition indicates that the ISA Server Control service is not running.

ISA Server Control Not In Running State [Unexpected]

This alert condition indicates that the ISA Server Control service terminated unexpectedly.

ISA SERVER Detected A Possible Land Attack

AIS Monitoring Platform has observed an land attack was attempted against a computer protected by ISA Server. This alert occurs when a Transmission Control Protocol (TCP) SYN packet or User Datagram Protocol (UDP) packet is sent with a spoofed source Internet Protocol (IP) address and port number that is identical to that of the destination IP address and port. The effect of this makes it appear that the host computer has sent a packet to itself. If this attack is successful, then a loop is created and the computer crashes.

ISA Server Web Filters Cannot Be Initialized

AIS Monitoring Platform has observed Web filters either cannot be initialized, or recent configuration changes cannot be applied. This issue may occur if a Web publishing rule is corrupted in the Microsoft Internet Security and Acceleration (ISA) Server 2006 or ISA Server 2004 firewall policy.

Last modified April 17, 2020