Hi Carlo --
I checked in with the Windows Server product team on this question and
they've provided the following answer:
*******************
PNRP requires a constant CPU and network resources on a machine publishing
a peer name. These resources are very small. It is highly unlikely that
an end user's computing experience will ever be affected by PNRP.
PNRP is capable of operating in multiple scopes, called clouds. If the
computers in your work group are all sitting on the same subnet, you will
be able to use PNRP in the link local scope. This will not produce any
Internet bound traffic. If the machines sit on different subnets, your
software will have to use PNRP in the global scope. In this case, the
machines participating in the system will generate Internet bound traffic.
Either way, PNRP typically consumes a small amount of bandwidth - typically
much less than 1Kbps to keep a name published.
******************
Thanks --
James McIllece, Microsoft
Please do not send email directly to this alias. This is my online account
name for newsgroup participation only.
This posting is provided "AS IS" with no warranties, and confers no rights.
>Subject: PNRP overhead
>From: "MSNews" <>
>Newsgroups: microsoft.public.windows.server.networking
>Reply-To: "MSNews" <>
>
>Is there any overhead or excess traffic or any other cost in using PNRP on
>a
>group of 5 workstations in a domain?
>one of our developers needs it for an app to work.
>
>Carlo
|