http://blogs.msdn.com/p2p/archive/2007/07/03/ping.aspxWhen it comes to troubleshooting networking problems nothing is more trusted then ping. It is probably the first networking utility that everybody masters. When you want know if communication works between point A and B ping is your friend. Often timesen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/p2p/archive/2007/07/03/ping.aspx#3995206Sun, 22 Jul 2007 08:50:13 GMT91d46819-8472-40ad-a661-2c78acb4018c:3995206MarkusV<p>Thanks for your posts - keep them coming. I am having some issues with ping and PNRP (both on Vista and XP) which make me wonder if ping is still applicable with regards to PNRP. </p> <p>I have a successful P2P application working fine in the local network. However, I cannot ping the global seed server. </p> <p>Here some tests:</p> <p>1) &quot;ping6 pnrpv2.ipv6.microsoft.com&quot; does not work (bad IPv6 address pnrpv2.ipv6.microsoft.com.)</p> <p>2) &quot;ping6 www.kame.net&quot; (a known IPv6 site) works fine</p> <p>nslookup cannot find a IPv4 nor an IPv6 address for pnrpv2.ipv6.microsoft.com. But it can do that for e.g. 6to4.ipv6.microsoft.com and the above www.kame.net. </p> <p>I have ping problems with pnrpv2.ipv6.microsoft.com at the office on both Vista and XP, and at home. However, since I live in Japan, I tried the nslookup in addition from a clean machine in the Seattle area (within a customer's network via remote desktop) and I get the same nslookup results. </p> <p>Am I just having technical issues on my various machines or is ping not the right tool to trouble-shoot seed server issues?</p> http://blogs.msdn.com/p2p/archive/2007/07/03/ping.aspx#6183028Tue, 13 Nov 2007 23:45:45 GMT91d46819-8472-40ad-a661-2c78acb4018c:6183028The things that are better left unspoken<p>A little while ago I showed how to manage the basic firewall in Windows Server 2008. Recently I found</p>