Advanced Client Configuration
For most WinSock programs, you do not have to change the default Firewall Client configuration. However, in some situations, you may have to add client configuration information. You can store the client configuration information in one of the following locations:
- Mspclnt.ini: This file is the global client configuration file that is located in the Firewall Client installation folder. The Mspclnt.ini file is periodically downloaded by the client from the ISA Server computer and it overwrites previous versions. As a result, if you make configuration changes at the ISA Server computer, the setting is automatically downloaded to the client.
- Wspcfg.ini: This file is located in a specific client program folder. The ISA Server computer does not overwrite this file. As a result, if you make configuration changes in this file, these changes apply only to the specific client.
The Firewall Client software looks for a Wspcfg.ini file in the folder in which the client WinSock program is installed. If this file is found, Firewall Client looks for a [
WSP_Client_App] section, where
WSP_Client_App is the name of the WinSock program without the .exe file name extension. If this section does not exist, Firewall Client looks for the
[Common Configuration] section. If this section also does not exist, Firewall Client looks for the same sections in the Mspclnt.ini file. Firewall Client uses only the first section that it finds during this search to apply the program-specific configuration settings.
Sample Wspcfg.ini file
The following text is an example of the [
WSP_Client_App] section in a client configuration file:
[WSP_Client_App]
Disable=0
NameResolution=R
LocalBindTcpPorts=7777
LocalBindUdpPorts=7000 7022, 7100 7170
RemoteBindTcpPorts=30
RemoteBindUdpPorts=3000 3050
ServerBindTcpPorts=100 300
ProxyBindIp=80:110.52.144.103, 82:110.51.0.0
KillOldSession=1
Persistent=1
ForceProxy=i:172.23.23.23
ForceCredentials=1
NameResolutionForLocalHost=L
The following list describes the possible entries that you can put in a configuration file for a WinSock program: