1. Did you run WinsockFix, or WinsockXPFix ?
2. Re-registering core cryptographic/security-related dlls often fixes the problem; see this post for specific instructions on that, as well as a few other possible solutions.
3. Is this problem specific to IE? Install Firefox and see if you experience the same access problems.
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370
1. Post the full details of the DCOM error; they might help. To do so:
Double-click on a DCOM error to open its properties window. In the Properties window, click on the button with the graphic of two pieces of paper on it; the button is at the right of the window just below the up arrow/down arrow buttons. You won't see anything happen when you click the button, but it will copy all of the details to the Windows clipboard. You can then paste the details into your next post here.
2. Before running the actual WinsockXPFix repair, did you have the program make a backup of your Registry first?
Of course you did, because you, like most other people, are a cautious and careful troubleshooter, right? :mrgreen:
If you were paranoid enough to make the Registry backup, run the ERDNT.exe program found in the backup folder to restore the Registry to its "pre-fixed" state. See if that eliminates any of the problems.
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370
{22D6F312-B0F6-11D0-94AB-0080C74C7E95} is the Class ID for a version of Windows Media Player. Is it always that CLSID listed in the event log errors?
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370