Does any one know of a way to tweak Remote Assistance Invitations? Here's the
scoop, have a remote worker with a company notebook. This notebook has
multiple network interfaces. As an example the remote invitation looks like
this after cracking it open in notepad
RCTICKET="65538,1,72.225.x.x:5068;192.168.x.x:3389;10.3.x.x:3389;192.168.x.x:3389;192.168.x.x:3389;notebookx.corp.net:3389,
Public IP VMWare IP VPN IP VMWare IP
VMWare IP FQDN
The remote worker connects to the companies VPN, then sends out the remote
invite. Some workstations will connect with the remote invite just fine across
the VPN. Other workstations will first try to connect to the Public IP, after
timing out it tries to connect to the VMWare IP. After timing out a second
time the remote invite session fails.
Directly editing the remote invite cause corruption. As a work around I have
manually added a static route on the workstation to point request to the public
IP of the remote invitation to the VPN tunnel. This works with varying degrees
of success.
My googlefu is failing and I have been unable to find a way gain more control
over how the remote invite is created (ideally specifying the order of the IP
address's listed), or on the other end which IP address the remote assistance
connection should try to connect to.
Does any one have any food for thought on this? In advance thanks for any
advice!
Thank you,
Fred
~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
