Microsoft Shared Fax gets bogged down on long distance faxes

The firm that I work at is using Microsoft Shared Fax Console on a
Windows 2000 PRO machine. All of the other workstations in the office
send faxes through the one machine (all running Windows 2000 PRO).
Sometimes, when we send faxes (mostly long distance) the fax will not
go through. For a while, none of the long distance faxes were going
through. Most commonly, the Fax Console gets a busy signal. All of
these faxes send perfectly through our manual fax machine.

Notes:
Yes, I have set up dialing rules for the modem. Some of these faxes
did eventually go, but it was sometimes days later.

Thanks,
Jeff

Henry
Sun Sep 19 17:13:25 CDT 2004

You may want to check the Line Quality on the Fax Line.
Most telcos will have a number that you can call that will fax back a
detailed report including signal:noise ratios etc.

You may also want to increase your pause time between the area code and
number to be called ( add a comma for each 2 second pause you want )
and ensure you're not running other services such as Call waiting etc on
that
Fax line.

Depending on the value you place on the Fax facility and your time and
effort in tracing/debugging, it may pay to go with a more robust and
feature rich 3rd part solution. (such as Winfax, GFI Faxmaker etc....)

--
Henry Craven {SBS-MVP}
Melbourne Australia

"Jeff Masse" <jeff_jam@hotmail.com> wrote in message
news:13566be9.0409181306.5bb663e8@posting.google.com...
> The firm that I work at is using Microsoft Shared Fax Console on a
> Windows 2000 PRO machine. All of the other workstations in the office
> send faxes through the one machine (all running Windows 2000 PRO).
> Sometimes, when we send faxes (mostly long distance) the fax will not
> go through. For a while, none of the long distance faxes were going
> through. Most commonly, the Fax Console gets a busy signal. All of
> these faxes send perfectly through our manual fax machine.
>
> Notes:
> Yes, I have set up dialing rules for the modem. Some of these faxes
> did eventually go, but it was sometimes days later.
>
> Thanks,
> Jeff