solomon

Members
  • Posts

    12
  • Joined

  • Last visited

Everything posted by solomon

  1. 9926 was the version just released. I was able to repro that on two boxes, so I'm curious to see if you repro it on yours if you upgrade. I just actually saw the same issue on my win7 box too. Didn't have time to dig into it but adding a password on the share fixed that box up again. I feel like SMB shares have been pretty squirly since I upgraded unraid to 5.0.6. Maybe I'll try to throw my backup back on there and see if it fixes things.
  2. This fixed it. You can even switch it back and forth without rebooting and see it work. Looking at the reported networking issues for windows 10 I see a lot of reports of people unable to hit their NAS boxes. Hopefully Microsoft figures out it's a problem for their next release. Thanks for posting the fix, appreciate it. Solomon
  3. Some other weird things showed up too. When I tried to hit the OSX share it prompted me for a password. When I tried to hit the unraid share it just failed. I had to manually send a user with a "/user:" for it to work. Definitely some kinks somewhere.
  4. So a few weird things. I couldn't access the Mac from win10. I then setup an account on the Mac side instead of public and then it started working. So I went to unraid and setup an account for one of my shares. Win10 was then able to access that share, and suddenly able to access all the other shares without accounts associated with them.
  5. I just setup win10 on a VM to test it and it has the same issue. My wind8.1 VM works fine.
  6. I verified both unraid and my win10 box are both in WORKGROUP
  7. I verified I'm still able to hit the box from my mac on the same networking using: smb://tower. Anyone else have windows10 issues?
  8. I just tried disabling the fireawll and same issue Unraid has all the shares set to public.
  9. Hello, A bit ago I updated by long standing unraid build to 5.0.6. I also setup a new windows 8.1 box. The box would hit unraid fine at \\tower for awhile and then suddenly stop working. It then only worked if I hit it by the ip address \\10.1.10.18. I've since upgraded to windows10 and now I can't hit the unraid box through SMB at all. I could still hit it via http. \\tower System error 5 has occurred. Access is denied. C:\Users\Solomon>net use * \\tower\videos System error 1240 has occurred. The account is not authorized to log in from this station. Any ideas how to get me back up ? Thanks, Solomon
  10. Hello, It would be nice to get some running specs of this server. I have a custom unraid box but it's a bit slow and draws too many Watt's. What's the draw on the atom box and what kind of copy numbers and parity check numbers are expected ? Thanks ! Solomon