Windows10 SMB share failure after OSMC 2016.9-1 upgrade

In early October I upgraded nicely working 2016.8-1 VERO and Pi3 systems to 2016.9-1.

The Windows file shares using IP address (eg: broke, now report no network connection.
(however the network connection is there). No re-establishment is possible.

After several day of messing around I discover using "WORKGROUP and the computer name
that the file shares CAN be seen, established and used ???

I am using the IPaddress since this was recommended here the last time the file shares quit.

Not an urgent problem for me but very puzzling… Willing to make tests as required.

We would need to see a log here. There haven’t been any changes to the Samba implementation since April in OSMC.