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???

Are you serious? Winfax Pro? Have you posted accurate information?
Are you saying the "host PC" is only running Windows XP? Is this a P2P?
--
Russ Valentine
[MVP-Outlook]
"Virgilijus" wrote in message
...
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.



"Russ Valentine [MVP-Outlook]" wrote:

Are you serious? Winfax Pro? Have you posted accurate information?
Are you saying the "host PC" is only running Windows XP? Is this a P2P?
--
Russ Valentine
[MVP-Outlook]
"Virgilijus" wrote in message
...
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???

Surely you know Winfax Pro is dead and gone. Why would Microsoft have a
solution for Symantec's dirty laundry?
--
Russ Valentine
[MVP-Outlook]
"Virgilijus" wrote in message
...
Yep... Seems like the problem is with the RPC server and read one post
stating to look at ms for a resolution.



"Russ Valentine [MVP-Outlook]" wrote:

Are you serious? Winfax Pro? Have you posted accurate information?
Are you saying the "host PC" is only running Windows XP? Is this a P2P?
--
Russ Valentine
[MVP-Outlook]
"Virgilijus" wrote in message
...
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???

Virgilijus

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:
http://www.paulscomputerservice.net/...are/winfax.php

This forum still actively discusses WinFax Pro issues:
http://www.getfaxing.com/cgi-bin/ib3...=SF;f=17;st=50

--


Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


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



"Russ Valentine [MVP-Outlook]" wrote:

Are you serious? Winfax Pro? Have you posted accurate information?
Are you saying the "host PC" is only running Windows XP? Is this a
P2P? --
Russ Valentine
[MVP-Outlook]
"Virgilijus" wrote in message
...
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???

Russ

WinFax Pro is not dead and gone. It does present difficult to resolve
issues!
http://www.getfaxing.com/cgi-bin/ib3...=SF;f=17;st=50

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Russ Valentine [MVP-Outlook] wrote:
Surely you know Winfax Pro is dead and gone. Why would Microsoft have
a solution for Symantec's dirty laundry?
Yep... Seems like the problem is with the RPC server and read one
post stating to look at ms for a resolution.



"Russ Valentine [MVP-Outlook]" wrote:

Are you serious? Winfax Pro? Have you posted accurate information?
Are you saying the "host PC" is only running Windows XP? Is this a
P2P? --
Russ Valentine
[MVP-Outlook]
"Virgilijus" wrote in message
...
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???

But it is not supported and for all intents and purposes is incompatible
with Windows XP.
--
Russ Valentine
[MVP-Outlook]
"Gerry" wrote in message
...
Russ

WinFax Pro is not dead and gone. It does present difficult to resolve
issues!
http://www.getfaxing.com/cgi-bin/ib3...=SF;f=17;st=50

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Russ Valentine [MVP-Outlook] wrote:
Surely you know Winfax Pro is dead and gone. Why would Microsoft have
a solution for Symantec's dirty laundry?
Yep... Seems like the problem is with the RPC server and read one
post stating to look at ms for a resolution.



"Russ Valentine [MVP-Outlook]" wrote:

Are you serious? Winfax Pro? Have you posted accurate information?
Are you saying the "host PC" is only running Windows XP? Is this a
P2P? --
Russ Valentine
[MVP-Outlook]
"Virgilijus" wrote in message
...
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???

Russ

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.

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Russ Valentine [MVP-Outlook] wrote:
But it is not supported and for all intents and purposes is
incompatible with Windows XP.
Russ

WinFax Pro is not dead and gone. It does present difficult to resolve
issues!
http://www.getfaxing.com/cgi-bin/ib3...=SF;f=17;st=50

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Russ Valentine [MVP-Outlook] wrote:
Surely you know Winfax Pro is dead and gone. Why would Microsoft
have a solution for Symantec's dirty laundry?
Yep... Seems like the problem is with the RPC server and read one
post stating to look at ms for a resolution.



"Russ Valentine [MVP-Outlook]" wrote:

