fax sharing not supported in Windows 2000 Server

I'm trying to share a faxmodem installed in a Windows 2000 Server, but the "Sharing" tab of the modem properties claims that "Sharing is not supported". There used to be an article in the MSKB numbered 220139 that acknowledged this problem - unfotunately, this article is no longer available. There are 200 points available for anyone who can provide a workaround for this problem.

Here are things I've already tried:

1.) MSKB 301200
2.) MSKB 265223
3.) Winfax Pro 10.0 (which has some unadvertised technical deployment restrictions that make it worthless in 80% of production networking environments, so don't buy this if you plan to use it in any deployment other than standalone use at home.)
4.) Technet sbfupd.exe download - which is for Small Business Server 4.5 only.

There may be money in the budget for the purchase of a 3rd party fax sharing product, but it will be a bit of a hard sell after the Winfax Pro fiasco (Pro - ha! should be called Winfax Amateur. What garbage.)
Who is Participating?

Improve company productivity with a Business Account.Sign Up

Computer101Connect With a Mentor Commented:
PAQed, with points refunded (200)

E-E Admin
Hey Doublehorn,

Small Business Server 2000 does have fax sharing as an add-on on one of it's many cd's, if you have a copy of that lying around, it would be a cheap thing to try but i'm not sure if it'll install and run on a non-sbs 2000 server...

Personally i have had the same problem a while ago in trying to make the my workplace a bit closer to the paper-less office utopia... and i found that GFI FaxMaker is very good for this. What you can with that, is print to it from workstations - appears as a printer on each wks and just pops up a form window to fill out when printing to it. it also supports faxing straight through Outlook which is quite nice.
In terms of receiving if you're chasing that aswell, it can be set to receive faxes, convert them to pdf and stick them in a folder or inbox.

The cheaper but a bit more labour and skill intensive solution which i also find quite good is hylafax. it's a freeware, open source faxing server, but it only runs on linux. It basically appears as a postscript printer on each wks. The nice thing about hylafax is that you can program it yourself. for instance i set it up so that when you send a document to it it scans the postscript for the string "To: " and when it finds that string it grabs the number which follows and faxes to it. Then it looks up the user account which submitted the job, runs an LDAP query via SAMBA, grabs that username's email address and sends either a failure notice or a confirmation that it was sent. In that example i set any receiving faxes to arrive at the receptionists inbox in pdf format. Was a bit of a bitch to set up, but now that it's running i haven't had a problem since (running the last 6 months...) This is just to give you an idea of what you can do with it... :)

Anyway, hope this is of some use to you.
Lee W, MVPTechnology and Business Process AdvisorCommented:
No comment has been added to this question in more than 21 days, so it is now classified as abandoned..
I will leave the following recommendation for this question in the Cleanup topic area:
PAQ - Refund

Any objections should be posted here in the next 4 days. After that time, the question will be closed.

EE Cleanup Volunteer
doublehornAuthor Commented:
Hello to everyone who contributed to this question (including txsolutions, whose comment I missed reading until today - sorry about that tx.)

Ultimately, I ended up abandoning shared faxing in Win2K Server as none of the 3rd party shared faxing apps (even GFIfaxmaker and Hylafax, which do seem like the nicest apps of this kind) could integrate smoothly with the 911 CAD suite made by FDM for which I needed shared faxing in the first place.

After much experimentation and many tears, I ended up convincing my Fire/Rescue client to purchase a cheap Dell workstation for installation of Win2003 Server for use as a dedicated fax server, whose shared faxing service works quite nicely, although it requires 2 separate, unintuitive fax service management consoles where there really ought to be one if you ask me. The CAD suite communicates adequately (not perfectly, even today) with the fax service and the client is happy enough.

If I had it to do all over again, I'd not have spent a single second with shared faxing on Win2K server, although I still like it better than 2003 server for everything else.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.