"Use system default proxy" not working

Tri · Post by **Tri** » Wed Jun 22, 2005 8:37 am

Client 3.07

The "Use system default proxy" used to work when we connect ot the Vault server using an IP address.

On the site we are working on, the proxy policy has changed so that direct IP no longer work. We must specify the Vault Server via a DNS name. Since then, "Use system default proxy" no longer works. We must specify explictly the proxy settings via "Use a manual configured proxy".

Is there any reason?

Note: I don't think this is related to Client 3.07, I have seen this happen with previous versions.

Thanks in advance.

Post by **jeremy_sg** » Wed Jun 22, 2005 9:00 am

Does the "Use system default proxy" list the right proxy in the checkbox? There is one known bug with the .Net framework where it cannot do automatic proxy configuration, so that could be the cause of the problem.

Tri · Post by **Tri** » Wed Jun 22, 2005 9:14 am

In IE the settings are:
Address: theProxy.company.com
Port: 80

In Vault Client:
"Use the systemm default proxy (http://theProxy.company.com/)"

The values are not entirely identical, however this worked OK when Vault Server was a direct IP address.

Post by **jeremy_sg** » Wed Jun 22, 2005 10:20 am

You never mentioned what didn't work when you had system default checked. Maybe that will give us a clue.

Tri · Post by **Tri** » Wed Jun 22, 2005 10:42 am

Oh sorry, here is the error msg when the connection failed with "Use the systemm default proxy"

"Unable to connect to https://vaultserver.company.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 underlying connection was closed: The remote name could not be resolved"

Post by **jeremy_sg** » Wed Jun 22, 2005 11:15 am

The number one possibility is that the proxy can't resolve the name for your vault server. Can you use the vault server name in IE to see the asmx page?