>>The data is transferring and it times out. We have that same situation with other testers as well. As soon as the request has been launched for at least 30 seconds, it'll time out. And, it times out while transferring. The lights on the router are flashing a lot when transferring and that is the case when it happens.
>>
>>As for ClientProperty(), I only saw the Timeout parameter and that is only for the connection and not the transferring.
>
>It's all related... change it - it'll help with the problem.
>
>Another alternative - use wwSOAP. It'll go through completion no matter what...

I mentioned ClientProperty() but I should have mentioned ConnectorProperty(). If you use low level and make use of ClientProperty() then this might work in your case. That might be why you mentioned it should work. Have you tried the ConnectorProperty() approach directly. This is where it does not work here. Otherwise, can you show me an example on establish the low level reference in order to benefit of that property?

Basically, right now, we are loading the object like this:

loUniversalThread=Createobject("mssoap.soapclient")
loUniversalThread.mssoapinit("http://www.levelextreme.com/universalthread.wsdl")

From that point, if we show the ConnectorProperty('Timeout') value, it'll show 30000. If we change it and show it again, it'll show our new value. However, from this point, it has no effect on the duration of the download. However, as you said, if we make use of the ClientProperty() instead, that might work. However, I'm not sure how to establish that reference to the current object.