Fax Service 2003 error

[Alan Johnson]

Hi,

I have installed MS Fax service on Windows 2003 server
member server. I cannot get it to work - I get
error 'Could not open a connection to the fax service.
The Fax serive may not be started or the computer name may
be incorrect' when I open Fax service Manager. I also get
accessed denied when I try configure the fax in Fax
Manager.

Any ideas????

 

[chk]

I got exactly the same issue with an SBS2003 server, it is driving me nuts.


chris.

 

[Naresh [MSFT]]

Hi,

Fax Service Manager requires Administrator privileges to configure the
service and the 'fax service' should be up and runnning when opening the
Service Manager. So verify the status of the fax service in Services.msc.
If the problem still persists give more detials on the issue by
eloborating on the exact Error messages you get at different stages.

--
Naresh Chandrasekaran,
Microsoft Printing, Imaging and Fax Team

This posting is provided "AS IS" with no warranties, and confers no rights.

Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

 

[Charles Crooks]

I am also having problems with MS Fax on 2003.

Originally, the fax service worked fine. The problem seems to have started
after a successful promo to domain controller status.

At all times during the testing, I've be logged on with Admin privileges.

The specific event id is: 32041 from MS Fax. The specific error code is
1307.
Currently the machine is the second domain controller in the network.
I checked the services tab. Fax service is started. Trying to access the
Fax Service Manager, I get from Fax (local) "Could not open a connection to
the fax service", "The fax service might not be started, or the computer
name might be incorrect". Once I hit ok, the Microsoft Fax Service Manager
displays showing the fax service status error at the top of the dialog box
grayed out and the stop button red.
When the Fax Console displays, the error at the bottom states "All fax
printer are inaccessible".

Charles

 

[Charles Crooks]

I have a fix...

The first DC was a win2k standard server. Added a Win2003 Server to the
network. . Did a DCPROMO, reps ok. The problem was caused by the first DC
was still the FSMO, certain Win2003 special accounts such as the required
NETWORK SERVICE were made inactive. Following the info in MS Article
827016, I made the reconmended changes. Then I followed vivian's
reconmendations.

This problem can be caused by some incorrect security settings. Please make
these changes to your Domain Controller group policy

1. Go to administrative tools and open the default domain controller policy

2. Go to local policies\user rights assignment

3. Add the account NETWORK SERVICE to the following rights

Replace a process level token
Generate security audits
Adjust memory quotas for a process
Logon as a service

4. Add the following accounts to "Generate Security Audits"

Local System
Administrators

5. Do a policy refresh and then test the fax service.

Thanks.

 

[chk]

Excellent ! This fixed the problem, thank you !

I have a fix...

The first DC was a win2k standard server. Added a Win2003 Server to the
network. . Did a DCPROMO, reps ok. The problem was caused by the first DC
was still the FSMO, certain Win2003 special accounts such as the required
NETWORK SERVICE were made inactive. Following the info in MS Article
827016, I made the reconmended changes. Then I followed vivian's
reconmendations.

This problem can be caused by some incorrect security settings. Please
make
these changes to your Domain Controller group policy

1. Go to administrative tools and open the default domain controller
policy

2. Go to local policies\user rights assignment

3. Add the account NETWORK SERVICE to the following rights

Replace a process level token
Generate security audits
Adjust memory quotas for a process
Logon as a service

4. Add the following accounts to "Generate Security Audits"

Local System
Administrators

5. Do a policy refresh and then test the fax service.

Thanks.

 

[Alan Johnson]

CAUSE
=====
This issue may occur if the following policy settings are
not assigned to the Network Service account on the domain
controller:

- The "Adjust memory quotas for a process" policy setting

- The "Generate security audits" policy setting

- The "Log on as a service" policy setting

- The "Replace a process level token" policy setting

The Fax service runs under the Network Service account. To
use the Fax service, the Network Service account must be
added to the policy settings in the list. This issue may
occur if Group Policy settings that were applied at the
domain level modified the policy settings for the Network
Service account on the domain controller.

RESOLUTION
==========
To resolve this issue, make sure that the Network Service
account is added to the following policy settings on in
domain policy and local policy:

- The "Adjust memory quotas for a process" policy setting

- The "Generate security audits" policy setting

- The "Log on as a service" policy setting

- The "Replace a process level token" policy setting

Both domain policy and local policy affect these fours
settings. The result is a combination of both domain
policy and the local policy, but the domain policy
overrides the local policy. Please check both of them.

Step 1: To configure the policy settings for the Network
Service account in domain policy, follow these steps:

1. On one of the domain controllers, click "Start", point
to "Administrative Tools", and then click "Default Domain
Security Settings".

2. Expand "Local Policies", and then click "User Rights
Assignment". The policy settings are displayed in the
right pane.

3. Double-click the policy setting that you want to add
the Network Service account to.

4. If the Network Service account is not listed in the
list of users and groups that are assigned to that policy
setting, click "Add User or

Group".

5. In the "Select User or Groups" dialog box,
type "Network Service" (without the quotation marks) in
the "Enter the object names to select"

box, and then click "OK".

6. Verify that "NETWORK SERVICE" is displayed in the list
of users and groups that are assigned to that policy
setting, and then click "OK".

Step 2: Check the local domain policy

1. On the problematic server, click Start >> Run, input
gpedit.msc and click OK.

2. Then follow the same steps to check "user rights
assignment" to make sure that the four user rights have
been added for the Network Service account.