Hi, you are right. This is on the NAS booted into the boot environment from the Nov update during which the issue was never seen.
I can boot into the Dec update based BE and send this info to you. However that will need sometime.
These are shares in a build environment. Not exactly production, but quite actively used.
Would you like me to update and boot into that environment and send that info to you? Let me know. I can try it over a weekend when this is not used and post the output.
I have understood what you have said about the nightly dev updates.
Hi,
Today I did get to try the latest update available and check for that hosts allow and deny after booting into the latest update BE. I did get to see options to edit allowed and denied hosts in the UI for the SMB share and it looks like some IP ranges were present. Not sure from where they are inherited.
I wanted to leave this running, but the AD connection was failing due to some issues and I did not have time to debug the problem.
So in the latest available updates the options to edit the allowed and denied hosts in present.
However the AD binding failure did not allow me to test this further. I will find sometime to debug this and check sometime in the coming weekends and report back on how it works.
Thanks for the help so far. Will get back on this.