PNRP Debugging Guide Part 1

re: PNRP Debugging Guide Part 1

adityayadav76 — Thu, 20 Mar 2008 12:53:00 GMT

Hi,

I try to start P2P channel inside a C# inproc COM component loaded in IE as an add in.

It says default resolver not available.

Can you add how to resolve that, information on the p2p debugging section on your blog?

re: PNRP Debugging Guide Part 1

DJDrEvil — Fri, 21 Mar 2008 15:30:50 GMT

adityayadav76: Did you verify you have PNRP enabled like the article says? If so make sure you set the resolver to PNRP. And make sure your security settings match.

For instance in the example chat app (converted from the horrible app.config to an imperative configuration):

<snip>

InstanceContext instanceContext = new InstanceContext(new ChatApp(member));

NetPeerTcpBinding chatBinding = new NetPeerTcpBinding();

chatBinding.Security.Mode = SecurityMode.None;

chatBinding.Resolver.Mode = PeerResolverMode.Pnrp;

DuplexChannelFactory<IChatChannel> factory =

new DuplexChannelFactory<IChatChannel>

(instanceContext,

chatBinding,

"net.p2p://chatMesh/ServiceModelSamples/Chat");

IChatChannel participant = factory.CreateChannel();

<snip>

re: PNRP Debugging Guide Part 1 - not quite working yet ...

JohnSpence — Wed, 23 Apr 2008 17:55:30 GMT

Hello, and thanks for the excellent blog. Great information. I am experimenting with IPv6, p2p, and PNRP myself, and am having some difficulty, which I heop you can help me with, if I may ask.

I cannot resolve a WICN name – which I think should use peer-to-peer – across the Internet between 2 Vista machines.

Machine 1 is the resolver. It has an insecure name:

C:\Windows\system32>netsh p2p pnrp peer show machine

Machine Name: 0.johnspencecommand

Use this format DNS name in other applications to refer to this machine: johnspencecommand.pnrp.net

The machine name is being published.

The machine name is configured to be published automatically.

It appears healthy, IPv6-wise and peer-to-peer-wise:

C:\Windows\system32>ping -6 pnrpv2.ipv6.microsoft.com

Pinging pnrpv2.ipv6.microsoft.com [2002:4136:e383::4136:e383] from 2001:0:4137:9e50:10e0:a53c:bc49:7236 with 32 bytes of data:

Reply from 2002:4136:e383::4136:e383: time=99ms

Reply from 2002:4136:e383::4136:e383: time=39ms

Reply from 2002:4136:e383::4136:e383: time=37ms

Reply from 2002:4136:e383::4136:e383: time=38ms

Ping statistics for 2002:4136:e383::4136:e383:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 37ms, Maximum = 99ms, Average = 53ms

C:\Windows\system32>netsh p2p pnrp cloud show list

Scope Id Addr State Name

----- ----- ----- ---------------- -----

3 7 0 Alone LinkLocal_ff00::%7/8

1 0 1 Active Global_

3 8 1 Alone LinkLocal_ff00::%8/8

C:\Windows\system32>netsh p2p pnrp diag ping seed Global_

SOLICIT sent to address: [2002:4136:e383:0000:0000:0000:4136:e383]:3540.

ADVERTISE returned 5 ID(s) in 31 milliseconds.

43426ed07784caf6419afa2f3151070e.7700660055004400db83fb20d5b7f063

ebe5fb41d500284b100b52cd9618b245.770066005500440084df496e190f8050

9e486c7978a1145b20a2ee92070be60c.27b05c1726601f9741ccc39c9040d919

dd1f6e0abfc116e5bb0cf701af6d3211.77006600550044000a698795bd09b505

1f183b562327e9b71f3a7a0d6b522417.4a082a03175c52061d8d901fee15d14a

Machine 2 is the target. It has a secure name.

C:\Windows\system32>netsh p2p pnrp peer show machine

Machine Name: 54ffc35aa154438b885004fb541e88f64576c8ef.

Use this format DNS name in other applications to refer to this machine: p.p54ffc35aa154438b8850

541e88f64576c8ef.pnrp.net

The machine name is being published.

The machine name is configured to be published automatically.

It appears healthy, IPv6-wise and peer-to-peer-wise:

C:\Windows\system32>ping -6 pnrpv2.ipv6.microsoft.com

Pinging pnrpv2.ipv6.microsoft.com [2002:4136:e383::4136:e383] from 2002:ccf5:c614::ccf5:c614 with 32 bytes of data:

Reply from 2002:4136:e383::4136:e383: time=24ms

Reply from 2002:4136:e383::4136:e383: time=23ms

Reply from 2002:4136:e383::4136:e383: time=22ms

Ping statistics for 2002:4136:e383::4136:e383:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 22ms, Maximum = 24ms, Average = 23ms

C:\Windows\system32>netsh p2p pnrp cloud show list

