IBM's stated reason for adopting SMB2 was because of the security holes in
SMB1. But if you disagree with this then it becomes quite easy to say
"there's no reason for it".
What I fault IBM with is trying to point fingers at Microsoft and say
their client is misbehaving. To me, this is like saying "there's no
problem with our (name your TCP service here). The Denial Of Service is
only because of nefarious activity on the internet.". Instead they should
harden their implementation of SMB2 to not blow when these situations
occur.
When they started pulling this crap is when I moved my file serving off of
IBM i and on to Windows.
IBM's documentation on this is twofold:
- One, the MTU documents some printing issues when adopting SMB2.
- Two, they have a document regarding their sniveling and how you can
workaround it.
http://www-01.ibm.com/support/docview.wss?uid=nas8N1021348
Rob Berendt
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
