| Author |
Message |
![[Post New]](/Sysforums/templates/default/images/icon_minipost_new.gif) 11/02/2009 15:29:20
|
Brakerm19
SysAider
Joined: 03/09/2008
Messages: 9
Offline
|
When using the SysAid Deployment Tool (version 5.6.0.4) to deploy the agent to sysaid client systems there seems to be a very inconsistant listing of those systems that will report the version status of the SysAid Agent.
What causes the Deployment tool to not display the version information. Does this have anything to do with a firewall setting?
Please Advise.
For example:
Microsoft Windows Network
<tab>WorkGroup
<tab><tab>Computer1
<tab><tab>Computer2 (alive)
<tab><tab>Computer3 (alive)
<tab><tab>Computer4 (alive, running SysAid version 5.6.0.4)
<tab><tab>Computer5 (alive, running SysAid version 5.6.0.4)
<tab><tab>Computer6
<tab><tab>Computer7
<tab><tab>Computer8 (alive)
|
|
|
11/02/2009 18:12:38
|
techguy
SysAid Mod
Joined: 11/06/2008
Messages: 1506
Location: England
Offline
|
Older versions of the agent prior to 5.5 did not give a version number out, so maybe those machines are on older versions of the agent.
see this thread here:- http://www.ilient.com/Sysforums/posts/list/211.page#385
|
Need help? Try the SysAid wiki first! - http://sites.google.com/site/sysaidwiki |
|
|
12/02/2009 02:59:30
|
Global-ICT
Super SysAider
Joined: 08/07/2008
Messages: 86
Location: Netherlands
Offline
|
I had the same problem.
seems to be the Windows firewall settings.
also had the problem with the AVG internet security client.
Edwin.
|
|
|
12/02/2009 08:21:08
|
Haim
SysAid Wiz
Joined: 15/04/2008
Messages: 2449
Offline
|
Hey everyone,
The SysAid agent is transmitting its version in port 8193 UDP, and the deployment tool is listening on this port when you open it.
This is the procedure from the first version of the agent, so this is not related to the agent's version.
Please make sure that on your machine, port 8193 is open in the firewall, this can also be effected by the firewall on the client machine.
Usually disabling or adding an exception to the windows firewall solve the issue.
Bes regards.
Haim
|
Pushing IT forward |
|
|
13/02/2009 07:32:07
|
Brakerm19
SysAider
Joined: 03/09/2008
Messages: 9
Offline
|
Thanks for the information.
All the client agents were version 5.6.0.4 or 5.6.0.2
I have been also able to verify it was a windows firewall issue. As a workaround I have added the %programfiles%\SysAid\IliAS.exe as a program exception in the windows firewall. This caused all the agent versions to populate in the deployment tool as well.
I will make note of the UDP port as I would rather define a port exception versus a program exeption.
brakerm19
|
|
|
20/02/2009 15:31:15
|
drivenbywhat
SysAider
Joined: 19/02/2009
Messages: 41
Offline
|
I have a follow up question  . I too am in agreement that the firewall blocks udp port 8193 from "listening" and therefore the deployment tool can't show the correct version. However, why doesn't it block other requests? Since anything the server needs to communicate with the agent will go to port 8193 on the client wouldn't it be blocked by the firewall since there's no exception for it? I just find it odd that the only problem occurs with the deployment tool. For example, when I remote or do an inventory check that request will go to the agent and the agent reports back with the inventory or it starts up the RC. Yet I don't have an exception for port 8193 so why do these requests bypass the firewall?
|
|
|
22/02/2009 02:31:14
|
Lev
SysAid Mod
Joined: 18/08/2008
Messages: 508
Location: Haifa, Israel
Offline
|
Drive
Perhaps your answer is in the question.
As far as I remember RC and inventory don't work on udp 8193.
The biggest problem with ports is in the deployment.
|
DONT !!! DONT TOUCH THE KEYBOARD !!! |
|
|
23/02/2009 12:48:27
|
Haim
SysAid Wiz
Joined: 15/04/2008
Messages: 2449
Offline
|
The remote control default port is 4228 (tcp),please make sure that the admin machine (the machine you are controlling from) can accept connection on this port.
Best regards.
Haim
This message was edited 1 time. Last update was at 23/02/2009 12:48:37
|
Pushing IT forward |
|
|
25/02/2009 16:25:13
|
drivenbywhat
SysAider
Joined: 19/02/2009
Messages: 41
Offline
|
Okay perhaps I need to rephrase my question. At any given point in time the only port that is listening for sysaid is the agent on port 8193 am I correct? Since the agent is what drives everything else before any other ports are opened. So when I want to do an RC there is no RC client already listening for an RC connection. The RC request is made from the sysaid admin webpage that is sent to the sysaid agent. Then that agent knows to open up the RC client so it can connect to the admin pc on port 4228. If this is how it works then there were no problems with port 8193 not being opened on the firewall yet the agent listened and followed the request. Do I make sense now? If so, I can go back to my original question and ask why does the agent have a problem showing the version # in the deployment tool on port 8193 yet it doesn't have problems with any other types of requests on port 8193?
|
|
|
25/02/2009 18:33:26
|
Adam Racer
SysAid Customer Relations
Joined: 09/07/2008
Messages: 156
Offline
|
Unfortunately, that is not correct. By default, SysAid listens on port 8080, not 8193.
Port 8193 only reports back the agent version and is not used by the remote control tool.
During a remote control session, the administrator's workstation will communicate with the SysAid server on port 4228, while the SysAid server will communicate with the client's workstation on port 8080 (or whichever port SysAid is listening on).
|
|
|
02/03/2009 13:06:44
|
drivenbywhat
SysAider
Joined: 19/02/2009
Messages: 41
Offline
|
Seems I am not being understood  . Perhaps a screenshot will help. If you look at the screenshot it will show all the ports the client pc is listening on. As you can see the only port related to sysaid is 8193. No other ports in the screenshot are related to sysaid. This port 8193 is the sysaid agent itself. Before any other types of requests can be made to the client by the server it has to go here first. For example, if you want to do RC session the server first needs to go to the agent on the client, which is port 8193, to tell it to get ready for an RC session. At that point in time the agent opens up another connection to go back to the server on port 4228. But like I said everything starts with 8193 first. If this port is closed nothing will work because this is the agent port itself. If I close this port and try an RC session I will never be able to do an RC session because the agent is not on. Port 8193 is not only for reporting back the agent version to the deployment tool. So going back to my original question, even though I have a firewall and don't have port 8193 as an exception any type of request I make to the agent from the server works. However, the agent version will not report back which is weird because anything else works fine.
Well it seems I can't attach the screenshot to this post.
This message was edited 2 times. Last update was at 02/03/2009 14:15:37
|
|
|
03/03/2009 08:37:53
|
Lev
SysAid Mod
Joined: 18/08/2008
Messages: 508
Location: Haifa, Israel
Offline
|
This is the screenshot from Drivenbywhat.
Adam and Haim can you please continue with this issue?
![[Thumb - port.JPG]](/Sysforums/upload/2009/3/3/0bc35b8b05647d3e5fdba80d09b29944_2016.jpg__thumb)
|
| Filename |
port.JPG |
|
| Description |
|
| Filesize |
63 Kbytes
|
| Downloaded: |
9 time(s) |
|
DONT !!! DONT TOUCH THE KEYBOARD !!! |
|
|
03/03/2009 09:21:31
|
Haim
SysAid Wiz
Joined: 15/04/2008
Messages: 2449
Offline
|
drivenbywhat,
Perhaps we didn't fully explained the agent and how it works.
Your screenshot is showing that the agent is only listening on port 8193 which is correct.
To initialize remote control or inventory, the agent doesn't need to listen to any port since the agent is configured to access the server once every 30 seconds (as default) to check if there are any "tasks" for it.
Those tasks are remote control and inventory.
This is why the agent doesn't listen on the other ports.
The software which does listen to port 4228 is the remote control view on the administrator side.
I hope this clear up the matter.
Best regards.
Haim
This message was edited 1 time. Last update was at 08/03/2009 06:55:37
|
Pushing IT forward |
|
|
03/03/2009 11:41:07
|
drivenbywhat
SysAider
Joined: 19/02/2009
Messages: 41
Offline
|
 Ah, now I understand. It only listens on 8193 to give the deployment tool its version number. Other than that it is actually making connections to the server to check for any tasks rather than listening for server tasks. Got it!
As for the 4123 for RC I thought it was 4128 & 4228?
Thanks for all your help so far guys.
|
|
|
03/03/2009 12:09:29
|
techguy
SysAid Mod
Joined: 11/06/2008
Messages: 1506
Location: England
Offline
|
So you mean I have got 400+ assets talking on my network every 30 seconds to the server to see if there is any work to be done?, I don't like the sound of this at all, talk about network congestion....! I would prefer the remote control tool to just sit there listening in our environment, and then the agent would only need to poll once an hour for any other tasks to do like inventory or agent upgrades.
But I can understand why you have done this, to avoid multiple firewall issues and rules and you may not always know the current ip address of that device.
This message was edited 2 times. Last update was at 03/03/2009 18:23:05
|
Need help? Try the SysAid wiki first! - http://sites.google.com/site/sysaidwiki |
|
|
![[Up]](/Sysforums/templates/default/images/icon_up.gif){kind=icon}
![[WWW]](/Sysforums/templates/default/images/icon_www.gif){kind=icon}
