BrunoX

Members
  • Posts

    5
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

BrunoX's Achievements

Noob

Noob (1/14)

0

Reputation

  1. My problem is that my card (460) isn't detected at all with the latest drivers which results in Folding@Home only using the CPU.
  2. Thanks, that's good to know. Although I'm more interested in getting it to work for Folding@Home which I believe doesn't utilize NVENC/NVDEC - could be wrong though.
  3. I thought so as well but as Diondk said, the problem is that none of the older Nvidia Unraid versions have a Nvidia driver before version 400.
  4. Is there a way to downgrade the driver version? I have an older Nvidia card (GTX 460) and the latest driver (440.59) doesn't support it, however, Linux driver 390.132 from Nvidia does.
  5. I've been struggling since I got Unraid to find an answer as to why I haven't been able to connect to my Unraid server via SMB version 2.0 and above on Windows 10. I went through many threads here in the forum and a few more places, other than having SMB 1.0 activated, none of the solutions I could find worked. Until now... I'm sharing my solution in case this might help others in a similar situation. This is meant for people that haven't managed to get any of the other solutions working for SMB 2.0 and above. The main points of my situation were: SMB 1.0 activated - access worked immediately SMB 1.0 deactivated - Windows prompted a network error saying 'Windows cannot access ________' or 'Network path not found' when I tried accessing my shares Neither connecting to hostname (e.g. \\tower) nor IP address ( e.g. \\192.168.x.x) worked However sending a PING through CMD/Powershell to both the hostname ( \\tower) and IP address ( \\192.168.x.x) received a reply from the server Enabling insecure guest logons solution in this thread did not solve my issue: If the points above match your situation then follow my solution below. If your situation differ from above, e.g. ping doesn't generate a reply, your issue might be caused by something else. Instructions: TL;DR: For some reason Workstation service was stopped when SMB 1.0 was disabled. If Workstation service is stopped, try turning it on, if it runs = problem solved. If error 1075 pops up, delete keys "DependOnService" and "DependOnGroup" under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation then reboot. Now start Workstation service, done. If you haven't already, uncheck everything related to SMB 1.0/CIFS File Sharing Support to disable SMB 1.0. You can find it under: Control panel -> Programs -> Turn Windows features on or off. Press OK when done and reboot if necessary. Open Windows Start menu and search for Services and click on it. Alternatively, press Windows key + R and enter services.msc to open it. In the Services window that opened find a service called: Workstation - This is the Windows service that handles the SMB protocol communication Right click on it and open Properties. Check the Service Status, does the status say Stopped? Good. (However, if it does say Running and you still cannot access your shares on Windows via SMB versions above 1.0 unfortunately this solution won't work for you.) Now try starting the service clicking on the Start button. This did not work for me, I received an error that said: Continue to the next step if you received this error as well. If it actually started for you then great you're done, make sure Startup type is set to Automatic and click on Apply and OK. This should now allow you to establish SMB connection and access your shares. 5. Open up the Registry Editor either through the Start menu by searching for Registry Editor or press Windows key + R and enter regedit. Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation Select LanmanWorkstation and on the right side you should see several keys. Look for two keys called DependOnService and DependOnGroup. I only had one of them, DependOnService. - Before you do any changes here export the LanmanWorkstation registry file as a backup, just in case something goes wrong. Delete only the two keys (or the one you have) mentioned above, after that reboot your computer. Finally, go back into Services and start the Workstation service which should now start successfully. Confirm that the Service Status says Running and Startup type is set to Automatic, hit apply and OK if needed. That's it. You should now be able to establish SMB connection and access your shares with a more secure version of the SMB protocol. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- I have confirmed that SMB is using a higher version than 1.0 between my PC and Unraid. I used the following command in Powershell (run as admin): Get-SmbConnection The output gives you information about connections to shares: ServerName ShareName UserName Credential Dialect NumOpens ---------- --------- -------- ---------- ------- -------- tower Documents PC\BrunoX MicrosoftAccount\user 3.1.1 1 Dialect equals SMB version.