yeah.. went there.. those settings involve messing with each clients' registry though.. right?.. doesnt sound like a real great workaround.. even temporarily.. glad or sad to hear that we're not the only one getting bit right now..

also.. provided we went the registry route.. any idea if we could modify the server only.. and get by.. or would the workstation also have to be modified?


>See http://support.microsoft.com/default.aspx?kbid=834489
>
>It is causing a lot problems right now.
>
>There are settings in the article to disable this new feature. It can be a good workaround until someone founds a real fix!
>
>
>>We currently use Microsoft's Internet Transfer Control in a VB6 app and we use it to http to a website and pull down a more recent copy of the executable if necessary.. we noticed within the last two days that this isnt working anymore.. the app is unable to connect to the website.. what we have found so far .. is that the machines that are having the problem are machines that have applied the most recent critical update for IE6 and when we looked at the write up.. the update fixes a security hole with being able to sppof an address via InternetOpenURL.. we also have observed that this functionality continues to work when one of the machines (either the server and/or the workstation) has not applied the update.. (we have a second app that refers to a different server that hasnt been updated.. and the second app works fine.. the first app does not).. I have been looking all over the net for similar complaints and have found absolutely zero.. anyone out there? We're stumped.. Microsoft
>>broke their own ActiveX object that came with VB6 (Visual Studio Enterpise/Development Edition) and hasnt even thought about addressing the issue?.. I'm really perplexed that I havent seen any other posts.. Google, Microsoft.com, Universal Thread.. etc.. Any ideas folks?
>>
>>Thanks in advance...
>> -- Len