Often the real problem with troubleshooting Netscape is deciphering the cryptic error messages themselves. Before you begin troubleshooting, try to access the same URL a few times. Temporary network glitches may clear by the time you reload the page. To make sure that your workstation and connection are functioning properly, try to access another site immediately after receiving the error. If you receive the same error several times on different sites that you have been able to access before, the problem may be with your own connection. The following troubleshooting tips assume you have tried to troubleshoot your own connection first. Error Possible cause Tools & Tips Unknown file type, no viewer configured for file type, or unable to launch external viewer. There are many file types that Netscape will recognize automatically (e.g., JPEG, GIF, and AU). If you are receiving this message, this is Netscape's way of telling you that the program has run into a file type it has not been configured to handle. If you are downloading files, all you need to do is to click on Save to Disk and select the directory where the downloaded file should be stored. You can minimize the Saving Location window and go back to browsing. You will notice that your connection will be somewhat slower. Can't run Netscape after downloading the newest version. You may not be installing the file properly. Download the file and store it in an empty directory. Double-click on the file in File Manager. Your screen may go black and you will see a message that files are being expanded. After a minute or so, your screen will go back to File Manager. If you select Window | Refresh, you will see the installation files for Netscape have been automatically expanded into the directory you selected. Double-click on SETUP.EXE and begin the installation. The server does not have a DNS entry. TCP/IP stack not present or malfunctioning. Temporary network slowness or problems. Can't access Internet through firewall. Requested site may not exist. If you can reach another remote site successfully, chances are your TCP/IP stack is functioning. If you can't, try disconnecting, rebooting, and reestablishing your connection. Traceroute the host name to make sure it exists. 404 Not Found. URL may not exist. Memory and disk caches may be set too low. Under Options | Preferences, raise the cache gradually in 1000K increments. Confirm URL when possible with creator or webmaster. 404 Access Denied. File permissions are not set correctly or are not set to be accessed by certain groups. If you believe that this is an error, you could try emailing the web page owner. Otherwise, there really isn't anything you can do. 503 Service unavailable. Network lag/slowness or problems. Traceroute the site to see if it is live. Socket is not connected. Usually temporary connection problem. Try two other Web pages on different sites. If you still get the error, you may wish to disconnect and reconnect to your Web server. Connected timed out. Network slowness or problems. Traceroute the host site to determine if the site is accessible from your machine. Can't use Netscape to view a local file. MOZOCK.DLL not loaded or used. Check your Netscape directory to make sure that MOZOCK.DLL is available. If not, downloading a newer version or reinstalling Netscape may help. You can find this file at Netscape. Reentrant call to interrupt window. Usually seems to happen if you click "Stop" before a page has finished loading. If you experience this often enough, try opening another Netscape window to go to another site. In a moment or two go back to the old window and exit then. Connection reset by peer. Remote host reset your connection. Usually clicking "Reload" will bring up the URL normally. System call 'connect' failed: connection refused. Netscape was unable to connect to the remote host. Often occurs because a system is down or not accepting connections. Use Traceroute to see if the host is live or not. Can't read newsgroups. Network connection information in Preferences incorrect, or problem with your provider's news server. Check to make sure that Preferences | Mail and News | Servers information is complete and correct. If the problems continues, contact your provider to report the problem, and see if anyone else has reported similar problems. FTP transfers hang or disconnect after connecting successfully to FTP host. Problem with SLIP/PPP TCP/IP stack configuration (e.g., Trumpet Winsock). Change the MTU value in your stack software from 1500 to 1006. Error 57 when attempting to FTP. Usually occurs when an ftp server is overloaded or very busy. Try to download the file at off-peak hours. Does not indicate a problem with netscape. "Reload" button doesn't really reload all files. This is usually frustrating to Web authors. Netscape checks to see if there have been any changes of the files in cache vs. the files on the server. Problems can result if the time/date stamp on the server or on your workstation are incorrect. Force a complete reload: Shift-Ctrl-R or hold down Shift and click "Reload".