Windows 3.x Windows 95/98 Windows NT Macintosh Search Submit Technical Article

Win 95/98 Tech Notes

1. When trying to open Internet Explorer you receive the error message "An Unexpected Error has occurred...":
         Customer can get connected, but is unable to open any web pages, and is unable to get email. Usually the result of a problem with the wsock32.dll file or the winsock.dll file.
   
   
2. "DSP could not be downloaded - Error 1010 - problem 2"
         Result of invalid entries in the dialing properties (Usually a 1 in front of the number to be dialed.)
   
   
3. "An exception OE has occurred at 0028:C102A872 in VxD ...":
         Can occur if certain specific data packets are deliberately sent during a TCP/IP session.
   
   
4. "Iexplorer caused an invalid page fault in module Gdi32.dll"
         Occurs when loading the home page. Active content such as a Java text applet seem to cause this problem.
   
   
5. "INF install failure...File copy session is already open."
         Occurs during the installation of the browser while copying files. Happens because TSR's like WebScan and VirusScan are running in the background.
   
   
6. "IE cannot open Internet site http://www...., the connection was reset."
         Either they are not connected at the time, or it is a possible problem with the wsock32.dll file.
   
   
7. "<Program> caused an invalid page fault in module WININET.DLL."
         Can be caused by a corrupt History or Cookies folder or file.
   
   
8. "Invalid Page Fault in MFC40.dll" or "Invalid Page Fault or GPF in Netscape Mail."
         Caused by corrupt mailboxes.
   
   
9. "Internet Explorer is unable to open Internet site ... The site was not found. Make sure the address is correct and try again."
         Usually occurs when user is not connected, it is not avalid web address, or there is a problem with the DNS settings in the connection icon.
   
   
10. "Internet Explorer could not connect to the Internet site ftp://ftp.xxx.xxx. The server returned extended information."
          Sever is down or busy.
    
    
11. "Internet Explorer caused an invalid page fault in module SHDOCVW.DLL at 013f:7150319c."
          Occurs when a user clicks on a hyperlink in IE 3.0 and they have a program known as Hurricane installed. Hurricane acts as a RAM doubler/enhancer.
    
    
12. "Internet Explorer caused an invalid page fault in module comctl32.dll."
          This occurs when clicking on Internet Mail. Caused by a conflict between .dll files.
    
    
13. "Internet Explorer caused a General Protection Fault in GDI.exe"
    
    
14. "Java Script Error in line xxx"
          Java script coding errors.
    
    
15. "Post Dial or Terminal Error."
          Occurs when Dial software tries to open up a Post Terminal Window.
    
    
16. "MPREXE caused an invalid page fault in module Kernel32.dll."
          Corrupt password (.pwl) file.
    
    
17. "Required .dll file, c:\windows\system\svrapi.dll not found."
          Occurs when Dial-up Networking is not installed properly.
    
    
18. "RNAAPP caused an invalid page fault in RNAAPP.EXE"
          Occurs when trying to connect.
    
    
19. "rundll32 caused an invalid page fault in module rnaui.dll."
          Occurs when Dial-Up Networking is installed from Windows 95 OSR2 onto a system with the retail version of Windows 95.
    
    
20. "TAPI.EXE caused a General Protection Fault (GPF) in module kernel32.exe."
          This error occurs up as a result of some kind of miscommunication between the modem and Windows 95.
    
    
21. "Unable to initialize the network layer, check your winsock for errors..."
          Occurs while trying to use Netscape.
    
    
22. "A required .dll file, Url.dll, was not found."
          The file is missing or damaged. Should be in the c:\Windows\System folder.
    
    
23. "Unable to Start Application. One of the required components may be busy ... please retry."
          Corrupt Address book file.
    
    
24. "RAS 650 Error" when dialing.
          Error occurs when dialing out.

Windows NT Tech Notes

1. How to Connect to Internet Service Providers from Windows NT 4.0
         This article describes how to configure Windows NT 4.0 Dial-Up Networking (DUN) to connect to your Internet Service Provider (ISP).
   
   
2. Troubleshooting Internet Service Provider Login Problems
         This article describes how to troubleshoot Internet service provider (ISP) logon problems. This article discusses only logon problems, not modem or dialing problems.
   
   
3. Troubleshooting Modem Problems Under Windows NT 4.0
         This article describes procedures to help you diagnose and fix problems when you are unable to dial out using your modem in Windows NT 4.0 with Dial-Up Networking (DUN).
   
   
4. Cannot Install Modem After Removing and Reinstalling RAS
         After you remove and reinstall the remote access service (RAS) in Windows NT 4.0, the Install New Modem Wizard may be unable to detect your modem.
   
   
