Remote assistance connection-problems
Posted on 2006-03-20
Case: I wish to offer remote assistance to the users in the company, when they are connected on our LAN or remote by VPN.
With a group policy I've allowed both Remote Desktop access (for test purposes) and Remote Assistance access to the workstation (XP), and with a group policy I made sure that the windows firewall are not preventing access between the LAN and VPN-users, as well as there are no firewall between the LAN and VPN. When testing, I connect from our domain-controller (2003) with remote desktop and remote assistance to the workstation which I wish to control remotely.
Here comes my headache:
When the workstation are connected to the LAN, I can connect via remote desktop and I can offer remote assistance - No problems. The terminal service is listening on port 3389.
When the workstation are connected from VPN, I can connect via remote desktop - but I can not offer remote assistance to the computer. The remote assistance client complains: "The remote server machine does not exist or is unavailable" - even though the service is listening on port 3389, and that I can remote desktop to the workstation, as well as I can ping to the workstation of course.
I've tried to monitor the ISA-server on which the VPN are running, and all traffic between the workstation and the domain controller is being categorized into the access rules, and all traffic are given status "Allowed"
Have you got any ideas on what is wrong here?
Thanks in advance.