Windows Server 2003 fax problem

From: Kevin (anonymous_at_discussions.microsoft.com)
Date: 12/08/04


Date: Wed, 8 Dec 2004 08:24:55 -0800

I have the same problem. I'm running Win 2003 Server with
the latest updates. My server is a domain controller, and
is attached to two 3com modems. If i remove and reinstall
the fax service, it works for a few hours and then fails
to allow users to submit faxes. The Application log shows
the following:

Event type: Error
Event Source: Microsoft Fax
Event Category: Outbound
Event ID: 32091
Description: The fax was not submitted successfully
because a connection could not be made to the fax service.

The following error occurred: 5.
This error indicates the cause of the error.

Sender Machine Name: \\TEST.
Sender User Name: test.
Sender Name: test.
Number of recipients: 1.

>-----Original Message-----
>I've recently setup the faxing service on two different
Windows 2003
>Std. domain controllers (different domains, different
locations) and
>shared the fax printer but have the same problem on both.
>
>I can send a fax from the server.
>
>I can send a fax from a client computer if the user is a
domain admin
>and everything works as expected. The fax shows up in
the outbox while
>it's sending and moves to the sent items upon completion.
>
>But with domain users the fax appears to go but nothing
happens. It
>never shows up in the fax console outbox or sent items.
No errors are
>logged either. I've read several posts about a domain
policy issue but
>this is something different.
>
>I don't know if it matters but I think I installed the
fax service
>before promoting these servers to domain controllers.
>
>Anybody seen this one?
>.



Relevant Pages

  • Re: What are the best general things to do after a dirty shutdown (Server SBS)
    ... You should check the dirctory services event log and the system event logs for errors and warning in addition to running the dcdiag /c /v command. ... This event can occur if the domain controllers ... Directory Server Diagnosis ... Verifying that the local machine ALPHA, ...
    (microsoft.public.windows.server.sbs)
  • Re: What are the best general things to do after a dirty shutdown (Server SBS)
    ... You should check the dirctory services event log and the system event logs for errors and warning in addition to running the dcdiag /c /v command. ... This event can occur if the domain controllers ... Directory Server Diagnosis ... Verifying that the local machine ALPHA, ...
    (microsoft.public.windows.server.sbs)
  • Re: What are the best general things to do after a dirty shutdown (Server SBS)
    ... test network connectivity to local domain controllers. ... Directory Server Diagnosis ... Verifying that the local machine ALPHA, ... The File Replication Service Event log test ...
    (microsoft.public.windows.server.sbs)
  • Re: Net logon error event id:3096
    ... Verifying that the local machine yblrtgswip1, ... Connecting to directory service on server yblrtgswip1. ... No record of File Replication System, ... interval between domain controllers. ...
    (microsoft.public.win2000.active_directory)
  • Re: GP to force Daily Restart
    ... The Security System could not establish a secured connection with the server ldap/DC01.corp.com/corp.com@xxxxxxxxx No authentication protocol was available. ... The network path was not found. ... domain controllers log these events every five minutes. ... every computer on the network must use DNS servers that can resolve SRV ...
    (microsoft.public.windows.server.sbs)

Loading