NetCFax F.A.Q Page

LATEST NetCFax RELEASES (December 31, 2006)
NetCFax PRO+ 3.60
NetCFax Pro 3.16
NetCFax 2.75
        
Most importantly, you must be logged in to Windows using an account that has full administrator rights.  We recommend that you use a local Windows administrator login account rather than a domain administrator account to perform the installation of the fax client.
       
Once the fax client has been installed, (and the machine has been restarted if you are prompted to do so), you need to login with administrator rights again to install the fax printer driver.  Once that is done, the fax client can be used by any level of login account to the domain controller.

If you see a message telling you that NetCFax cannot find a DLL (typically NCPWSOCK.DLL, but this may be a different DLL file name) then please follow the instructions below...

Windows Domain controllers can impose various policy limitations on all of the clients connected to them.

To overcome this, all you should need to do is to copy some DLL files to the fax clients main installation folder, which then ensures that each user account is still able to find the required libraries.

Releases BEFORE 2.65.7 and 3.00.7
The files that need to be copied to the fax client install folder can be found using Windows explorer in the following two folders :

x:\program files\common files\netcplus
x:\program files\common files\intervations

All you need to do is to COPY **all** of the files from BOTH these folders to the MAIN installation folder of the fax client (typically x:\program files\netcfax client).  DO NOT copy the folders form the common file tree, just the DLL files themselves. Once this is done, start the fax clients and they should then work correctly.

Releases FROM 2.65.7 and 3.00.7and later

If you checked the option provided by the fax client install to tell it that it would be running under a Windows Domain, you should not see this problem, as the install will have installed the libraries in the main client installation folder.  Please check for the missing file in that folder, and only if it is not there, follow the instructions below.
     
The files that need to be copied to the fax client install folder can be found using Windows explorer in the Libraries sub folder of your NetCFax installation (typically in x:\program files\NetCFax client or wherever you installed NetCFax).  

All you need to do is to COPY **all** of the DLL files from this folder to the **MAIN** installation folder of the fax client (typically x:\program files\netcfax client).  ONLY copy the DLL files themselves. Once this is done, start the fax clients and they should then work correctly.
       
You must also ensure that the fax client has FULL READ AND WRITE access to it's own **entire** installation folder tree, as this may possibly have been limited by the domain controller policies inherited by the Windows domain client's.  If it cannot write data to these folder(s) it will not work correctly.

What to do if you find the print options in the fax cabinet of fax viewer cause NetCFax to crash.

We identified a problem caused by some bad printer drivers that do not appear to return the correct information when interrogated for printer details prior to printing.

This has been worked around (March 9 2006) and a new upgrade system put on the upgrades page of our web site. Just upgrade your systems (server and clients) and these will then print correctly.

Using Windows Terminal services (WTS and Remote Desktops)

Please note that with the release of 2.70 and 3.10 the NetCFax Client CAN NOW be run as a WTS application by more than one person at a time. All clients receive and will use their own personal client configurations when they login to any available NetCFax server.

Running the NetCFax Server on a 
Windows Domain Controller machine or a Windows Server that provides RDP sessions

In case you were wondering, the NetCFax Server runs very happily on a Windows 2003 server, and once started by logging into the server with a Windows server administrator's login account, you can let the server automatically drop into "Locked" mode without it effecting the fax server.  

However, if you want to run the NetCFax server on the same Windows Server system as the fax client, and the fax client(s) will be accessed via RDP sessions, then you MUST START AND RUN THE FAX SERVER ON THE WINDOWS SERVER MACHINE ITSELF, AND NOT UNDER ANY RDP SESSION.  (This forces it to run in Winstation 0)

If you are not providing access to the fax clients on that machine via RDP sessions, then you can certainly run the Fax Server  under any one of the Remote Desktop Sessions, and providing that is not disconnected automatically after any fixed period by the Terminal services configuration, it will be available to anyone on your network. 

The server will continue to run and be accessible to the fax clients on all machines that can connect to the 2003 server using a normal TCP connection.

Return to main FAQ page...