×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
"NetServer is protocol compliant and changes need to be made on the client"?!? Seriously IBM!
-----Original Message-----
From: Rob Berendt [mailto:rob@xxxxxxxxx]
Sent: Thursday, April 13, 2017 12:07 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Die 7.1 Die!!!
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
midrange.com
