Remote Assistance - Cannot establish connection over Teredo
Hi! In my setting, I am trying to offer remote assistance to various client computers. Since I cannot guarantee, that every client's router is configured to allow UPnP, I've run my test runs with UPnP disabled. Both computers run Windows 7. The novice had Easy Connect available from the start. On the experts computer, which is located in a corporate network, I used the command "netsh interface teredo set state enterpriseclient" to enable Teredo, thereby gaining access to the Global_ PNRP cloud and enabling Easy Connect. Unfortunately, I could not establish a connection between expert and novice, trying both Easy Connect and the invitation file. The connection attempt simply aborts after a while. I tried the following to pin down the problem: I checked the Teredo state on both machienes using "netsh interface teredo show state". Both states are "qualified". I checked the state of the PNRP Cloud using "netsh p2p pnrp show statistics Global_". Both machines have a IPv6 address assigned. The number of cached entries seems a little low (like 10) to me, the estimated cloud size is zero most of the time, but grows while testing. I registered a name on both machines using "netsh p2p pnrp peer add register 0.name Global_" and tried "netsh p2p pnrp peer trace 0.name Global_". Both machines could resolve the other's names and found routes of maybe five hops. I could resolve the PNRP name automatically generated by Easy Connect on my novice computer from my expert computer. I tried the Internet Connectivity Evaluation Tool. It reports a symmetric NAT for my expert computer, but the teredo state reports "restricted" most of the time. The troubleshooting tool offers no help on my experts computer. I think it complains about having no public ipv4 address on the novices computer, but since this is located remotely, I am not sure at the moment. I can use Easy Connect to establish a Remote Assistance connection to the novice computer from my home computer, so the problem should be at the experts side. Now I am a little stumped. I expected Remote Assistance to work, once I had ipv6 pings going both ways, but it didn't. I am pretty sure that our router has no functionality to filter Teredo packets. My question is: What else could go wrong here, and how do I find out? Are there any diagnostic tools I could try to get to the bottom of this? Is there a comprehensive specification for the network setting remote assistance (and easy connect) need to work? I've found most specifications to be very cunsomer oriented and light on technical detail. =) Thanks in advance! Jens Ameskamp
May 19th, 2010 3:13pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics