Many security_mode=share issues here, what's the problem?

Please see the latest update from L3 Engineer: I debugged this issue again in 4.1.10 yesterday. After ReadyNAS firmware upgrade from 4.1.8 to 4.1.10, the samba model also upgrade from 3.0.37 to 3.5.16. If user created a new share when NAS run firmware 4.1.10, it would add a new property for the share. Below is the key information: nas-06-3F-A6:/etc/samba# cat smbpasswd test-4.1.8:1003:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:[NU ]:LCT-00000000: test-4.1.10:1004:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:[NDU ]:LCT-00000000: #　which means samba disallow user access this share. If you edit this configuration file delete parameter “D”, restart the samba, then it would be access without password. I did not know whether this is samba 3.5.16 issue or our NAS FrontView issue. My colleague told me the NAS and Samba 3.5.16 has some compatibility issue when it worked “Share” mode. Our recommend solution is changed to “User” mode, and most of our user accepted our suggestion. I am sorry I give you unclear information, because the ReadyNAS NV+ 4.1.10 is stable firmware, I did not know when we will release a new firmware, so I give you a unclear feedback. Now there are 2 solutions: Now there are 2 solutions: 1. Changed to “User” mode, 2. Edit the /etc/samba/smbpasswd configuration file and delete the parameter “D”, then it would be worked. - Question: Why the share be create in 4.1.8 can be access without password? - Answer: because when NAS worked in 4.1.8, and user create a share, it has not parameter “D”, so it can be work.

chirpa wrote:
NTGR abandoned Share security mode a few years ago. User mode with Guest access was the replacement, but not fully tested obviously for all scenarios. Since its not supported anymore, and was only on Sparc, which is EOL, I doubt you'll see anything from NTGR on the issue.

These issues occur because the folders or libraries that you are trying to back up or restore include a reparse point. Reparse points resemble Windows shortcuts or to Unix symbolic links. A reparse point may be used to point to a file that is temporarily relocated on a different drive. For example, a reparse point would allow a folder such as C:\DVD to point to Drive E, the actual DVD drive.

Issue 2 This issue occurs if the reparse point is a mounted volume that contains compressed files (for example, multimedia files, .zip files, and so on).

Work around issues that occur when you try to back up files Issue 1 and Issue 2 To work around these issues, remove the reparse point from the library, and then run the backup wizard again. To back up content for this reparse point (in this case, the FAT volume or the mounted volume), select the absolute path of this location in the Windows Backup configuration user interface. To locate reparse point folder or its subfolder, follow these steps: Click Start button, type CMD in the Search program and files box and then press Enter. In the Command Prompt window, type DIR /AL /S and then press Enter. The list of JUNCTION (one type of reparse point) list is displayed. Note You see several entries that say "junction" and the location that the entries point to (“junction point” is another name for “reparse point”). When a program tries to write to a directory that is really a reparse point, those files are sent (completely blindly to that program) to the other directory instead. To delete mounted volume reparse point, follow these steps: Locate the reparse point you found, right click the reparse point icon and click Properties. In the General tab, confirm the folder Type is Mounted Volume and then delete this folder.

27/09/2011 14:45 <JUNCTION> Application Data [C:\Users\X\AppData\Roaming]
27/09/2011 14:45 <JUNCTION> Cookies [C:\Users\X\AppData\Roaming\Microsoft
27/09/2011 14:45 <JUNCTION> Local Settings [C:\Users\X\AppData\Local]
27/09/2011 14:45 <JUNCTION> My Documents [C:\Users\X\Documents]
27/09/2011 14:45 <JUNCTION> NetHood [C:\Users\X\AppData\Roaming\Microsoft
27/09/2011 14:45 <JUNCTION> PrintHood [C:\Users\X\AppData\Roaming\Microso
27/09/2011 14:45 <JUNCTION> Recent [C:\Users\X\AppData\Roaming\Microsoft\
27/09/2011 14:45 <JUNCTION> SendTo [C:\Users\X\AppData\Roaming\Microsoft\
27/09/2011 14:45 <JUNCTION> Start Menu [C:\Users\X\AppData\Roaming\Micros
27/09/2011 14:45 <JUNCTION> Templates [C:\Users\X\AppData\Roaming\Microso
0 File(s) 0 bytes

Directory of C:\Users\X\AppData\Local

27/09/2011 14:45 <JUNCTION> Application Data [C:\Users\X\AppData\Local]
27/09/2011 14:45 <JUNCTION> History [C:\Users\X\AppData\Local\Microsoft\W
27/09/2011 14:45 <JUNCTION> Temporary Internet Files [C:\Users\X\AppData\