Re: V7R3 mapped drive issues from Win2008 R2 Server

Hi Buck

Ain't we having fun now?

The fix for the Change Notify Behavior is a Win 10 fix, and for the 1607 build only that I know of. I am currently running the 1709 build of Win 10 that I got as the Creator's Update or some such name.

IBM's article - Rob cited it - has instructions on a registry change in Windows to disable the behavior. It said it is for XP and also works on version up through 7.

I am not sure that this notify behavior would affect being able to create a mapped drive, but it might - we have at least 1 person on Win 7 who is connecting to the 7.3 box with SMB 2 just fine - go figure!

We have change SMB to version 1 and probably ain't gonna change, it seems it will have the fewest potential issues - we've lived with it for years with no problems, right?

Vern

On 2/21/2018 10:35 AM, Buck Calabro wrote:

On 2/16/2018 5:25 PM, Rob Berendt wrote:

<snip>
SMB2 to Win7 completely killed a mission critical application.
What choice did I have?
Tell the boss that I'd rewrite payment processing ASAP?
</snip>
But it's no longer necessary. Just put the current fixes on both.

Without specific documentation about /what fix/ [1] alters this SMB2
Change Notify behaviour on Windows 7, I will not get permission to
re-enable SMB2 on the IBM side.

[1] I spent several hours with my friends Google and Microsoft and came
up empty handed for a Windows 7 fix.