Using the Pharos HP iMFP solution the display shows a 200.2 error when attempting to login.

Problem:

When using the Pharos HP iMFP Solution our HP printer displays a 200.2 error message. The error indicates that the printer is unable to establish a connection to it's configured parent server.

 Investigation:  

First, if this is a newly installed HP iMFP Application Server the device is configured to connect to then check to see if the JediAuthService.svc web page is functional.

http://your.servername.domain/hpimfp/auth/jediauthservice.svc

You should see the JediAuthService web page, any other result indicates that a Role Feature is missing or there is an incorrect setting in IIS somewhere.

Second, while there are a variety of reasons outside of the control of our solution on the device, the next item to verify is that the DNS configuration of the device is correct. Check this by logging into the printer and verifying its TCP/IP v4 settings to ensure the DNS settings are correct. Even if they are it is possible that the DNS servers are not providing the correct name resolution information to the device.

Additionally you can test the DNS servers that the device is configured to use by using the NSLOOKUP command.

1. Open an administrative command prompt.

2. Type NSLOOKUP to open the Windows utility.

3. Type 'SERVER x.x.x.x' and use the IP Address of the DNS Server the Device is using.

4. Type in the hostname of the Blueprint/Uniprint Server (Pharos Products both use the iMFP Software) that this device is configured to communicate to.

**This tells the NSLOOKUP command to use a specific DNS Server and you can test to see how it resolves a specific hostname.

Note: Most often you will still be able to PING the printers IP Address and print directly to the device via its IP Address. This does not mean that the printer is able to resolve using DNS the servers hostname it is to connect to or connect back to the server. Using PING only verifies that the NIC on the printer is able to respond to an ICMP Packet.

Unfortunately there are other reasons that can cause a devices TCP connection attempt to the server fail that are not visible to the device, this can make it difficult to determine why the device is failing to connect to the server.