Problem publishing Vault with ISA Server 2000

[marcorusso]

I'm trying to use Vault 3.0 via Internet publishing Vault Server through an ISA Server 2000. I have Vault Server on a server behind the firewall. I published the web server with ISA Server 2000, with both this options enabled:
- Send the original host header
- Allow delegation of basic authentication credentials

If I connect to Vault inside the LAN (not passing through ISA) everything works well.
If I start Vault client from an outside PC trying to access via intranet, then I can logon and choose repository; after this I can see file on repository but I get the following error message:

An error has occurred. The error message is:
The Vault server could not be contacted to perform the operation. Your network connection to the server may have been interrupted. Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client.

If I try to check-in something or I try to view a file in repository (or ask for a Show History, or any other command), I still get the same error.

Someone has the same configuration working?
Thank you

Marco Russo

[jeremy_sg]

I have a few questions for you. Could you email me your phone number using the button below this post?

[NTTAKR]

I think we might be seeing the same problem here.
We are not using ISA Server as Firewall, but I know we do have a firewall and we experience the same error messages.

Internally all works well and externally we have errors stating the server cannot be connected like the error mesage you stated. #

Did you get any resolution to your problem?

Thanks
Andreas

[jeremy_sg]

The solution for Marco was to disable http keepalives for his IIS server. The cause was that his Vault server was running on Windows XP, which can only support 10 simultaneous connections. ISA was starting a new connection for every request instead of respecting keepalives. This meant the server ran out of available connections.