Just wanted to add that on Vista Business clients outgoing faxes work fine
using "Windows Fax and Scan".

--
Thanks!



"Walter Kanov" wrote:

Hi,

i have a simple 2008 server setup. One server running everything (active
directory controller, file/print sharing, sql database, IIS, etc) including
fax server.

I can see incoming faxes and can send new faxes on the server using Windows
Fax and Scan just fine.

I can also see the "Fax on Server" printer on my windows xp pro sp2 clients
just fine, and open Fax Console and see all the faxes that came in just fine.

The problem is that when i click "New Fax" button in the Fax Console or
choose "Send a Fax" from the file menu in the Fax Console on the windows XP
clients, nothing appears. Mouse pointer switches to hourglass for a second
or two and then goes back to normal. Status bar says ready. When I choose
Fax Printer Status in Fax Console it says "Server" in the Fax Printer column,
and "Online" in the Status column.

After reboot, upon first attempt to send a fax, i get two messages in the
event log from Microsoft Fax source:
Event ID: 32026
Description: Fax Service failed to initialize any assigned fax devices
(virtual or TAPI). No faxes can be sent or received until a fax device is
installed.

and

Event ID: 32068
The outgoing routing rule is not valid because it cannot find a valid
device. The outgoing faxes that use this rule will not be routed. Verify that
the targeted device or devices (if routed to a group of devices) is connected
and installed correctly, and turned on. If routed to a group, verify that the
group is configured correctly. Country/region code: '*' Area code: '*'

So it appears that it either can't read rules from the server (there is only
one default built-in rule there that it is ok to send faxes using the modem).
Or it wants me to define rules on each client, but where would i do that?

Any help would be appreciated.

--
Thanks!


p.s. I tried
http://support.microsoft.com/kb/884018/EN-US/
and
http://h10025.www1.hp.com/ewfrf/wc/g...name=c00270202
thinking that this may be a permissions issue. But neither one has helped.