This might be way off base but...
A couple of days ago I had a client that could get to 98% of his internet sites but could not get to 2 secure sites that he used. On one of the sites he had his website and he could view it but if he tried to do any changing on it he always got a timeout when he posted the updates. After trying everything in the book I finally changed the ethernet packet size and everything started working OK (don't ask me why).
Try this: go to a dos prompt and type "ping-f -l xxxx " (no quotes). Change the "xxxx" to any packet size. I'd start with 1490. If you get a message that states the packet needs to be fragmented then rerun the ping with a lower value. Do this until you get to a packet size that pings successfully.
Once you have a good packet size add 28 to it (for the frame overhead) and that value will be the largest packet size that you can send without a need for fragmentation. Get a utility like DRTCP (you can get this from www.dslreports.com) and adjust the MaxMTU setting for tcpip protocol to the size you came up with above. Reboot and retry.
For some reason I haven't figured out yet, some broadband providers seem to be using smaller ethernet packet sizes thanthe default 1500, and for some other reason I haven't figured out yet there appears to be some sites that don't respond to these and thus timeout. I know this corrected a timeout problem with this person. I ended up setting a MaxMTU of 1490 (1462 being the max packet size I could send with the ping command) and kaboom, no more problems.
My guess is that this won't solve your ActiveX problem (but then again, who knows, maybe that's a timeout problem too?).
Try it and see what happens.DrBob:>)