Firewall and Proxy Server considerations when using Netop Portal communication

Rules or exceptions may need to be created that allow communication through a proxy server or firewall to communicate with the Netop Portal service. When you configure Netop Remote Control to use the Netop Portal communication, there are situations when access must be allowed through a company's proxy server and/or firewall.

Proxy settings

A proxy server is a server application or appliance that acts as an intermediary for requests from clients seeking resources from servers that provide those resources.

The Proxy settings can be defined on both Guest and Host, from Tools – Program Options – General – Proxy.

By default, no proxy is used when initializing the Netop Portal communication profile. This setting can be changed, to either attempt to detect and use the current proxy settings of the system (usually they can be seen by opening Internet Options – Connections – LAN Settings from Windows) or to manually specify a proxy server address and port to be used.

NOTE: Proxy authentication is not yet supported in this version.

• Guest

• Host

For the Impero Connect Portal service, the following communication needs to be allowed:

connect.backdrop.cloud domains

Outbound HTTPS (Port 443):

• accounts.connect.backdrop.cloud¹
  
• device.connect.backdrop.cloud¹
  
• connect.backdrop.cloud¹
  
• api.connect.backdrop.cloud¹
• dl.connect.backdrop.cloud¹
• secure.connect.backdrop.cloud¹
• get.connect.backdrop.cloud²
• remote.connect.backdrop.cloud²
• nas.connect.backdrop.cloud³
• wcs.connect.backdrop.cloud³

TCP (Port 443)³

• cm.connect.backdrop.cloud
• Ireland: s1-cs-eu-west-1.connect.backdrop.cloud:443 | 52.211.129.227 (static IP)
  
• Frankfurt: s1-cs-eu-central-1.connect.backdrop.cloud:443 | 52.28.221.32 (static IP)
  
• Singapore: s1-cs-ap-southeast-1.connect.backdrop.cloud:443 | 52.74.247.93 (static IP)
  
• Tokyo: s1-cs-ap-northeast-1.connect.backdrop.cloud:443 | 54.64.34.84 (static IP)
  
• Sao Paolo: s1-cs-sa-east-1.connect.backdrop.cloud:443 | 54.232.255.105 (static IP)
  
• N Virginia: s1-cs-us-east-1.connect.backdrop.cloud:443 | 54.164.69.65 (static IP)
  
• Oregon: s1-cs-us-west-2.connect.backdrop.cloud:443 | 54.148.245.185 (static IP)
  
• Bahrain: s1-cs-me-south-1.connect.backdrop.cloud | 157.175.10.43 (static IP)

WebSockets Secure (Port 443)

• wss.connect.backdrop.cloud¹

TCP & UDP²:

• s1-ice-ap-northeast-2.connect.backdrop.cloud | 3.34.203.149
  
• s1-ice-ap-south-1.connect.backdrop.cloud | 13.126.197.58
  
• s1-ice-eu-west-1.connect.backdrop.cloud | 52.228.62.188
  
• s1-ice-us-east-1.connect.backdrop.cloud | 54.157.42.39
  

Outbound HTTPS (for SSL certificate validation):

• GlobalSign ROOT CA R1
  • *.globalsign.com
• Amazon Root CA1
  • *.amazontrust.com

netop.com domains

Outbound HTTPS (Port 443):

• accounts.netop.com¹
• deviceapi.netop.com¹
• portal.netop.com¹
• portalapi.netop.com¹
• portal-dl.netop.com¹
• secure.netop.com¹
• get.netop.com²
• remote.netop.com²
• nas.netop.com³
• wc-eu-wcs.netop.com³

TCP (Port 443)³

• wc-eu-cm.netop.com
• Ireland:
  • cs-eu-west.netop.com:443 | 52.211.129.227 (static IP);
  • s1-wcs-eu-west-1.netop.com | 18.203.12.45 (static IP);
  • s2-wcs-eu-west-1.netop.com | 52.214.177.66 (static IP);
• Frankfurt: cs-eu-central.netop.com:443 | 52.28.221.32 (static IP);
• Singapore:
  • cs-ap-southeast.netop.com:443 | 52.74.247.93 (static IP);
  • s1-wcs-ap-south-1.netop.com | 13.126.31.199 (static IP);
  • s2-wcs-ap-south-1.netop.com | 65.1.183.153 (static IP);
• Tokyo:
  • cs-ap-northeast.netop.com:443 | 54.64.34.84 (static IP);
  • s1-wcs-ap-northeast-2.netop.com | 3.34.222.89 (static IP);
  • s2-wcs-ap-northeast-2.netop.com | 3.35.80.48 (static IP);
• Sao Paolo:
  • cs-sa-east.netop.com:443 | 54.232.255.105 (static IP);
  • s1-wcs-sa-east-1.netop.com | 18.231.9.29 (static IP);
  • s2-wcs-sa-east-1.netop.com | 54.94.75.28 (static IP)
     
• N Virginia:
  • cs-us-east.netop.com:443 | 54.164.69.65 (static IP);
  • s1-wcs-us-east-1.netop.com | 54.89.190.50 (static IP);
  • s2-wcs-us-east-1.netop.com | 54.145.155.159 (static IP);
• Oregon: cs-us-west.netop.com:443 | 54.148.245.185 (static IP);
• Bahrain:
  • cs-me-south.netop.com:443 | 157.175.10.43 (static IP);
  • s1-wcs-me-south-1.netop.com | 15.184.106.141 (static IP);
  • s2-wcs-me-south-1.netop.com | 15.185.152.47 (static IP);
• Cape Town:
  
  • cs-af-south.netop.com:443 | 13.245.250.222 (static IP);
  • s1-wcs-af-south-1.netop.com | 13.245.254.74 (static IP);
  • s2-wcs-af-south-1.netop.com | 13.245.148.178 (static IP);

WebSockets Secure (Port 443)

• wss.netop.com¹

TCP & UDP²:

• portal-ice-ap-northeast-v2.netop.com | 3.34.203.149
• portal-ice-ap-south-v2.netop.com | 13.126.197.58
• portal-ice-eu-west-v2.netop.com | 52.228.62.188
• portal-ice-us-east-v2.netop.com | 54.157.42.39

Outbound HTTPS (for SSL certificate validation):

• GlobalSign ROOT CA R1
  • *.globalsign.com
• Amazon Root CA1
  • *.amazontrust.com

If you protect your computer using a local firewall, make sure that you configure the firewall so that you allow the following Netop Portal executable files to run and be accessed from outbound LAN/internet access:

• nhstw32.exe (Host)
• ngstw32.exe (Guest)
• Netop Ondemand.exe

For assistance with your firewall configuration, please contact the firewall software provider.

Mass Deployment

To mass deploy the Host application when using the Portal communication profile, refer to the following link.

NOTE:
1 Services required by Netop Remote Control and Netop OnDemand.
2 Services required by Netop OnDemand.
3 Services required by Netop Remote Control.

Article Number: 373
Posted: Mon, Oct 20, 2014 12:18 PM
Last Updated: Mon, Dec 20, 2021 5:19 PM

Online URL: https://kb.netop.com/article/firewall-and-proxy-server-considerations-when-using-netop-portal-communication-373.html