Error Messages
This section is designed to help you ascertain and fix problems signaled by a WinProxy error message.
Binding Messages
-
- Unable to Bind DNS Proxy:
- The DNS Port (53) is being used by another application. If you're operating under Windows NT, be sure the Microsoft DNS Server isn't running. If you want to use a different DNS server, disable DNS in WinProxy. If you don't know of a DNS server on this machine, look for other proxy or firewall applications that you may have tried recently. Many will use the DNS port. You'll need to disable that software.
- Unable to Bind DHCP:
- The DHCP Port (67) is being used by another application. This is often another proxy or firewall that is still operating on the machine. You'll need to disable this other application for Win- Proxy's DHCP server to operate.
- Unable to Bind HTTP Proxy: The HTTP Port (typically 80) is being used by another application. If you're running a web server on this machine, set it (or WinProxy) to listen on a different port (e.g., 8080). In Win dows NT, disable the Web Services or change the port under Internet Service Manager. On the Windows NT Server, go to Microsoft Internet Information Server/Internet Services Manager. On Windows NT WorkSta tion, go to Microsoft Peer Web Services.
- Unable to Bind Mail Proxy:
- The Mail Port (typically 25) is being used by another application. This port is used for sending mail. You'll typically get this message when you're running a mail server on the same machine. Disable Mail Host IP (SMTP services in WinProxy or assign different ports to the mail server and WinProxy for SMTP.
- Unable to Bind Post Office Proxy:
- The POP3 (typically 110) is being used by another application. This port is used for checking mail. You'll typically get this message when you're running a mail server on the same machine. Disable POP3 Host IP (POP) services in WinProxy or assign different ports to the mail server and WinProxy for POP.
- Unable to Bind FTP Proxy:
- The FTP Port (typically 21) is being used by another application. You'll typically get this message when you're running an FTP server on the same machine as WinProxy. If this is the case, disable FTP in WinProxy or assign a different FTP port to WinProxy (i.e. 8021). In Windows NT, disable the Web Services under Internet Service Manager or change the port in WinProxy. On Windows NT Server go to Microsoft Internet Information Server/ Internet Services Manager. On Windows NT WorkStation go to Microsoft Peer Web Services.
Common WinProxy & Web Browser Error Messages
304 Invalid port number or address specified
The port number or the address specified in the Post command was invalid. Please retry your command.
400 WinProxy Modem Connection Failed
WinProxy was unable to establish a dial-up connection to the Internet. Dial Up networking returned error_code.
403 Forbidden Commands
There are several things in WinProxy - particularly the site restriction functions - that can give you a forbidden error. Whenever WinProxy issues a 403 error code, it will also supply additional information about the reason for the 403, including what function (such as the blacklist) is responsible for the message. If you are getting a 403 message with no additional information, then most likely the error message is coming from a server or an application other than WinProxy.
The request was not properly formatted. WinProxy will permit requests only with properly formatted strings. This error is usually generated by programs that do not strictly follow the http 1.0 or 1.1 specification.
Secure Sockets attempted to use a restricted port - CONNECT command refused. This problem is typically caused by a secure server improperly configured, or by an application attempting to access a protocol other than SSL through the SSL proxy. The CONNECT command restriction can be disabled in the HTTP Setup in WinProxy/ File/Settings. The specified request was not permitted due to a possible security breach or memory allocation error.
420 Socket Errors
- Unable to create socket-the WinProxy server may be too busy.
- This means that all available sockets on the system are in use. Wait until some of the socket connections are freed. If WinProxy is running on a Win dows 95 system, consider moving it to a Windows NT system with its higher number of sockets.
- Unable to bind data connection to specified port.
- WinProxy was unable to listen for a connection on a spe cific port. This could happen if there is another service already using that port. It can also happen in FTP if there is an error binding the data connection.
- Unable to set up asynchronous communication.
- This is an internal TCP/IP error.
- Incorrectly Formatted URL.
- The URL was formatted incorrectly. For example, a URL with a space in it (spaces are not permitted in URLs).
- Protocol Not Supported.
- The requested protocol is not supported; i.e., Gopher enabled in the browser.
425 Connection Errors
- Unable To Connect To Remote Host.
- Either the host is not accepting connections or there was a network error (an error in local IP addressing during setup might cause this). WinProxy tried to establish a connec tion to a server but the server either refused the connection or was not available. This could indicate that the remote server is down, or that the name or IP address specified is incorrect, or that the appropriate server is not running on the specified machine.
- Connection Refused by Remote Host.
- Same as above.
- Connection Refused.
- Too many people are already using WinProxy. Try again later. In WinProxy Home Edition this message is returned when the simultaneous three-user limitation has been reached.
- Connection refused.
- You are not authorized to use the specified protocol through WinProxy. This message indicates that the particular user requesting the connection does not have permission to use the requested protocol (if user restrictions were enabled under the User's Tab). It's also possible that a connection was requested and the required protocol was not configured. User configuration is available in WinProxy/File/ Settings/Users. Protocol configuration is available in WinProxy/File/Settings/Protocols.
- Unable to establish PASV FTP connection.
- The FTP server returned an error to the PASV command. This error is only returned if the checkbox in FTP setup states that all the FTP transactions should use PASV mode. That checkbox should only be set if you're running behind a filtering router, which does not permit incoming connections.
430 Protocol Errors
- Unable to Resolve Name.
- You'll generally get this message when DNS is not configured correctly on the WinProxy Server or client machine. It may also be caused by an incorrect URL. For DNS configuration please refer to Chapter 7.
- Unauthorized.
- You are not authorized to use this protocol. A connection was received on a protocol not permitted in the WinProxy configuration. This message may be returned if FTP is disabled but a user requests a FTP connection through WinProxy. Protocol configuration is available in WinProxy/File/Set tings/Protocols.
501 FTP Error
FTP server returned an invalid response to PASV command: The response from the PASV command could not be understood. Try disabling the Passive option in the FTP Protocol in WinProxy. In FTP clients, select the USER@SITE FTP method instead of PASV method.
