Bug 150200 - SAMBA Client config tool reports XP computer--NOT WORKGROUP(s) in neighborhood.
Summary: SAMBA Client config tool reports XP computer--NOT WORKGROUP(s) in neighborhood.
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-12 00:09 UTC by Thomas Brightman
Modified: 2006-02-21 12:22 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Brightman 2006-02-12 00:09:09 UTC 
When configuring wireless node in a Workgroup, the YaST Samba client tool reports another workgroup node in what should be the list of detected workgroups.  The actual workgroup is NOT reported.

The network is wireless with ESSID=69lr and the workgroup name=69lr.
Comment 1 Michael Gross 2006-02-13 11:54:17 UTC 
Please attach the YaST logfiles located in /var/log/YaST2.
Comment 2 Guenther Deschner 2006-02-14 10:34:47 UTC 
I'm wondering how YasT detects that; someone can comment what tool/libs are used for that?
Comment 3 Michael Gross 2006-02-14 11:06:12 UTC 
Should be in the logs (any called external tool)
Thomas: Mailing the data to me is of virtually no use. Always attach reqested files and information here. Comments would also go right here. Thanks.
Comment 4 Lars Müller 2006-02-15 19:14:44 UTC 
Thomas: How do you expect the workgroup name should be set?  AFAIK DHCP only provides settings for netbios name server and scope if set on the DHCP server side.
Comment 5 Michael Gross 2006-02-21 12:22:02 UTC 
Thomas: Please reopen this report once you can give an answear.