In a typical organization, there is no need to change any of the existing firewall or proxy rules. All communication between the uniFLOW Online service and the components on the company network take place via HTTPS (port 443, outbound), which is usually allowed for regular website access.
However, if you have restricted access out of your network for devices, general access to the below URL’s and IP addresses need to be granted to reach uniFLOW Online.
www.nt-ware.com:
5.9.111.67
78.46.35.44
UK | DNS | IP |
Deployment* | <tenant>.uk.uniflowonline.com | 51.132.34.151 |
Tenant creation / device registration via device UI** | www.uk.uniflowonline.com | 51.132.34.151 |
NTWOIS service*** | ntwois.uk.uniflowonline.com | 52.151.72.165 |
Azure IoT Hub***** | ukiothubuniflow.azure-devices.net | - |
EUROPE | DNS | IP |
Deployment* | <tenant>.eu.uniflowonline.com | 40.113.96.203 |
Tenant creation / device registration via device UI** | www.eu.uniflowonline.com | 40.113.96.203 |
NTWOIS service*** | ntwois.eu.uniflowonline.com | 13.73.143.121 |
Azure IoT Hub***** | euiothubuniflow.azure-devices.net | - |
JAPAN | ||
Deployment* | <tenant>.jp.uniflowonline.com | 13.71.129.59 |
Tenant creation / device registration via device UI** | www.jp.uniflowonline.com | 13.71.129.59 |
NTWOIS service*** | ntwois.jp.uniflowonline.com | 13.78.27.73 |
Azure IoT Hub***** | jpiothubuniflow.azure-devices.net | - |
AUSTRALIA | ||
Deployment* | <tenant>.au.uniflowonline.com | 13.70.152.165 |
Tenant creation / device registration via device UI** | www.au.uniflowonline.com | 13.70.152.165 |
NTWOIS service*** | ntwois.au.uniflowonline.com | 23.101.239.160 |
Azure IoT Hub***** | auiothubuniflow.azure-devices.net | - |
SINGAPORE | ||
Deployment* | <tenant>.sg.uniflowonline.com | 52.187.22.132 |
Tenant creation / device registration via device UI** | www.sg.uniflowonline.com | 52.187.22.132 |
NTWOIS service*** | ntwois.sg.uniflowonline.com | 52.163.85.154 |
Azure IoT Hub***** | sgiothubuniflow.azure-devices.net | - |
USA | ||
Deployment* | <tenant>.us.uniflowonline.com | 137.117.90.136 |
Tenant creation / device registration via device UI** | www.us.uniflowonline.com | 137.117.90.136 |
NTWOIS service*** | ntwois.us.uniflowonline.com | 137.116.127.38 |
Azure IoT Hub***** | usiothubuniflow.azure-devices.net | - |
CHINA | ||
Deployment* | <tenant>.cn.mdsflowonline.com | 42.159.6.167 |
Tenant creation / device registration via device UI** | www.cn.mdsflowonline.com | 42.159.6.167 |
NTWOIS service*** | ntwois.cn.mdsflowonline.com | 42.159.114.81 |
nt-ware.com / mdsflowonline.com **** | mdsflowonline.com | 139.217.14.177 |
Azure IoT Hub***** | cniothubmdsflow.azure-devices.cn | - |
* The site where the service is hosted.
** For creating tenants and onboarding devices via the Canon imageRUNNER ADVANCE device user interface. It will also need to resolve and access 'www.nt-ware.com' and 'device.c-cdsknn.net'.
*** NT-ware OAuth Identification Service
**** Provides technical resources, for instance, downloads of tools and software like the MEAP applets.
***** IoT Hub is a managed service, hosted in the cloud, that acts as a central message hub for bi-directional communication between the uniFLOW SmartClient and the devices it manages.
IOT Hub has a temporary "static" address, which is subject to change over time, so there is no IP address that can be documented here. Microsoft suggests following best practices, described in this article docs.microsoft.com/en-us/azure/iot-hub/iot-hub-understand-ip-address