Down the SMB rabbit hole again
Ohhhhhhh… The bookmark “display name” goes in the “display name” field, not in the password field. Forehead slap! With that sorted out, new MiX to MiX SMB bookmarks can be created like so:
Add storage > LAN (Samba) > search local* > select > append port and enter credentials > Save.
Those worked for connecting from Android with MiX as client but not for PCs. Here are some observations.
- In the “search local” results PCs and linux boxes with SMB shares are visible at the top of the list preceded by special character, and displaying the DNS name and IP address, and with customary SMB port 445 already appended.
- One exception to the previous is that, while creating a MiX SMB bookmark to a MiX SMB server running on the same device, then the “search local” results also include that MiX server on the same device in the top section with name and IP and port (not necessarily 445).
- Where there is any dependency on DNS and DHCP there is potential irregularity.
- In the “search local” results the target server in this test is listed as unknown and does not include port, but it worked after appending port as described above. This occurs even if the customary port 445 is set for the server.
- As to PCs, enabling the Windows 10 SMB client component did not help nor did I expect it to since it is not needed for any other devices. While doing some research I did find some cases where LAN Manager authentication level settings had an impact on SMB access.
General details:
https://learn.microsoft.com/en-us/w...trict-ntlm-ntlm-authentication-in-this-domain
NTLMv1 NTLMv2
https://www.truenas.com/community/threads/smb-problem-on-win-10-client-fn11-rc.54316/
I wonder if MiXplorer is using that older protocol which in turn could be the limitation for PCs but I’ve got too many good SMB connections on my network to fiddle with those particular policy settings without confirmation from hootanparsa that they are needed.
That all being said, I forget, what was it that a MiX SMB server is supposed to do that cannot already be done other ways.
Ohhhhhhh… The bookmark “display name” goes in the “display name” field, not in the password field. Forehead slap! With that sorted out, new MiX to MiX SMB bookmarks can be created like so:
Add storage > LAN (Samba) > search local* > select > append port and enter credentials > Save.
Those worked for connecting from Android with MiX as client but not for PCs. Here are some observations.
- In the “search local” results PCs and linux boxes with SMB shares are visible at the top of the list preceded by special character, and displaying the DNS name and IP address, and with customary SMB port 445 already appended.
- One exception to the previous is that, while creating a MiX SMB bookmark to a MiX SMB server running on the same device, then the “search local” results also include that MiX server on the same device in the top section with name and IP and port (not necessarily 445).
- Where there is any dependency on DNS and DHCP there is potential irregularity.
- In the “search local” results the target server in this test is listed as unknown and does not include port, but it worked after appending port as described above. This occurs even if the customary port 445 is set for the server.
- As to PCs, enabling the Windows 10 SMB client component did not help nor did I expect it to since it is not needed for any other devices. While doing some research I did find some cases where LAN Manager authentication level settings had an impact on SMB access.
General details:
https://learn.microsoft.com/en-us/w...trict-ntlm-ntlm-authentication-in-this-domain
NTLMv1 NTLMv2
https://www.truenas.com/community/threads/smb-problem-on-win-10-client-fn11-rc.54316/
I wonder if MiXplorer is using that older protocol which in turn could be the limitation for PCs but I’ve got too many good SMB connections on my network to fiddle with those particular policy settings without confirmation from hootanparsa that they are needed.
That all being said, I forget, what was it that a MiX SMB server is supposed to do that cannot already be done other ways.