Search

Error 004 - Fatal Communications Error
 

"004 - Fatal Communications Error"

In most cases the reason for the error will be contained in the text near the end of the Communications Log.  Scroll through the log until you find the line that reads: "Communications Session Ended at <time>"

Scroll back up a few lines and look for one of the following Error Messages.
 

• Check for other active applications that may use the modem. Some common programs would be: FAX programs, Internet dialers, and company interface programs. If in doubt about any application, close it and try Express communications again.
• If RAS (Remote Access Services) are enabled on the computer, this could make the modem appear to be in use.  RAS is enabled to allow users to dial into the host computer from another computer.  Since the modem is always ready for an incoming call, it appears to be in use.
• Internet browsers do not alway prompt the user to disconnect the modem dialer program when Explorer is closed. Unless the user manually disconnects or turns off the computer, the dialer may stay active, leaving the modem connected to the Internet. Check the system tray in the lower right corner (where the time is displayed) of the Windows task bar to see if there is a dialer icon there. It usually appears as a small computer with two modems "talking" to each other. If so, double click it and choose the Disconnect option.
• If you are unable to determine what might be open or using the modem, shut down all programs, restart Windows, and then try communicating with Express again.

The following computers may have manufacturer installed communications applications installed that can interfere with other communications programs. Disable the mfgr installed application, restart Windows, and try again.

• Compaq - "Operator"
• Packard - Bell - "PB Navigator (fmedia.exe)
• Acer - "Acer Explorer" (loaded from WIN.INI)
• AST - "Desktop" (shell=desktop.exe) uses communications port

Exit Express and launch Terminal (Windows 3.x) or Hyperterminal (Windows 95).

In Terminal, select Communications and then Settings. Set the Connector to the port where the modem resides and save the setting. On the blank screen with the blinking block cursor, type ATZ. The modem should respond with an OK.

Exit Terminal and try the Express communications again.

If this only solves the problem until the next time the system is rebooted or until the next time Windows is started, there is something being executed by Windows on startup that is accessing the modem or port. If solutions 1 or 2 do not apply, this may be something for their tech to look at.

Have them FAX in the AUTOEXEC.BAT, CONFIG.SYS, SYSTEM.INI and WIN.INI files and we can examine them for potential conflicts.
 

MT-F, No 8250 Present:

• The Windows version of the Express for Windows communications (MTW.EXE) is attempting to open the Com Port that was specified by the user when Express was installed.  This message - in most cases - means that the Com Port that was specified   does not exist.  Change to another Com Port and try again.  (If you are not sure of the correct Com Port, Windows® 95, 98, and NT® provide a Modem Diagnostics icon in the Control Panel that will help you locate the proper port)
• In some cases, Express for Windows will default to it's DOS based communications driver - MT.EXE.  If this occurs, and the modem in use is a "winmodem" (i.e. it requires Windows based driver files in order to operate), this error may occur.  
  • Locate the file AMSEXPW.INI in your system's Windows directory and open it with some type of editor - Notepad, etc.
  • Locate the line in the file that begins: CommModule=.............
  • If the last entry on this line is MT.EXE, change it to MTW.EXE.
  • Save the file, restart Express, and try again.
• If you are using a Windows based communications server or modem pooling program that installs a Com Port redirector on each workstation, following the instructions in the step immediately preceeding this one.  If the CommModule is set to MT.EXE, instead of MTW.EXE,  change it to MTW.EXE.
• If you are using a Windows based communications server or modem pooling program, make sure that you have configured Express for the correct Com Port for the redirecto.  Also, make sure that your redirector is active!

• This error could mean that the Com Port exists, but there is no modem installed on that port. Change to the correct port and try again.
• If the modem is an external modem, make sure it is turned on.
• Reset the modem and PC.  The modem or port may be locked or not responding. (It is best if you can power off both the modem and PC.)
• Change the Flow Control setting in the Express for Windows modem profile to NONE, instead of RTSCTS.

• The Com Port selected may be valid, but does not have a modem on it.  Change to the correct Com Port for your modem and try again.
• Reset the modem and PC.  It is possible that the modem or port may have locked or failed to respond properly.
• There may be a possible hardware problem with the Com Port, modem or modem cable. Change the Flow Control setting in Express to NONE, or select another modem profile in Express that already has Flow Control set to NONE (such as #Default).
• If your modem uses "Non-Standard" interrupts, change the Protocol to Polled.   Select Communcation, then choose Settings. Select the Port Setup tab and change the Protocol to Polled.
• If  the modem has dialed and connected, but then almost immediately has disconnected, check the setting for Ignore CD on the Options tab in Communications | Settings.  Make sure it is set on YES.

• Make sure that the Account Number and Password you have specified in Express for Windows are correct.
• In some cases, this may be due to "garbage" characters being transmitted during login.
  • Reset the PC and modem.
  • Make sure the phone line to the modem is securely plugged into both the modem and the wall.
  • Make sure you have chosen the proper modem type in the Express for Windows program.
  • Lower the baud rate to a slower speed.

Contact iiX at 1-800-683-8553 and select the option for "If your account has been placed on Hold...."
 

This page has been viewed 13494 times | Document Rating is  2.00 / 5.00 | Last Updated on 4/28/2004 7:08:41 AM