Configuring Proxy Server 1.0 with the IPX ProtocolLast reviewed: April 15, 1997Article ID: Q165341 |
The information in this article applies to:
CONFIGURING PROXY SERVER 1.0 WITH THE IPX PROTOCOL ==================================================Section 1: Configuring Proxy on a Network With Novell NetWare Servers Section 2: Configuring Proxy on an Ethernet Network with No NetWare Servers Section 3: Configuring Proxy on a Token Ring Network with No NetWare ServersSection 4: Troubleshooting IPX Proxy Clients NOTE: For best results, please follow all instructions carefully and do not omit any steps unless specifically advised to do so.
SECTION 1: CONFIGURING PROXY ON A NETWORK WITH NOVELL NETWARE SERVERS
If your network contains Novell NetWare servers or IPX routers that seed the network with the correct IPX frame type and network address, both the client and server IPX configuration can be set to Auto. This will force the proxy server and client to obtain their IPX settings automatically.
Proxy Server Settings
Proxy Client Settings for Windows NT Server ClientsSet the IPX protocol for auto configuration:
the client computer. If the connection succeeds, you will see the message: Client Control Protocol matches the server control protocol. Test further by using FTP or Telnet to connect to a site on the Internet. Proxy Client Settings for Windows NT Workstation ClientsSet the IPX protocol for auto configuration:
the client computer. If the connection succeeds, you will see the message: Client Control Protocol matches the server control protocol. Test further by using FTP or Telnet to connect to a site on the Internet. Proxy Client Settings for Windows 95 ClientsSet the IPX protocol for auto configuration:
IPX/SPX."3. On the Advanced tab, enter Frame Type = Auto and Network Address = 0. 4. Reboot the client and install the Winsock Proxy client. 5. Test for connectivity by running Chkwsp32 /F from the Mspclnt folder on the client computer. If the connection succeeds, you will see the message: Client Control Protocol matches the server control protocol. Test further by using FTP or Telnet to connect to a site on the Internet. SECTION 2: CONFIGURING PROXY ON AN ETHERNET NETWORK WITH NO NETWARE SERVERSIf you do not have a Novell NetWare server on the network (or a computer running Windows NT server with an internal network number configured), IPX clients will not autoconfigure their IPX settings correctly. Windows NT will not respond to the client's routing information protocol (RIP) broadcasts for the external network number. This occurs even if an external network number and frame type are defined on the Windows NT Server computer. NOTE: If your connection to the Internet is through a modem or ISDN adapter with RAS, skip step 1. If you have many IPX clients, the following client and server setting should allow you to autoconfigure your IPX clients:
Proxy Server Settings
Proxy Client Settings for Windows NT Server ClientsSet the IPX protocol for auto configuration: 1. In Control Panel, double-click the Network icon, click Protocols, and then click NWLink IPX/SPX Compatible Transport.2. Use the Internal Network Number: 00000000. 3. Choose Auto Frame Type Detection. 4. Install the WinSock Proxy client 5. Test for connectivity by running Chkwsp32 /F from the Mspclnt folder on the client computer. If the connection succeeds, you will see the message: Client Control Protocol matches the server control protocol. Test further by using FTP or Telnet to connect to a site on the Internet. Proxy Client Settings for Windows NT Workstation ClientsSet the IPX protocol for auto configuration:
the client machine. If the connection succeeds, you will see the message: Client Control Protocol matches the server control protocol. Test further by using FTP or Telnet to connect to a site on the Internet. Proxy Client Settings for Windows 95 ClientsSet the IPX protocol for auto configuration:
IPX/SPX."3. On the Advanced tab, enter Frame Type = AUTO and Network Address = 0. 4. Reboot the client and install the Winsock Proxy client. 5. Test for connectivity by running Chkwsp32 /F from the Mspclnt folder on the client computer. If the connection succeeds, you will see the message: Client Control Protocol matches the server control protocol. Test further by using FTP or Telnet to connect to a site on the Internet.SECTION 3: CONFIGURING PROXY ON A TOKEN RING NETWORK WITH NO NETWARE SERVERSIf you do not have a Novell NetWare server on the network and are using Token Ring cards on the internal side of the proxy server (or on a computer running Windows NT server with an internal network number configured), IPX clients will not autoconfigure their IPX settings correctly. Windows NT will not respond to the clients RIP broadcasts for the external network number. This occurs even if an external network number and frame type are defined on the Windows NT Server computer. NOTE: If your connection to the Internet is through a modem or ISDN adapter with RAS, skip step 1. If you have many IPX clients, the following client and server settings should allow you to autoconfigure your IPX clients:
Proxy Server Settings
Proxy Client Settings for Windows NT Server ClientsSet the IPX protocol for auto configuration:
the client computer. If the connection succeeds, you will see the message: Client Control Protocol matches the server control protocol. Test further by using FTP or Telnet to connect to a site on the Internet. Proxy Client Settings for Windows NT Workstation ClientsSet the IPX protocol for auto configuration:
the client computer. If the connection succeeds, you will see the message: Client Control Protocol matches the server control protocol. Test further by using FTP or Telnet to connect to a site on the Internet. Proxy Client Settings for Windows 95 ClientsSet the IPX protocol for auto configuration:
IPX/SPX."3. On the Advanced tab, enter Frame Type = AUTO, Network Address = 0. 4. Reboot the client and install the Winsock Proxy client. 5. Test for connectivity by running Chkwsp32 /F from the Mspclnt folder on the client computer. If the connection succeeds, you will see the message: Client Control Protocol matches the server control protocol. Test further by using FTP or Telnet to connect to a site on the Internet. Troubleshooting IPX Proxy ClientsIf you follow the preceding steps, your IPX clients may still experience connectivity problems. See the following troubleshooting guide for more information: When you use the command Chkwsp32 /F, you receive one of the following error messages:
Server Is Down! -or- Unable to refresh configuration filesIf the TCP/IP protocol is installed on the client computer but TCP/IP is not enabled on the proxy server's internal network card, this error will occur. Some clients on the network may require TCP/IP to be installed for certain applications or some clients may have Remote Access Services installed for modem connections with TCP/IP bound to the RAS adapter. There are two workarounds for this type of problem: Method 1: Remove TCP/IP from the clients. Method 2: Force the clients to use only IPX.
You can force the clients to use only IPX for all Winsock Proxy connections. To do this, edit the Mspclnt.ini file on the Proxy server. Simply remove the [Servers Ip Addresses] section. The Proxy clients will refresh their configuration automatically every six hours, so it is not necessary to refresh all of the clients manually.If the Mspclnt share on the proxy server is not accessible, these errors may also occur. Make sure the client has access to the Mspclnt share on the proxy server. Verify that the client has permissions to this share on the server. If the client is not a member of the same domain or does not belong to any trusted domain, do one of the following:
Move the client configuration files to a share on a server that the clients have access to. -or- Enable the guest account on the Proxy server so that any client will have access to the share.NOTE: Click to clear the Enable Access Control check box in the Winsock Proxy service properties if the clients are not part of the domain that the proxy server belongs to. To move the configuration files, create a share on a server the client has access to. The server can be a NetWare Server or Windows NT Server. Edit the Mspclnt.ini file on the proxy server and change the [Master Config] path to reflect the new location. Copy the Msplat.txt and Mspclnt.ini files to the new share. Any new clients installed will contain the new location settings. Click to clear the Enable Access Control check box in the Winsock Proxy service properties if the clients are not part of the domain that the proxy server belongs to. You receive the error message:
Failed to determine protocol family for Control ChannelThis error message can occur if the Mspclnt.ini file is missing the [Servers IPX Addresses] section, or the name of the section is mistyped (for example, singular instead of plural). Confirm that the section is present and typed correctly. If it is incorrect, the Mspclnt.ini file on the server must also be corrected, because the clients periodically update themselves from the server. You find that images or pages are broken or incomplete on the Winsock Proxy client. Try setting the Maximum Connections and Maximum Sockets for the Windows 95 IPX client above the default values. For additional information on this topic, please see the following article(s) in the Microsoft Knowledge Base:
ARTICLE-ID: Q142489 TITLE : Problems After Modifying Maximum Connections or Sockets Value |
Keywords : kbenv
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |