Limetech posted some very informative information about issues with 'users' share access issues, Windows and SMB. My gut feeling is that the issue is on the Widows end of the equation but I can't quite put my finger on what triggered it.) Johnnie.black posted up about what he found in a series of posts in this thread: (I thought I had it 'fixed' when I switched to using Explorer++ as a Windows file manager but that started giving me problems. In my own case, I have reverted my Test Bed server back to 6.1.9 because of SMB issues copying files off of the server. (Or they are smart enough to avoid this whole can of worms!) I have attempted to help out folks because I do have some knowledge and, apparently, we don't have too many folks who have a real in-depth knowledge in the inter-workings of Samba. What fixes one persons problem doesn't fix the next person's problem that appears identical. A solution that worked last week, doesn't work this week. The problem is that solutions to SMB/Samba issues are more like witchcraft than science. You already do have a FAQ entry, it could be expanded, or it could point to the more comprehensive doc(s). I'd be happy to help any way I can, sticky the result in General Support.
#Windows 10 lanscan full
You've written about some of these several times, would you be interested in putting it all together? I don't know if a wiki page is better, or a long post, first authored by you, to which moderators at least could add to, or perhaps a full thread, moderated to only include posts on the issues but not user support posts.
#Windows 10 lanscan plus
If you want to force your unRAID server to become the Local Master, add these lines to the 'Settings' > 'SMB' icon > 'SMb Extras' tab:įrank, I'd really love to see all of this plus more collected into a comprehensive document on Windows issues with unRAID, both as to visibility problems (workgroup, local master, etc) and credentials/permissions issues. I tend to suspect that some of their updates have broken some things. Plus, there are some nagging issues as MS has recently revised their version of SMB and the Samba group is still playing catch up. Then restart with your server and after about ten minutes start to add back in your computers slowly one at a time. I have never figured out quite how Samba resolves this issue.) Sometimes, the best way to resolve issues is to shutdown every computer using SMB. (Windows ignores capitalization and Linux honors it. As a result, its polling intervals are actually quite long- think minutes! Be sure that all of the name of your workgroup on all of your computers have the same name and all are in CAPS only. Be aware the SMB can take a lot of time to resolve everything the network (It was written basically back in the days when the 80368 was the 'king of the hill') and was intended to add as little overhead to the CPU as possible.
0 kommentar(er)
