---
title: "DNS failure on client machines"
slug: "dns-failure-on-client-machines"
updated: 2024-04-01T17:20:48Z
published: 2024-04-01T17:20:48Z
canonical: "kb.pharos.com/dns-failure-on-client-machines"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.pharos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# DNS failure on client machines

Why when I attempt to start the Pharos 7.1 Services do I receive the following error message:

"No route to host"

---

Under certain network configurations, some Pharos components fail to start up and instead produce the error message "No route to host".

This is due to the failure of the Domain Name Service to resolve a computer name into the correct IP address. To overcome this, add the IP address of the computer that runs the Pharos SignUp Server for the PC in question to the host configuration on the client PC.

For NT and Windows 2000 PCs, add a line containing the IP address and the machine name (separated by a space) to the file ‘lmhosts’ located in system32\drivers\etc.

e.g. 255.255.255.255 mainserver

## Related

- [Uniprint: Using Pharos Popups the Notify dialog not appearing on the client machine](/uniprint-using-pharos-popups-the-notify-dialog-not-appearing-on-the-client-machine.md)
- [Xerox iMFP: Authentication failure with error "Unknown error unable to authenticate".](/xerox-imfp-authentication-failure-with-error-unknown-error-unable-to-authenticate.md)
- [Client machines do not shut down from the logon screen.](/client-machines-do-not-shut-down-from-the-logon-screen.md)
- [Blueprint Tracker keeps failed jobs on the client machine.](/blueprint-tracker-keeps-failed-jobs-on-the-client-machine.md)
- [Changing the server Host Name value in the Pharos Administrator for DNS resolution.](/changing-the-server-host-name-value-in-the-pharos-administrator-for-dns-resolution.md)