Talk:Peer Name Resolution Protocol

This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects:

Computing Low‑importance This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing Low This article has been rated as Low-importance on the project's importance scale. Microsoft (inactive) This article is within the scope of WikiProject Microsoft, a project which is currently considered to be inactive.MicrosoftWikipedia:WikiProject MicrosoftTemplate:WikiProject MicrosoftMicrosoft Microsoft Windows (inactive) This article is within the scope of WikiProject Microsoft Windows, a project which is currently considered to be inactive.Microsoft WindowsWikipedia:WikiProject Microsoft WindowsTemplate:WikiProject Microsoft WindowsMicrosoft Windows

So could this be implemented by other people or is M$ the only ones allowed to use the protocol? The bellman 09:14, 8 November 2006 (UTC)Reply

They've patented it so only MS can use it in the US, but no one else needs it. BTW: My first thought after reading the articule was: "Oh so they've finally got the netbios name service to work properly, only took them 20 years". 86.16.135.53 09:21, 12 November 2006 (UTC)Reply

Why does no one else need to use it? No one else outside the US or no one outside of MS? Is there a comparable solution for Linux and the Mac? Mk2337 05:34, 1 December 2006 (UTC)Reply

is zeroconf/Avahi comparable to this?--72.40.148.147 17:13, 23 January 2007 (UTC)Reply

The article doesn't mention the most important: what is this used for? Does this provide name resolution or DNS in a LAN ? If I have 3 computers on my network and want to share files between them, can I use this instead of hosts.txt(static IP's) or port 137(dynamic IP's) ? (supposing the computers have an IPv6 stack)

What on earth is the purpose of this protocol? A IP6 LAN decentralized name resolver (replacing WINS)? Or a Layer 5/6 OSI Model protocol/API for easily creating DHT swarms of any data/purpose?Patcat88 (talk) 14:00, 9 March 2008 (UTC)Reply

Its not a generic DHT API, though it rather uses a DHT-like structure for storing the name/address/hash mappings. Rather think of it as a service registry without any centralized server (technically it can be used as a registry for any resource, not just service endpoints). You can use it for WINS like name resolution - have file servers register their names and addresses in PNRP and clients query the address via PNRP. Or you can use it like Bonjour-like zeroconf service discovery - have services register their addresses and some metadata via PNRP and have clients issue PNRP queries. Or you can even use it for applications like IM or games - have these applications register the address and who is available on the address via PNRP and others can have than information via PNRP resolutions. PNRP gives you a very important tool to enable all these scenarios. But it isn't an end to end solution. All these scenarios will need a significant amount of custom coding. --soum ^talk 14:14, 9 March 2008 (UTC)Reply

One more thing, it is not just limited to the LAN, you can configure it to scale out over the internet. But considering a n log n lookup time, you better not try peering with someone on the other side of the continent. --soum ^talk 14:18, 9 March 2008 (UTC)Reply

Please have a look at Justin Smith's interesting article on MSDN. I added the link and hope it will help to understand what's PNPR is. Windows 7 "homegroup" feature seems to heavily rely on PNPR and so it might be desirable to develop some basic understanding. HTH:-) Sigrid 82.139.211.39 (talk) 13:16, 6 February 2009 (UTC)Reply