Performance Vision
Smart Agent
  • Register
  • Edit account
  • Forgot password?
  • ??????
    Home / Products / NetDecision Utilities / NetDecision Managed File Transfer (MFT) Server print version

    NetDecision Utilities
    List of the products

    NetDecision Managed File Transfer (MFT) Server

    NetDecision Managed File Transfer (MFT) Server

    The NetDecision MFT Server is an enterprise class managed file transfer server that provides FTP, TFTP and HTTP services in single system.

    The server implements full TFTP specification including RFC 1350 and all extensions specified in RFC 2347-2349 (blocksize, transfer size, timeout options). The server implements full FTP specification including protocol extensions. The server also implements HTTP 1.0 with NetDecision Server Pages (NDSP CGI) support for dynamic page generation. This technology uses NetDecision Scripting Language as backend (CGI) page generation program/script.
    The NetDecision MFT server uses a multithreaded architecture for high-performance and maximum reliability. The software enables the administrators to reach the maximum performance, when transfering the data. 

    NetDecision Anywhere LaunchPad uses MFT server internally to upload files to remote hosts, remote backups and remote software updates.

    What is TFTP?

    TFTP, or Trivial File Transfer Protocol, is a very basic file transfer protocol. It is very simple, doesn’t have any security authentication, and usually used for transferring small files.  It uses UDP, which doesn’t have error checking like TCP does. And, it’s best suited for transferring smaller files over a LAN, rather than an larger network like the Internet.

    For a network administrator, TFTP is an essential way of backing up router and switch configuration files. It could also be used to providing PXE boot files to thin-clients or network-based workstation installation systems.

    Technical Specifications

    • RFC 1350 "The TFTP protocol (Revision 2)" This document describes the basic TFTP protocol.

    Protocol extensions

    • RFC 2347 TFTP Option Extension 
    • RFC 2348 TFTP Timeout Interval and Transfer Size Options
    • RFC 2349 TFTP Blocksize Option

    What is FTP?

    FTP or file transfer protocol is a commonly used protocol for exchanging files over any network that supports the TCP/IP protocol (such as the Internet or an intranet). There are two computers involved in an FTP transfer: a server and a client. The FTP server, running FTP server software, listens on the network for connection requests from other computers. The client computer, running FTP client software, initiates a connection to the server. Once connected, the client can do a number of file manipulation operations such as uploading files to the server, download files from the server, rename or delete files on the server and so on. Any software company or individual programmer is able to create FTP server or client software because the protocol is an open standard. Virtually every computer platform supports the FTP protocol. This allows any computer connected to a TCP/IP based network to manipulate files on another computer on that network regardless of which operating systems are involved (if the computers permit FTP access).

    Technical Specifications

    • RFC 959 "FILE TRANSFER PROTOCOL" This document describes the basic FTP protocol.
    • RFC 854 "TELNET PROTOCOL SPECIFICATION" The FTP protocol is implemented on top of Telnet which is specified in this document. Especially the specification of the NVT (Network Virtual Terminal) is of importance.

    Protocol extensions

    • RFC 2389 "Feature negotiation mechanism for the File Transfer Protocol" Describes the FEAT command to detect available protocol extensions and the OPTS command to change the behaviour of some features.
    • RFC 2640 "Internationalization of the File Transfer Protocol" Describes the use of UTF-8 encoding for filenames. Since the original FTP standard did only allow 7-bit US-ASCII as encoding, this extension is fully backwards compatible. However, a few servers and clients are wrongly assuming the local encoding is used for the FTP protocol. Thus this extension seemingly creates incompatibilities where there in fact are none.
    • RFC 3659 This RFC introduces the MLS* family of commands for a machine parsable directory listing format. It also clarifies the use of REST and introduces a specified way to present the server"s directory structure using TVFS (Trivial Virtual File Store). In addition, it introduces the SIZE and MDTM commands. It makes it very clear, that the MDTM command should only be used to get the timestamp of a file and should not be used to set the timestamp, as that would add ambiguity.
    • EPLF specification "Easily Parsed LIST Format" Describes a machine parsable directory listing format.
    • The "MFxx" Command Extensions for FTP. This IETF draft describes the MFMT command to change the file modification time.

    What is HTTP?

    The Hypertext Transfer Protocol (HTTP) is an application-level protocol with the lightness and speed necessary for distributed, collaborative, hypermedia information systems. It is a generic, stateless, object-oriented protocol which can be used for many tasks, such as name servers and distributed object management systems, through extension of its request methods (commands). A feature of HTTP is the typing of data representation, allowing systems to be built independently of the data being transferred.

    HTTP has been in use by the World-Wide Web global information initiative since 1990. This specification reflects common usage of the protocol referred to as "HTTP/1.0".


    • Standards compliant
      • TFTP - implements RFC 1350, RFC2347, RFC2348, RFC2349
        • Supports all RFC defined options including:
          • Total Size (tsize)
          • Block Size (blksize)
          • Timeouts
        • Supports block numbers rollover/wrap (allows to transfer large files up to 4GB)
      • FTP - implements RFC 959, RFC 2389, RFC 2640, RFC 3659, EPLF, MFXX commands
      • HTTP 1.0
    • Multithreaded architecture (implemented as thread pool) for ultra high-performance and maximum reliability 
    • Built-in logging facility
    • Shows active transfers (including progress indication)
    • Shows HTTP requests stats
    • Built-in security subsystem to restrict clients access
    • Runs as desktop application or Windows service (using NetDecision Service Manager)
    • Small memory foot print (C++ implementation)
    • MS Office like graphical user interface for configuration and monitoring
    Developed by WebMechanica Copyright © 2001-2016 NetMechanica e-mail