Welcome to MSDN Blogs Sign in | Join | Help

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:

207.46.185.230  http://account.healthvault-ppe.com

207.46.185.232  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.

Published Saturday, November 08, 2008 3:17 PM by vaibhavb

Comments

# PPE Environment Network Maintenance - 12 Nov 2008 | Tmao Coders

Friday, November 14, 2008 6:14 PM by Dmitry

# re: PPE Environment Network Maintenance - 12 Nov 2008

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 207.46.185.232:443

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

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

over a maximum of 30 hops:

 0  NS1wks024.ns.corp [172.16.40.182]

 1  172.16.40.1

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

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

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

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

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

 7  64.208.27.26

 8  207.46.45.85

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

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

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

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

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

14     *        *        *

Computing statistics for 325 seconds...

Friday, November 14, 2008 6:46 PM by vaibhavb

# re: PPE Environment Network Maintenance - 12 Nov 2008

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.

regards,

Vaibhav

New Comments to this post are disabled
 
Page view tracker