I will try this then let you know.
Thanks.
Main Topics
Browse All TopicsI am using a DCOM client to connect to the DCOM server on another machine. Both are running Windows XP. I am using the same user user account on both the machines. I have disabled security on both sides.
If both the client & server are on the same machine, I am able to make the connection successfully.
When the server on on another machine, I get error 80080005.
Any ideas why this is happening.
Thanks.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Sorry. It did not make any difference. There has to be something else.
I also checked all the event logs. I can see the security audits of the connection with the user id. This audit is successful. So, the remote connection comes to the machine. Maybe it is not connecting to the COM server. Dont know why...
I don't know if this will help at all, but it might give you a few ideas to try:
http://blogs.msdn.com/adio
Particularly the first comment:
I had a similar problem with a poorly designed COM server that, in a few cases, deadlocked (waiting for a mutext to be signaled) just before calling CoRegisterClassObject.
Another possible cause of this error is a debugger that breaks into the COM server EXE process and will not let the process call CoRegister... in a timely manner.
The third case when I saw this error was something about a COM server registered by the Installshield installer "only for this user" (Administrator), but the launching user was another account.
Business Accounts
Answer for Membership
by: jkrPosted on 2008-04-10 at 13:22:47ID: 21328978
Have you tried the following?
Select allOpen in new window