Problems using web services & ISA Server

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Mike Malter - 23 Mar 2005 00:45 GMT

I have a standalone Windows Server 2003 running IIS, SQL Server and ISA
Server.

We've managed to successfully disable socket pooling, got vpn working and
have published a web site.

The box is designed to call web services on a series of servers scattered
throughout the United States and pull detailed activity records and then
aggregate and report. The problem is that we get the following error
message whenever we try to hit any of our servers: "The underlying
connection was closed: Unable to connect to the remote server."

I've nosed around a bit and thought it might have something to do with the
way IE was configured. We messed around with the web.config file to make
sure that the proxy was not using the system default, which didn't help. We
have to use the proxy because we can't get out otherwise.

Has anyone had any experiences with successfully running a web site and web
services on a box using ISA Server?

Any help would be greatly appreciated.

Thanks.

Mike Malter

Reply to this Message

Mike Malter - 23 Mar 2005 01:00 GMT

Forgot to mention we are running ISA Server 2000.

>I have a standalone Windows Server 2003 running IIS, SQL Server and ISA
>Server.
[quoted text clipped - 21 lines]
>
> Mike Malter

Reply to this Message

[MSFT] - 23 Mar 2005 07:41 GMT

Hello Mike,

To make a web service crossing a firewall, we have to set is Proxy
property. For example:

IWebProxy proxyObject = new WebProxy("http://proxyserver:80", true);
math.Proxy = proxyObject;

Also, to test the proxy, can you access other web pages on the same server
in IE?

Luke

Reply to this Message

Mike Malter - 25 Mar 2005 00:09 GMT

Luke,

Thanks for jumping in but actually this is not ultimately what solved the
problem. I finally had to open a case and use one of my tech support
incidents with the ISA Server group.

The solution was to create allow packet filters for port 80 and 433. The
reason is that nothing can get out on an ISA box unless there is a packet
filter for it. For clients not on the box, there is NAT, proxy or the
firewall service itself but the problem arises when you are on the actual
ISA box itself and try to do something.

Thank you for your willingness to help.

Mike

> Hello Mike,
>
[quoted text clipped - 8 lines]
>
> Luke

Reply to this Message

[MSFT] - 25 Mar 2005 06:38 GMT

HI Mike,

Thank you for the clarify. I really appreciated it.

Luke

Reply to this Message

Problems using web services & ISA Server

Free Magazines