Hi all,

 

I have an Unraid server which I use to hold backups of my VMs and Windows machines in my home network/lab. Everything was working fine until I decided to make some network changes today and now, even though I have reversed all the changes, none of my Windows machines can see the Unraid shares.

I was trying to put a firewall between my cable modem and my network switch which involved giving my new firewall the modem gateway IP and changing the modem IP to a new one. Multiple modem and firewall reboots and IP changes later, I gave up and put everything back as it was before I started. No changes were made to Unraid at all. Now, whenever I try to view my shares from a Windows device, I get this...

 

<IP> is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

 

We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organisations network and try again. If you previously signed in on this device with another credential, you can sign in with that credential.

 

Things I've tried...

• Removing the Unraid server from the domain, making sure it's computer account was removed and adding it back to the domain.
• Rebooting domain controllers
• Rebooting Unraid
• Ensuring my account (Domain Admin) is not locked out
• Mapping to other Windows shares which seems to prove the domain is OK.

 

I've attached my diagnostics here.

unraid-diagnostics-20231129-1415.zip

 

Would appreciate any help you can give as I'm out of ideas now.

 

Many Thanks

 

Paul

Just remembered, I DID make a change to Unraid this morning. I updated to version 6.12.5. 

I'll start looking to see if I can go back a version and see if that fixes it.

Downgraded to 6.12.4 and the problem remains 😪
 

At least it looks like it wasn't the update then.

I looked at your Diagnostics file and you  have a static IP address of    192.168.0.110   assigned to your Unraid server.  You also have some type of bonding set up on your two NIC's.    (You probably need to have your server assigned to the same subnet as your SMB clients.) 

 

Do you have access to the server via the GUI?

Hi,

 

Thanks for replying.

 

That is the correct IP for the Unraid server - my whole network is 192.168.0.0/24 so everything is in that subnet. Also yes, I have bonding on my NICs and my switch is configured the same.

 

I can access the Unraid GUI and it seems to be working fine. I can also SSH to Unraid from other Linux boxes.

 

Everything was working up until this morning, before I updated AND messed about with my gateway.

I reread your first post and it appears that you are using an AD setup.  There is a sub-forum devoted to this topic.  (Many/Most of us are using Peer-to-Peer SMB networking and AD is so much more complex to setup that we can't really help much.  Hopefully, the folks who are GURUs in getting things to work under AD will be monitoring that forum.)

 

    https://forums.unraid.net/forum/102-active-directory/

 

 

Well, I have it working now, but it's weird.

Today I decided in desperation to turn off SMB on the shares, turn off SMB in settings and reboot. Then turn on SMB in settings again and re-enable SMB on the shares - and it all started working again.

 

Curious, I then decided to upgrade to 6.12.5 again, which again broke my shares.

Downgraded back to 6.12.4 - still broken. Repeated fix from above - now working.

So, I think the problem may be in 6.12.5. 

Samba was upgraded from 4.17.10 to 4.17.12 between those two versions of Unraid.  So there is a possibility that sometime has been changed in Samba that impacts your setup. 

 

You might want to posted up here:

 

     https://forums.unraid.net/bug-reports/stable-releases/

 

 

Thanks for that info.

 

I will do a little more investigation first (i'd like to try and only update the samba package to prove that's the issue), but it will have to wait until next week as my monthly parity check has started and I don't want to start/stop the array while that's running.