Are you serious? Winfax Pro? Have you posted accurate information?
Are you saying the "host PC" is only running Windows XP? Is this a
P2P? --
Russ Valentine
[MVP-Outlook]
"Virgilijus" wrote in
message ...
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???

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.
--
Russ Valentine
[MVP-Outlook]
"Gerry" wrote in message
...
Russ

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.

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Russ Valentine [MVP-Outlook] wrote:
But it is not supported and for all intents and purposes is
incompatible with Windows XP.
Russ

WinFax Pro is not dead and gone. It does present difficult to resolve
issues!
http://www.getfaxing.com/cgi-bin/ib3...=SF;f=17;st=50

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Russ Valentine [MVP-Outlook] wrote:
Surely you know Winfax Pro is dead and gone. Why would Microsoft
have a solution for Symantec's dirty laundry?
Yep... Seems like the problem is with the RPC server and read one
post stating to look at ms for a resolution.



"Russ Valentine [MVP-Outlook]" wrote:

Are you serious? Winfax Pro? Have you posted accurate information?
Are you saying the "host PC" is only running Windows XP? Is this a
P2P? --
Russ Valentine
[MVP-Outlook]
"Virgilijus" wrote in
message ...
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???

Russ

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


--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Russ Valentine [MVP-Outlook] wrote:
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.
Russ

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.

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Russ Valentine [MVP-Outlook] wrote:
But it is not supported and for all intents and purposes is
incompatible with Windows XP.
Russ

WinFax Pro is not dead and gone. It does present difficult to
resolve issues!
http://www.getfaxing.com/cgi-bin/ib3...=SF;f=17;st=50

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Russ Valentine [MVP-Outlook] wrote:
Surely you know Winfax Pro is dead and gone. Why would Microsoft
have a solution for Symantec's dirty laundry?
Yep... Seems like the problem is with the RPC server and read
one post stating to look at ms for a resolution.



"Russ Valentine [MVP-Outlook]" wrote:

Are you serious? Winfax Pro? Have you posted accurate
information? Are you saying the "host PC" is only running
Windows XP? Is this a P2P? --
Russ Valentine
[MVP-Outlook]
"Virgilijus" wrote in
message
...
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???

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.
--
Russ Valentine
[MVP-Outlook]
"Gerry" wrote in message
...
Russ

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


--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Russ Valentine [MVP-Outlook] wrote:
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.
Russ

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.

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Russ Valentine [MVP-Outlook] wrote:
But it is not supported and for all intents and purposes is
incompatible with Windows XP.
Russ

WinFax Pro is not dead and gone. It does present difficult to
resolve issues!
http://www.getfaxing.com/cgi-bin/ib3...=SF;f=17;st=50

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Russ Valentine [MVP-Outlook] wrote:
Surely you know Winfax Pro is dead and gone. Why would Microsoft
have a solution for Symantec's dirty laundry?
Yep... Seems like the problem is with the RPC server and read
one post stating to look at ms for a resolution.



"Russ Valentine [MVP-Outlook]" wrote:

Are you serious? Winfax Pro? Have you posted accurate
information? Are you saying the "host PC" is only running
Windows XP? Is this a P2P? --
Russ Valentine
[MVP-Outlook]
"Virgilijus" wrote in
message
...
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???

Russ

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?

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Russ Valentine [MVP-Outlook] wrote:
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.
Russ

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


--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Russ Valentine [MVP-Outlook] wrote:
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.
Russ

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.

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Russ Valentine [MVP-Outlook] wrote:
But it is not supported and for all intents and purposes is
incompatible with Windows XP.
Russ

WinFax Pro is not dead and gone. It does present difficult to
resolve issues!
http://www.getfaxing.com/cgi-bin/ib3...=SF;f=17;st=50

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Russ Valentine [MVP-Outlook] wrote:
Surely you know Winfax Pro is dead and gone. Why would Microsoft
have a solution for Symantec's dirty laundry?
Yep... Seems like the problem is with the RPC server and read
one post stating to look at ms for a resolution.



"Russ Valentine [MVP-Outlook]" wrote:

Are you serious? Winfax Pro? Have you posted accurate
information? Are you saying the "host PC" is only running
Windows XP? Is this a P2P? --
Russ Valentine
[MVP-Outlook]
"Virgilijus" wrote in
message
...
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???

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.
--
Russ Valentine
[MVP-Outlook]
"Gerry" wrote in message
...
Russ

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?

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Russ Valentine [MVP-Outlook] wrote:
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.
Russ

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


--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Russ Valentine [MVP-Outlook] wrote:
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.
Russ

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.

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Russ Valentine [MVP-Outlook] wrote:
But it is not supported and for all intents and purposes is
incompatible with Windows XP.
Russ

WinFax Pro is not dead and gone. It does present difficult to
resolve issues!
http://www.getfaxing.com/cgi-bin/ib3...=SF;f=17;st=50

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Russ Valentine [MVP-Outlook] wrote:
Surely you know Winfax Pro is dead and gone. Why would Microsoft
have a solution for Symantec's dirty laundry?
Yep... Seems like the problem is with the RPC server and read
one post stating to look at ms for a resolution.



"Russ Valentine [MVP-Outlook]" wrote:

Are you serious? Winfax Pro? Have you posted accurate
information? Are you saying the "host PC" is only running
Windows XP? Is this a P2P? --
Russ Valentine
[MVP-Outlook]
"Virgilijus" wrote in
message
...
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???

Russ

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?


--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Russ Valentine [MVP-Outlook] wrote:
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.
Russ

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? --


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Russ Valentine [MVP-Outlook] wrote:
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.
Russ

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


--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Russ Valentine [MVP-Outlook] wrote:
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.
Russ

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.

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Russ Valentine [MVP-Outlook] wrote:
But it is not supported and for all intents and purposes is
incompatible with Windows XP.
Russ

WinFax Pro is not dead and gone. It does present difficult to
resolve issues!
http://www.getfaxing.com/cgi-bin/ib3...=SF;f=17;st=50

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Russ Valentine [MVP-Outlook] wrote:
Surely you know Winfax Pro is dead and gone. Why would
Microsoft have a solution for Symantec's dirty laundry?
Yep... Seems like the problem is with the RPC server and
read one post stating to look at ms for a resolution.



"Russ Valentine [MVP-Outlook]" wrote:

Are you serious? Winfax Pro? Have you posted accurate
information? Are you saying the "host PC" is only running
Windows XP? Is this a P2P? --
Russ Valentine
[MVP-Outlook]
"Virgilijus" wrote in
message
...
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???

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.
--
Russ Valentine
[MVP-Outlook-in disrepute]
"Gerry" wrote in message
...
Russ

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?


--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Russ Valentine [MVP-Outlook] wrote:
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.
Russ

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? --


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Russ Valentine [MVP-Outlook] wrote:
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.
Russ

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


--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Russ Valentine [MVP-Outlook] wrote:
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.
Russ

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.

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Russ Valentine [MVP-Outlook] wrote:
But it is not supported and for all intents and purposes is
incompatible with Windows XP.
Russ

WinFax Pro is not dead and gone. It does present difficult to
resolve issues!
http://www.getfaxing.com/cgi-bin/ib3...=SF;f=17;st=50

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Russ Valentine [MVP-Outlook] wrote:
Surely you know Winfax Pro is dead and gone. Why would
Microsoft have a solution for Symantec's dirty laundry?
Yep... Seems like the problem is with the RPC server and
read one post stating to look at ms for a resolution.



"Russ Valentine [MVP-Outlook]" wrote:

Are you serious? Winfax Pro? Have you posted accurate
information? Are you saying the "host PC" is only running
Windows XP? Is this a P2P? --
Russ Valentine
[MVP-Outlook]
"Virgilijus" wrote in
message
...
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???