Troubleshooting

Web Proxy Service Troubleshooting
WinSock Proxy Service Troubleshooting
Performance Troubleshooting
RAS Troubleshooting

Web Proxy Service Troubleshooting

Web Proxy Server Problems
Web Proxy Client Problems

Web Proxy Server Problems

HTTP/1.0 500 Server Error (An attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client.)

This error occurs when changes are made to the home directory properties for the WWW service and Web Proxy service is also in use. If the home directory setting is changed to specify a remote UNC path name (i.e. \\servername\sharename) and not a currently mapped local drive path (such as D:\InetPub\Wwwroot), all requests that are made through the Web Proxy service will fail.

To correct the problem, stop and restart the WWW and Web Proxy services using Internet Service Manager. As an alternative, create a virtual directory entry instead of altering the default local drive path for the home directory when adding directory names that use remote UNC path names.

HTTP/1.0 500 Server Error (-number)

This error occurs when Windows NT Challenge/Response authentication is used on Microsoft Proxy Server to validate proxy clients. Microsoft Proxy Server uses the password authentication specified in the WWW service properties to validate Web Proxy clients. Examine the form of password authentication in use for WWW services by using Internet Service Manager. As a temporary alternative, select basic (clear-text) authentication and report the error to your support provider.

HTTP/1.0 500 Server Error (The specified module could not be found.)

This error occurs when certain proxy binaries are not installed in the correct directory for proxy scripts. Verify the location of your IIS scripts directory. Make sure there is a Proxy subdirectory under this directory location.

Web Proxy Client Problems

RealAudio does not work when set to use a proxy.

The WinSock Proxy service included with Microsoft Proxy Server handles all Windows Sockets-based applications transparently. Therefore, it is not necessary to configure RealAudio to use a proxy. Disable the proxy option in RealAudio’s View|Preferences dialog box.

FTP using Netscape Navigator shows all files as plain text when attempting to download.

This problem occurs for some versions of Netscape Navigator configured to use the Web Proxy service of Microsoft Proxy Server. When Netscape navigator sees the HTTP document-type header, it attempts to display the FTP contents on screen without examining it. To work around this problem, hold the SHIFT key when clicking a link to download a file.

HTTP error 5 occurred.

Connection was refused for a proxy-configured client browser. If anonymous logon is allowed for IIS, then the IUSR_computername account will be used by Microsoft Proxy Server to authenticate clients. Microsoft Proxy Server will check that proxy client users have access to a requested service. Check that the IUSR_computername account is listed on the Web Proxy service Permissions property sheet for the requested service (FTP, HTTP and so on) that is being affected.

HTTP error 18 occurred.

This error can occur when attempting to use a browser configured for the Web Proxy service for FPT service. It is caused by the FTP directory on the remote computer being empty. (Note: WinSock Proxy FTP does not return this error if the directory is empty.)

HTTP error 12 occurred.

If the private network is running TCP/IP, the Local Address Table (LAT) is configured to specify that the server’s internal IP address is located on the local network. Check that the IP address assigned for the server’s internal network adapter is included in the LAT.

HTTP error 10060 occurred.

This error indicates a time out occurred in attempting to reach the URL targeted server . The most common reasons for this are:

The destination host is too busy.

The destination host (on the Internet) is currently not available.

A network link in the path to the destination host is not available.

WinSock Proxy Service Troubleshooting

WinSock Proxy Diagnostic Utility
WinSock Proxy Server Problems
WinSock Proxy Client Problems

WinSock Proxy Diagnostic Utility

When the client Setup program is run and the client software is installed on a computer, a WinSock Proxy diagnostic utility is installed into the Mspclnt directory on the client. This utility presents configuration information that is useful when troubleshooting WinSock Proxy conditions.

For computers running 32-bit operating systems, the utility is named Chkwsp32.exe. For computers running 16-bit operating systems the utility is named Chkwsp16.exe.

To run the WinSock Proxy diagnostic utility

On the client computer, open the MS-DOS command-prompt window and change to the Mspclnt directory.
Run the utility with the -f option.
For example, on a client computer running the Windows 95 operating system, type:

chkwsp32 -f

WinSock Proxy Server Problems

Inability for user to access or administrate different protocols for WinSock Proxy service.

By default, the Administrator user logon account is the only account allowed to access any port regardless of port configuration. To allow other users to access or administrate protocols or assigned ports:

Check the LAT to make sure that the user computer’s IP address is included.

Use Internet Service Manager to check that the protocol has been added.

Use Internet Service Manager to check that the user (or a group the user belongs to) has been granted permission to use the protocol.

Ping fails to work with WinSock Proxy.

