nas

3 Topics

Cross domain AD auth for a NAS using an alias name
This is a bit of an interesting one. I've got a NAS system that for various reasons has multiple names on the network, about 5 at the last count. SMB1 is now disabled across the board which is causing issues with the NAS. If the NAS is accessed using it's actual hostname, all is good. If the NAS is access using an alias it works some of the time but not all. The big problem is that when the NAS is accessed using an alias name from a trusted domain it just throws up an access denied. I've tried a few things with SPN's as per https://support.microsoft.com/en-gb/help/3181029/smb-file-server-share-access-is-unsuccessful-through-dns-cname-alias but I've not been able to get it to work. So, how do I get computers in domain2 to access a NAS joined to domain1 using an alias name? Any suggestions very gratefully received as I've run out of ideas. Thanks!
Solved
Gary Williams
Dec 13, 2019 Place Windows Server for IT Pro
2.4KViews
0likes
1Comment
Green screen critical process died when mapping a nas drive.
I get a green screen critical process died error when mapping a synology nas drive. This causes windows to crash and restart.
Gib39
Mar 07, 2022 Place Windows Insider Program
2.2KViews
0likes
7Comments
Windows smb client and Zone.Identifier (WSL) authentication problem
hi together, we have an import process which import data from a csv file from a nas. I have change the nas server (from old to new server) and activate smb logging. Now i can see the following problems. We have on the nas a local user for application access and on the windows client side a other local user too (different names). Client machine is windows version 1809 build 17763.6414 (windows 10 enterprise ltsc). 1. problem - wrong Authentication Data for writing "Zone.Identifier" We configred the authentication data in the import process and the process used this data for access to the csv files. But it looks like that windows meta data process don't use this authentication data. I saw in tcpdump pcap file 4 smb sessions. First and secound smb sessions use the authentication data for the access to the 2 csv files. The third smb session use no authentication data. so that the access don't work. Whatevery windows in the third smd session will doing. The fourth smd session use a mix of source maschine name und destination user, which is not correct. I add read/write access for everbody, so that i can see, what is doing in the fourth session. Windows will writing/access to the Zone.Identifier file. 1. smb session: User: <nas>.<domain>\<nas_user> 2. smb session: User: <nas>.<domain>\<nas_user> 3. smb session: User: \ 4. smb session: User: <client machine name>\<nas_user> 2. problem - ignore "Do not preserve zone information in file attachments" setting now i activate this setting, so preventing writing of this kind of informations/files. But the windows client ignoring it. I have reboot the windows client and repeat the import process and windows tried to writing the zone information again. I change the setting about the following way. admin: gpedit.msc -> User Configuration > Administrative Templates > Windows Components > Attachment Manager and than enable the policy named "Do not preserve zone information in file attachments". Is this a know issue or hae sameone any idea? I would prevent the 3. and 4. smd session, so the access for the meta data proccesses. best regards Christian Voigt
Christian_Voigt
Jul 31, 2025 Place Windows 10
101Views
0likes
3Comments