If so, why would changing protocols in the share configs make a difference to shares you cannot connect to from Zidoo? You've not said what if any error messages show up on the Zidoo for failed connections, e.g. Is there any possibility to activate the smb logs on OMV? So I see, if the Zidoo can at least contact the server and is rejected? I didn't find any log files on the Zidoo side.įeBo2 I'm puzzled because the screenshot in your first post appears to show Zidoo Z9X connecting to some SMB/CIFS shares on OMV6 using SMB2. I now followed again the instructions here …etting_up_a_shared_folder and the following chapter, but that's, what I already have.
#Samba server android windows 10#
The only info I could find is, that Windows 10 seems to use SMB3_11, but the Zidoo seems to use the SMB2_02. Kodi or directly from Windows, using "\\my-server" in Windows Explorer or in the Network Devices section of the Windows Explorer, I can still access them. The message is always, that the server is unavailable. The strange thing is, since upgrading to OMV 5, I can access the already configured smb shares with my Zidoo, but I cannot add the new and I cannot newly add one of the earlier existing smb shares. The smb shares were accessible with OMV3 / 4 with my Zidoo Z9X android media player.
In OMV5 I added two new smb shares in OMV. I setup OMV samba shares with OMV3 or 4 and upgraded to OMV5.
0 kommentar(er)
