I am trying to connect to Vault Server (version 3.5.1) sitting behind ISA Server 2000 (published with Web Server Publishing Rules on ISA Server).
When I connect within local area network everything goes fine. I can connect and work with my repository. When I try to connect from the outside world I just can connect to VaultServer (status is "connected") and choose the repository but after that I get scary looking message:
"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."... and then something about 403 Error: Access Forbidden
This, I think, is very similar (if not the same) problem a user nicknamed "marcorusso" had (http://support.sourcegear.com/viewtopic.php?t=2680) but the thread does not provide any help.
I just wonder if someone has solved this issue.
Thank You
Maciek
Vault Server Behind ISA Server 2000
Moderator: SourceGear
Could you check your Event Viewer and see if any errors were logged there at the same time?
Do you have any monitoring of the traffic through the ISA server happening so that you could maybe see at what point it blocks access?
Also, you can connect using the following addresses, right?
http://<vault server>/vaultservice
http://<vault server>/vaultservice/vaultservice.asmx
And here's Microsoft's article on allowing 3rd party traffic through: http://support.microsoft.com/default.as ... -us;295667
Do you have any monitoring of the traffic through the ISA server happening so that you could maybe see at what point it blocks access?
Also, you can connect using the following addresses, right?
http://<vault server>/vaultservice
http://<vault server>/vaultservice/vaultservice.asmx
And here's Microsoft's article on allowing 3rd party traffic through: http://support.microsoft.com/default.as ... -us;295667
There are no errors logged in the Event Viewer both at client and server side at the time I try to connect.
I run briefly through ISA logs but didn't find anything unusual beside the fact that Vault Server behind ISA is returning HTTP Error code: 403 (one of the subsequent calls in web proxy log to vaultservice.asmx page results with this error code). It happens RIGHT AFTER I successfuly logon with Vault Client to Vault Server and choose the repository.
I can connect without any problems to these pages:
http://<vault server>/vaultservice
http://<vault server>/vaultservice/vaultservice.asmx
I can also login and view repository via ~/VaultService/VaultWeb/login.aspx
The computer with Vault server installed behind ISA has full access (all IP traffic) enabled through ISA Server (configured policy rules).
The computer with the Vault client is not part of the corporate network (it's neither Secure-NAT client nor has the Firewall Client installed). It uses no proxy to connect to Vault server.
I run briefly through ISA logs but didn't find anything unusual beside the fact that Vault Server behind ISA is returning HTTP Error code: 403 (one of the subsequent calls in web proxy log to vaultservice.asmx page results with this error code). It happens RIGHT AFTER I successfuly logon with Vault Client to Vault Server and choose the repository.
I can connect without any problems to these pages:
http://<vault server>/vaultservice
http://<vault server>/vaultservice/vaultservice.asmx
I can also login and view repository via ~/VaultService/VaultWeb/login.aspx
The computer with Vault server installed behind ISA has full access (all IP traffic) enabled through ISA Server (configured policy rules).
The computer with the Vault client is not part of the corporate network (it's neither Secure-NAT client nor has the Firewall Client installed). It uses no proxy to connect to Vault server.
Here's another discussion I found that seems to sound similar to your situation: http://community.sgdotnet.org/forums/thread/10923.aspx. Try their suggestions and see if that helps.