Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Serv-U Managed File Transfer & Serv-U FTP Server > Serv-U - Knowledgebase Articles > Serv-U Gateway on a DMZ

Serv-U Gateway on a DMZ

Table of contents
Created by Dhalia Turiaga, last modified by MindTouch on Jun 23, 2016

Views: 1,171 Votes: 2 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

Environment

  • Serv-U version 15.x
  • Windows Vista/7/8, Server 2008/2012 - C:\ProgramData\RhinoSoft\Serv-U (Folder is Hidden in Windows by default)
  • Windows 2000/XP, Server 2000/2003 - C:\Program Files\RhinoSoft\Serv-U
  • Linux - /usr/local/Serv-U

Detail

If Serv-U is on a NATted set up, use the IP that is in the gateway’s interface therefore it is the private IP address and not the public one as seen on the screenshot below:

 

 

Last modified

Tags

Classifications

Public