External vs internal access

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
jimmurray
Posts: 24
Joined: Fri Jan 11, 2008 7:24 am

External vs internal access

Post by jimmurray » Fri Feb 29, 2008 2:09 am

Hi,

Wha'ts the best way of dealing with his scenario:-

Got a laptop that I use to access vault in the office, from home or at a client site. This isn't a problem if I can use a vpn as I can login using the internal IP address of the server; 172.20.2.100.

However if I can't use the vpn and need to use HTTP/HTTPS then I need to use an external address(82.152.xx.xx) to access the server. I can login via the vault client as it lets me change the server address on sign in but if I try to access any source it uses the internal address 172.20.2.100 which won't work outside the office. What's the best way of dealing with this ? I could use a dns entry for the vault server e.g. vaultserver and have an entry in the hosts table which I change to either the internal or external address as needed but would prefer not to. I'm using the previous version of Vault to the one just released and am using the the Vault VS 2005 Client.

Thanks
Jim

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Fri Feb 29, 2008 3:00 pm

If you can't get the VPN configured to use the internal address, then the solution would be to modify your hosts file. Otherwise you'd need to rebind the project every time you open it with a different Vault Server connection string.
Linda Bauer
SourceGear
Technical Support Manager

jimmurray
Posts: 24
Joined: Fri Jan 11, 2008 7:24 am

Post by jimmurray » Sat Mar 01, 2008 3:34 am

What's the easiest way of changing the projects to use a dns name rather than an IP address. At the moment I've got:

<SccAuxPath>http://172.20.2.100/VaultService</SccAuxPath>

in all my projects. i've tried unbinding and then binding using a dns name rather than IP addresss but when I exit and reload the project it always looks for 172.20.2.100.

jimmurray
Posts: 24
Joined: Fri Jan 11, 2008 7:24 am

Post by jimmurray » Wed Mar 05, 2008 12:34 am

Is there any way of doing this?

ian_sg
Posts: 787
Joined: Wed May 04, 2005 10:55 am
Location: SourceGear
Contact:

Post by ian_sg » Wed Mar 05, 2008 5:13 pm

You've got the right solution: use DNS rather than IP.

The fact that your binding isn't updating is a bug (that will be fixed in 4.1.1). In the mean time, the work-around is to exit the dialog after unbinding to get it to notice the change:

1) Open the solution (offline if necessary).
2) Go to the change bindings dialog. Unbind everything.
3) Exit the dialog by pressing OK.
4) Go back to the change bindings dialog. Bind everything to the right server.
5) Exit the dialog by pressing OK.

This user had the same problem: http://support.sourcegear.com/viewtopic.php?t=9636
Ian Olsen
SourceGear

jimmurray
Posts: 24
Joined: Fri Jan 11, 2008 7:24 am

Post by jimmurray » Thu Mar 06, 2008 4:30 am

Thanks for your help, much appreciated. Do you have an approximate date for release of 4.1.1?

Jim

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Wed Mar 12, 2008 8:45 am

Vault 4.1.1 should be released later this month.
Linda Bauer
SourceGear
Technical Support Manager

Post Reply