>Since I'm not in the mood for a lecture from one of our network support staff, I thought I'd take another stab at this issue in this forum.
>
>After seeing all the Web Services stuff at GLGDW last week, I spent a fair chunck of time this weekend building a cool demo showing the capabilities of Web Services. The intent was/is to show the Web Services demo at a conference we put on for the users of our products (it takes place next week) and explain some practical uses of Web Services for credit unions.
>
>I put the demo together on my home P.C., where I access the Internet with a cable modem. Here at work, we access the Internet through some type of firewall (Proxy Server is also used).
>
>I'm almost certain the problem I'm having has something to do with getting the web services request back through our (brick) firewall. When I run a simple little program to access info from a Web Service, after anywhere between 20 and 45 seconds, I get an OLE error - Unknown COM Status code.
>
>So, the question is ... has anyone else been experiencing similiar problems? And if so, was there some setting that had to be changed, for example, on Proxy Server, or anywhere else for that matter - to make this work?
>
>Any feedback would be appreciated. And, yes, I did have a look at the SOAP Toolkit help file, but I'm new to this stuff so it was kind of over my head.

The only time I got that error was for long requests. It times out at 30 seconds. Even if the download has already started, it'll time out at 30 seconds. The download has to finish before it kicks in.

But, if you can run it from a modem connected without a firewall, then the problem might be when behind a firewall.