I regularly work at the office (where I don't need a proxy) and offsite at customer's locations, where I do need a fixed proxy.
My trouble is that Vault Client 4.1.4 can't seem to work with the "Automatic - use system proxy" setting.
When I'm at the office, I explicitly need to set the Vault Client to "Do not use a proxy", and when I'm at the customer site, I need to specifically use "Use a manually configured proxy". This is not a showstopper, but a really annoying issue.
First of all: is this a known problem? Any hope that this issue was fixed in Vault 5.x ?
Second of all: is there a way to influence that setting externally? I have a script that switches my IE and Firefox settings between office and customer sites, so if I could include a step or two to switch those Vault Client settings in the process, that would be a great workaround for now.
Thanks for any hints or pointers!
Marc
Trouble with proxy settings - Vault Client 4.1.4
Moderator: SourceGear
Re: Trouble with proxy settings - Vault Client 4.1.4
Do you close and reopen Vault when you are moving to a different site, or do you just hibernate your computer with Vault open?
Could you try setting Vault to "Automatic - use system proxy" and then reboot your computer? Can Vault connect then?
Could you try setting Vault to "Automatic - use system proxy" and then reboot your computer? Can Vault connect then?
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: Trouble with proxy settings - Vault Client 4.1.4
That's what I'm doing - but still: if I have my settings to "Automatic", even after rebooting, Vault cannot connect to our server. When I pick the manual configuration, it works flawlessly.Could you try setting Vault to "Automatic - use system proxy" and then reboot your computer? Can Vault connect then?
Marc
Re: Trouble with proxy settings - Vault Client 4.1.4
Using the System Default in Vault means it's going to use what is specifically entered in IE. It can't do the detect that IE can do. Only IE can do that particular detect. If you had a proxy entered in IE, then Vault can pick that up, or if you had IE set to use no proxy, Vault can read that.
The way to deal with this will be to continue doing as you have been, or you can change the registry keys where the proxy information is. You might be able to use some sort of registry switcher on the registry keys, but I'm not sure on that one. The registry settings for proxy can be found under HKEY_CURRENT_USER\Software\SourceGear\Vault\Client\Settings.
The way to deal with this will be to continue doing as you have been, or you can change the registry keys where the proxy information is. You might be able to use some sort of registry switcher on the registry keys, but I'm not sure on that one. The registry settings for proxy can be found under HKEY_CURRENT_USER\Software\SourceGear\Vault\Client\Settings.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: Trouble with proxy settings - Vault Client 4.1.4
Yes I understand that - but the point is: the proxy IS properly set in IE, and even then, Vault can't function with it. I can see in Vault that it "sees" the right proxy - but if I use the "Automatic" setting in Vault, and even if in Vault I see that it sees the right proxy, it still doesn't work.Beth wrote:Using the System Default in Vault means it's going to use what is specifically entered in IE. It can't do the detect that IE can do. Only IE can do that particular detect. If you had a proxy entered in IE, then Vault can pick that up, or if you had IE set to use no proxy, Vault can read that.
The way to deal with this will be to continue doing as you have been, or you can change the registry keys where the proxy information is. You might be able to use some sort of registry switcher on the registry keys, but I'm not sure on that one. The registry settings for proxy can be found under HKEY_CURRENT_USER\Software\SourceGear\Vault\Client\Settings.
Re: Trouble with proxy settings - Vault Client 4.1.4
Are you using the Detect function inside IE or did you manually enter in the proxy information there?
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support