5. How to Troubleshoot PCMCIA Modems in Windows NT
         This article describes how to troubleshoot a PC Card (PCMCIA) modem in Windows NT.
   
   
6. Using an Unsupported Modem with Windows NT RAS
         Some modems that are not listed on the Windows NT Hardware Compatibility List (HCL) can still be used successfully with Windows NT Remote Access Service (RAS).
   
   
7. MODEM.INF Settings for US Robotics Modems
         US Robotics has a file available containing updated MODEM.INF settings for use with all of their modems. These MODEM.INF settings have been tested with the Remote Access Service (RAS) software included with Windows for Workgroups 3.11, Windows NT version. 3.1, and Windows NT version 3.5. The file, MDMUSR.INF, can be downloaded from the US Robotics BBS at (847) 982- 5092.
   
   
8. Third-Party RAS MODEM.INF Files
         The Microsoft Windows NT Hardware Compatibility List (HCL) lists a number of modems supported for use with Windows NT Remote Access Services (RAS). Modems not listed on the HCL, however, work with RAS if you supply RAS with the command strings required by the modem. You can supply RAS with these command strings by appending a new section for your modem to the %SystemRoot%\SYSTEM32\RAS\MODEM.INF file. Some modem vendors have created MODEM.INF sections for their unsupported modems to operate with RAS or to update the MODEM.INF for their supported modems. The table below lists third- party vendors, their phone numbers, and the names of files containing MODEM.INF sections.
   
   
9. Updated MODEM.INF Available For Megahertz Modems
         If you use Windows NT Remote Access Service (RAS) and a Megahertz modem, you can obtain a software support release from Megahertz Corporation that contains a new MODEM.INF file with updated drivers for all Windows NT supported Megahertz modems.
   
   
10. FTP, WWW, and Telnet Fail over RAS Even Though Ping Works
          On your computer running Windows NT or Windows 95, when you use Remote Access (RAS) or Dial-up networking with the PPP and TCP/IP protocols enabled, you cannot connect to computers on the Internet that are running the World Wide Web (WWW), FTP, Telnet, or other software that relies on TCP/IP packets to exchange information. PING.EXE and TRACERT.EXE, however, still function correctly.
    
    
11. RAS Error 720 When Dialing Out
          When you try to dial out using Remote Access Service (RAS) or Dial-Up Networking (DUN), the following error message may appear: ...
    
    
12. RAS Errors 611 and 720 With PPP or SLIP
          When you attempt to dial out from a Windows NT Remote Access Service (RAS) client using the Remote Access protocol Serial Line Internet Protocol (SLIP) or Point to Point Protocol (PPP) to a TCP/IP server, one of the following error messages appears: ...
    
    
13. Remote Access Errors 657 and 659 with Dial-Up Networking
          If you use a script to connect to a remote server with Dial-Up Networking, you may receive one of the following error messages: ...
    
    
14. Err Msg: Error 692: Hardware Failure in Port or Attached....
          When you dial a Remote Access Services (RAS) server in Windows NT, you may receive the following error message as the modem starts to initialize: ...
    
    
15. Err Msg: Error 720: No PPP Control Protocols Configured
          When you attempt to connect to a Remote Access Service (RAS) Server using the TCP/IP protocol, you may receive the following error message:
    
    
16. How to Install and Configure Windows NT 4.0 Dial-Up Networking
          This article describes how to install and configure Windows NT 4.0 Dial- Up Networking (DUN) and the Remote Access Service (RAS) client for a connection to a Windows NT or third-party RAS Server.
    
    
17. Troubleshooting RAS Client Issues in Windows NT 4.0
          This article contains steps to help you troubleshoot issues with the Remote Access Service (RAS) in Windows NT 4.0. This article focuses on issues that can occur when you use RAS to dial into another computer or an Internet service provider (ISP).
    
    
18. Phonebook Entry Is Not Updated After Changing Modem
          After you change the modem in your Windows NT-based computer, you may experience one or more of the following problems: ...
    
    
19. Troubleshooting Problems Communicating on the Internet
          This article describes how to troubleshoot problems communicating with servers on the Internet using an Internet browser, ftp, or Telnet.
    
    
20. Calling Card Settings Ignored by Phone Dialer
          The Windows NT 4.0 Phone Dialer tool may not use the calling card settings as defined in the Telephony tool in Control Panel.

MAC Tech Notes

1. Apple Menu Missing Options. (Under File, Edit, View...)
         If a Mac System using OS 8.0 or 8.1 is set to Simple Preferences, certain items may not appear on the Apple drop down menu.
   
   
2. Connection Attempt Failed (PPP Dialer)
         To resolve the above error message when it occurs in the Open Transport PPP Dialer.
   
   
3. The Domain Name Servers Are Not Responding.
         Occurs most often when using MacTCP and the ConfigPPP Dialer.
   
   
