× 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.



On 6/28/2017 2:55 PM, Arco Simonse wrote:

Regarding disabling SMB V1 and enabling SMB V2 on the i, there is a known
problem with SMB V2 between the i and MS windows: Microsoft Windows
Explorer is ignoring a STATUS_NOT_SUPPORTED response that is returned to it
from the IBM i server on a Change Notify request.

see http://www-01.ibm.com/support/docview.wss?uid=nas8N1021348

Both IBM and Microsoft seem not willing or able to solve this.

Any thougths of the group?

If there's a single word that describes my feelings about this, it's
'betrayed'.

I spent untold hours constantly advocating, _promising_ that we could
consolidate workloads on IBM i. It took years - literal years - to move
workload to IBM i. Just one example: I have trading partners who email
spreadsheets to us. The users Save As... onto the IFS where RPG
programs read them. Our business just works. Now, with SMB2, that
process is /broken/ and unusable.

In order to continue to process my daily workload, I have been forced -
by IBMs intransigence - to disable SMB2 and revert to the insecure SMB1.
Worse than that: I am now between Scylla and Charybdis: Run an insecure
system, or tell management that their IBM platform really is a second
class citizen. That they were, in fact completely correct that the old
AS/400 should be replaced with modern Windows machines.

My professional credibility is shot.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.