Bug 378988

Jim: Could you please take care of this bug?

Created attachment 207616 [details]
Please View only in KsystemLog

If ever there was a need for a 'default' button it is in the 'Expert Global Settings' as current defaults do NOT permit a MS Workgroup to view the Linux Network by any means either with or without a NetBIOS layer bound to native TCP V4. Current Defaults may permit a Windows Domain to access the Linux Network but this is not the case as above for a workgroup where there is no authentication source from the MS Windows Side

Other thoughts:
What functionality is gained from only assigning a MS-workgroup OR MS-Domain to a Suse PC????
Is this functionality not created by just creating a Samba Server????
Sorry not clear why there is a need to only create a MS-WorkGroup OR Domain Membership without creating a Samba Server.
If a Samba Server is established and nominates a WorkGroup OR Domain membership what is gained or conflicts by also creating membership only via Windows Domain Membership.
Sorry to ask the obvious????

Are you reporting a bug, or asking for discussions on these items?  I'm sorry, it's not clear to me from the previous comments.

On #4, "windows domain membership" and a samba server can both be created.  The domains for each must be the same, though.  Perhaps your machine would be a member server in a domain, and you want users to logon through their domain credentials.  

On the original comment, I'm not sure what your actual problem is, so could you be more specific about what symptoms you're having besides messages in the log.  Also, could you attach the samba logs themselves instead of the ksystemlog which appears to be one very large line.  See http://en.opensuse.org/Bugs/Samba for more details.

Yes, this is a bug, however there more I watch what establishing a Samba Server does, the more the process becomes confused.

1. Once a Samba Server is created, instead, of requesting an election between itself and the other Windows Workgroup members -It demands that the samba server IS the Master Browser - I can find no logic in this demand.

I can also find no logic in YAST of Both creating a Samba Server, which established the workgroup (same as other Windows PC's), to the other functionality in Yast which solely joins a Linux PC to a Workgroup or Domain.

I can also find no logic in the 2 x different yast services which both establish the same workgroup or domain - The only difference in one (Join a Domain or Workgroup) is that a Samba Server is not started.

Again I find no logic in this sole function as it is duplicated in starting a Samba Server. 

What logic is there in Yast for a Linux PC Soley Joining a Workgroups or Domain when at all times this achieves nothing but to complicate the issue and with both function permits even more possible discrepancies between adhering to the same workgroups name of domain name. 

The log which is attached IS the Samba Log, however to ease you viewing of the log it can we formatted nicely for inspection by Ksystem Log.

On the original bug description:
What functionality is not working?  Simply having elections is a normal part of the process.  Depending on the role and OS version/level, windows PC's have an election process, so just seeing messages about being a master browser or not is normal.  Is something actually not working, or crashing, or stopping?

On the multiple yast views of the same domain info:
This is a design issue, and it is currently being reevaluated, but it is not a matter of broken function, so it would not be changed as part of a bugzilla report.  However, addressing your comment #4, there is a situation in which you would only have a domain membership set and yet have a samba server (including no need to have it packaged).  I'm not defending the multiple views, simply answering in what situation it would be used.

On the ksystem log:
Perhaps it's the way it's been attached/detached to bugzilla, but even looking with ksystem, it's still only 7 lines, each of which runs on with many lines of actual log.

The query relates to a combination of both the demand that the Samba Server,not the normal process of election, needs to become the Master Browser amongst a Group Of MS PC's. Why does the Samba Server assume further responsibilities that it does not need as a translation tool between MS and Linux that the Workroups PC's now are subservient to in their own browsing functions

With respect to multiple YAST tools, You will find that IF you both Start A Samba Server, and then Join say a Workgroup, of the same name, via this access this circumvents the default sharing, in respect to write issues, if the Linux Directory structure, as a Login ID is now required from a Workgroups PC to write anything to Samba by way of printer or file access - By also joining a workgroup pay particular attention to the options that should NOT inherently cause, but do issues of Login and Write access.

Re- Assigning as Fixed Later to see what comes of the changes indicated in #7.
Re- Assigning as Fixed Later as reporter re-assess the bug title and cloned status and lack of accuracy of reply in #6 #7 

Because the LATER and REMIND resolutions have been removed, the resolution of this bug has changed from LATER to WONTFIX. If this bug needs to be reconsidered, reopen it and set a future "Target Milestone for Fix."