Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Serv-U Managed File Transfer & Serv-U FTP Server > Setup Serv-U Gateway on public IP Address

Setup Serv-U Gateway on public IP Address

Created by Daniel Repasi, last modified by MindTouch on Jun 23, 2016

Views: 13 Votes: 1 Revisions: 4

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

 

 

Environment

All Serv-U versions deployed with Gateway

 

 

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
//  http://www.dnscrawler.com/tools.php
//
// -------------------------------------------------------------------------------------
// 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

 

 

 

Last modified
02:38, 23 Jun 2016

Tags

Classifications

Public