Re: P2P Groups and LinkLocal Cloud

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Geogy Samuel [MSFT] (geogys_at_online.microsoft.com)
Date: 05/11/04 

Date: Tue, 11 May 2004 10:43:18 -0700

Chris,

I would need some more information from your system:
    * Is "SSDP Discovery Service" running on your system?
    * And can you send us the output of "c:\>netsh p2p pnrp cloud show
names", please?

Thanks
Geogy

"Chris Dix" <anonymous@discussions.microsoft.com> wrote in message
news:499B93F5-BDDB-4D96-BC61-26EC48A744E8@microsoft.com...
> Hi Geogy,
>
> I did check both firewalls, and they are both disabled.
>
> Also, I did leave the windows open in the netsh test, and that did not
> seem to help. My issues with the link local clouds for groups still
> remain.
>
> My success with graphs at link local has been through my own modified
> application (one of the samples with the library I have written). It
> seems that I have no problem with graphs at either the global or link
> local scope, and groups at the global scope also work. It remains that
> only link local groups are the problem. I will continue some tests and
> try to get you any results that I have. If you have any other ideas, let
> me know.
>
> Thanks for your help.
>
> Chris Dix
> http://www.thoughtpost.com/p2p.aspx
>
>
> ----- Geogy Samuel [MSFT] wrote: -----
>
> You did mention the firewall disabled. Is this the Internet Connection
> Firewall? Can you also check if the IPv6 firewall is disabled.
>
> Also in the register and resolve test, after you added 0.test1, was
> that
> netsh session still active or did that session just end right away. A
> PeerName registaration (by calling add) is only valid for as long as
> the
> netsh session is active. So you will have to resolve in the second
> window
> while the 1st session is still active. This can only be done by first
> getting into the netsh environment (c:\netsh) and then add a peer name
> ("p2p
> pnrp peer add 0.test1 <link local cloud name>").
>
> GraphChat and GroupChat by default register and resolve PeerNames in
> the
> Global Cloud. Have you made changes to these applications to run under
> the
> Link Local cloud?
>
> Thanks for your patience,
> Geogy
>
> "Chris Dix" <anonymous@discussions.microsoft.com> wrote in message
> news:8017D9D0-4D0D-4C44-8BDA-3B94B30EC527@microsoft.com...
> >> Thanks for the specific questions, Geogy. Here's what I have
> found:
> >> ----- Geogy Samuel [MSFT] wrote: -----
> >> Few things for you to try and respond to:
> >> * What is the error code returned back when you get a
> connection
> > failed
> > event?
> > - All I get is the PEER_GROUP_EVENT_CONNECTION_FAILED event from the
> > group. I am not sure where to check a specific error code, the docs
> say
> > no data is returned with this event. Can I do a GetLastError()?
> The
> > original call to PeerGroupConnect succeeded, it just fires this
> event
> > later on.
> > * Is the validity time of the invitation issued for the invited
> node
> > correct?
> > - The time seems to be correct.
> > * Is firewall enabled on your system by any chance?
> > - I have the firewall disabled during my testing.
> > * How many NICs do you have on your system?
> > - Just one NIC.
> > * Use netsh commands to test register and resolve on link local
> > clouds. Open
> > up 2 command prompt windows and type "netsh" in each of them. In
> the
> > first
> > window type in...
> > "netsh p2p pnrp peer add 0.test1 <link local cloud name>"
> > And the second window, type in "netsh p2p pnrp peer resolve
> > 0.test1
> ><link local cloud name>"
> > Please let us know if the resolve in the second window
> > succeessfully
> > found the first node.
> > - OK, here's where it gets interesting. The second window did not
> find
> > the first node. In fact, the first window also failed to find the
> first
> > node. In both cases, the command returned: "Resolve started...
> Timeout.",
> > even though the add command said "OK".
> >> What I find even more interesting is that the nodes created by the
> > GraphChat application, as well as my .NET wrapper for the Graphing
> API,
> > are valid and can be found using the resolve syntax you suggested,
> from
> > either window! For those, I get back results like this:
> >> Found: Comment: Thoughtpost
> > Addresses: [fe80:0000:0000:0000:0250:f2ff:fe78:13e6]:1029
> tcp
> >> I guess the question is, what is the difference between that add
> command
> > (and the GroupChat app) and the way that the GraphChat app registers
> a new
> > node?
> >> Thanks,
> > Chris Dix
> > http://www.thoughtpost.com/p2p.aspx
> >

Relevant Pages

  • Re: SOHO firewall dropping incoming 443 connections - incorrect state
    ... The only incoming connection that I allow is an HTTPS port ... Occasionally the firewall seem to just start denying HTTPS ... > There appears several ways to resolve this: ... External user disconnects from dialup reconnects, ...
    (comp.security.firewalls)
  • Resolved
    ... > From the exchange server, I'm able to telnet to hotmail or other mail ... my firewall is working ok. ... >> with the external server in the time specified. ... >> and this still does not resolve the issue. ...
    (microsoft.public.exchange2000.protocols)
  • Re: Page cannot be Displayed in IE. Firefox works fine.
    ... Chances are that another program (possibly malware) is causing this. ... turn on the Windows Firewall before ... The Parasite Fight http://www.aumha.org/a/quickfix.htm Note that for ... To resolve this problem in Internet Explorer, ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: Page cannot be Displayed in IE. Firefox works fine.
    ... > Chances are that another program (possibly malware) is causing this. ... > turn on the Windows Firewall before ... > The Parasite Fight http://www.aumha.org/a/quickfix.htm Note that for ... > To resolve this problem in Internet Explorer, ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: P2P Groups and LinkLocal Cloud
    ... You did mention the firewall disabled. ... So you will have to resolve in the second window ... GraphChat and GroupChat by default register and resolve PeerNames in the ...
    (microsoft.public.win32.programmer.networks)