Multi-homed server does not report expected IP

Technote (FAQ)


Why is your multi-homed server not reporting the expected IP?


Server Protection for Windows chooses the first IP in the Windows binding order to use the reported Agent IP.


You can manually set the Agent IP value by adding a tuning parameter to the sigs.ini file on the agent itself:

agent.ip = [ip_address]

For instance, on a system that has multiple adapters listening on and, you could fix the agent.ip value to one or the other by adding either

agent.ip =


agent.ip =


There is not a way to modify sigs.ini from SiteProtector; as such this change must be made manually on each agent.

If your sigs.ini is encrypted, you will need to disable 'Encrypt configuration files' in the Administration policy under Agent Protection, push this policy to the agent, and modify the plain-text policy while the sensor is stopped. 'Encrypt configuration files' can be re-enabled afterward and the changes will be retained in the encrypted version of the file

Currently there is no way to configure the agent to use a DHCP address assigned to a given interface.

IBM Host Protection Documentation IBM Infrastructure Security Forums IBM Security Support Channel on YouTube IBM Fix Central Fixes and Updates IBM Security License Key and Download Center Subscribe to My Notifications for Important Product Alerts IBM Security Contact Support

Document information

More support for:

IBM Security Host Protection

Software version:


Operating system(s):


Reference #:


Modified date:


Translate my page

Content navigation