Connect via multiple network paths.

[dractivex]

Hi,

We have just switched to Vault 4.1.3.18336. We have two offices, with head office being in Burton and a smaller development facility out of UK. We have setup the Vault server at our UK office, everything works great locally. I then gave access to our developers at the offshore office via an external IP address and there were no problems getting the project using Vault Client.

However, the nightmare begins when the offshore office tries to open the project in Visual Studio 2008. VS cannot connect to the Vault Server because the bindings in the solution file are using the netbios name of our Vault Server, which is meaning less to the offshore office. I rebound the solution at offshore office and it worked, however, now the external IP address is saved in the solution file making us unable to connect to Vault server via LAN.

Is there any solution to this issue?

Thanks and regards,

Dave

[Beth]

What sometimes works best for users is to have the internal users connect using the external address. This might be the easiest solution.

Is the external address right on the server, or does it go to a router that forwards to the server?

[ian_sg]

I'd suggest having the external users add an alias to their hosts file to resolve the internal name to the address that works for them. (Or vice versa, depending on which would affect fewer developers.)