October 25, 20223 yr After the my server plugin issue this morning I can not access any mounts on my unraid server. I can ping from unraid terminal to windows ip I can ping from cygwin terminal to unraid ip When I try to connect i get: M:\ is unavaiable. When I go to Map network drive then click browse and select the server "TOWER" it returns: \\TOWER is not accessible. You might not have permission to use this network resource...." This qualifies as a really odd failure - to me at least. tower-diagnostics-20221024-2034.zip
October 25, 20223 yr Community Expert It sounds like Widows 10 is not allowing you to connect to your server with what it considers to be an insecure connection. (It may have worked in the past but MS has been known to plug security holes with its automatic updates!) I would suggest that you look at this post and setup your SMB connection using the instructions in the PDF file in this post. You will be setting up a User on the Unraid server and a Windows credential to automatically log you onto your Unraid server whenever you first access the server. https://forums.unraid.net/topic/110580-security-is-not-a-dirty-word-unraid-windows-10-smb-setup/#comment-1009109
October 25, 20223 yr Author I will attempt this, but I can almost guarantee that this will not work. As I did not change anything on the windows side between the smb mount functioning and it not. The linked document says "...edge case situation where a brand new Windows 10 computer..." This is a system that has been running for a long while with no network additions or changes. Edited October 25, 20223 yr by lonebear more details
October 25, 20223 yr Author 14 minutes ago, lonebear said: I will attempt this, but I can almost guarantee that this will not work. As I did not change anything on the windows side between the smb mount functioning and it not. The linked document says "...edge case situation where a brand new Windows 10 computer..." This is a system that has been running for a long while with no network additions or changes. results as expected - no change. Again - as the system was and is working to the internet. And a bit of additional detail. It is certainly not on the windows side as I can access both the internet, and a web cam that is in the 192.168.1.x network.
October 25, 20223 yr Community Expert This is a first. So bear with me. A bit of housekeeping first: You did set up a User on your Unraid server. (As I recall with the recent versions of Unraid, you can't use an e-mail address as a user name...) You set up a credential for that user on your Win10 client using the Credential Manager. You rebooted your Win10 client. (Once Win10 logs into the server, rebooting is the fastest way to logout!) Be sure to verify that you entered the correct password in the Windows Credential Manager because it is a 'blind' type and no second entry to verify the first 'blind' entry. If it still is not working, let's start to see what is going on. (I got information about your specific server from your diagnostics file so any one else who is reading this reply will have to make changes to match their Unraid setup!) First, open up Windows Explorer (also called, Windows file manager or File Explorer). In the address bar, type \\tower You should now see the shares on your Unraid server. If you don't, try the following in the address bar: \\192.168.1.169 Assuming you see the shares, try clicking on the TV share (that one is public so you should have access to it...) Did you gain access to it? If not, get a screen capture of the error message. Edited October 25, 20223 yr by Frank1940
October 25, 20223 yr Author I was fully running with authentication as a user for some shares and open for others. The credential existed. The system was working. I removed and recreated the credential. There have been multiple reboots of server and workstation.
October 25, 20223 yr Community Expert 1 hour ago, Frank1940 said: You should now see the shares on your Unraid server. If you don't, try the following in the address bar: \\192.168.1.169 Did you get the same response from the above address? (This should be the IP address for your Unraid server.) You should be able to see the server even if you can't access any of the shares. If you can't see the server, upload a new copy of the diagnostic file.
October 25, 20223 yr Author 42 minutes ago, Frank1940 said: Did you get the same response from the above address? (This should be the IP address for your Unraid server.) You should be able to see the server even if you can't access any of the shares. If you can't see the server, upload a new copy of the diagnostic file. Same failure. These are all steps I have gone through multiple times. The network is functional. I can get to the internet. I can get to another device on 192.168.1. I can get to at least one docker (plex). The only failure is to SMB shares. tower-diagnostics-20221025-1207.zip
October 25, 20223 yr Community Expert Your ability to connect to the Internet has absolutely nothing to do with your inability to access the server. See here for that discussion: https://forums.unraid.net/topic/34889-dynamix-v6-plugins/page/44/?tab=comments#comment-462656 (Both can be affected by a hardware problem in the network-- switches, wiring, NIC ---but if that hardware is working then two are independent.) SMB is complex (and I have long considered it a Kludge) and fixing SMB/samba issues is more akin to witchcraft than science. Let me provide another link to show some of what goes on: https://forums.unraid.net/topic/25064-user-share-problem/?tab=comments#comment-228392 The above link is old (2013) and some of the items (like 'guest' access) discussed have been blocked by Microsoft because they are security risks. Read from pg 14 of the PDF file for "Case 3" for information about this. Another issue is SMBv1 (some times called NetBIOS as well as some terminology). It is normally turned off in Windows and LimeTech has recently turned it off on all new installs of Unraid. This is normally only an issue for older devices (like 2010 media players) but it can be another source of potential issues. The most important fact that has to be paramount on your mind as you troubleshoot SMB problems from a Windows PC is that the first time a server is accessed, it will be logged into that server. That login will be what that Windows client will use for all access to the server. If that login is of the 'guest' variety, the Windows client will normally deny access to any share on the server. It may even offer you a login prompt widow but that will always fail since only one connection from a Windows client is allowed to each server. As a corollary, the simplest way to force a SMB logout from a server to to reboot the client. (OK, there is a command line command that will do it. I have included it below.) net use * /delete Remember that most of automatic updates that Microsoft sends out on the second Tuesday of every month usually address security issues. And some of those are SMB security issues. If you are not setting up your SMB network to their latest recommendations, these updates can break things. One more question, are you trying to access things via Active Directory (AD) as that is another issue entirely?
October 25, 20223 yr Author 6 hours ago, Frank1940 said: Your ability to connect to the Internet has absolutely nothing to do with your inability to access the server. See here for that discussion: https://forums.unraid.net/topic/34889-dynamix-v6-plugins/page/44/?tab=comments#comment-462656 (Both can be affected by a hardware problem in the network-- switches, wiring, NIC ---but if that hardware is working then two are independent.) SMB is complex (and I have long considered it a Kludge) and fixing SMB/samba issues is more akin to witchcraft than science. Let me provide another link to show some of what goes on: https://forums.unraid.net/topic/25064-user-share-problem/?tab=comments#comment-228392 The above link is old (2013) and some of the items (like 'guest' access) discussed have been blocked by Microsoft because they are security risks. Read from pg 14 of the PDF file for "Case 3" for information about this. Another issue is SMBv1 (some times called NetBIOS as well as some terminology). It is normally turned off in Windows and LimeTech has recently turned it off on all new installs of Unraid. This is normally only an issue for older devices (like 2010 media players) but it can be another source of potential issues. The most important fact that has to be paramount on your mind as you troubleshoot SMB problems from a Windows PC is that the first time a server is accessed, it will be logged into that server. That login will be what that Windows client will use for all access to the server. If that login is of the 'guest' variety, the Windows client will normally deny access to any share on the server. It may even offer you a login prompt widow but that will always fail since only one connection from a Windows client is allowed to each server. As a corollary, the simplest way to force a SMB logout from a server to to reboot the client. (OK, there is a command line command that will do it. I have included it below.) net use * /delete Remember that most of automatic updates that Microsoft sends out on the second Tuesday of every month usually address security issues. And some of those are SMB security issues. If you are not setting up your SMB network to their latest recommendations, these updates can break things. One more question, are you trying to access things via Active Directory (AD) as that is another issue entirely? was able to clear with net use * /delete. Still getting error using any method _other_ than \\tower in explorer bar. I also enabled nfs in windows services so I expect I'm using that now instead of smb. And it appears to run slower than befor. Still annoyed that this happened. Ah well. ETA: Copies and moves appear to inconsistently fail to these mounts. Edited October 25, 20223 yr by lonebear more details
October 29, 20223 yr Author Still only a semi-functional network/system. Copy or move to the server over nfs (as opposed to smb) often hangs for minutes. I still can not connect via smb to unraid.
October 30, 20223 yr Author On 10/25/2022 at 1:22 PM, Frank1940 said: Your ability to connect to the Internet has absolutely nothing to do with your inability to access the server. See here for that discussion: https://forums.unraid.net/topic/34889-dynamix-v6-plugins/page/44/?tab=comments#comment-462656 (Both can be affected by a hardware problem in the network-- switches, wiring, NIC ---but if that hardware is working then two are independent.) SMB is complex (and I have long considered it a Kludge) and fixing SMB/samba issues is more akin to witchcraft than science. Let me provide another link to show some of what goes on: https://forums.unraid.net/topic/25064-user-share-problem/?tab=comments#comment-228392 The above link is old (2013) and some of the items (like 'guest' access) discussed have been blocked by Microsoft because they are security risks. Read from pg 14 of the PDF file for "Case 3" for information about this. Another issue is SMBv1 (some times called NetBIOS as well as some terminology). It is normally turned off in Windows and LimeTech has recently turned it off on all new installs of Unraid. This is normally only an issue for older devices (like 2010 media players) but it can be another source of potential issues. The most important fact that has to be paramount on your mind as you troubleshoot SMB problems from a Windows PC is that the first time a server is accessed, it will be logged into that server. That login will be what that Windows client will use for all access to the server. If that login is of the 'guest' variety, the Windows client will normally deny access to any share on the server. It may even offer you a login prompt widow but that will always fail since only one connection from a Windows client is allowed to each server. As a corollary, the simplest way to force a SMB logout from a server to to reboot the client. (OK, there is a command line command that will do it. I have included it below.) net use * /delete Remember that most of automatic updates that Microsoft sends out on the second Tuesday of every month usually address security issues. And some of those are SMB security issues. If you are not setting up your SMB network to their latest recommendations, these updates can break things. One more question, are you trying to access things via Active Directory (AD) as that is another issue entirely? As I expected, it _appears_ to be an unraid issue. I finally got off _my_ duff and translated what i needed from RH to slack and also noticed that the dashboard and main had " Array Started•Starting services." up. So I looked, and /etc/rc.d/rc.samba status returns "Starting Samba" and that specific failure persists even after a fresh reboot.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.