easy connect
I am unacle to connect with easy connect. I get an error unable to connect to global peer to peer network. I have a wrtn160n linsys router ver1. Everthing seems to be fine. I went to my customers site his works he has everything I have except his router is a version2. Is there any setting in my router I need to change or something in my OS Win7 64 bit pro.
July 15th, 2010 8:43pm

You need to check that your version supports win7 you should also update the firmware.
Free Windows Admin Tool Kit Click here and download it now
July 15th, 2010 9:54pm

My system is windows 7 64 bit with all updates. My firmware is updated on my router. Any other suggestions would be appreaciated since I the one supposed to connect remotely. I never had a problem with XP.
July 16th, 2010 1:24am

my router supports win 7
Free Windows Admin Tool Kit Click here and download it now
July 16th, 2010 2:41am

http://homesupport.cisco.com/en-us/home?referrer=www.linksysbycisco.com peter If you find a posting or message from me offensive,inappropriate or disruptive,please ignore it. If you dont know how to ignore a posting complain to me and I will be only too happy to demonstrate :-) "Cmedina" wrote in message news:b83a2888-b2b2-4e20-9e47-5f721fbf9906... my router supports win 7
July 16th, 2010 5:01am

Hi, The common reasons for problems you might run into when trying to use Easy Connect are listed below: l Both computers aren't running Windows 7. l Access to the Internet is limited. l Your router doesn't support Easy Connect. For more information, please refer to the following Microsoft article: Why can’t I use Easy Connect with Windows Remote Assistance? The “Unable to connect to global peer to peer network” error message mostly can be caused due to the router cannot support the Peer Name Resolution Protocol (PNRP). I would like to suggest you contact the Linksys Router Support to confirm if this router supports PNRP and how to enable it. In order to remove the possible third party software conflicting issue, you may also try to disable the antivirus programs and firewalls, then test the issue in Clean Boot. If the issue persists, you may consider to use the Invitation File to establish Windows Remote Assistance or change another router which can support PNRP. For more information, please read Windows Remote Assistance: frequently asked questions. Regards, Arthur Li TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
July 16th, 2010 6:29am

Hi, I would like to confirm what is the current situation? If there is anything that I can do for you, please do not hesitate to let me know, and I will be happy to help. Regards, Arthur Li TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com. Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. answer your question. This can be beneficial to other community members reading the thread.
July 19th, 2010 6:01am

As it turns out my router does not support pnrp. I have a linksys wrt160n ver1. A linksys wrt160n Ver 2 is suppored but you can not upgrade the firmware from a ver1 to a ver2. Note ver3 will also work.
Free Windows Admin Tool Kit Click here and download it now
July 20th, 2010 5:01am

Two things to note: 1) A third party firmware might help you. I run DD-WRT which does support PNRP. If you are comfortable with flashing your router, you might try that route. 2) Make sure the Peer Naming Resolution Protocol is working on your machine. Go to task manager and see if the service is running. If not, go to your Services in the control panel and try to start the service. If the start fails for some reason, you will get an error code which you can then use to help you troubleshoot further. In my case, a file got corrupted and needed to be deleted and recreated. Someone had the solution for me here: http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/6b5a72eb-6523-4af9-85ab-3694d7cc457a In case that link doesn't work: From an elevated CMD prompt. Net stop p2pimsvc /y Then delete the following file. "C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking\idstore.sst" reboot and you should be able to rejoin the homegroup. Credit goes to Brian - MSFT3
August 11th, 2010 3:33pm

As it turns out it was not my router. It has to do with vmware vitural network adapters. Disabling them fixes the problem. Hope this helps someone else
Free Windows Admin Tool Kit Click here and download it now
September 8th, 2010 4:23am

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

Other recent topics Other recent topics