If you plan to install LifeCycle Manager Server using server's (M3 Home Server) hostname instead of IP address, be sure that name resolution is working on your network. The server hosting LifeCycle Manager Server service must be accessible from LifeCycle Manager Client (M3 Project Admin Client/Server) using LifeCycle Manager Server hostname or FQDN.
Avoid using the underscore (_) character in hostnames. Refer to
All active network cards installed on a server and connected to the LifeCycle Manager Server or LifeCycle Manager Services must be configured to use the following:
A Fully Qualified Domain Name (FQDN)
A static IP address
Special consideration has to be taken if the server is configured with multiple network cards or addresses. LifeCycle Manager database (on the M3 Home Server) binds by default to the network card listed as primary. If a LifeCycle Manager Client connects to the LifeCycle Manager Server using the secondary network adapter, the LifeCycle Manager Server service cannot bind to the LifeCycle Manager database. You have to connect to the LifeCycle Manager Server using the primary network card.
A reserved IP address if the network card is configured to use Dynamic Host Configuration Protocol (DHCP).
Do not forget to configure reverse DNS lookup for all enabled network cards installed in your server.
Network cards that are not attached to the network must be disabled.