Windows 7: Remote Assistance and linksys router

A new router should do it according to the technet advisor. Not many options left at this point.

I figured the router might be the problem right from the start but the firmware for your particular Linksys model is outdated and there doesn't look to be any recent updates for it.

So if you ran the Internet Connectivity Evaluation tool, and it Says NAT (Network Address Translation) is not supported it means that you might have a moderate to strict NAT (That's my guess), You can change this usually, by just forwarding the ports on your router. In this case you will need to forward ports 3389 TCP, and 3389 UDP..(Same ports but different protocols)

I have found your router and a step by step guide to help you forward the ports HERE..

Hope this Helps..and Happy Holidays.

EDIT: If this does not work, then I would go for chev65's idea...Also I noticed in the step by step guide They are using an older firmware version. Meaning that it may look different and things might be changed around...

Would it help if someone could post a brand and model # of router that actually allows RA to work? It would be great if detailed router configuration arcana is included so that those of us who aren't network professionals could follow along.

I have tried the MS connectivity tool on three routers, and all fail at something.

Linksys WRT54GS v6 (several years old): UPnP test "not run", although it is certainly enabled in the router's config.

D-Link DIR615 (new, "Compatible with Windows 7"): NAT test "not supported" and UPnP test "not run".

D-Link DIR628 (new, compat. w/Vista and 7): same as above. Also, port 3389 forwarded.

At a complete loss about this. Thought I read somewhere that the MS connectivity tool for Vista doesn't work reliably in 7, but cannot remember for sure. This should be much easier than it is.

Maybe RA is only for IT pros, not normal home users. Sorry for the pessimism, but I'm getting increasingly frustrated.

Well followed the step by step, fwd 3389 on BOTH tcp and udp. ran their port fwd checker tool and it says they are not open.


went into windows firewal advanced security and created two new rules one for tcp 3389 and one for udp 3389. port fwd checker still says it is not open.


i wil try a ra tomorrow if i can if not i will check chev's idea, wil hve to go back and see which post you were referring to.


i dunno tiger direct as a new netgeat N router for 25 bucks if all else fails...

thanks agin

I dont buy that, i used it all the time with xp..granted the other user had to be xp as well but it worked flawlessly... with Windows 7 i am supposed to be able to RA with any other version of windows.... i shall not rest till i get this damn thing to work LOL

Hi JustWatching,

Just out of curiosity do you use any other Third party Firewall or Anti-virus ?? If you have it's worth try in Selective Startup

Justwatching,

Have been struggling with RA on my desktop. Discovered that it is working on my laptop (also Windows 7 Pro). Rooting around within networking settings, and after making sure my network type was set as "Home", I found one setting which differed between my laptop and desktop.

Network and Sharing Center > Change advanced sharing options (on left pane) > Public > Public folder sharing --on the lappy Turn on sharing so anyone...... was checked. On my desktop Turn off Public folder sharing was checked instead. After changing that one setting on the desktop, magically Easy Connect began working--my desktop will now find the "peer-to-peer network" when trying the Easy Connect option. I was easily able to use my laptop to "request" RA help from my desktop via Easy Connect, and vice versa. Would not work before. I have not been able to try a RA session to another computer across the net and behind its own router yet, but I suspect it will work now provided the other computer and router have appropriate settings.

Hope this helps you.

I'm glad it's working for you kokopelli. That is the reason I posted all the info, because small things are usually what keeps this from working and I was covering all the basics start to finish for that very reason.

I wouldn't think that the public folder settings would affect RA when RA needs to have homegroup enabled in order to function correctly. That is very stange indeed and there is no reason it should be working like that. I'm glad you got it working none the less.

I have posted this page about a million times. Maybe that was a good idea after all.

Without understanding the nuances of networking, it seems to me to be a small detail, but it apparently was the one factor preventing my desktop from connecting to the Easy Connect network "out there". It was also preventing the Microsoft tool from properly surveying my router for the necessary supported features.

I'm glad you reported back in. The public file sharing settings page seems to be responsible for more than meets the eye. Apparently RA and Remote Desktop are controlled by the settings on that page.

I think we can officially mark this as solved.