[Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array]

3 hours ago, dlandon said:

Ok.  Here's the deal.  Using sec=ntlm is no longer supported because it has been removed from the Linux Kernel:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=76a3c92ec9e0668e4cd0e9ff1782eb68f61a179c

 

I removed the sec=ntlm when mounting SMB 1.0 because it generated an error.  The error you are seeing now is because the Epson printer only supports ntlm and Unraid doesn't.  There's nothing I can do to get around this.

No worries, all is good. Thanks for trying though. 

[Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array]

7 minutes ago, dlandon said:

Try using the IP address instead of the server name.

The printer has the latest firmware and I believe it only uses SMB 1.0. 

 

I tried to mount the share using the IP address, but I am getting the same error. I guess unraid is trying to get rid of devices that use SMB 1.0. 

[Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array]

On 6/18/2022 at 6:22 PM, dlandon said:

Fixed in the next release.

I updated the plugin to 2022.06.19 but I'm still getting errors unfortunately. Here's what I tried so far:

1. Restarted the unraid server and reinstalled the plugin

2. Changed the password (I'm using a very simple password)

3. Disabled authentication

Any other suggestion I can do to check on my end? Thank you.

 

tower-diagnostics-20220621-1754.zip

[Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array]

10 minutes ago, dlandon said:

Fixed in the next release.

Thank you for your hard work! 

[Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array]

35 minutes ago, dlandon said:

I have a server that I can force to be SMB 1.0 only and I can reprodice your issue.  Let me spend some time looking into the issue.  It looks like samba made some additional security changes to SMB 1.0.

Thanks for looking into this. I can confirm that it successfully mount my share on 6.9.2 but not on the new unraid OS 6.10.x. I was thinking that this issue might be tied to the new unraid OS.  

tower-diagnostics-20220618-1811.zip

[Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array]

11 hours ago, dlandon said:

 

The remote mount is failing when trying to use SMB 2.0:

Jun 17 21:04:01 Tower unassigned.devices: Mount SMB command: /sbin/mount -t 'cifs' -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=2.0,credentials='/tmp/unassigned.devices/credentials_memorycard' '//EPSON3640/memorycard' '/mnt/remotes/EPSON3640_memorycard'
Jun 17 21:04:01 Tower kernel: CIFS: Attempting to mount \\EPSON3640\memorycard
Jun 17 21:04:01 Tower kernel: CIFS: Status code returned 0xc000000d STATUS_INVALID_PARAMETER

 

When this fails, UD will attempt to use SMB v1.0 to mount the remote share, which is what you have shown in the log snippet.  I'm not sure what the STATUS_INVALID_PARAMETER is referring to, but it may be your credentials on the remote server.  I would change the credentials on the remote server and then re-do the UD remote share to match.  Try to not use any special characters.

The share that I was trying to mount uses SMB 1.0 (NetBIOS is enabled on my SMB setting).

I changed the credentials of the share and also tried without any credentials but still unable to mount it and got the same error. 

[Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array]

I updated my Unraid OS to 6.10.3 from 6.9.2 but I am unable to mount a smb share. It was mounting the share just fine on 6.9.2 but not on the new OS 6.10.3. I double checked the settings and everything is the same. Is there anything I can check on my end to help solve this issue? Thank you.

tower-diagnostics-20220617-2107.zip