Scope Id Addr State Name

----- ----- ----- ---------------- -----

1 0 1 Active Global_

3 9 1 Alone LinkLocal_ff00::%9/8

C:\Windows\system32>netsh p2p pnrp diag ping seed Global_

SOLICIT sent to address: [2002:4136:e383:0000:0000:0000:4136:e383]:3540.

ADVERTISE returned 5 ID(s) in 16 milliseconds.

b6d0794c499046c5cadfc01536db002d.77006600550044005b393e190cfdde63

28ff4dad424be37881574c5b7cafed48.3868793538aeb1a0fb4e7965a50220ad

935ed522a39e19bc1b986791b3193827.7700660055004400d18a27218748a023

43b45bbf33a3556fa6a667d8d11fa220.ee05d8cf78b9301148377b37d87bd7b3

08cfe1ec25d6f7d9906fa11831c176ba.7700660055004400b13ac1b417ca9d59

But, from Machine1, I cannot resolve the address from the name:

C:\Windows\system32>ping p.p54ffc35aa154438b541e88f64576c8ef.pnrp.net

Ping request could not find host p.p54ffc35aa154438b541e88f64576c8ef.pnrp.net. Please check the name and try again.

C:\Windows\system32>ping -4 p.p54ffc35aa154438b541e88f64576c8ef.pnrp.net

Ping request could not find host p.p54ffc35aa154438b541e88f64576c8ef.pnrp.net. Please check the name and try again.

C:\Windows\system32>ping -6 p.p54ffc35aa154438b541e88f64576c8ef.pnrp.net

Ping request could not find host p.p54ffc35aa154438b541e88f64576c8ef.pnrp.net. Please check the name and try again.

And I may not know how to use the “diag ping host” command.

C:\Windows\system32>Netsh p2p pnrp diag ping host p.p54ffc35aa154438b541e88f64576c8ef.pnrp.net Global_

Error: Host name not found in cache.

C:\Windows\system32>Netsh p2p pnrp diag ping host 204.245.198.20 Global_

Error: Host name not found in cache.

But I can use “diag ping host” and reach the IPv6 address, so that connectivity works.

C:\Windows\system32>Netsh p2p pnrp diag ping host 2002:ccf5:c614::ccf5:c614 Global_

SOLICIT sent to address: [2002:ccf5:c614:0000:0000:0000:ccf5:c614]:3540.

ADVERTISE returned 5 ID(s) in 452 milliseconds.

2cceee486e2d1b846f7c3a6411f727dc.77006600550044008e2e4080b15f7392

3605f2f5ec64b905f8fda7a03a8961f6.c3c62c0bce2f436480cd530348235ed2

4234f486e9d838c110dcb9abb006c84c.34cc78e3b55c052a25f332c0bffebaf2

63735cc68b9b5164ee13d3a7535d600e.76b3007632cf3e8aad072a01a3d1c6a1

7ce78401dbf30c927a445fb59cd2d250.7700660055004400583e793cc1bcb258

Why can I not ping the target by name and resolve the name using PNRP? Thanks for any insight.

re: PNRP Debugging Guide Part 1

JohnSpence — Fri, 25 Apr 2008 18:46:45 GMT

I'm back. Another question - more of a confirmation this time.

I have MachineC. It is at a global IPv4 address, and has a 2002::/16 IPv6 address - 6to4.

I have given it a WICN, secured.

When I resolve the name on MachineD (RFC1918 address, and using Teredo), I believe the PNRP resolution is done over IPv6, because of the "traceroute" output. Is this process only and always done over IPv6 - never IPv4?

When the traceroute finishes, I see the resolution has been to the IPv4 address. Then if I ping the node by WICN I do an IPv4 ping. Is this just the stack being smart and saying "IPv4 to a global address is better than IPv6 via Teredo?"

When I open a remote desktop connection from MachineC to MachineD using MachineD's WICN it also appears to run over IPv4. Also correct?

Next, immediately after getting the traceroute working and seeing the resolve, I run the command "netsh p2p pnrp diag host <MachineD-WICN> Global_" and I get an error, specifically "Error: Host name not found in cache.". Why is the name not in my cache - I'm using it for ping and Remote Desktop.

Thanks for any insight.

re: PNRP Debugging Guide Part 1

JohnSpence — Fri, 25 Apr 2008 18:55:39 GMT

Sorry for the confusion. I see I transposed MachineC and MachineD in the last two paragraphs above. In my question and example, the "client" machine is always MachineD (Teredo), and the target is always MachineC (routable IPv4). Jeez.

re: PNRP Debugging Guide Part 1

JohnSpence — Thu, 01 May 2008 20:53:08 GMT

Hello again. I'm not sure how I fixed my problems, but I did, and so no need for anyone to reply to the posts above. If the activity on this thread picks up I will post some debug information that helped me. Thanks.