L
Larry Heimendinger
I have been unable to get a Remote Assistance invitation through a
firewall/router to a destination machine. I opened ports 135 and legacy 3389
so that those ports are directed to the system, but alas, nothing. I also
put the computer into the DMZ on the router and still no luck.
I checked the software firewalls, and I remote assistance was enabled as an
exception. To back that up read the next paragraph.
However, if I use Remote Desktop to reach another computer on the same
network (behind the firewalls), and use the SAME invitation file, the remote
assistance connection works great.
I opened the invitation with notepad, and I found this looking rather correct:
RCTICKET="65538,1,192.168.10.34:64931;9X.23X.1XX.XX7:15525,*
I modified the actual IP address by replacing some characters with X.
However, the internal address looks fine. Is that port 15525 that it is
coming in on? Does remote assistance take some additional port handling I am
not accounting for?
firewall/router to a destination machine. I opened ports 135 and legacy 3389
so that those ports are directed to the system, but alas, nothing. I also
put the computer into the DMZ on the router and still no luck.
I checked the software firewalls, and I remote assistance was enabled as an
exception. To back that up read the next paragraph.
However, if I use Remote Desktop to reach another computer on the same
network (behind the firewalls), and use the SAME invitation file, the remote
assistance connection works great.
I opened the invitation with notepad, and I found this looking rather correct:
RCTICKET="65538,1,192.168.10.34:64931;9X.23X.1XX.XX7:15525,*
I modified the actual IP address by replacing some characters with X.
However, the internal address looks fine. Is that port 15525 that it is
coming in on? Does remote assistance take some additional port handling I am
not accounting for?