Error message: The service could not be contacted. Please make sure the service is started before running the client.

When clients attach to HP Web Jetadmin, the software performs a redirect using the an IP address from the NIC that the application selected during startup. Sometimes, servers have multiple NICs and HP Web Jetadmin does not always pick the correct NIC and, during client launch, may re-direct to the wrong IP address on the network. When this happens, the client fails to start. Below is a scenario and an instruction for configuring HP Web Jetadmin to bind to the correct NIC.

Scenario:

Server has multiple NICs, not all of which are accessible by clients:

• NIC1=192.168.0.35 - accessible to clients
• NIC2=192.168.10.10 - not accessible to clients
• NIC3=192.168.20.254 - not accessible to clients and selected by HP Web Jetadmin during startup

In this case the clients will be browsing to 192.168.0.35 or its IP Hostname (DNS). When they do, HP Web Jetadmin will redirect to 192.168.20.254 and the client startup will fail. In this case, the administrator of the HP Web Jetadmin server will need to configure to allow H) P Web Jetadmin to bind to the correct NIC. Follow these steps to configure HP Web Jetadmin to bind to a specific NIC.

Steps:

1. Locate file …\Program Files\Hewlett-Packard\Web Jetadmin10\Config\WjaService\System.Remoting.config.
2. Open the file System.Remoting.config in a simple text editor such as Notepad.
3. Edit the text to add the additional item as shown below:
   BEFORE (partial text):
   
   rejectRemoteRequests="false" tokenImpersonationLevel="Impersonation"
   
   secure="true" protectionLevel="EncryptAndSign"
   impersonate="false" >
   AFTER (partial text):
   
   rejectRemoteRequests="false" tokenImpersonationLevel="Impersonation"
   
   secure="true" protectionLevel="EncryptAndSign"
   impersonate="false" machineName="xxx.xxx.xxx.xxx" >
   
4. Once the additional item ‘machineName="xxx.xxx.xxx.xxx"’ has been added to the file, save and close the file.
5. Restart the HPWJA service.
6. Once the service has completely started, browse to the client start page and verify success.