Tools

Setup Serv-U Gateway on public IP Address

Serv-U Gateway by default does not listen for Serv-U control connections on 1180 on any public IP addresses as most customers use private IPs combined with static NAT rules in their DMZ.

First published date

11/29/2018 10:56 PM

Last published date

11/29/2018 10:56 PM

Overview

Serv-U Gateway by default does not listen for Serv-U control connections on 1180 on any public IP addresses as most customers use private IPs combined with static NAT rules in their DMZ.

 

The following gateway configuration setups are supported:

  • Serv-U with Public IP - Gateway with a different Public IP with CIDR
  • Serv-U with Private IP - Gateway with Public IP with CIDR
  • Serv-U with Private IP - Gateway with Private IP

 

The following gateway configuration setup is NOT supported:

  • Serv-U with Public IP - Gateway with Private IP

Product section

Serv-U Managed File Transfer & Serv-U FTP Server

Resolution

​Customers who use public IPs in their DMZ segment, will need to edit Gateway's Accept-Public-IP-CIDRs.txt file to include the IP scope of Serv-U.

The Accept-Public-IP-CIDRs.txt file is located in the Serv-U Gateway installation directory:

C:\Program Files\RhinoSoft\Serv-U Gateway\Accept-Public-IP-CIDRs.txt

 

 

Reference file for example:

// Serv-U Gateway Public Address Listening File
//
// If any IP address CIDR entries below are uncommented (removal of leading //),
// then Serv-U Gateway will listen for incoming Serv-U control connections on all
// public IPv4 and IPv6 addresses on this machine.
//
// Entries below control the IP addresses from which Serv-U control connections
// will be accepted.  These entries MUST be full CIDR notation.  For a detailed
// explanation of CIDR notation visit these pages:
//
//  http://en.wikipedia.org/wiki/Classle...Domain_Routing
//  http://www.subnet-calculator.com/cidr.php (© 2018 Sohopen.co.uk, available at http://www.subnet-calculator.com/, obtained on December 4, 2018)
//  http://www.dnscrawler.com/tools.php (© 2018 DNSCrawler.com, available at https://www.dnscrawler.com/, obtained on December 4, 2018)
//
// -------------------------------------------------------------------------------------
// IpV4 Example: Gateway has an IP address of 11.11.11.11; Serv-U is connecting from
//               22.22.22.22
//      - No entry is necessary for the 11.11.11.11 address because Serv-U Gateway will
//        listen on all public IP addresses
//      - The following CIDR access control entry is necessary to receive Serv-U control
//        connections from 22.22.22.22
// 22.22.22.22/32
// -------------------------------------------------------------------------------------
// IpV6 Example: Gateway has an IP address of 1111::; Serv-U is connecting from
//               2222::
//      - No entry is necessary for the 1111:: address because Serv-U Gateway will
//        listen on all public IP addresses
//      - The following CIDR access control entry is necessary to receive Serv-U control
//        connections from 2222::
// 2222::/128

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.