Posts: 108
Joined: 19.Aug.2004
From: US
Status: offline
I recently installed the Microsoft Firewall Client (2004) on an XP laptop (all of the Microsoft Recommended Updates are installed). I have not configured the client at all. The laptop is not connected to the LAN/WAN (it is standalone). If I attempt to create or test an ODBC connection against a local database using the ODBC Administrator, the ODBC Admin hangs. It does not matter what driver I use--Pervasive, Microsoft SQL, etc.--the behavior is the same. I exited the client and tested the ODBC connection again and the ODBC Admin still hangs. I then uninstalled the client, and everything works fine again.
To test whether this was an isolated incident, I tested an ODBC connection against data on a Windows 2000 workstation (data is local) and the test was successful. I then installed the Firewall client and tested the ODBC connection--and I got the same behavior--the system hangs. I configured the client to use the ISA server and then tested ODBC--which still hangs. I exited out of the client and tested again--ODBC still hangs. I uninstalled the client--ODBC works fine again.
It appears that NT4 workstations are not affected.
Has anyone else seen this behavior (or know what might be causing it)? My company does nothing but work with databases all day--I hope there is a solution to this or all my hard work on ISA 2004 will be for nothing--because I won't be able to use it.
Posts: 108
Joined: 19.Aug.2004
From: US
Status: offline
If I'm simply configuring an ODBC connection to a LOCAL database (a database that exists on the same computer), is there anything that needs to be configured on the ISA Server?
Posts: 108
Joined: 19.Aug.2004
From: US
Status: offline
Tom,
I've been working hard to try and make the proxy client work with Pervasive SQL 2000i. Is there an easy way to tell if the app adds an LSP to the protocol stack? In Pervasive's KB, they mention "Pervasive Network Services Layer"--sounds like it is indeed a possibility.
Posts: 108
Joined: 19.Aug.2004
From: US
Status: offline
Thanks Tom,
There doesn't appear to be a test I could run to identify whether Pervasive SQL 2000i uses LSP's. However, I looked in Pervasive's settings and saw that the ODBC Administrator is set to use Winsock TCP/IP as the preferred protocol when talking to Pervasive (and there wasn't a better option). So suspicions are very high that LSP's are used.
Now that I have identified that Pervasive SQL 2000i and the Microsoft Firewall Client do not play nicely with each other, and that this very probably is due to the fact that Pervasive uses LSP's, is there anything I can do about it?
You must have run into this sort of thing before--any help you can provide would be greatly appreciated.
Posts: 108
Joined: 19.Aug.2004
From: US
Status: offline
My company develops software which supports Pervasive SQL and Microsoft SQL. Pervasive SQL and Microsoft SQL is installed on every person's computer within the organization (developers need it to develop apps, customer support needs it to support the product, sales needs it to demonstrate the product, etc.).
When I started this project, a friend of mine (who is also a LAN Admin) warned me that it took him weeks to install, configure, and test ISA Server and when he began to deploy it using the firewall client he had so many issues with the client locking up computers (because of compatibility problems with third party software) that he had to remove ISA Server altogether. He currently has that "I told you so" grin and I'm desperately looking for a way to make it work.
Posts: 478
Joined: 3.Jun.2003
From: Albuquerque NM USA
Status: offline
Hi all,
I just thought I'd point out that the freeware tool Spybot Search & Destroy can display a list of Winsock LSPs installed on a system (switch the UI to advanced mode).