Has anyone using a NAS for their network storage had issues connecting after the latest Windows Update (April 2018 / version 1803)? I've got ours setup using SMB and since the update it has been a nightmare to actually connect to the device, regardless of which SMB format I use or whether SMB1 is turned on or off in Windows. Connections aren't working with UNC paths or mapped drive letters. network is fairly basic - no domains or AD being used, just users signing into the NAS.
I have a Virtual Machine here thats on 1803 (for testing, prior to updating the office) and its running fine, accessing the NAS. It even has all of the ADSK stuff on it, which was deployed (after 1803) from the NAS. Our setup sounds a bit different than yours, but we didnt make any changes, before testing that VM. It just worked, all along.
Windows 10 Pro 1803 (17134.48) installed on 5.1.2018.
Synology 1817+ / 1815+
DSM 6.1.5 (pending updates to 6.1.6)
We access by both UNC (production machines) and Drive Letter (not production machines). They are on a Domain, however. But i cant see that being the reason its working (but maybe?)
Other than the Domain it seems about the same. In the DSM, which version(s) of SMB are enabled? I believe the issue has to do with SMB1 being deprecated in 1803, and devices that were on SMB2/3 aren't quite as prone to issues but I don't really have a good way to test that at the moment, at least that I can think of.
Synology is set to Max SMB2, Min SMB1.
weird. I wonder if the Domain has an affect.
sidenote: there is a hack involving the Hosts file that seems to resolve the issue if it happens, but I can't figure out why it happens in the first place other than the SMB change.
Ehhhhhh, i really wouldnt be happy having to edit and rely on Hosts files, on all the machines. Thats a really sucky thing to have to do.
I tried to test access to my DS214+, by upgrading a VM to 1803. Windows Update **** the bed.
Also, I find it funny that the site actually flags the old fashioned English past tense of passing stool. How is anyone supposed to talk about Microsoft or Autodesk when all the verbs and adjectives get the **** treatment?!
Wait... The Windows Update failed, or you successfully updated, and that killed your connection to the NAS?
The former. And twice. Third time seems to have produced an actual update. But not sure if it's 1803 yet. Gawd I hate Windoze.Originally Posted by Twiceroadsfool
EDIT: Updates are now at 5%. Looks like I can actually test in the morning. We need a *** emoji. ;0 (wow, excrement gets the *** treatment too. But by god I'll beat the sensors. We need a Mr Hankey emoji! Take that automation!
I'm 1No. M2x2.5 screw away from finding out if the original m2 SSD, (w/ a pre-1803 Win10 OS) will launch a recently returned, new mobo, Alienware R5 so can't confirm - but willl - if I remember this thread.
But in the meantime, my "handbag-friendly" (with each day confirming itself as my best IT purchase ever!) - albeit on Win8.1 - has no issue connecting to my DSJ213.
If that helps?
One imagines it doesn't.
Posting Permissions
LinkBack URL
About LinkBacks
Reply With Quote