With Windows Server 2012, Microsoft sets the record straight and releases a full-featured FTP server, bundled with the operating system-ready to use, without the need to first bring (installation) files to your Server Core installation. Besides Secure Publishing, it also featured IPv6 support, virtual host names, user isolation, improved directory browsing, and authentication for non-Windows accounts. FTP 7.5 was released out of band for Windows Server 2008 R2. To this purpose, both the FTP data channel and the FTP control channel (for credentials and FTP commands) to transfer files come with an RFC-based implementation of FTPS (FTP over SSL), which allows you to encrypt data on the control channel, on the data channel, or on both channels. The ability to encrypt FTP traffic with SSL was first introduced in FTP 7.5 and called Secure Publishing. Thus, the transfer of data with FTP on these platforms (as with all older Windows Server platforms with built-in FTP servers) is unencrypted and can be intercepted while in transit. With that being said, you might not want to use Server Core installations of Windows Server 2008 or Windows Web Server 2008 as an FTP server, since these two Windows Server editions do not offer the ability to run an FTP server with SSL. Windows Server 2008, Windows Web Server 2008, Windows Server 2008 R2, and Windows Server 2012 all came with IIS, which is the main Server Role to turn Windows Server into an FTP server. Because the File Transfer Protocol (FTP) is adjacent, today, in its use cases to web servers, Microsoft has shared the FTP Server Role Service under the Internet Information Services (IIS) Server Role, like the many web server Role Services I discussed in the previous part of this series.ĭue to this grouping, you can use any Server Core installation as an FTP server, just as you can use any Server Core installation as a web server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |