Troubleshooting proxy issues
On the Home > General tab of the Configuration Manager, you can define settings to allow your service to communicate through a proxy server. The settings you define here are only used by the CPS. In most deployments, this is sufficient, since all communication with the PrinterOn Directory flows through the CPS.
📘 Instructions
However, there are two scenarios in which simply setting the CPS proxy settings is insufficient:
If you have implemented a Hybrid Direct deployment, in which each component communicates directly with the PrinterOn Directory. In this case, you’ll need to configure the proxy settings for PAS and PDS individually.
For more information on configuring proxy settings for a component, see Configuring the proxy settings for an individual component.
If you have a proxy configured in the Internet Explorer/Windows settings. In this case, the Windows proxy functionality causes a known issue to arise that prevents PrintAnywhere from communicating with other local components.
To work around this issue, you’ll need to configure the proxy settings for PrintAnywhere, and then whitelist the local addresses required by CPS.
For more information on configuring proxy settings for PrintAnywhere, see Configuring the proxy settings for an individual component.
For more information on whitelisting certain addresses, see Configuring proxy exceptions.