Jump to content

fl0at

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About fl0at

  • Rank
    Member
  1. Going to mark as solved, but here is solution. Joining Domain not sufficient, here. Have to also add a host entry to the AD through DNS manager. So for me, in WS2016, I went to DNS, Forward Lookup, selected Domain, then right clicked in space to bring up context menu. Then add host Name: DROP FQDN: DROP.KH.LOCAL IP: Static IP as set in Unraid Add host, then can navigate to shares.
  2. I'm on trial, trying to get this thing to meet my needs because I really want to use this as my NAS. But I'm running into some pretty basic configuration issues. Everything from small things like TLD not being honored in Network Settings, to the biggest thing, which is that I cannot access user shares over SMB, when domain joined. Here are my steps: Client PC: Windows 10, 1803 AD/DC: Windows Server 2016 Domain: KH.LOCAL Unraid: Networking Settings DNS points to AD/DC. Unraid Server Name (Settings -> Identification): DROP.KH.LOCAL SMB (Settings - > SMB) set to Yes, Active Directory Join AD using a domain admin (also the account testing from the client PC) I can verify I've joined by going inside Active Directory Users and Computers in the AD/DC, and see that the Unraid server is listed. I can go in terminal and ping: KH.LOCAL and get a response, or any other computer on the domain, and get a response. I can also ping other computers on the domain just by computer name, without needing FQDN. I can ping DROP which resolves to the right IP. I can ping DROP.KH.LOCAL which resolves to 127.0.0.1 I cannot ping DROP.KH.LOCAL, from anywhere else, though. Or DROP. Or drop. Or drop.kh.local. I cannot access the web ui over drop.kh.local, either. But, I continue along, anyway. I start the array, and add a share, Test. The only thing I set is the name. I then click on it and see that export is Yes, and security is public. Now, at this point, when SMB is using workgroups, under SMB column on Shares, it'll show "Public" or whatever the permissions is. Here, I get "-" I stop the array and reboot. Just in case. I come back in, I verify still domain joined. Can still ping from Unraid to the ad/dc, and other computers on the network. I then try to using File Explorer to open address \\drop\ or \\DROP\ or \\drop\Test or \\DROP\Test or \\drop.kh.local\ or \\Drop.kh.local, nothing works. Anyone got AD working that can give me a hand?
  3. Reproduce: Management -> Settings -> SMB -> Enable: Yes (Active Directory) -> Apply Scroll to Active Directory Settings. Join domain. RDP to AD/DC Server. If using Windows Server, run Active Directory Users and Computers (dsa.msc), select Computers, refresh and see that Unraid server is in domain joined. Return to Unraid Management -> Settings -> SMB -> Active Directory Settings -> enter domain admin password and click Leave. Page will refresh showing still joined. Return to Windows -> Active Directory Users and Computers. Refresh. Notice Unraid server is no longer in the list. Unraid server is now not domain joined, but shows as joined, until system is rebooted. Upon reboot, will show as not joined, and can now join a domain. No dockers, plugins or anything installed.
  4. To reproduce: Management UI -> Settings -> FTP Server Set FTP server: Disabled then Apply. Status in top right should show Status: Stopped Click Dashboard then Reboot icon. Proceed. Once back up, Settings -> FTP Server, Status: Running System: Just upgraded to 6.7.0 from 6.6.6. Still in trial (28 days remaining...), active directory joined, no dockers, plugins, and one user share created. That is as far as I've gotten, except to disable FTP and then reboot due to the ugprade...
  5. Yes, 6.6.6 is working for me now. I have a bad USB port on the desktop I'm using to write to the stick. Switching ports on the write side seems to have solved it. The FSCK*.rec on the boot drive were from me hard shutting down, or maybe shutdown -h now. Have to check shutdown -h now when I get home, cause that is how I killed it last night. But I'll clean install again before I register the key. Thanks again.
  6. Using USB creator with stable and letting it download and put on seems to fire up just fine, so I'm just going to assume something screwy with writing the stick happened, and marked this as solved. Thanks for the help @trurl
  7. Tried another port. Tried another drive. Then I tried another version. Version 6.6.5 works fine. Version 6.5.3 works fine. Across both USB sticks, and any plugged in port. Version 6.6.6, which hashes exactly as shown on the download page does not work in either USB stick, in any port. I think it is bugged for fresh installs.
  8. Which line/lines in syslog are you basing that off of, out of curiosity?
  9. New to unRaid. Figured I would try the trial. I downloaded the ZIP, and tried the manual (legacy) make boot batch file inside Win 10. But that didn't work (UEFI). So I downloaded the Unraid USB Creator, and used local zip. Worked great. Booted into unRaid, GUI, and used default user: root. I hit the LIME icon for start menu, and went to "unRAID Web Interface." Showed "Unable to connect." I went to tty1 and showed that I had an IP from my net. I logged into dd-wrt admin and showed that TOWER was DHCP'd the same IP. I went into WIN 10 and attempted to load HTTP and HTTPS on that IP. And on HTTP and HTTPS://TOWER/ (though not everyone allows NetBIOS but whatever). No joy. Additionally, I'm posting this message from FireFox running inside the Web GUI. So definitely got internet access. How do I access the Web Interface? unRAID seems like it would be a good fit for my needs... but not off to a great selling start.