Not really a problem, but as I do not unterstand, what is happening, I ask for advice:
I have a file and print server (Suse 11.2) running perfectly (almost). The workgroup name initially was “HOME”. There are WinXP, MacOS9 and Vista Clients using files via Samba and print via Cups. Internet connection goes by a Fritz.Box DSL router, which is also the central dhcp-Server. Now a MacBook’s MacOSX entered the scenario. Internet connection was ok, but it did not want to participate the Windows Workgroup. It could use the appletalk connection as MacOS9 does, but not the smb connection. It asked username, workgroup and password. No success. Entry in Samba log file: NT_STATUS_ACCESS_DENIED.
After some googling I found out, that a misconfigured DNS should be the problem. When changing the name of the workgroup to “WORKGROUP” or “FRITZ.BOX”, it would be ok. So, why did WinXP and Vista work, but not MacOSX? I changed the Workgroup name for all of them to “WORKGROUP”, and, fine, it worked. So far, no problem.
But, on my WinXP Desktop PC, also Suse 11.2 is installed (early stage of migration process ). And on the MaxOS9 G4 besides MAcOS9 also Ubuntu 10.40 is installed. When booting the Ubuntu system, I had to alter the workgroup, using the administrative tools to “WORKGROUP” and everything worked as expected. The Suse 11.2 desktop PC, however, has no separate entry for a smb client entry. So I changed the workgroup entry in /etc/samba/smb.conf from “HOME”, which had worked perfectly since then, to “WORKGROUP”. But, it did not work. All other PCs were able to participate in this workgroup, but not the Suse 11.2 desktop PC. But, surprise, when changing the smb.conf entry of the Suse 11.2 desktop PC to “fritz.box”, it entered the workgroup “WORKGROUP” without any problems.
Maybe, this is an issue concerning the Fritz.Box dhcpd, which unfortunately is unable to enter a workgroup manually. But why is it impossible to enter a certain workgroup, even when the connection dialog asks for the workgroup name, as MacOSX did (BTW, Suse 11.2 only asks for user/psswd, not for Workgroup, so you could never choose, which workgroup to enter)?
So, finally, the Win-PCs work as nice as before, the MacBook does its job as all the other members of “WORKGROUP”, the Suse 11.2 desktop does its job, however as a member of “fritz.box”. Well, it works, but, to my sense of a well configured system, this is kind of patchwork, which should become fixed.
Swerdna’s excellent samba pages did not help.
Any explanation is welcome (sorry for the lengthy story).