Re: Fax Service in Windows Server 2003

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Shawn P. Ryan (spryan_ca_at_hotmail.com)
Date: 05/04/04


Date: Tue, 4 May 2004 12:36:08 -0400

Wes,

I am having this problem on SBS2003, but do not have the Domain Controller
Security

Policy console, do you know how to get to it? I have the Local Security
Policy console, but it seems to be locked and I can not add any users or
groups to the items you mention, as the button is greyed out. Do you know
how to get around this?

Regards,

Shawn P. Ryan

"Wes Baggerly" <wbaggerly@labsoftlims.com> wrote in message
news:ueIFqeMGEHA.2208@TK2MSFTNGP09.phx.gbl...
> I found the answer on another string. It was posted by Vonid from
Microsoft.
> This problem seems to occur when you try to install Fax Services on a
domain
> controller. Here is what Vonid said:
>
> [Beginning]
> Fax Service runs under the account NETWORK SERVICE. In most cases on DC,
> such issues happen when applying the domain policy changes the policies
that
> apply to NETWORK SERVICE. The following policies need to be enabled for
> NETWORK SERVICE for fax to work.
>
> (1) Adjust memory quotas for a process
> (2) Generate security audits
> (3) Log on as a service
> (4) Replace a process level token
> [End]
>
> If your having this problem on a domain controller then this is were you
can
> find the settings:
> (Start | All programs | Admistrative Tools | Domain Controller Security
> Policy)
> In the left pane, choose Local Policies then User Rights Assignment. You
> will then see the setting on the right.
>
> If your having this problem on a local machine then this is were you can
> find the settings:
> (Start | All programs | Admistrative Tools | Local Security Policy)
> In the left pane, choose Local Policies then User Rights Assignment. You
> will then see the setting on the right.
>
> I hope this helps everyone. The more we get this answer out there the
easier
> it will be for others to find it.
>
> Wes
>
>
> "Wes Baggerly" <wbaggerly@labsoftlims.com> wrote in message
> news:uPt$V4AGEHA.4084@TK2MSFTNGP11.phx.gbl...
> > I just installed the Fax Service in Windows Server 2003 and I get the
> > following errors when I open the Fax Service Manager: "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 click OK the console will open but there are no devices. I then
try
> > to open the properties I get "Access denied".
> >
> > A shared fax does show up in the Printers and Faxes. But when I try to
> > access those properties I get this message: "You do not have permissions
> to
> > complete this operation. Contact the fax administrator for more
> > information." I click OK and the properties open.
> >
> > I have always logged on as Administrator with all of the rights. I have
> also
> > tried to fix this by installing different modems and uninstalling and
> > reinstalling the software many times. I have seen one other post about
> this
> > but it was a reply to an original, but I did not find any post with an
> > answer. Does anyone have any suggestions on how I might fix this?
> >
> > Thanks in advance.
> >
> >
>
>



Relevant Pages

  • Re: OSX doesnt play nice... what a suprise (rolls eyes)
    ... >In Windows, from Administrative Tools, select Domain Controller Security ... I could not for the life of me find these settings. ... On an XP box, go to Local Security Settings, Local Policies, ... Security Options, Domain Member: Digitally encrypt... ...
    (comp.sys.mac.advocacy)
  • RE: Could not open connection to fax service
    ... I was installing on a domain controller. ... Fax Service runs under the account NETWORK SERVICE. ... find the settings: ... choose Local Policies then User Rights Assignment. ...
    (microsoft.public.win2000.fax)
  • Re: Network + AD = Tighten Security
    ... > Dear Steve, ... >> addition I would enable auditing of logon events on the domain controller ... >> zones of your users to have minimum settings and taking advantage of the ... You should also run Microsoft Baseline Security ...
    (microsoft.public.win2000.security)
  • Re: "broken"/missing ACLs?
    ... explains many of the settings that can cause a problem. ... >the domain controller consistently. ... >for the network adapter, bad CAT5 cable, or even a problem with the switch ... >> icon and the ACL name itself is a long string of alphanums. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Importing .adm settings to other domain controllers
    ... out from the report the settings that are critical for compliance. ... with anywhere from 5 to 100 client workstations in the hospital. ... ensure that the domain controller policies lock down the system as much as ... instructions in the install manual. ...
    (microsoft.public.windows.group_policy)