[ossec-list] ossec 1.2 and 1.3 problems handling Window servers with multiple IP addresses

["Peter M. Abraham" <peter.m.abraham@xxxxxxxxx>]

Greetings:

I'm testing ossec (now 1.3) on two of our Window servers in addition
to our Unix-based servers; and one of the problems we are running into
is that on one of our Window servers, we have multiple IP addresses.

When I created the agent, I used the host name and primary IP address
for the server.

Note:  The Windows server involved runs H-Sphere from http://www.psoft.net/
and H-Sphere will modify the network card settings having the primary
IP be the most current IP as set up by a customer, and the advanced
tab will have the other IP addresses (so the true primary IP is still
in the list).

Can a future version of the Windows agent be set up to force calling
the ossec server from the authorized IP it was provided in the agent
key?

Does anyone have any ideas for what I can do in the mean time so that
ossec will work consistently on the server (right now I'm considering
using the second network card which only has one IP)?

Thank you.