Thomas Tilley
[ Home ] [ Publications ] [ Resume ] [ Family ] [ Projects ] [ The Others ] [ Sitemap ]
[ Home ] [ Publications ] [ Resume ] [ Family ] [ Projects ] [ The Others ] [ Sitemap ]
This post will demystify what people mean when they say “BNET FTP,” explore why it still appears in legacy systems, and—most importantly—explain why you should move to modern, secure alternatives.
The good news: modern protocols like SFTP and FTPS are easy to deploy, widely supported, and secure by design. Retire your BNET FTP this quarter, and your future self (and security auditor) will thank you. Have you encountered a “BNET FTP” server in your environment? Share your experience in the comments below. And if you need help migrating legacy file transfers, contact our team for a free assessment. bnet ftp
BNET FTP: Understanding the Legacy, Risks, and Modern Alternatives This post will demystify what people mean when
The short answer: BNET FTP isn’t a widely recognized standard protocol like SFTP or FTPS. Instead, it typically refers to FTP servers hosted on networks (using Banyan’s “StreetTalk” naming service) or, more commonly in gaming circles, a misnomer for file transfers related to Battle.net (Blizzard’s gaming service). In enterprise contexts, “BNET” can also stand for a private, internal network segment using legacy IBM or Banyan systems. Have you encountered a “BNET FTP” server in