The Horizon Mirage system and clients use default communication ports. Make sure that the correct ports and protocols are selected for the system.

The Horizon Mirage Management server and Horizon Mirage servers use external and internal communications, as follows:

External communications to communicate with the Horizon Mirage clients or Management console

Internal communications to communicate with each other

Ports and Protocols for Horizon Mirage Components

Component

Communications

Port

Protocol

Notes

Horizon Mirage service

External

8000

TCP/IP or SSL/TLS

The only port required for communications between Horizon Mirage clients and servers.

Note

SSL/TLS is optional and can be enabled as described in Install the Server SSL Certificate.

Horizon Mirage Branch Reflector

External

8001

TCP/IP

Used for communication between the branch reflector and the local peers at the remote site.

Horizon Mirage Management service

External

8443

TCP/IP

Used for communication between the Mirage Management console and the Mirage Management service. SOAP Message-level Security is applied.

Horizon Mirage Server service

Internal

135, 445

TCP/IP

Used for control communication between the Mirage Management service and the Mirage server.

Note

You may limit access to this port to incoming connections from the Mirage Management service host.

File Portal

Internal

8444

TCP/IP

Used for communication between the IIS server and the Mirage Management Server.

Horizon Mirage Edge server

Internal

8000

TCP/IP

Used for communication between the Edge Server and the Mirage server.

Note

The port must have DNS update access.

Internal

389, 636

TCP/IP

LDAP or LDAPS

Used for communications between the Mirage Edge server and the LDAP servers.

Internal

1001

TCP/IP

Used for communications between the Mirage server and the Mirage MMC console.

External

8000

TLS/SSL

Used for communication between the Mirage client and the Mirage Edge server.