RDP-Yesterday Yes, Today No

[Guest]

"The specified remote computer could not be found" when I attempt RDP
connection to office PC. Office PC behind Netgear router, Windows Firewall
deactivated, Norton Internet Protection in use. My laptop has the same
Firewall scenario. When someone at the office sends me a Remote Assistance
request via Messenger I see absolutely nothing; when I send them the same
request, the Remote Assistance starting window comes up for them but nothing
further. Is this an IpAddress thing, seeing as the office PC is behind the
router? Strange it worked just fine yesterday. Thanks if anyone is wiser (not
difficult!).
SET

 

[Shenan Stanley]

"The specified remote computer could not be found" when I attempt
RDP connection to office PC. Office PC behind Netgear router,
Windows Firewall deactivated, Norton Internet Protection in use. My
laptop has the same Firewall scenario. When someone at the office
sends me a Remote Assistance request via Messenger I see absolutely
nothing; when I send them the same request, the Remote Assistance
starting window comes up for them but nothing further. Is this an
IpAddress thing, seeing as the office PC is behind the router?
Strange it worked just fine yesterday. Thanks if anyone is wiser
(not difficult!).
SET

Open the request file. What IP does it have?
The public one of the router?

Is port forwarding (and/or uPnP) enabled/configured properly on the
router(s)?

 

[Guest]

Shenan, how swift! The request Remote Assistance file comes to me over Live
Messenger. How do I "open" it to see the IP address? I normally just click
"Accept Invitation". As to the router - I'll have to ask her to go into the
Netgear configuration and meddle - almost certainly curtains for Windows!!
But if you can get me in via Remote Assistance with this IP Address thingy,
then I could do it myself on her screen. Many thanks so far.

 

[Guest]

Shenan, I made some progress this evening. She ran whatismyIp and it came
back with a real IpAddress like 209.169.131.66 as opposed to an internal
address. Also she ran netstat -a and it came back showing a line for port
3389 like : Protocol=TCP / Local Address=Viglen:3389 / Foreign
Address=Viglen:0 / State=Listening (Viglen being the computer name). So it
would appear port 3389 is enabled and listening properly for my remote
requests. Does this help? Many thanks again. Appreciated.

 

[Guest]

Hi Shenan,
Progress! I managed to get into the router configuration remotely. I
verified Remote Desktop on port 3389. I enabled UPnP. I allocated a fixed
internal-LAN ip address of 192.168.0.2 to the PC that I need to connect to
via Remote Desktop. Might one think i should now be able to RDP that PC
there? 'Cos I still can't get in! Thanks again.