On Tue, Sep 11, 2012 at 8:45 AM, rohan kamat <[email protected]> wrote: > I have done that too. Ihave also reinstalled the client and sever. Still I > getthe message as never connected. > > I have added my agent address in the white lists too of the server config. > > wHAT SHOULD
>> Are packets making it to the manager on port 1514/udp? >> >> If so, are the replies making it to the agent? >> >> Is this your only agent? Are other agents working? >> >> Does the agent have multiple IP addresses? Is the correct one being >> >> used? > On Thursday, December 8, 2011 10:11:12 AM UTC-5, dan (ddpbsd) wrote: >> >> On Tue, Dec 6, 2011 at 4:33 AM, Bruno Vernay <[email protected]> wrote: >> > >> >> Are packets making it to the manager on port 1514/udp? >> >> >> >> If so, are the replies making it to the agent? >> > >> > I don't know how to be sure, but there are no firewall between the two >> > at >> > least. >> > >> >> >> >> Is this your only agent? Are other agents working? >> > >> > No other agent configured. >> > >> >> >> >> Does the agent have multiple IP addresses? Is the correct one being >> >> used? >> > >> > It has only 10.1.5.50. I even disabled IPv6 on the windows client. >> > >> > >> > Just to be sure: my client is v2.6 and the AlienVault uses v2.5.1 >> > server, >> > could it be a problem ? >> > >> > >> >> It could be. Newer agents with older managers is definitely an >> "unsupported" configuration.
