FortiClient and Quickbooks/other app conflicts

We encountered a similar issue with systems that had Quickbooks installed, and then attempted to load the Forticlient software. The symptom is that the multi-user version of a Quickbooks .qbw file will not load from a network drive and a network error is displayed, and the error message points to a possible winsock problem with the TCP/IP stack. When we called Fortinet Technical Support they gave us a clue about what was going on by suggesting a utility called LSPFIX.EXE which will allow the user to disable the LSP (Layered Service Provider) .dll that may be involved in the winsock errors. Using this tool we can disable the Fortilsp.dll, but this only takes care of the symptom and does not explain the root cause. It appears that the LSPFIX.exe utility removes selected LSP providers from the winsock catalog file. We had some XP systems that installed the Forticlient and Quickbooks together without any problems, so there was some specific winsock issue with the other systems. One of my theories is that these systems had other AV products on the systems with LSP overlays that had not been completed removed using their " uninstall" scripts and/or spyware components that had not be completely removed. The methods to show and reset the winsock catalog at the command line: >netsh winsock show catalog >c:\winsock.txt will show what LSP models have been added. >netsh winsock reset catalog will reset the winsock catalog back to default, but then the LSP applications will have to be reinstalled (such as Fortclient, Google Desktop, etc.) Quickbooks 2006 uses a TCP/IP over NETBIOS and port 10160 that needs to be opened on the client and server side; at first we thought that adding the Forticlient had affected these requirements. It appears that the real issue is the winsock database conditions prior to installing the Forticlient, and I' m still working on a consistent fix. I' ll post my results after testing.