rabidduck

Thanks I ended up taking the drive out and testing it in a docking station to see if it would show up, the drives spins but but never shows up, guess it's time for an RMA ;[

My parity drive was marked as faulty that was only a year old, and no idea how long it's actually been faulty, as I don't check the webUI often. So I took array offline, unassigned parity, and restarted array to it would forget the parity to try and rebuild. However now the drive isn't even an option to select in the menus, is it toast or am I missing some other option? If it's helpful I did a lshw -class disk in the terminal and the disk isn't there either Also a side question since I've never thought about this until now, if the drive is indeed toast how do I physically know which one it is? My drives are both the same brand/size so not actually sure how to physically ID it. https://easyupload.io/vbs7sb Also here is a download of the Diag files

Didnt work for me unfortunately. Ill take a look through that thread for anything new. I also did a quick test on my Windows 7 Machines and they both were able to interact with the unraid machine fine so I at least know that is working. EDIT: Found my fix it was adding in Windows Credentials like below(Kudos to random One post guy named navidos) and using a non root user(root didn't work), hopefully if anyone googles a similar situation to mine they find this.

It's set to private, I tried to change it up public then I couldn't see the unraid machine anymore(I could still connect to the WebUI) when I did that.

The same Network error that happens with the IP.

I was indeed typing it incorrectly however doing it the correct way (and in explorer) as you mention gives the same Network Error(both doing it with the \Nas and without.. Heres a quick screenshot just to help verify I'm not doing something silly. Also a screenshot of my shares.

Hi! I just recently building my first nas and was looking to use unraid. I installed v6.6.6 and everything seemed to be going fine. I currently can see the TOWER (which has been renamed to UNRAID, as I found some post that recommended renaming it). However when I attempt to 'open' it from the Windows (10) explorer it gives a 'network error - Windows cannot access \\UNRAID'. Reading through carious support threads on the forums here and other sites the most common suggestion I came across was to make sure you connect via IP and not by name due to windows issues. When I attempt to use \\192.168.1.68/NAS1 (NAS1 is the name of my share) it gives the same error. Some other things to mention that I have done is that I have made sure to enable the SMB1 stuff in Windows(I've attempted connecting with and without it). I can access the WebUI no problem via host name or IP. I have installed Dynamix Local Master to confirm that the unraid machine is the master. I've also installed Fix Common problems and it didn't find anything that would effect my connection problems. I've also tried the Map Network Drive in Windows however that didn't work for me either. At this point I haven't been able to find any other things to try to get it to work and am at a loss as to what to try next. Thanks in advance! unraid-diagnostics-20190220-1738.zip