---
title: "Pharos PopUp printing outside the Windows Domain when the system is on a specific Windows Domain."
slug: "pharos-popup-printing-outside-the-windows-domain-when-the-system-is-on-a-specific-windows-domain"
updated: 2024-04-01T08:19:35Z
published: 2024-04-01T08:19:35Z
canonical: "kb.pharos.com/pharos-popup-printing-outside-the-windows-domain-when-the-system-is-on-a-specific-windows-domain"
---

> ## 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.

# Pharos PopUp printing outside the Windows Domain when the system is on a specific Windows Domain.

Is it possible to utilize Pharos PopUps outside of our Windows Domain?

---

This is normally not possible. Uniprint was designed with a Domain or Enterprise environment in mind. When building the PopUp package, it's built with the server name that's entered in Pharos, and if that's not resolvable, it won't print, and PopUps will not have the ability to function as desired.

However if your DNS is configured such that clients outside your Windows Domain can resolve IP's to host names that re inside your Windows Domain then potentially they may work. Networking and routing also play a big factor in the communications between the Pharos Popup Client and the Pharos Server components.

## Related

- [Monitor Translator error: "Received Soap Fault: 2; Translator.ConnectFailure; Failed to create SOAP client object"](/monitor-translator-error-received-soap-fault-2-translatorconnectfailure-failed-to-create-soap-client-object.md)