PPE Environment Network Maintenance – 12 Nov 2008

On Nov 12 2008 around 5PM PST the HealthVault PPE (Pre-Production Environment) will be conducting required network maintenance that will change the IP addresses of the DNS records to the values below:  http://account.healthvault-ppe.com  https://platform.healthvault-ppe.com

Partners may need to update their firewall or access rules to accommodate the new IP addresses associated with the above DNS entries. Please use the comments below to let us know any of your concerns or questions about the same.

Comments (3)
  1. Dmitry says:

    We are getting an error after authenticating with healtvault:

    A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

    Also pinging the IP address fails and here is the result of pathping:

    Tracing route to platform.healthvault-ppe.com []

    over a maximum of 30 hops:

     0  NS1wks024.ns.corp []


     2  x403b0941.ip.e-nt.net []

     3  xd8ad1781.ip.e-nt.net []

     4  x403b04c7.ip.e-nt.net []

     5  so-2-0-0.ar1.nyc1.gblx.net []

     6  te1-1-10g.ar3.dca3.gblx.net []



     9  ge-7-1-0-0.blu-64c-1b.ntwk.msn.net []

    10  ge-7-1-0-0.wst-64cb-1b.ntwk.msn.net []

    11  ge-7-0-0-0.wst-64cb-1a.ntwk.msn.net []

    12  ge-1-0-0-0.cpk-64c-1a.ntwk.msn.net []

    13  ten3-4.cpk-76c-1b.ntwk.msn.net []

    14     *        *        *

    Computing statistics for 325 seconds…

  2. hi Dimitry

    We filter ICMP(ping) so no response should be expected. Can we have more details about your problem. I see that you authenticate but it fails after? Is it possible that you have fire wall rules for port 80 or 443?

    Can we get your appid, so we can check our logs for any issues.



Comments are closed.

Skip to main content