Winfax Pro sharing problems

I just install a new PC with win-xp/sp3 and in trying to setup winfax with
sharing to the host pc, which is also running win-xp/sp3 but I keep getting
the error RPC server not available when the client tries to connect to the
host pc (2 other pcs have no problem). In the even log, I get:

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10009
Date: 6/11/2009
Time: 10:35:56 AM
User: NAUJAS\Virgil
Computer: NAUJAS
Description:
DCOM was unable to communicate with the computer Home using any of the
configured protocols.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Any ideas what is causing this??? Or how to fix it???

Yep... Seems like the problem is with the RPC server and read one post
stating to look at ms for a resolution. :)

Surely you know Winfax Pro is dead and gone. Why would Microsoft have a
solution for Symantec's dirty laundry?

I am a Winfax Pro user and use it a lot on a Windows XP SP3 platform.
There are problems running Winfax Pro, which can be difficult to resolve
and may prove insoluble. My usage is on a standalone computer so I have
no experience of trying to share between computers.

I found this link:

This forum still actively discusses WinFax Pro issues

WinFax Pro is not dead and gone. It does present difficult to resolve
issues!

Is not supported is not totally the situation! I thought as you until I
conducted research to contribute to this thread. You can still pay
Symantec for help with a Winfax Pro issue.

Notwithstanding it would more helpful if you referred persons requiring
help with WinFax Pro issues to the forum at
http://www.getfaxing.com/cgi-bin/ib3...=SF;f=17;st=50

Making negative comments about WinFax Pro does not help users when
solutions can often be found

But it is not supported and for all intents and purposes is incompatible
with Windows XP.

Most of us feel it is more helpful to encourage users to move on to a
product they will actually be able to get to work.

When did that become my job? The topic of this group is support of
Microsoft's fax software for XP.
I haven't the time to try out all the third party fax software in the
market.

Then suggest a better freely available alternative! You probably do not
as you do not know one!

If I were an attractive lady I wouldn't want you for a Valentine. You're
so unhelpful and so unco-operative! I suggest you do not answer future
questions about WinFax Pro as your replies are so negative. I gave you a
simple way to respond with the link to the forum. This does not stop you
expressing your views about the antiquity of WinFax Pro. Why bring the
MVP logo into disrepute by being so obstinate?

Bit of an over-reaction I'd say. You're the one who criticized me for being
hard on Symantec, so I simply explained why my recommendations differ from
yours. The archives of this group reveal there are many here who feel that
Symantec really dropped the ball on WinFax Pro but were less than
forthcoming about it with their customers, leaving many stranded with a
product they can not get to work on current platforms. That's why I don't
encourage users to continue to look for solutions with the product.
Sadly, Microsoft never stepped up to the plate to make their XP fax software
a viable alternative.

I'm not sure I understand why you are requesting me to pass on the link if
in my opinion it might send users into a dead end. Since you feel otherwise,
couldn't that be your job?
The beauty of these peer-to-peer newsgroups is that they permit many
opinions and let savvy end users figure out what might work best for them.
The more opinions the better. None is worth more than another. So post more
often. Lend a hand around here. That's how it works.

You are no Peter Mandelson or Lord Mandelson etc as his official title
is now. He the Prince of Darkness and the Master of Spin in the UK at
the moment!

Where and when did I do this "You're the one who criticized me for being
hard on Symantec"?

I agree with your comments about Symantec and Microsoft Fax. They have
made decisions neither of us can reverse.

My only disappointment is that you choose to react in this way "That's
why I don't encourage users to continue to look for solutions with the
product." The users have a useful product and are seeking help. It's not
their fault that Symantec chose to act the way they did. Why punish the
user for what Symantec did?

As I said in my last post all you need to do is pass the link on as a
possible source of help. Is that too much to ask

I did on this occasion. However, my knowledge does not cover printer
problems to any depth. I generally cover other Windows XP newsgroups. It
is just that as a user of WinFax Pro I have some idea of how the
programme works.

" it might send users into a dead end" Of course it might but at least
they are more likely to find out why! Your way perpetuates a nanny knows
best situation. Surely it is better to give users the opportunity to
choose.

I notice you did not answer this question. "Where and when did I do this
"You're the one who criticized me for being hard on Symantec"?"

I never told you how you should post. You told me how I should post: "I
suggest you do not answer future questions about WinFax Pro as your replies
are so negative. It would more helpful if you referred persons requiring
help with WinFax Pro issues to the forum at
Making negative comments about WinFax Pro does not help users when solutions
can often be found."
I'll post my thoughts. You post yours. Seems to be the way the world works.

Ok, if other clients are connecting to the Host, then the problem is
specific with the CLIENT PC. Do not , and I repeat D O N O T change any
settings on the Host.

- Make sure no firewall is blocking, or anti-virus that could be blocking
ports. As a test, turn off all firewall and anti-virus on the client PC.
You'll need to add "wfxctl32.exe" to your exceptions in the firewall (if
enabled)
- Make sure DCOM is enabled on the PC. (you'll have to look this up)
- What version of WinFax is the client using? is it the same as the Host?

the site referenced in other posts has changed, if all fails you can always
post

Russ I always enjoyed your informative posts regarding winfax se & outlook
back in the ol2000 and ol98 days..why all the hate for winfax now?

It's not hate. It's just becoming fed up with a company and product that has
served its end users poorly in my opinion. WinFax SE was just the first
indication of the problem. The product never worked even after two versions
but no one took responsibility for that fact nor attempted to fix it. That
same lack of support and development eventually overtook even the flagship
product. I know. Caveat emptor. But emptor was never given any indication
that the product was no longer undergoing any development that would keep it
current and functioning.

I think that has happened since I posted but thanks for your
information.