Bug 193638

I suppose this is not a problem with YaST but with Samba.
Please provide some more information (commands, (error)messages, logs).

Samba functions very well. Only when restricted by user controls does it fail.
When file permissions are set to secure the work group is displayed but you are unable to expand the work group. When file permissions are set to easy the group expands to revile all printers.

Do the samba logs (/var/log/samba/*) contain any relevant entries (like "permission denied")?

You can also try to find out which entry in /etc/permissions.secure causes the problem by comparing it with /etc/permissions.easy and/or manually applying the permission changes with chown and chmod (will be reset by next SuSEconfig run!).

Reassigning to the Samba maintainers for help.

Scott: About which 'file permissions' are you talking?

Scott: You use /etc/sysconfig/security:PERMISSION_SECURITY="secure"?

Even if set this we're able to get the list of printers.  At least with CUPS.  In this case we use libcups and no external binary.

Please provide the output of:
testparm -s --parameter-name 'printing' 2>/dev/null

Sorry for delay

I am using the YAST>Security and Users>Local Security

Output from Linux system follows

couston@scott:~> su
Password:
scott:/home/couston # testparm -s --parameter-name 'printing' 2>/dev/null
cups
scott:/home/couston #

End output

The problem with not being able to expand workstation printers occurs on MS-Windows when you change the YAST>Security and Users>Local Security...I can get a screen shot before and after if you like??? from a Networked MS Windows PC...give me a day or so.

If you select "Network Server" and view Details the file permissions are set to "secure" and help suggests this a a good think to have in place anyway.

The following Help is available in YAST>Security and Users>Local Security.
Quote

Other Security Settings
In this dialog, change miscellaneous settings related to local security.
File Permissions: Settings for the permissions of certain system files are set according to the data in /etc/permissions.secure or /etc/permissions.easy. Which file is used depends on this selection. Launching SuSEconfig sets these permissions according to /etc/permissions.*. This fixes files with incorrect permissions, whether this occurred accidentally or by intruders.
With Easy, most of the system files that are only readable by root in Secure are modified so other users can also read these files. Using Secure, certain system files, such as /var/log/messages, can only be viewed by the user root. Some programs can only be launched by root or by daemons, not by ordinary users. The most secure setting is Paranoid. With it, you must decide which users are able to run X applications and setuid programs.

Unquote

Additional info was provided on 3rd of August f this ear yet still no change in need info part. Bug has been altered now to new and re opened. If you require still more info. Please ask. I had not heard from you and accepted the need into I supplied was sufficient - however this is not the case. I have not been asked to provide more information happily

Kind Regards Scott

Scott, it's your job to tick the box "This comment provides the needed information.  Change the status of this bug back to ASSIGNED." once you have given the information.  The developer still waits for that acknowledgement and therefore has not reacted.

I'll tick the box now for you and ask you to do so next time yourself.

Closing NOREPSONSE, due to missing information. Please retest on openSUSE   
11.0 and create a new bug report if the problem still persists.

????? This has major issues with without fix. To be able to use this function, it put single click at odds and for those users the should run of dingle click