sgt_spike Posted September 1, 2018 Share Posted September 1, 2018 I've recently converted my drives to encrypted xfs. Now I can't access any of my shares in Win10 file explorer. This could be a windows problem and I wouldn't think the conversion could cause the problem. At this point it's hard to tell. According to Win diagnostics (yes, I know, not a good tool to use) Unraid is refusing my conection. I can ping it, and access IU via IE. If I'm missing something, please let me know Link to comment
genie137 Posted September 1, 2018 Share Posted September 1, 2018 In what way are you unable to access your shares? Is it refusing your credentials or not connecting at all? Link to comment
Frank1940 Posted September 1, 2018 Share Posted September 1, 2018 Have you read through this thread? https://forums.unraid.net/topic/53172-windows-issues-with-unraid/ Link to comment
sgt_spike Posted September 1, 2018 Author Share Posted September 1, 2018 2 hours ago, genie137 said: In what way are you unable to access your shares? Is it refusing your credentials or not connecting at all? It's not connecting at all. I tried opening a share through file explorer and I get the error "The network path was not found. As you can see from the attachment I can ping the server but can't access it to add files. Link to comment
Frank1940 Posted September 1, 2018 Share Posted September 1, 2018 Try using Windows Explorer (Windows File Manager) withe address \\192.168.1.111 and see what the result is. Link to comment
Squid Posted September 1, 2018 Share Posted September 1, 2018 There's a whole thread on windows issues with unRaid (actually with all NAS systems), but you can save yourself a world of trouble and instead of referencing \\tower, simply use the IP address instead Link to comment
sgt_spike Posted September 1, 2018 Author Share Posted September 1, 2018 I get the same thing. I have been reading through the windows issues thread. I've downloaded the dynamix local master plugin trying to see who the local master is. That's as far as I've gotten Link to comment
sgt_spike Posted September 1, 2018 Author Share Posted September 1, 2018 Enabling Samba and making the server the local master fix it. I'm good now. I'm probably guilty of it crapping out on me, oh well I fix it. Thanks for the support Link to comment
Frank1940 Posted September 1, 2018 Share Posted September 1, 2018 Post up your Diagnostic File Tools >>>> Diagnostics in a new post. EDIT: Glad to see you got it working. I was not looking forward to wading through a syslog file looking to see if SMB was running or if it had issues! 😌 Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.