Port 1364 is where IBM Sterling Connect:Direct listens for server connections. When enterprises need to transfer files reliably between systems—mainframes, Unix servers, Windows machines—this is where those connections land.
What Runs on Port 1364
Service: Network DataMover Server (ndm-server)1
Protocol: TCP and UDP
Official assignment: IANA-registered in the User Ports range (1024-49151)
Port 1364 handles server-side connections for IBM Sterling Connect:Direct, a point-to-point file transfer solution used by enterprises worldwide. Port 1363 handles the requester/client side and API connections, while 1364 is where the server listens.2
The Network Data Mover Story
Connect:Direct wasn't always called Connect:Direct. It started as Network Data Mover (NDM)—a high-speed file transfer product created for IBM mainframes running MVS.3
This was before the web. Before FTP became ubiquitous. When moving files between mainframes meant you needed something that could handle massive transfers without corruption, with guaranteed delivery, and with the ability to restart if something failed halfway through.
Network Data Mover solved that problem. It became the standard for enterprise file transfer—the thing banks used to move transaction files, the thing insurance companies used to exchange policy data, the thing that kept business-critical data flowing between systems that absolutely could not afford to lose a byte.
In 1993, after Systems Center, Inc. was acquired by Sterling Software, NDM was renamed to Connect:Direct.3 The name changed, but the mission didn't. The product went through several corporate hands—Sterling Commerce acquired by SBC Communications in 2000, then sold to AT&T, then purchased by IBM in 2010.3
Through all of that, port 1364 kept doing its job. Listening. Transferring. Delivering.
How It Works
Connect:Direct is a point-to-point file transfer system. Unlike FTP where you connect to a server and manually navigate directories, Connect:Direct is designed for scheduled, automated transfers between known systems.
You define a transfer: what file, from which system, to which destination, when to run it, what to do if it fails. Connect:Direct handles the rest.
Port 1364 is where the receiving server listens for these connections. When a transfer initiates, the sending system connects to port 1364 on the destination, authenticates, and begins moving data. The protocol handles compression, encryption, checkpoint restart (if a transfer fails midway, it can resume from where it stopped), and notification when the transfer completes.
This isn't about humans transferring files. This is about systems transferring files—reliably, repeatedly, without supervision.
Why This Port Matters
Some ports carry web traffic. Some carry email. Port 1364 carries the files that make enterprise operations possible.
The payroll data that moves from HR systems to banks. The transaction logs that flow between data centers. The batch files that insurance companies exchange at night. The inventory updates that retail systems share with suppliers.
These transfers happen in the background, often overnight, scheduled to run when systems are less busy. Most people have no idea they're happening. But if port 1364 suddenly stopped working, businesses would notice immediately.
When you check your bank balance and the number is correct, there's a decent chance a Connect:Direct transfer over port 1364 helped make that happen.
Registered Port Range
Port 1364 falls in the registered ports range (1024-49151). These ports are registered with IANA for specific services, but they're not reserved the way well-known ports (0-1023) are. On most systems, regular users can bind to these ports, though in practice they're usually managed by system administrators.
The registration provides a standard: if you're running Connect:Direct, you know to expect traffic on ports 1363 and 1364. Firewalls know what to allow. Documentation knows what to reference.
Security Considerations
Connect:Direct connections on port 1364 should be carefully controlled:
- Firewall rules: Only allow connections from known, trusted systems
- Authentication: Connect:Direct has its own authentication mechanism—use it
- Encryption: Modern versions support TLS for encrypting data in transit
- Monitoring: Watch for unexpected connection attempts on port 1364
Older deployments sometimes run without encryption. If you're transferring sensitive data—which enterprise file transfers almost always are—make sure encryption is enabled.
Checking What's Listening
To see if anything is listening on port 1364 on your system:
On Linux/macOS:
On Windows:
If Connect:Direct is running, you'll see it listening on this port. If nothing is listening and you don't use Connect:Direct, that's normal—this is a specialized enterprise tool, not something consumer systems use.
Related Ports
- Port 1363 — Network DataMover Requester (ndm-requester), the client/API side of Connect:Direct2
- Port 10000 — NDMP (Network Data Management Protocol), a different protocol for NAS backup despite the similar name
- Port 21 — FTP, the predecessor for many file transfer needs (though Connect:Direct solves different problems)
The Port That Keeps Working
Port 1364 has been doing the same job since before most of the Internet existed. The technology has evolved—encryption added, new platforms supported, performance improved—but the core purpose remains unchanged.
Move files. Reliably. Between systems that matter.
This isn't glamorous infrastructure. It's not the kind of thing that makes headlines. But it's the kind of thing that, if it stopped working, would quietly break thousands of business processes that people depend on.
That's what port 1364 carries. The files that need to arrive. Every time.
Byla tato stránka užitečná?