NetCFax F.A.Q Page

Because of the way that Microsoft have implemented support for Windows Services there are a few things you need to be aware of before configuring the NetCFax server to be run as a Windows Service.

The major issue is the fax server's need to access any networked resource.

Microsoft allow you configure Services to run under the default LOCAL SYSTEM ACCOUNT, or under a specified Windows login account. Sadly, the LOCAL SYSTEM ACCOUNT has absolutely NO ACCESS AT ALL to networked resources.

Therefore, if you have the NetCFax Server configured to automatically print faxes to a network printer, or possibly to have PDF copies of received faxes saved to a folder on a networked machine, you MUST USE THE "Specific windows login account" option when configuring the NetCFax Server Service.

If you do not do so, the auto printing and saving of PDF files will simply not occur.

We have no idea why Microsoft impose such a ridiculous limitation on the operation of Windows Services, but these are simply the facts and we are passing them on to you to save you a lot of wasted time and effort (that we have had to do) wondering why NetCFax is not doing what it says it will do.

If the NetCFax server is running as a Windows Service that DOES NOT INTERACT with the desktop, it also means that you cannot print anything to the Fax Server printer as it cannot interact and request a filename for the file generated from you.  This is logical, as you should not be trying to use the fax server as another fax client in that environment.

We hope this helps you configure your Fax Server Service more painlessly

Return to main FAQ page...