Why does the machine or applications on the machine running the Kaseya Agent experience errors and instability when the Network Driver Access is enabled?
This includes Active Directory / LDAP, Oracle, HP Photosmart and Office all-in-one printers, Sage Software ACT! applications and other programs which attempt to access the network stack at a low level.
There may also be TCP/IP related errors in the event logs.
Crash dumps may refer to a driver called 'kaseyasp.dll'
To monitor and control network access on a per application basis, Kaseya's Network Access Driver inserts a service provider into the TCP/IP stack using a method well defined by Windows programming standards. This technique works well for all programs that conform to Microsoft's programming guidelines for network communications. In some cases other applications or drivers may also have direct access to the TCP/IP stack, and this can cause incompatible operation which may break the TCP/IP stack.
There is currently no fix for this, other than to disable the network access driver, stop the Kaseya Agent service, and reboot the affected systems.
To re-enable the driver properly, once the machine has been rebooted, enable the network access driver, stop the Kaseya Agent service, and reboot the same systems.
The features provided by the Network Acces driver are network statistics and access control to the network by applications. If this is not needed, then there is no need to enable this. See http://help.kaseya.com/WebHelp/EN/VSA-Online-Help.asp?407.htm for further information about this feature as well.
If the machine is still able to check into the Kaseya server, disable the driver using Audit tab > Network Access and then reboot the machine. If the TCP/IP stack is broken, running "netsh winsockreset" may restore communication to the machines where a crash has happened and allow unloading of the driver via the Kaseya UI.
Kaseya Windows Agents