Did XP SP2 break DCOM? [Yes - Resolved]

I just got a brand-new system the came with XP SP2. My server is XP SP1 and my other client is also XP SP1.

The client with SP1 can use DCOM correctly, all my components are working fine between it and the server with SP1.

However, this new system, with DCOM settings exactly the same, refuses to load the client DCOM consuming app, giving me Error #70, Permission Denied.

I've been over this many times and I'm sure the settings on the SP2 client are the same as the settings on the SP1 client.

The server settings are EVERYONE, INTERACTIVE, and GUEST, so that should include the SP2 client in the trust domain.

The only thing left to suspect is SP2. Is that possible? I have completely killed off SP2's "manditory" firewall. There is no other firewall or AV running. All security updates are installed.

Any ideas? Do I have to re-install XP without SP2?

Thanks!

Dave

I had the same sort of problem: I kept on getting 'The stub received bad data'

I uninstalled XP2 and everything worked fine again.

Still running on SP1 now.

LOt's of 'old' programs don't run on SP2, including an lot of M$ products, this is due to the fact that thes programs use 'illigal' tricks or holes that have been plugged by SP2.
Even M$ breaks it's own rules.
Just look on MSDN for the official list with progrs that don't run (80 or so i believe)

MSDN:
http://support.microsoft.com/default.aspx?kbid=842242

talks about programs that stop working due to ports being blocked by the new firewall.

I turned off the firewall completely, so this should not be a factor. I am wondering if DCOM is actually broken by SP2. It seems to be the case - I hope I am wrong.

According to MSDN:
http://www.microsoft.com/technet/pro.../sp2chngs.mspx

Quote:

---

The DCOM infrastructure also has additional access control restrictions to reduce the risk of a successful network attack.

---

But they don't go into detail what the effects to DCOM are, or how to deal with it... Any help?!?!

HELP!

Thanks in part to this article:
http://blogs.msdn.com/greggm/archive...29/200907.aspx

I got DCOM to work with XP Prop SP2. So I guess this is resolved finally - yay!

Dave