Problem with 3.1.6, seems to redirect to http://machinename/

lassevk · Post by **lassevk** » Tue Jan 03, 2006 5:32 am

After upgrading to 3.1.6 I can no longer reach the vault database over the internet.

When trying to reach the vault web client I get as far as the initial page, and the next link leads to http://machinename/... which is of course a local machine name on the network the machine is on, not available over the internet. The Admin and Client applications never get as far as any logging on, they hang with the small tooltip window saying it is connecting.

This always worked in 3.1.5, but now I can only reach 3.1.6 locally, unless I manually add the name of the machine to the hosts file along with the correct ip address.

Is there a way to make Vault redirect to a specific hostname in this case?

lbauer · Post by **lbauer** » Tue Jan 03, 2006 1:21 pm

Does using just the IP address work? Did something change in your network setup or DNS around the time you upgraded? I don't know of anything that might have changed in Vault to cause this.

lassevk · Post by **lassevk** » Wed Jan 04, 2006 3:41 am

I logged in to Vault and checked in some files to make sure, then upgraded to 3.1.6. After that I could no longer log on to Vault.

After doing a double reboot, I could log back in and that worked all yesterday.

Today, it's back to being unavailable so I probably have to reboot the server once more.

lassevk · Post by **lassevk** » Wed Jan 04, 2006 6:01 am

Ok, I've found the problem and it has nothing to do with Vault.

Apparently I had managed to turn on the wireless network on the machine and it had both a cable connection and a wireless connection and this apparently doesn't work very well. When I turned it off, both 3.1.5 and 3.1.6 worked nicely.

My fault all along

Additionally, now that SQL Server 2005 is out, you should put on your todo list to update the help resolution text about a missing sgvaultuser error, at this url:

http://kb.sourcegear.com/VaultHelp/mess ... ailDBConn)

Since this requires different steps now with 2005.

In any case, it seems to work like it should now.

lbauer · Post by **lbauer** » Wed Jan 04, 2006 10:00 am

Glad you got it sorted out. Thanks for the tip about updating the queries for SQL Server 2005