Ping.exe uses Winsock.dll only when looking up the domain host name of the server you are trying to ping. Once the DNS name lookup has completed, Ping.exe uses ICMP for connection. If you have an internal DNS server, make sure its IP address is contained in the Local Address Table (LAT), C:\Msp\Msplat.txt, that is configured during Setup. Also, check your Ping utility program. If you are using an application to ping with that requires use of a third-party Windows Sockets DLL, ICMP ping results may be unpredictable.

WinSock Proxy service problems with other third-party TCP/IP stacks.

Currently, Microsoft Proxy Server has not been tested with other third-party TCP/IP implementations. Use of a third-party stack may produce unpredictable results.

Server domain name look-ups failing on local network.

The WinSock Proxy service redirects all DNS look-ups to the computer running Microsoft Proxy Server. If you have an internal DNS server, make sure its IP address is contained in the Local Address Table (LAT), C:\Msp\Msplat.txt, that is configured during Setup. Domain names that do not contain dots are considered internal names to Microsoft Proxy Server.

WinSock Proxy Client Problems

Internal subnetwork is not reachable through a WinSock Proxy client application.

Check that the subnetwork address ranges are included in the Local Address Table (LAT), C:\Msplat.txt. If there are internal subnet addresses missing from the LAT, add the missing IP address pairs to the server LAT file (C:\Msp\Msplat.txt) so that these address changes will be propagated to all clients when the next table update cycle is performed by Microsoft Proxy Server.

Cannot connect to other ISP after installing WinSock Proxy client.

The WinSock Proxy client is set up for use with the internal network. When you connect to another Internet Service Provider, you are now on a different network, and the WinSock Proxy client must be disabled.

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, 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 sometimes to a private ISP. To correct this condition, you can turn the WinSock Proxy client on and off using the WinSock Proxy Client application in the Control Panel.

WinSock Proxy service problems with other third-party TCP/IP stacks.

Currently, Microsoft Proxy Server has not been tested with other third-party TCP/IP implementations. Use of a third-party stack may produce unpredictable results.

Windows For Workgroups clients using IPX not able to access WinSock Proxy Service for Proxy Server.

IPX is currently supported only for Windows 95 and Windows NT clients.

Prompting to “Enter domain credentials” each time a new Windows Sockets application is launched.

Domain credentials are required each time a new Windows Sockets application is launched and another Windows Sockets application is not currently active. If the first Windows Sockets application is left open and minimized, there is no need to resupply domain credentials for successive Windows Sockets applications that are loaded for the same domain.

Performance Troubleshooting

Browsing internal Web sites works, but external WWW sites do not appear in user browse lists.

Try to ping the server IP address for Microsoft Proxy Server from the client computer’s command prompt.

If the response is “Bad IP address,” check to see if you have any local WINS or DNS servers used for client address resolution. Verify that any active name servers used for your client TCP/IP protocol configuration are configured correctly. For further assistance, contact your network administrator.

Private network performance is slow for all clients accessing the same server.

If performance is slow for WinSock Proxy client requests to particular servers on the private network, check that the IP addresses of those servers are included in the Local Address Table (LAT). The information in the LAT identifies the range of IP addresses of your private network. If an internal server is not listed in the LAT, WinSock Proxy clients will redirect their connections to it through Microsoft Proxy Server.

To check or correct this condition, use Microsoft Internet Service Manager and, for each computer running Microsoft Proxy Server in your network, review the IP address ranges listed in the Construct Local Address Table dialog box. (This dialog box is accessible from the Edit Local Address Table (LAT) button, on the Services property sheet of both the WinSock Proxy and Web Proxy services.)

Add IP address ranges or individual IP addresses as necessary.

–Or–

You can directly read and edit the Msplat.txt file, located by default in the C:\Msp\clients directory of each computer running Microsoft Proxy Server.

Slow connection from a client using a Windows Sockets connected application on a local network.

If certain local addresses are slow, the problem may be caused by WinSock Proxy attempting to redirect a local connection. To prevent this, check that the local computer you are attempting to establish connection to is defined in the Local Address Table (LAT). The client LAT is contained in C:\Mspclnt\Msplat.txt.

RAS Troubleshooting

RAS does not hang up calls or disconnect properly after dialing

To ensure that RAS always disconnects after each dialing attempt, a value in seconds for Idle seconds before hanging up must be set in Logon Preferences for the RAS phonebook entry that is used by Microsoft Proxy Server for dial-out. Dialing settings made in User Preferences are not observed when a non-user service (such as Microsoft Proxy Server) dials. Logon preferences are accessed by selecting More from within Dial-Up Networking. For more information on configuring RAS preferences, see RAS online Help or your Windows NT product documentation.