Share via

ISA2004 Firewall Client "bind" error on a client

  • Article

Sorry for not getting this post out yesterday...

 

Well, yesterday was all about winsock calls in the network stack on a client machine and the ISA2004 Firewall Client.  The issue was after upgrading to ISA2004 and deploying the ISA2004 Firewall Client to the clients, a 3rd party app would give a "bind" error when it was launched.  It looked like the app was possibly a) not using the Windows networking API's or b) using the Windows API's improperly.  The workaround for this case was to set an exception in ISA2004 for the application to not use the Firewall Client.  The setting is here:  ISA Management -> Configuration -> General -> Define Firewall Client Settings.  On the Application Settings tab, click New.  In the name, type in the name of the executable on the client (don't include the .exe extension), set the Key to Disable and the Value to 1. 

 

It may take up to 6 hours for this setting to get pushed to the client.  To kick it in the pants, we rebooted the client.