Help: Using white list on router block Vault client access

[vipulsheth]

I am trying to resolve an issue that has surfaced recently and I was hoping you might be able to help. Here are the key points:

- We have recently installed a new load balancing router for our internet connection.

- This router allows us to configure white and black lists similar to ISA server.

- I want to be able to add my vault server to the white list among other sites that we normally access.

- As soon as I add this server to the white list, the vault client stops working. Note: I can still get to the vault server using Internet Explorer and load the web page.

- This led me to believe that the client needed other sites to be added to the white list. I used a packet sniffer which showed the client trying to access other sites like www.sourcegear.com, www.xmlschema.org and www.w3.org.

- I added these to the white list as well but that did not resolve the problem.

- I remove the white list and the problem goes away (vault client starts working).

- The router support folks point to sourcegear vault support. The vault support forums have not provided any additional information.



Any help you can provide will be great.

Thanks,

Vipul

[Beth]

Can you describe what you see when Vault "stops working"? Can you provide me a screen shot or the exact error message?

Could you turn on Client side logging? More information on that here: http://support.sourcegear.com/viewtopic.php?p=5375

Also, please place the Vault server log into debug mode. You may do this in the Vault Admin Tool, on the Server Options tab. After you change the log level, you will need to restart the IIS service by choosing Start->Run... and typing iisreset and hitting OK. Once IIS has been restarted, you will see more verbose log messages.

Once that is complete, then recreate the scenario so that the logs capture the information. You can send those logs to support at sourcegear.com (attn: Beth) and just reference this thread.

[vipulsheth]

I have attached a screen shot with the error message and another attachment with the client log file. It might be difficult to get the server logging enabled since this is a production server and I would have to go through several approvals. Will this be enough to identify the problem?

[Beth]

Note: I can still get to the vault server using Internet Explorer and load the web page.

Are you trying both of the following?

• http://<vault server>/vaultservice
  http://<vault server>/vaultservice/vaultservice.asmx

Do either of those fail?

Is there only one Vault / IIS Server through the load balancing? If
there are multiple servers, then it is unlikely this will work since
subsequent requests to a given action must hit the same server. If the
load balancing sends the request to a different server, the client will
encounter an error.

(Sorry, ignore the first post of mine.)

[Beth]

On the other websites you are seeing, your clients can turn off the version check on start up under Tools-Options-General and towards the bottom is an option Check for Latest Vault Version on Start-up. We ran a sniffer against our set up here and haven't seen calls to the other two sites (www.xmlschema.org and www.w3.org). If you have a log that identifies Vault as the culprit, could you send that through to support at sourcegear.com (attn: Beth) and reference this post?