December 4, 20178 yr Upgraded this morning; for now, I left C-State disabled... waiting for the next BIOS update.
December 4, 20178 yr On 12/2/2017 at 2:39 AM, johnnie.black said: Have you ever disabled any SMB2/3 related settings in Windows? Latest Samba disables NTLMv1 login by default, check if all your Windows SMB settings are default. Curious, is SMB v1.x disabled by default under unRAID now?
December 4, 20178 yr 4 hours ago, luisv said: Upgraded this morning; for now, I left C-State disabled... waiting for the next BIOS update. I got similar specs to you when it comes to hardware, yet my system kept crashing a couple of times everyday even with the c-state disabled and the ram at stock, is your system running smooth?
December 4, 20178 yr 11 hours ago, johnnie.black said: You don't need SMB1, unRAID defaults to SMB3, try again after starting unRAID in safe mode, if still unable to connect the problem is likely on the Windows side, a new Windows install using default settings should work without issues, try with another computer or borrow a friend's laptop. Running in safe more. Still no dice.
December 4, 20178 yr 11 hours ago, FredG89 said: Like I said in a previous post. I already made sure that SMB1 was enabled. I doubt the issue is SMB support on the client OS. A few suggested tests: 1) Make sure the SMB port is accessible from the Windows machine: "telnet 10.10.1.15 445". 2) Make sure the UnRAID server has not disconnected from the Domain (if domain joined). I find that my server disconnects from AD every so often and I need to rejoin it to get things working again. 3) Try connecting to a specific share rather than browsing the machine (i.e. \\10.10.1.15\share). 4) Try the simplest case- create a new user under unraid and new share and try and access it. 5) Try from a different client machine. 6) Create a VM on Unraid running another Linux distro that supports SMB and see if the Windows machine can access it. Hope one of them helps.
December 4, 20178 yr 45 minutes ago, ssb201 said: I doubt the issue is SMB support on the client OS. A few suggested tests: 1) Make sure the SMB port is accessible from the Windows machine: "telnet 10.10.1.15 445". 2) Make sure the UnRAID server has not disconnected from the Domain (if domain joined). I find that my server disconnects from AD every so often and I need to rejoin it to get things working again. 3) Try connecting to a specific share rather than browsing the machine (i.e. \\10.10.1.15\share). 4) Try the simplest case- create a new user under unraid and new share and try and access it. 5) Try from a different client machine. 6) Create a VM on Unraid running another Linux distro that supports SMB and see if the Windows machine can access it. Hope one of them helps. I tried to telnet on 445 and it didn't give a success response 1. Does not connect 2. Unraid Was never joined to a Domain 3. Connecting to a specific share does not work 4. I don't think this is going to work as I can't get to the root share 5. This works from Ubuntu and macOS (Linux and Unix) 6. I don't really have the room to spin up a VM Edited December 4, 20178 yr by FredG89
December 4, 20178 yr 25 minutes ago, FredG89 said: Do not specify a user name. You are just trying to see if you can establish a TCP connection to the port. It should go to a blank screen and ignore anything you type if the connection is established. Use CTRL-] to terminate the connection. Assuming that works you can eliminate firewalls or any other issues with network connectivity. You may also get a little more information about the error if you try to connect via command line. net use \\10.10.1.15\share /u:username You can also see "net use" and delete any existing connections in case they are screwing it up "net use * /del" Edited December 4, 20178 yr by ssb201
December 4, 20178 yr 5 minutes ago, ssb201 said: Do not specify a user name. You are just trying to see if you can establish a TCP connection to the port. It should go to a blank screen and ignore anything you type if the connection is established. Use CTRL-] to terminate the connection. Assuming that works you can eliminate firewalls or any other issues with network connectivity. You may also get a little more information about the error if you try to connect via command line. net use \\10.10.1.15\share /u:username You can also see delete any existing connections in case they are screwing it up: net use * /del O ok. In that case it works, goes to a blank screen. Got you. I did receive information on the issue and it appears that Windows is trying to beef up security. Here is the fix. https://support.microsoft.com/en-us/help/4046019/guest-access-smb2-disabled-by-default-in-windows-10-server-2016 Edited December 4, 20178 yr by FredG89
December 5, 20178 yr On 11/28/2017 at 5:57 PM, tgggd86 said: Upgraded from 6.3.5 to 6.4.0-rc14. Uptime for 48 hours so far no issues. Running a Ryzen 1700 build. Will plan on undoing all the "fixes" needed to get Ryzen to run once I determine there's no overall stability issues. Will report back if all the Ryzen issues end up being resolved. Been running now for a week. Upgraded the BIOS for my GA-AX370-Gaming 5 MOBO w/ Ryzen 7 1700. Put all mobo settings at defaults (c-states enabled) and it crashed just like before. Is this a for sure an AMD issue? Been running another ryzen system on Win10 and Ubuntu 17.10 with zero stability issues.
December 5, 20178 yr Author 4 hours ago, tgggd86 said: Been running now for a week. Upgraded the BIOS for my GA-AX370-Gaming 5 MOBO w/ Ryzen 7 1700. Put all mobo settings at defaults (c-states enabled) and it crashed just like before. Is this a for sure an AMD issue? Been running another ryzen system on Win10 and Ubuntu 17.10 with zero stability issues. Yes this is an AMD issue which they will fix with a bios update (if they can). See here: https://bugzilla.kernel.org/show_bug.cgi?id=196683 Maybe your server never goes idle long enough for bug to manifest?
Archived
This topic is now archived and is closed to further replies.