Chimera Computing Ltd


Troubleshooting FAQ


  • I get "ERROR: Connection refused by remote host" when running EFS as a service with MS Proxy yet it runs fine standalone?
  • You may notice the log file in EFS will have the following when EFS is run as a service (yet it runs fine standalone)

    01/01/00 12:00 - logging into POP server
    ERROR: Connection refused by remote host

    This is due to the permissions for the WinSock Proxy on Microsoft Proxy 2. Although Administrators have permission to use the WinSock Proxy the \SYSTEM does not so the EFS Service is denied access to the Proxy when run as service. Ensure the SYSTEM has administrative permissions to the Proxy.
  • Why doesn't EFS automatically dialup my ISP? I get "Remote host unreachable" errors?
  • EFS does not have an auto-dial feature - this is simply old technology. For those who still do use dialup modems, there is the 'Open COM Port Check' option. There are many other customisable options for checking with EFS, such as using Marker file checking (write a batch file that initiates a connection, then creates a file "marker.efs" in the EFS folder which will initiate EFS to check) There is also a "Pre Check" option that enables you to execute a file (such as a dialup script or ping a router to initiate a connection) including a delay period before EFS checks.
  • I get a message in the detail window saying "550 Unable to relay for [e-mail address]"
  • The relaying problem is due to routing restrictions put on your mail server. If you are running Microsoft Exchange server, open Exchange, go to "Connections", open the properties for the "Internet Mail Service". Click on the "Routing" tab, then, if you are running Exchange Service Pack 1 or higher, you should have a button called "Routing Restrictions". Click on that. In here, you setup routing restrictions which effectively stop certain IP addresses or ranges "relaying" mail. You need to change the settings in here to allow relaying from the host where EFS is running. Add this IP address in the "Hosts and clients with these IP addresses" box. For more information, see: Preventing the IMS from Relaying UCE messages
  • SBS Management console stops working after EFS installation
  • When installing a 'fresh' version of EFS on a Microsoft Small Business Server the Manage Server Console may stop working. After opening the Console you may receive a dialog box that states:

    An ActiveX control on this page is not safe.
    Your current security setting prevent running unsafe controls on this page
    As a result, this page may not display as intended

    After pressing ok, you receive a Microsoft Explorer Script Error dialog box similar to:

    An error has occurred in this script on this page
    Error: Object doesn't support this property or method:

    The icons for the Console show up without any text and you can not do anything but close it.

    To resolve this problem, perform the following:

    1) goto the SBS computer and open an msdos prompt
    2) change directory to c:\winnt\system32
    3) make sure comcat.dll is v5.0
    4) run 'regsvr32 -u comcat.dll' at the msdos prompt
    5) replace comcat.dll v5.0 with comcat.dll v4.71
    6) run 'regsvr32 comcat.dll' at the msdos prompt

    (Many thanks to Vincent Auletta for this fix)
  • I get a CRC error when installing EFS/ERC
  • This generally indicates that the download did not complete successfully. Check that the file size is the same as that indicated next to the download link. If it is not, you will have to download the file again. If you want to provide a mirror for EFS downloads, please contact us and in return we will provide a visible and detailed description of your site as well as the "mirror link" for free.
  • I receive a "Network not available" error but all my settings appear to be correct?
  • This problem has been found with MS Proxy Server. You may be able to resolve this problem by reinstalling the proxy client on Small Business Server. This is simply a case of selecting PROGRAMS--MICROSOFT PROXY CLIENT--SETUP from the start menu and reinstalling over the top of the existing setup.
  • I get errors when running EFS after an upgrade, what's wrong?
  • These errors are generally due to older controls - specifically the mail control. For EFS version 5.0 and lower, check you are running latest versions of the .OCX files:

    MMAIL32.OCX (ver 5.10.007)
    MSCOMM32.OCX (ver 5.01.4319)

    To check, right click each file from your System directory, choose properties then click the Version tab. If they are earlier, you can download these files here

    Also, check your System directory for MFC40.DLL and MSVCRT40.DLL. Make sure MFC40.DLL is dated October 6th, 1995 or later and MSVCRT40.DLL is dated September 29th, 1995 or later. If your files are older, you can download these files here
  • I get "Runtime error 50003" after upgrading?
  • This is caused by an outdated COMCTL32.OCX file. You must be running version 5.01.4319 or later. Download the latest file here, install then re-run EFS.

  • EFSCHK says my "CTL3D32.DLL" file is out-of-date, where can I get the latest?
  • The latest version and file size of "CTL3D32.DLL" is:
    O/S           Version           Size (bytes)
    ===           =======           ============
    Windows 95 2.31.000 26,624
    Windows 98 2.31.000 45,086
    Windows NT 2.31.000 27,136
    Click the appropriate link to download the latest file.


    (Chimera Computing Ltd)