Configuring the Client Setup Program
Installing Clients
Removing Clients
Reviewing the Client Setup Log
Web Proxy Clients
WinSock Proxy Clients
Using the WSP Client Application
Creating a Local LAT File
Editing the Mspclnt.ini File
Configuring Windows Sockets Applications
During Microsoft Proxy Server setup, you are asked to complete a Client Configuration dialog box. The options in this dialog box are used to create an Mspclnt.ini file, which is installed on the server, along with a client Setup program. Later, when a client connects to the server and runs the client Setup program, the Mspclnt.ini file is copied to the client, and determines its client configuration parameters. For information about using the Microsoft Proxy Server Setup program and completing the Client Configuration dialog box, see Server Installation.
If you need to change the servers copy of the Mspclnt.ini file after a server has been installed, you can:
Use a text editor to modify the servers Mspclnt.ini file, which is installed into the Msp\Clients folder on the server. (See Editing the Mspclnt.ini File, later in this chapter.)
If you need to change a clients copy of the Mspclnt.ini file after a client has been installed, you can:
Refresh the clients copy of the file by downloading the current version from the server, as described in Using the WSP Client Control Panel Application, later in this chapter.
Running Client Setup
Reinstalling a Client
Installing on a Dual-Boot Client
Running Client Setup from the Command Line
For information about upgrading a client from a preliminary release of Microsoft Proxy Server, see the Readme.txt file provided on the Microsoft Proxy Server compact disc.
You can set up a client computer by using either the Setup program or a Web browser.
To set up a client computer using the Setup program
For example, for the server Wolfhound, you would connect to \\Wolfhound\Mspclnt.
The client components will be installed, and the client computer will be configured according to the settings of the Mspclnt.ini file.
To set up a client computer using the clients Web browser
For example, for the server Delaney, you would type http://Delaney/Msproxy.
If the browser proxy settings configured by client Setup are not appropriate for a particular client, or if a clients Web browser is not Microsoft Internet Explorer or Netscape Navigator, then you must use the Web browsers own configuration interface to specify the name of the computer running Microsoft Proxy Server and the protocol port number. For more information see Web Proxy Clients, later in this chapter.
After installing a client, if you need to reinstall you can rerun Setup.
To use Setup to reinstall a client
Or
Connect to the Mspclnt share on the server and rerun client Setup from there, as described in Running Client Setup.
For computers running Windows 95 or Windows NT 4.0, you can also reinstall client software by using Control Panel.
It is possible to run client Setup and install the WinSock Proxy client software on a dual-boot computer. Client Setup should be run twice (once for each operating system). After the first installation, you must specify a different client directory. For example, install client software on the Windows NT operating system, then install client software on the Windows 95 operating system in a different directory.
Optionally, you can run client Setup from the command line and take advantage of the command-line options. The client Setup syntax is as follows:
setup [/r] [/u] [/q[1,t]]
where
- /r
Reinstalls the client.
Note The /r switch cannot be used with 16-bit clients (computers running Microsoft Windows 3.1 or Microsoft Windows for Workgroups).
- /u
Removes the client application but leaves shared components.
Note The /u switch cannot be used with 16-bit clients (computers running Microsoft Windows 3.1 or Microsoft Windows for Workgroups).
- /q
Runs client Setup in quiet setup mode. The screen displays progress windows and a Setup completion dialog box, but does not prompt the user to approve or modify installation settings. Quiet setup will always install the client software into the default directory (Mspclnt).
Note You can only use quiet mode for an initial setup. If a client is already installed, you cannot reinstall or remove it by using the /q option.
- /q1
Same as /q, but also hides the Setup completion dialog box.
- /qt
- Same as /q, but also hides the progress windows and completion dialog box. (After installation completes, the client computer will be restarted if a restart is required by the Setup program.)
The Uninstall Proxy Client dialog box appears.
All installed client components are removed from the computer.
You can also remove the client software by using the Setup program, but you must be connected to the Mspclnt share on the server.
Or
Connect to the Mspclnt share on the server and run client Setup from there, as described in Running Setup.
You can also remove client software by using Control Panel.
During client installation, the client Setup program creates a log, Mpcsetup.log, and places it in the root directory of the drive where the client is installed. (This location is C:\Mpcsetup.log.) If you encounter problems with client Setup, review this log by using any text editor (such as Microsoft WordPad or Microsoft Notepad).
About Web Proxy Clients
Configuring the Internet Application in Control Panel
Configuring Microsoft Internet Explorer 3.0 Clients
Configuring Microsoft Internet Explorer 1.5 Clients
Configuring Netscape Navigator Clients
Configuring Apple Macintosh Clients
Configuring UNIX Clients
Configuring the Servers Browser
Web Proxy Client Considerations
The term Web Proxy client refers to a client computer whose Web browser is configured to use the Web Proxy service on a Microsoft Proxy Server. Usually, this is accomplished by running the client Setup program, as described in Installing Clients earlier in this chapter.
If the browser proxy settings configured by client Setup are not appropriate for a particular client, you can reconfigure that clients Web browser (by using the Web browsers own configuration interface) after installing the client software. Also, if a clients Web browser is not Microsoft Internet Explorer or Netscape Navigator, or if client Setup does not successfully configure a clients Web browser to use the Web Proxy service, then you must use the Web browsers own configuration interface to specify the name of the appropriate Microsoft Proxy Server and the protocol port number (usually 80).
Each browser is configured through its own user interface. Typically, an applications relevant settings are found in menu items called Options, Preferences, or Settings. You can configure Internet Explorer by using the Internet application in Control Panel.
When you run client Setup, it will configure Microsoft Internet Explorer 2.0 as a client of Microsoft Proxy Server. However, you can also use the Internet application in Control Panel to specify the name of the Microsoft Proxy Server and the protocol port number. Internet Explorer 2.0 uses the settings from the Internet application, but other client applications may have their own property sheets or dialog boxes for their proxy service settings.
Open Control Panel and click the Internet icon.
Select the Advanced tab.
Select the Use Proxy Server check box.
In the Proxy Server box, type the protocol, proxy server name, and port number (for example, http://myproxy:80.)
Optionally, in the Bypass Proxy On box, type the name of computers, domains, and ports through which client applications can request objects without going through the Web Proxy service. For example, type domainname.com:80 to gain access to computers inside domainname and to services running on port 80 without using the Web Proxy service.
This option is useful if you want to access Internet servers within your private network.
When you run the client Setup program, it will configure Microsoft Internet Explorer 3.0 as a client of Microsoft Proxy Server. However, you can also use the browsers own configuration interface to set this up.
You can also configure the browser while it is running
Internet Explorer 1.5 is available for computers running the Windows NT 3.51 and Windows 3.x operating systems.
Start Internet Explorer, click the Tools menu, and click Set Proxy Server.
The Set Proxy Server dialog box appears.
Select the Use Proxy Server check box.
In the Proxy Server box, type the name of the server.
In the box after the colon, type the protocol port number (for example, 80).
When you run the client Setup program, it will configure Netscape Navigator as a client of Microsoft Proxy Server. However, you can also use the browsers own configuration interface to set this up.
In Netscape Navigator 2.01 for Windows NT and for Windows 95, you define the name of the computer running Microsoft Proxy Server and the port number for each protocol.
For each protocol you use with the Web Proxy service, you define a Microsoft Proxy Server name and port number in the Proxies property sheet.
To configure an Apple Macintosh client application running under UNIX, you need to specify the name of the computer running Web Proxy service and the Microsoft Proxy Server port number for the client protocol.
To configure a UNIX client application running under UNIX, you need to specify the name of the computer running Web Proxy service and the Microsoft Proxy Server port number for the client protocol.
If you use a browser from the server computer that is running Microsoft Proxy Server, and if that browser is configured as a client, you must configure that browser to use as its proxy the IP address of the servers network adapter card that is connected to the private network. Do not use the servers computer name or DNS name.
If you configure the servers browser to use the computer or DNS name, this name can be resolved to the IP address of a network adapter card connected to the Internet. When this occurs, requests from that browser will be filtered (because the LAT should not contain that IP address) and an Access is denied error will be returned.
Following are some considerations about Web Proxy clients:
Do not configure Helper applications to use the Web Proxy service. For example, the RealAudio player is used with the WinSock Proxy service. Do not configure the RealAudio client to use Microsoft Proxy Server. When configuring the RealAudio player, in the Proxy tab of the Preferences dialog box, specify no proxy.
The Web browser of a client running only IPX (not running TCP) will not be able to connect to the Web Proxy service on Microsoft Proxy Server if Microsoft Proxy Server is defined in the browser by using a domain or computer name. This can be remedied by editing the clients Web browser configuration to specify an IP address (not a computer or domain name) for the proxy.
Or
When installing Microsoft Proxy Server, in the server Setup programs Client Installation/Configuration dialog box, for Web Proxy Client type an IP address instead of a computer or domain name.
Then, when a client computer runs client Setup from the servers share, if the client browser is Microsoft Internet Explorer or Netscape Navigator, client Setup attempts to configure that browser to use the IP address of the specified Microsoft Proxy Server.
Note that when assigning multiple computers running Microsoft Proxy Server to clients in this manner, balance the load between Microsoft Proxy Servers by appropriately adjusting the number of IPX-only clients assigned to each computer running Microsoft Proxy Server.
A Domain Credentials dialog box may appear when you attempt to establish a connection using 16-bit client software from computers running the Microsoft Windows 95 or Microsoft Windows for Workgroups operating systems. To complete this dialog box and complete the connection request, supply a valid domain name, user name and password.
When a client sends a Gopher request, if the Gopher server supports Gopher Plus, then Gopher Plus tags are returned to the client by the Web Proxy service.
About WinSock Proxy Clients
WinSock Proxy Client Considerations
The term WinSock Proxy client refers to a client computer that is configured to use the Web Proxy service on a Microsoft Proxy Server. The WinSock Proxy client components are installed by running the client Setup program, as described in Installing Clients earlier in this chapter. The client Setup program does not configure individual Windows Sockets applications. Instead, the client computer is configured to use the WinSock Proxy service on a server. All Windows Sockets applications on that computer access the Internet through the WinSock Proxy service on Microsoft Proxy Server.
The WinSock Proxy service supports Windows Sockets version 1.1 applications. Before a Windows Sockets application can access the Internet through Microsoft Proxy Server, the server must be configured to permit access for the required protocol on the required outbound and inbound ports. For details on configuring server support for particular Windows Sockets client applications, see Configuring the WinSock Proxy Service.
In a private network with multiple Microsoft Proxy Server gateways, install an equal number of WinSock Proxy clients from each gateway to balance Internet traffic across all the gateways. For information about configuring multiple Microsoft Proxy Server gateways, see Server Administration.
Following are some considerations for WinSock Proxy client computers:
Even if the configuration parameters for the application allow it, do not set a Windows Sockets application on a computer configured as a WinSock Proxy client to use Microsoft Proxy Server.
Microsoft Exchange client software and WinSock Proxy client software can be installed on the same computer. However, do not install Microsoft Exchange Server software and WinSock Proxy client software on the same computer.
A Domain Credentials dialog box may appear when you attempt to establish a connection by using 16-bit client software from computers running the Microsoft Windows 95 or Microsoft Windows for Workgroups operating systems. To complete this dialog box and complete the connection request, supply a valid domain name, user name, and password.
If the Microsoft Proxy Server client software is installed on a computer that runs the Windows NT operating system, and the operating system is later upgraded, the WinSock Proxy client software will be disabled. To re-enable the computer as an WinSock Proxy client, reinstall the client software by running the client Setup program as described in Installing Clients, earlier in this chapter.
This could occur, for example, if you install the Microsoft Proxy Server client software on a computer running the Windows NT Workstation 3.51 operating system, and then upgrade that computer to Windows NT Workstation version 4.0.
Use the WSP Client application in Control Panel to enable or disable the WinSock Proxy client software, change the server from which client configuration files are downloaded, and download fresh copies of the WinSock Proxy client configuration files from that server.
Turning the WinSock Proxy Client On or Off
Changing the Server Used to Download Client Configuration Files
Updating the WinSock Proxy Client Configuration Files
After a computer has the WinSock Proxy client software installed, it is able to use Windows Sockets applications to access Internet sites through Microsoft Proxy Server on the corporate network. However, unless the WinSock Proxy client is turned off, the computer will be unable to use Windows Sockets applications to access any Internet sites through a dial-up connection to a private Internet service provider (ISP). This might occur, for example, if a user has a home computer that is sometimes used to connect to the corporate network, and other times to a private ISP. You can turn the WinSock Proxy client on and off by using the WSP Client application in the Control Panel.
From the client computer, open Control Panel and double-click the WSP Client icon.
The Microsoft WinSock Proxy Client dialog box appears.
Select or clear the Enable WinSock Proxy Client check box.
To turn on the WinSock Proxy client software and use Windows Sockets applications with Microsoft Proxy Server, select the Enable WinSock Proxy Client check box.
To turn off the WinSock Proxy client software and use Windows Sockets applications with a private ISP, clear the Enable WinSock Proxy Client check box.
Click
OK, then reboot the computer.
The WSP Client application can be used to change the server from which a computer downloads client configuration files. (Note that this is not necessarily the same server that the computer uses to access the Internet. That server is defined in the downloaded Mspclnt.ini file.)
The Microsoft WinSock Proxy Client dialog box appears.
Note The entry in the Configuration Location box must be a computer name. It cannot be a DNS name that resolves to multiple IP addresses.
The client is set to use the new
server as the source of its client configuration files,
and those files are downloaded to the client.
To update client configuration files, you can force an immediate download of client configuration files from the server to the client.
The Microsoft WinSock Proxy Client dialog box appears.
Fresh copies of the client configuration files are downloaded from the server to the client.
When the client Setup program runs, it installs a file named Msplat.txt into the Mspclnt directory on the client computer. The Msplat.txt file contains the Local Address Table (LAT), which defines the IP addresses of the private network.
In some situations the LAT table downloaded by the server may not completely define some addresses that a particular client needs to access in the private network. To correct this condition, you can edit the LAT on the server (which would propagate the updated LAT to all its clients) or you can create a local LAT for a particular client. You might create a local LAT, for example, to allow client access to a private subnet inside a private network.
To create a custom LAT table for a particular client, do not edit the clients copy of the Msplat.txt file, because each clients Msplat.txt file is overwritten at regular intervals by a fresh version downloaded from the server. Any changes you make locally are lost each time the server updates the file.
Instead, to create a custom LAT file for a client, use a text editor to create a file named Locallat.txt, and place it in the clients Mspclnt directory. In this way you can add additional IP address ranges that the client recognizes as part of the private network. The client will use both the Msplat.txt and Locallat.txt files to determine which IP addresses are part of the private network (and can be directly communicated with) and which IP addresses are on the Internet (and must be communicated with through Microsoft Proxy Server).
When creating a Locallat.txt table, enter IP address pairs in the file. Each address pair defines either a range of IP addresses (from the first, lower-number address to the second, higher-number address), or a single IP address (if both addresses of the pair are identical). The following is an example of a Locallat.txt file that has two entries. The first entry is an IP address range, and the second is a single IP address.
10.51.0.0 10.51.255.255 10.52.144.103 10.52.144.103
Note that the second entry is an IP address (not a subnet mask).
The Mspclnt.ini file contains client configuration information. The master copy of the Mspclnt.ini file is created by the Microsoft Proxy Server Setup program and is stored in the Msp\Clients folder on the server. Each instance of client software that is installed from a server receives a copy of the Mspclnt.ini file, which is stored in the Mspclnt folder on the client. The Mspclnt.ini file can be modified by using a text editor (such as Microsoft WordPad).
The following is a sample Mspclnt.ini file.
[Master Config]
Path1=\\COLLIE2\Mspclnt\
[Servers Ip Addresses]
Name=COLLIE
[Servers Ipx Addresses]
Addr1=00002610-0080d830525f
[Common]
Port=1745
Configuration Refresh Time (Hours)=6
Set Browsers to use Proxy=1
WWW-Proxy=COLLIE
WebProxyPort=80
The following table describes the entries in the Mspclnt.ini file.
Section | Entry | Description |
---|---|---|
[Master Config] | Path1 | A UNC path to the shared network directory on the server, containing the master copy of the client configuration files. |
[Servers IP addresses] | Name | The computer or DNS name for the WinSock Proxy server used by the client. (This entry will not appear if an IP address is used.) |
[Servers IP addresses] | Addr1 | The IP address of the WinSock Proxy server used by the client. (This entry will not appear if a computer or DNS name is used.) Additional entries are shown as Addr2, Addr3, and so on. |
[Servers Ipx Addresses] | Addr1 | The IPX address of the WinSock Proxy server. Additional entries are shown as Addr2, Addr3, and so on. |
[Common] | Port | The port Microsoft Proxy Server
uses for the control channel. This value will rarely be changed. It should be changed by the administrator on the servers master copy of the Mspclnt.ini file only if there is a conflict with another service on the server. This value should never be edited in the clients copy of the Mspclnt.ini file. |
[Common] | Configuration Refresh Time (Hours) | At this interval, specified in hours, the client will ask the server to download a fresh copy of the Local Address Table (Msplat.txt). |
[Common] | Set Browsers to use Proxy | In the servers file, set this value to 1 to have the client Setup program configure the client computers browser to use the proxy server defined in the WWW Proxy field. Set the value to 0 to prevent the client Setup program from configuring clients to use a proxy server. This field has no effect on the clients version of the file. |
[Common] | LocalDomains | A list of suffixes for names that will be resolved locally, separated by commas (,). Domain names that end in the listed strings are resolved at the client. |
[Common] | WWW-Proxy | In the servers file, if Set Browsers to Use Proxy is set to 1, the client Setup program will configure client browsers to use the proxy server named here. This field has no effect on the clients version of the file. |
[Common] | WebProxyPort | The listen-on port used by the Web Proxy service. In the servers file, if Set Browsers to Use Proxy is set to 1, the client Setup program will configure client browsers to use the port named in that box. This should be the same port number that is set for the WWW service of Internet Information Server. |
Advanced options for configuring individual Windows Sockets applications are not required for most applications to work with the WinSock Proxy service. In most cases, the default WinSock Proxy configuration will work with no need for further modification. However, in some situations the advanced options discussed in this section may be necessary.
Configuration information can be set for all WinSock Proxy applications in two ways:
WinSock Proxy service will first look for an Wspcfg.ini file in a client Windows Sockets application directory. If one is not found, WinSock Proxy service will use the settings found in the Mspclnt.ini file under the [Wsp client] section. The settings used for a particular Windows Sockets application are taken from one of these two files only.
The following is a sample [Wsp client] section in an Mspclnt.ini file. Keep in mind that where shared settings exist in both a Wspcfg.ini file and the Mspclnt.ini file located in the WinSock Proxy Client directory (C:\Mspclnt), application-specific settings made in Wspcfg.ini will override global settings in Mspclnt.ini.
[Wsp client] Disable=0 NameResolution=R LocalBindTcpPorts=7777 LocalBindUdpPorts=7000-7022, 7100-7170 RemoteBindTcpPorts=30 RemoteBindUdpPorts=3000-3050 MultipleAccessTcpPorts=100-300 MultipleAccessUdpPorts=500-900, 1000-2000 ProxyBindIp=80:10.52.144.103, 82:10.51.0.0
The following table describes the possible entries that can be placed in a configuration file.
Entry | Description |
---|---|
Disable | Disables WinSock Proxy service functionality; all functions are directly forwarded to the system. Note if the Disable value is set to 0, all following file entries are ignored. |
NameResolution | By default, resolution for all dot-convention names is redirected. Forces name resolution to local (L) or redirected (R), as specified. |
LocalBindTcpPorts | Specifies a TCP port, list, or range that will be bound locally. |
LocalBindUdpPorts | Specifies a UDP port, list, or range that will be bound locally. |
RemoteBindTcpPorts | Specifies a TCP port, list, or range that will be bound remotely. |
RemoteBindUdpPorts | Specifies a UDP port, list, or range that will be bound remotely. By default, this is set to 6970-7170 to support client computers running RealAudio player version 2.1 or newer. If this entry does not appear in the Mspclnt.ini file, when RealAudio player version 2.1 or newer is used with Microsoft Proxy Server it will display Buffering 18 in the status bar, and will not play sound. To resolve this condition, click the Stop button, and then click the Play button. |
MultipleAccessTcpPorts | Specifies a TCP port, list, or range used by a server application, so an accept operation on these ports is intended to serve clients both locally and on the Internet. By default, the socket is considered of client process with one connection, so the listening socket is reused. Requires that the port will be available both on the client and Microsoft Proxy Server. |
MultipleAccessUdpPorts | Specifies a UDP port, list, or range used by a server application, so an accept operation on these ports is intended to serve clients both locally and on the Internet. By default, the socket is considered of client process with one connection, so the listening socket is reused. Requires that the port will be available both on the client and Microsoft Proxy Server. |
ProxyBindIp | Specifies an IP address or list that will be used when binding with a corresponding port. Used by multiple servers that use the same port and need to bind to different ports on Microsoft Proxy Server. |
Note A port can appear in only one of the entries, either as Local, Remote (redirected), or MultipleAccess. There is no provision for client applications that require connections both on the private network and on the Internet. For such applications, incoming connections from the private network will be directed through Microsoft Proxy Server as well.
© 1996 by Microsoft Corporation. All rights reserved.