|
I Get it, IBM hasn't fixed something we consider 'broken'. That happens
sometimes and nobody is happy when that happens. Me included.
BUT Consider it IS Windows that is misbehaving in this case.
The specification for SMB2 declares the function in question to be
OPTIONAL. The IFS in IBM i does not have the needed internals to support
this OPTIONAL function. There fore IBM does not (key: because they cannot)
support this function.
So Windows machines insisting on attempting to use the function cause
performance issues by repeatedly banging on the server (IBM i) with this
function.
For Windows 10 there is supposed to be a fix (which I don't have the ID
Handy) and there is also a hotfix provided here (
https://support.microsoft.com/en-us/hotfix/kbhotfix?kbnum=
812669&kbln=en-US) for most other Windows versions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.