Can't connect through a firewall

[JoeJarvis]

I am trying out your product and am running into problems with my corporate firewall.

I am able to connect to my site through my browser. For example http://myserver/VaultService and http://myserver/VaultService/VaultService.asmx

Both of these urls connect successfully through internet explorer with my proxy settings configured. However when I try to connect via the vault client I am getting an error. I have configure the network settings to use the system default proxy and have also tried to use a manually configured proxy. But no matter what I do, I get the following error:

Unable to connect to http://xxx/VaultService. No server was found at the specified URL. Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client. Web Exception: The request failed with HTTP status 417: Expectation Failed.

(I replaced my real url with the xxx). I have even tried turning off the chunking.


Can you help? I want to buy the software but my boss won't let me until I get this part working.

[jeremy_sg]

Can you successfully connect through your proxy to vaultdemo.sourcegear.com?

[Guest]

I went to that site and created a user id/password for myself. I can connect via my browser but am still unable to connect through the Vault Client. I get the same "http 417, expectation failed" message.


Unable to connect to http://vaultdemo.sourcegear.com/VaultService. No server was found at the specified URL. Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client. Web Exception: The request failed with HTTP status 417: Expectation Failed.


Do I need to do some additional configuration on my pc? I am running windows xp, sp2 and am current on all the security updates that get pushed by ms.

[jeremy_sg]

The problem is something with the way that Vault is interacting with your proxy. It would be helpful to know what kind of proxy you have. Also, if your workstation and your server are on the same LAN, then it would be possible (and advisable for performance reasons) to bypass the proxy entirely.

The last report of an "Expectation Failed" error message was traced down to a company that had an older proxy, but they either fixed the problem or gave up, because they haven't followed through with me.

[Guest]

I found the answer to the HTTP 417 error. It turns out that it has nothing to do with the proxy but instead involves a very well hidden parameter in the vaultgui.exe.config file.

I spent many, many hours tracking down this particular issue. If you are interested in the resolution, please give me an email address and I will be happy to share.

[jeremy_sg]

I would absolutely be interested. You can email me using the button below this post.

[Paul Lyons]

Any resolution to this?

I'm having the same problem getting through my corporate firewall as well. I can connect via my browser but the client application fails with HTTP Status 417.

[jeremy_sg]

I never got an email with the needed change.

[Paul Lyons]

Any Suggestions?

I'm using version 3.0.1 build 2769 of the client. I've tried modifying the VaultGUIClient.exe.config with the proxy server address. <proxy usesystemdefault="false" proxyaddress="http://myProxyServerAddress:myPort" bypassonlocal="false"/> and <proxy usesystemdefault="false" proxyaddress="myProxyServerAddress:myProxyPort" bypassonlocal="false"/>

I've also tried modifying my machine.config file with the same information... to no avail. I still get the HTTP 417 error.

I'm stumped.

[jeremy_sg]

Email me your phone number using the button below. I'd like to see if we can figure out the magic solution.

[nmvabc]

Hi! I'm having the same problem. Can you send me the solution to patinhofeio@hotmail.com ?

[jeremy_sg]

Joe finally got back to me and recommended adding this line to the <system.net><settings> section in the VaultGUIClient.exe.config file.

Code: Select all

<servicePointManager expect100Continue="false"/>