- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Buffer error when using FTP
Operating System - OpenVMS
1748180
Members
4178
Online
108759
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-06-2008 10:16 AM
11-06-2008 10:16 AM
Re: Buffer error when using FTP
Welcome to the world of Internet standards and protocols and of RFCs and of de facto standards, and particularly where multiple incompatible and fully standards- or RFC-compliant methods can freely co-exist and (mostly) interoperate.
At its core, these inconsistencies and the "slop" in the various documents are why various vendors have or participate in "connect-a-thons" and such. And this is why an early or a dominant implementation might be incompatible with the standard or with the RFC, and then the other vendors can then choose to comply with the standard or comply with earlier (and buggy) implementations. (There are cases here with Microsoft browsers and ftp and OpenVMS servers won't play well together, if you want a specific citation.)
Welcome to the second-level world of ftp on OpenVMS, where different file transfer sequences can appear; where different record transfer modes can be negotiated depending on the capabilities of the client and the server. Various OpenVMS IP stacks have had longstanding implementation differences with STRU O VMS and VMS PLUS, for instance.
Further, the ftp design itself is from a different era of IP and of Internet networking; it has a number of inherent weaknesses including issues with performance and with firewalls. Not to mention its use of cleartext authentication. (ssh and sftp are better choices here.)
Per a longstanding industry maxim: if some particular product were truly "identical", then it would not be marketed as being "compatible". By accepted industry definition, "compatible" means "different". And ftp is compatible.
At its core, these inconsistencies and the "slop" in the various documents are why various vendors have or participate in "connect-a-thons" and such. And this is why an early or a dominant implementation might be incompatible with the standard or with the RFC, and then the other vendors can then choose to comply with the standard or comply with earlier (and buggy) implementations. (There are cases here with Microsoft browsers and ftp and OpenVMS servers won't play well together, if you want a specific citation.)
Welcome to the second-level world of ftp on OpenVMS, where different file transfer sequences can appear; where different record transfer modes can be negotiated depending on the capabilities of the client and the server. Various OpenVMS IP stacks have had longstanding implementation differences with STRU O VMS and VMS PLUS, for instance.
Further, the ftp design itself is from a different era of IP and of Internet networking; it has a number of inherent weaknesses including issues with performance and with firewalls. Not to mention its use of cleartext authentication. (ssh and sftp are better choices here.)
Per a longstanding industry maxim: if some particular product were truly "identical", then it would not be marketed as being "compatible". By accepted industry definition, "compatible" means "different". And ftp is compatible.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2009 05:40 AM
08-20-2009 05:40 AM
Re: Buffer error when using FTP
Thanks Guys.
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP