Thema: CIFS to Win10

Hi, I have just bought a ZGemma H7 box, and upgraded to OpenATV 6.4. It came with OpenATV 6.1 but the problem I am going to describe also applied to that.

I am trying to set up a CIFS connection to a Windows Network Share. All the stuff on the Windows side (NetBIOS, enabling SMB1.0 - which I know to be dangerous, setting up the share, allowing File Sharing, the firewall settings, Everyone as RW access to the share, etc.) has all been set correctly. I know because I have several Windows and Linux boxes pointing to the share, all working without problem.

But when I try to create a CIFS share under Enigma 2: first browse the Network Neighbourhood, save the username and password, and then enable the share, only gets me so far. I get the green dot showing me the share has been recognized (in Network Neighbourhood), but when I try to browse the folder, I get redirected all the time to "Parent Folder", and there appears (wrongly) to be no files in the share. I'm looking at /mnt/autofs/SHARENAME (which Enigma 2 creates as a combination of the [notional] server and share). I've tried this with more than one Windows box (i.e. as the target for the shares).

I've tried fiddling with different combinations - fstab, vers=2.0 (for SMB2.0), even (which I think is wrong), adding to the option set domain=WORKGROUP, all without success.

I should add, I've tried multiple deep restarts. Also, SAMBA/CIFS are enabled on the ZGemma box.

Can anyone please shed light on this crazy situation?

All three topics describe the rules on E2 side. The rest is within windows with firewall and security software.

1. Freischaltung Telnet / FTP / SSH // Enable Telnet / FTP / SSH

2. Mounten einer Freigabe eines Netzwerk-Teilnehmers

3. Beachten beim Einbinden von Shares im Freigabe-Manager

Add.:
"rw,utf8,vers=2.0" must be used to connect to new Win versions.

The user granted the access for using the share connection also has the right to access the file system content behind?
Which version of Win10 (more or less options in the networking between Home and Professional available)?

Thank you very much. Your help is much appreciated. Please see text at bottom IN UPPERCASE FIRST!

Answering your points:
1 (SSH, etc) was enabled.
2 I assume you mean browse the Network, add the username and password, and then enable the connection?
3 When enabling the connection, check that the vers=2.0 (for SMB2.0) is included in the option string. I can confirm all this has been done, and yet no ability to see files in the network shares!

Other points: "Everyone" has access on Windows when setting the (Advanced) share should deal with that - permissions are set when setting up the share. It is W10 and I am sadly very much aware that SMB1.0 is disabled by default; I have SMB1.0 still available on Windows box for other legacy kit.

JUST NOTICED (SERVER LOGS ONE OUT QUICKLY!), THE INSTRUCTIONS WERE LINKS. I WILL READ UP ON THESE LINKS NOW!

Hmmm. Maybe "Everyone" is not the best way in a network, even if it is personal internal use. There might be a benefit using a defined user and password (ex.: paul with 1234 for testing). That user must have permission on the pc with a local profile too, to optain right behaviour, i think. I have the user "root" oder "MyUser" in my systems in use, and everywhere access. There is no permission "Everyone" granted in any case, and the guest is deactivated / blocked.
The only corrections i made to my PC systems was to reactivate the adminstrative share. My users have the permission to use those, too. Not the savest way, but without port forwarding minimal calculated risk of my own.

You're welcome, and thanks for teh feedback.
So just a small mistake made the system not running as expected.
Have a nice day and time here.