Skip to content
English
  • There are no suggestions because the search field is empty.

Check connectivity to the ezeep cloud

Use these checks when a Connector is offline, sign-in fails across several devices or cloud printing cannot connect. Have the administrator responsible for the network review the requirements.

[Step] A. Allow outbound TCP 443 to ezeep and check DNS resolution

The device needs an Internet connection and access to ezeep over HTTPS:

  • Allow outbound TCP port 443.
  • Allow the ezeep domain pattern *.ezeep.com.
  • Ensure DNS can resolve the required ezeep hostnames.

These are outbound cloud-access requirements.

[/Step]

[Step] B. Allow Hub access to ezeep on 443 and Azure Devices on 8883

Hub remote access additionally requires access to:

  • *.ezeep.com on port 443.
  • *.azure-devices.net on port 8883.

For Hub-specific network settings and reconnection, check the Hub’s network and cloud connection. For a console-access problem, troubleshoot Hub console access.

[/Step]

[Step] ✓. Check service and Connector status, reconnect and print a test page

  1. Check service status for an incident affecting the same function.
  2. In the administrator portal, open Connectors and check the relevant device.
  3. Interpret its status: green means online; red means the last successful connection was more than ten minutes ago; grey means claimed but not connected.
  4. After correcting connectivity, reconnect the affected device and print a test page.

For the Windows tray-menu reconnection steps, use the session-error guide. The technical requirements contain the supported operating-system and browser requirements.

If access remains blocked, give your network administrator the affected hostname, port, device and time of failure. Include those findings when contacting support.

[/Step]