| Author |
Message |
![[Post New]](/Sysforums/templates/default/images/icon_minipost_new.gif) 14/05/2009 10:24:32
|
Uili
SysAider
Joined: 14/05/2009
Messages: 1
Offline
|
Hi,
i am getting this error when i am trying to install the Agent in a computer...
What can i do to solve this?!
Best regrats,
Guilherme
|
|
|
![[Post New]](/Sysforums/templates/default/images/icon_minipost_new.gif) 18/05/2009 03:02:20
|
Haim
SysAider
Joined: 15/04/2008
Messages: 2449
Offline
|
Hello Uili.
This error means that the agent could not connect to the SysAid server (connection time out).
Please make sure that you can login to SysAid from that machine using the same URL you typed during the installation.
Also, please make sure there is no firewall between that machine and the SysAid server that is blocking the SysAid port.
Best regards.
Haim
|
Pushing IT forward |
|
|
![[Post New]](/Sysforums/templates/default/images/icon_minipost_new.gif) 20/08/2010 13:09:43
|
SA Consultant
SysAider
Joined: 06/07/2009
Messages: 37
Location: Ecuador
Offline
|
Hi,
Did you resolve this issue??
I'm experiencing this error trying to manually install the agent on a remote site. The error appears after I enter the URL, account and serial and click on Next. I already opened this ports in both firewalls (remote site and server site):
TCP 139
TCP 445
UDP 137
UDP 8193
TCP 4228
What else could it be?? Is there maybe a way to increase the timeout time??
By the way, is agent v7.0.05
Thanks!
|
|
|
![[Post New]](/Sysforums/templates/default/images/icon_minipost_new.gif) 23/08/2010 12:04:50
|
itayH
SysAid Customer Relations

Joined: 23/09/2009
Messages: 1092
Offline
|
Hi SA Consultant,
If you are trying to deploy the agent on a computer in a remote location please follow the the instructions bellow:
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.
Please update us.
|
Best Regards,
Itay |
|
|