From version 5.4 and onwards, Zoom has added support to access Zoom services over a different LAN or WAN. With this feature it has become easier to access the Zoom server at another location OR in a completely different LAN with different DNS. People who are in a different network altogether or when multiple DNS names have different IP routing would be able to access Zoom server/Preview server without any issues.
To access web visual asset browser (WebVab) and visual approval (VA)
- Zoom web asset browser and visual review works on any browser with adobe flash support. For e.g on desktop/workstation/laptops etc.
- Access to Zoom preview server is required to run Zoom web asset browser and visual review.
- Usually ports
8873, 9873(SSL), and, 8443are required to connect to WebVab and VA (note: ports can differ in different deployments). Please make sure that from other LAN/WAN these ports are open and accessible to send and receive data.
- For e.g., if preview server is running with IP: 192.168.1.10 and you want to access it from IP:192.168.30.65, then make sure that IP:192.168.1.10 is accessible from machine 192.168.30.65 and the server’s ports 8873, 8443 are open. If some proxy is used to communicate between 192.168.30.X to 192.168.1.X then please configure the proxy to forward these ports from proxy to preview server.
- There are no restrictions on using any DNS name for accessing WebVab and VA through browser.
[Basic]: To access Zoom server from desktop clients.
See this article for setting up host names on Zoom server: NAT Setup for External Access to Zoom Services
No special treatment is required as long as Zoom desktop clients are in the same network and able to connect to Zoom server and preview server.
It is recommended to configure Zoom server and preview server to work on specific host name like:
zoom.mycompany.com -> for Zoom server (192.168.1.9)
preview.mycompany.com -> for Preview server (192.168.1.10)
As long as the desktop clients can resolve the host name configured on zoom server, they will work. Problems arise when someone tries to access Zoom server/preview from a different network with a different DNS server and the Zoom server name zoom.mycompany.com and preview.mycompany.com are not accessible. Perhaps, in the other DNS they want to use their own company/department name instead of mycompany.com. Let’s assume they want to use xyzcompany.com instead of mycompany.com.
In the above mentioned scenario if zoom.xyzcompany.com is pointing to 192.168.1.9 (i.e zoom.mycompany.com) and preview.xyzcompany.com is pointing to 192.168.1.10 (i.e preview.mycompany.com), desktop clients will work by entering http://zoom.xyzcompany.com:8880 instead of http://zoom.mycompany.com:8880.
|Original Zoom Preview/Server Host||DNS 2/Another Network||Status|
|zoom.mycompany.com||myzoom.xyzcompany.com||Incorrect – zoom and myzoom prefix doesn’t match|
|preview.mycompany.com||mypreview.xyzcompany.com||Incorrect – preview and mypreview doesn’t match|
|zoom.mycompany.com||zoom.xyzcompany.com||Correct – prefix zoom is same in both mycompany.com and xyzcompany.com|
|preview.mycompany.com||preview.xyzcompany.com||Correct – prefix preview is same in both mycompany.com and xyzcompany.com|
[Advanced]: To access Zoom server from desktop clients.
Many times it is not possible to use the same DNS prefix as in the section above. To overcome this, Zoom has provided an easy solution of mapping another host name to the Zoom configured host name.
Assuming that Zoom server and preview server are already configured and running with the following DNS host names and IPs:
Now let us assume another company/department wants to access Zoom server from an altogether different network of 192.168.30.X and with different DNS name of Zoom server my-server.xyzcompany.com and preview server my-preview.xyzcompany.com
They want to access Zoom servers as:
Connecting to http://zoom.mycompany.com would not work as the DNS server would be unable to resolve it (altogether different DNS topology from xyzcompany.com).
To make it work follow the steps below:
- Go to the client machine where Zoom client is installed and from where you want to connect to Zoom server.
Zoom client must be installed on the machine to follow this procedure
- Open Z -> Settings -> Advance Properties, and add a new property with name
true. If this property already exists, then ensure that its value is set to
- Open the command-line console application:
- Terminal app on a Mac
- Command Prompt on Windows
- Console/Terminal/shell prompt on Linux
- Run the following commands:
zm sethosts zoom.mycompany.com my-server.xyzcompany.com ENTER
zm sethosts preview.mycompany.com my-preview.xyzcompany.com ENTER
- Now run the command “
zm hosts” to print the hosts mapping.
zm hosts Enter
preview.mycompany.com -> my-preview.xyzcompany.com
zoom.mycompany.com -> my-server.xyzcompany.com
zm sethostscreates the mapping of Zoom server’s and preview server’s original DNS host names to new DNS host names for this client. And,
zm hostsprints all existing mappings.
- Once the mapping is added, you can connect to Zoom server by using the address:
"zm help sethosts":
Syntax: zm sethosts urls
The command supports the following options:
urls List of host names to correspond to the last listed host name.
Set the hostname that will be used, instead of the supplied hostname, for network communication.
# Set the Zoom client to use the hostname "server.myorg.com", instead of "zs.datacentre.local"
zm sethosts zs.datacentre.local server.myorg.com
# Remove the hostname replacement of "zs.datacentre.local"
zm sethosts zs.datacentre.local ""