- removed issue_posted
Samba shares with default security mode are not found
Issue #6
resolved
Samba shares on server configured with default (user) security mode are not found by the T3. When Samba security is left at the default setting or specified as security = user, the T3 will not find any CIFS shares on that server. Switching Samba config to use "security = share" will work with T3.
The T3 CIFS client should work with servers configured for both user and share security mode to be compatible with the widest possible selection of servers. Existing Beyonwiz products work with "security = user", so T3 should as well.
Reproduction steps
-
Set up a Linux system running Samba 3.6.x
- Configure the Linux Samba server similar to this:
root@server: cat /etc/samba/smb.conf [global] workgroup = WORKGROUP read only = yes security = user guest ok = yes
[Pictures] path = /home/peteru/Pictures
-
On the T3:
- Setup / Network / Network Browser will show the host, but when it is expanded the share is not there.
-
Switching the Linux Samba server config to use "security = share" will work with T3.
- Reconfigure the Linux Samba server similar to this (security option has been changed):
root@server: cat /etc/samba/smb.conf [global] workgroup = WORKGROUP read only = yes security = share guest ok = yes
[Pictures] path = /home/peteru/Pictures
-
On the T3:
- Setup / Network / Network Browser will show the host and when it is expanded the share is now visible.
Comments (14)
-
-
reporter
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from New to Testing.
-
reporter
- removed issue_status
This is still broken. I'm updating the steps to reproduce to be even more specific about how to test this.
The issue was updated with the following change(s):
- The status has been updated, from Testing to Not Fixed.
-
reporter
- removed issue_update
- removed issue_reproducability
The issue was updated with the following change(s):
- This issue's reproduction steps has been changed
- This issue's description has been changed
-
reporter
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from Not Fixed to Delegated.
-
reporter
- removed issue_priority
The issue was updated with the following change(s):
- The priority has been updated, from Normal to High.
-
reporter
- removed issue_priority
The issue was updated with the following change(s):
- The priority has been updated, from High to Critical.
-
reporter
- removed issue_severity
The issue was updated with the following change(s):
- The severity has been updated, from Normal to Major.
-
Account Deleted
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from Delegated to Testing.
-
reporter
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from Testing to Not Fixed.
-
- removed issue_depends
Bug report 157 now depends on the solution of this Bug report
-
Also worth noting when this occurs the whole UI is locked up for many many minutes. No Cancel, Mute, Volume or Power control possible.
At no time should the UI ever be unresponsive. All tasks that may take some time to complete should be able to be cancelled (or backgrounded if applicable)
See ticket
#157for further details. -
reporter
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from Not Fixed to Testing.
-
reporter
- removed issue_resolution
- removed issue_percent
- removed issue_close
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from Testing to Closed.
- This issue has been closed
- This issue's progression has been updated to 100 percent completed.
- The resolution has been updated, from Not determined to Fixed.
- Log in to comment
The issue was updated with the following change(s):