4. Error Type 1 - With FreePPP
         Potential Causes: Extensions Conflict, Insufficient Memory, Incorrect Memory Settings.
   
   
5. Error Type 1 - With Internet Connection Wizard.
         Caused by low memory settings or corrupt Internet Preferences.
   
   
6. Error Type 1 - While Browsing With Netscape Communicator.
         Usually a result of a memory related error.
   
   
7. Error Type 1 - PPP Not Installed Or Selected
         Potential Causes: Virtual memory not enabled, Insufficient memory for Internet Connection Wizard, PPP Dialer conflict.
   
   
8. Error Type 2 - While Browsing
         Select the Finder, and determine if any other browsers are running in the background.
   
   
9. Error Type 11 - While Browsing
         Potential Causes: Corrupt files in Netscape's disk cache, Not enough memory available in System Cache, Desktop file may be corrupt.
   
   
10. Error Type 11 - When Using Outlook Express
          Try modifying the memory and cache settings. ...
    
    
11. Error 39 - There Is An Error Saving Your Preferences
          Associated with a corrupted Netscape Preferences file.
    
    
12. Error Type 40 - Cannot Open Internet Mail and News Preferences
          Occurs when Internet Mail and News preferences are corrupted.
    
    
13. Error Type 491 - When Using ICW (Internet Connection Wizard)
          Occurs when running ICW on a 68000 - based Mac, error type - 491 may be generated as the Next button on the Setup Options screen is selected.
    
    
14. Error : Broken Pipe
          The Global Village Toolbox extension is not installed or configured correctly. This error message occurs most commonly on NuBus Power Macs with Global Village Teleport Gold II Modems.
    
    
15. FreePPP Not Installed Or Selected (Grey Connect Button In FreePPP Setup)
          Potential causes: FreePPP not selected in MacTCP or TCP/IP, FreePPP not enabled in Extensions Manager, Other PPP extensions in the Extensions folder, MacTCP or TCP/IP preferences are corrupt, Corrupt Finder Preferences, "Greg's Buttons"
    
    
16. Insuffient Memory To Load FreePPP
          Usually caused by an extension conflict
    
    
17. Modem Port In Use
          Potential Causes: Fax or other communication software is running in the background, A communication application may be loading at startup, Modem may not have released the previous port, A communications extensions conflict.
    
    
18. Netscape Is Unable To Locate The Server. The Server Does Not Have DNS Entry. Check The Server Name In The URL And Try Again.
          Potential Causes: Incorrect spelling of the URL or it is outdated, Incorrect Usrname or Password, Wrong or missing DNS entries in the MacTCP or TCP/IP when trying to access server, Corrupt MacTCP or TCP/IP Preferences, MacTCP or Open Transport (TCP/IP) Extensions not enabled, Extension conflict, Corrupt files in the Netscape Cache folder, Networking software is corrupt.
    
    
19. Netscape May Be Overloaded
          Error may occur in Netscape 4.0x due to a corrupted Preference file.
    
    
20. PPP Connection Was Terminated Unexpectedly.
          Occurs when the username or password is incorrect.
    
    
21. The Application "Account-Tool Could Not Be Opened Because 'ObjectSupportLib" Could Not Be Found.
          If you are running System 7.6 or 7.6.1 on any PowerMac and you have disabled the ObjectSupportLib by de-selecting it in Extensions Manager, removing it from the Extensions folder, selecting "All Off" in the Extensions Manager, or removing it from the Mac entirely you will receive the error message.
    
    
22. The Application Internet Connection Wizard 2.X Could Not Be Opened Because An Unexpected Error Occurred.
          This occurs when files which the Internet Connection Wizard requires are located in the wrong folder or are missing.
    
    
23. The Attempt To Load (URL) Failed - Internet Explorer
          Potential Causes: Incorrect spelling of the URL, or URL is outdated, Incorrect username or password, Incorrect DNS entries in the MacTCP or TCP/IP, Corrupt MacTCP or TCP/IP Preferences, MacTCP or TCP/IP Extensions disabled, Extensions Conflict, Memory conflict, Corrupt files in the Explorer Cache.
    
    
24. The Modem Does Not Seem To Be Responding. PPP Was Expecting "OK" From Your Modem. Your Modem May Be In Use Or Not Ready.
          Potential Causes: Fax or other communication software is running in the background, A communications extension conflict, Modem port speed is set to high, Modem port settings incorrect
    
    
25. The Modem Could Not Establish A Connection With The Remote Server. The Server May Be Having Problems Or It Didn't Answer.
          Potential Causes: Modem port speed is set to high, If the system has a Global Village modem, the Global Village Toolbox may not be running, A communications extensions conflict, Modem is not connected properly.