Fax in Win2k3

  • Thread starter Thread starter Yuval ben-david
  • Start date Start date
Y

Yuval ben-david

Hi,

I have 2 windows 2003 std, both as dc.
i tray to use the fax services, but no luck.
after installing the service & the fax machine {and
chek it}, when i tray to configure it throw the
fax manage, i get arror say's i don't have permissions;
{i am admin user}.
any ide ?
 
I have extactly the same problem.
So right now I am not running the Win2003 fax server as a DC.
There must be some way yo fix this, but so far I have not seen one.
It sure looks like a permissions problem caused when the DC removes all
local users, but that is purely a guess on my part.
 
If you are a domain admin are u able to perform the same operation
successfully?

--
Chandrasekar R
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.
 
Hi there, I am having exactly the same problem,
and yes I am a Domain Admin when I get the permissions error.
 
We tried reproing the problem in house but we couldnt. The following are the
steps that we performed:-

1. Installed a brand new Windows 2003 RTM Standard edition.
2. dcpromo to promote the machine as a DC.
3. Log in as the administrator, install fax and send a fax. Send a fax
succeeded successfully.


Are the above repro steps the same as that u performed??? Are you trying to
connect to the same local machine or to a remote machine (to you other
win2k3 box which is also a DC)?


Thanks,
--
Chandrasekar R
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.
 
The machine having the problems is running Windows 2003 SBS OEM standard.

I tried the same thing you did (trying to reproduce the problem on another
machine with a Windows 2003 standard installation) in a MS.VS 2005
environment, and everything went well. (Fax was working).

It does not matter, wether I try to connect localy to the WinSBS2003 box, or
from remote (from the Windows server in the virtual machine).

I tried to uninstall and reinstall the fax services a couple of times,
unsing booth the WinSBS2003 wizzard and the Windows software panel.
Nothind did solve the problem.

I also tried to trace the problem with regmon and filemon, but could not
find anything conclusive. The only thing I found was a "broken pipe"
response once in a while, during the comunication through the "faxvc" pipe.

chris.
 
Yuval had mentioned in the first mail that he was using Win2k3 Std edition,
that is the reason why we were using this SKU. We will try to reproduce the
problem using SBS2k3. Meanwhile Yuval can u please check whether you are
using Win2k3 Std or SBS2k3 Std?? Also Chris/Yuval if you can try a repro by
freshly installing SBS2k3 then please get back to me with the result.

Some more inline....

Thanks,
--
Chandrasekar R
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.

chk said:
The machine having the problems is running Windows 2003 SBS OEM standard.

I tried the same thing you did (trying to reproduce the problem on another
machine with a Windows 2003 standard installation) in a MS.VS 2005
environment, and everything went well. (Fax was working).
Click to expand...

By VS2005 do u mean the visual studio 2005 (beta version)? Why do u want to
install this?? Are u using the Fax Apis to send faxes or using the fax
console??
 
I am having the same problems as Yuval but I am using Windows 2003 Server
standard addition with all the latest security patches. The XP client
running SP1
with all the latest security patches. The server is configured as
a Domain controller which runs DSN and DHCP. The server also
has two network cards if that matters.
 
In my case I am running Win2003 EE, and adding it as a second DC in a
domain which was originally a Win2000 domain, and the master DC is still
the Win2000 Advanced Server machine. It has been upgraded to talk to the
Win2003 DC following the directions at technet.

Whether I install fax server before making the Win2003 box a DC does not
matter. In other words:

Make the Win2003 box a DC and then add fax, the results are fax cannot be
managed (permission denied).
Make the Win2003 box a fax server (works fine) and then make it a DC and fax
cannot be managed
(permission denied).

The message always indicates to talk to my fax administrator, which is me.
I am logged on as
administrator which is both a memeber of domain admin and enterprise admin
groups.

The workaround I am using is to not make the fax server a DC. That does
work.
 
Exactly the same case here

George Nentidis

Gerry Sinkiewicz said:
In my case I am running Win2003 EE, and adding it as a second DC in a
domain which was originally a Win2000 domain, and the master DC is still
the Win2000 Advanced Server machine. It has been upgraded to talk to the
Win2003 DC following the directions at technet.

Whether I install fax server before making the Win2003 box a DC does not
matter. In other words:

Make the Win2003 box a DC and then add fax, the results are fax cannot be
managed (permission denied).
Make the Win2003 box a fax server (works fine) and then make it a DC and
fax
cannot be managed
(permission denied).

The message always indicates to talk to my fax administrator, which is me.
I am logged on as
administrator which is both a memeber of domain admin and enterprise admin
groups.

The workaround I am using is to not make the fax server a DC. That does
work.
Click to expand...
 
I tried the fix mentioned by Charles Crooks in another related news item in
this group:

/Begin Quote:

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.




/End Quote.

This just worked for me. The Fax service manager is accessible and
properties can be
viewed and changed.

Lets hope it persists beyond the first reboot.
 
842207 is a KB that gives more details about how to make fax work in a DC.

Thanks,
--
Chandrasekar R
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.
 
Back
Top