[KLUG Members] SAMBA Problem

[Adam Williams]

> The problem you are having sounds very much like a name resolution issue as
> mentioned by Adam. Unless you have Active Directory, Windows clients behave
> VERY badly 

Windows behaving badly?  I thought that was what girls did?

> if they don't have WINS. Its basically a requirement. Your
> problem is most likely caused by the clients trying to resolve via broadcast
> and timing out finding the workgroup/domain. Once more time passes and they
> are in Windows, the broadcast is coming through and it can now resolve the
> Samba server. Is your Samba set up for Domain or Workgroup mode? Are you
> serving DHCP from the same box?

If they don't have a WINs server, enabling WINS server support on the
Samba box is as easy as "wins support = yes".  Then either assign the
Samba boxes IP as the WINS server on every box, if not using DHCP.  If
using DHCP just add the following to the network stanza -

 subnet 192.168.10.0 netmask 255.255.255.0 {
   authoritative;
   range 192.168.10.100 192.168.10.199;
   default-lease-time   129400;
   max-lease-time       172800;
   option routers 192.168.10.19;
   option domain-name-servers 192.168.10.18, 192.168.1.5, 192.168.1.9;
+   option netbios-name-servers 192.168.1.9;
+   option netbios-node-type 2;
     }