Error while connecting to vault remotely

Arun · Post by **Arun** » Tue Sep 04, 2007 5:10 am

When we tried to connect the vault client from remotely most of the it is not connecting, It dispalys unable to connect to server,the server committed a protocol violation, Attached the print screen for your reference.
But when we tried connecting to the webclient , its allowed to log in and then when we logged in to Vaultclient its connecting , Could you please let me know what could be the problem.
Attached the print screen of the error

Beth · Post by **Beth** » Tue Sep 04, 2007 7:39 am

Usually the protocol error indicates that the client you have installed is a different major version than the server you are trying to connect to.

Can you tell me the version of your client and then the server version?

The web client will be able to connect because that's not dependent on the client even being installed.

Arun · Post by **Arun** » Wed Sep 05, 2007 12:58 am

Hi Beth

The Vault version is 3.51(4786) and client tool version is 3.51(4786),

Attached the print screen of the version details.

Beth · Post by **Beth** » Wed Sep 05, 2007 10:04 am

I think I may see what's going on how. What are you entering for the server to connect to on your login box?

You should only need to put the name of the server. For example, if you use http://xxxxxxxxx.com/vault service to connect to the web client, then you would only enter xxxxxxxxxx.com into the Vault GUI client.

Are you on the same network, or are you remote from the network?

Arun · Post by **Arun** » Wed Sep 05, 2007 10:44 am

Iam connecting as you have specified Eg http://******.com

Beth · Post by **Beth** » Wed Sep 05, 2007 1:23 pm

Remove the http:// portion from your connection. The Vault client is not a straight http application. That will only work in the browser.

I'm attaching a screen shot of an example.

Arun · Post by **Arun** » Wed Sep 05, 2007 1:28 pm

Hi Beth

Iam using server name without http://, I mistakenly typed it.Attached the screen shot

Beth · Post by **Beth** » Wed Sep 05, 2007 1:33 pm

Ok, and you are still getting the same error?

Are you on an active directly domain? If so, then try t001.ad.xxxxxxxx.com.

Is it same to assume that t001 is the name of your server?