| Author |
Message |
![[Post New]](/Sysforums/templates/default/images/icon_minipost_new.gif) 25/08/2010 13:41:25
|
imodsupport
SysAider
Joined: 03/03/2010
Messages: 6
Location: Denver, CO - New York, NY - Washington D.C.
Offline
|
Having issuse with RC. We support 3 locations using SysAid...when RC into the 2 locations/networks I'm (admin) not part of, we connect via VPN then enter the virtual IP address in order to connect. This worked for a few weeks, now it is not working. Does anybody have a good and consistent way to RC into assets in SysAid if the asset is not on my netowrk or the worker is at home?
|
|
|
26/08/2010 23:59:05
|
SBIT
Super SysAider
Joined: 03/06/2009
Messages: 78
Location: Calgary
Offline
|
If you at your office, the best way to have the agents check in is via an external DNS name to your site - no VPN required.
However if you are at home and want to connect to the client, the way the SysAid agent works currently this is not going to work. Essentially in that situation you need some other method but then it gets messy i.e., creating VPNs and using RDP...
What we need is a firewall friendly solution such as this:
http://www.ilient.com/Sysforums/posts/list/2724.page#12359
|
|
|
27/08/2010 03:00:05
|
itayH
SysAid Customer Relations
Joined: 23/09/2009
Messages: 1092
Offline
|
Hi imodsupport,
These instructions also apply to machines that just need to access SysAid over the internet.
If you would like to install the SysAid Agent on machines located in a remote LAN in order to track / remotely control them, please do the following:
1. Your SysAid Server needs to have one of the following:
a. A Public/External IP address.
b. A port forwarded from your external IP address to the internal IP address of the SysAid server. So all requests to http://externalIP:8080 will be forwarded from your firewall/router to http://internalIP:8080.
2. If you have more than a few machines on the remote LAN, it is recommended that you install the Administrator Tools on one of the machines in the remote LAN, and then deploy the agent from that machine to the other machines. Otherwise, you can simply install with the manual install package. On the remote location, you can download the Administrator Tools from the Downloads page by logging in to your SysAid Server as an administrator.
3. When installing the Administrator Tools, you will need to enter the public/external IP address of your SysAid Server in the server URL, in order that this machine will be able to communicate with the server. The serial and account ID can be found on the Downloads page.
4. Once you have correctly installed the Administrator Tools, you can use the Deploy SysAid tool in order to automatically deploy the agents across the LAN at your remote location. After the deployment (several minutes or more, depending on the amount of assets and connection speed to the SysAid server), you should see those assets in your System -> Asset List / My Network Assets page.
5. If you wish to remotely control the assets in the remote LAN, you need to have one of two things:
a. A public IP address assigned to your workstation.
b. A forwarded port from your external (router) IP address to your workstation IP address.
On the assets remote control page, you need to enter the external IP address (which is then forwarded to your internal LAN IP address). You also need to have the Administrator Tools installed on your own workstation as well as have the “Sysaid Remote Control Viewer” running in the your system tray.
|
Best Regards,
Itay |
|
|
|
|
![[Up]](/Sysforums/templates/default/images/icon_up.gif){kind=icon}
![[WWW]](/Sysforums/templates/default/images/icon_www.gif){kind=icon}
