Analysis of Samba setup for a Workgroup in Version openSUSE 11.0 (i586) =============================================================================== Checking the following RPMs: samba, samba-client, yast2-samba-server, yast2-samba-client, kdebase3-samba All in the list are installed. Status: Pass =============================================================================== Calculatinging the IP range for your Workgroup/LAN Device name: ath0 IP address: 192.168.1.2 Device name: eth0 IP address: 192.168.1.3 Your "Trusted Network" is 192.168.1.0/24 Status: Pass =============================================================================== Report on Samba daemons The Samba smb daemon is running The nmb daemon is not running. PLease check in Yast --> System --> System Services (Runlevel) --> Expert Mode. Locate nmb in the list and make sure the service 'nmb' has checkmarks in runlevels 3 and 5 and has status 'Running' set to 'Yes'. You can turn it on with the 'Start/stop/refresh' button (use the 'Start now' option). openSUSE 11.0 has a bug whereby it takes 2-3 minutes for the 'Expert Mode' of the Runlevel GUI to appear Status: Fail =============================================================================== Check for active firewall SuSEfirewall2 is running Status: Pass =============================================================================== Check devices carrying Samba comms are in the "External Zone" of SuSEfirewall2 Device ath0 [IP=192.168.1.2] is in the "External Zone" in firewall settings Device eth0 [IP=192.168.1.3] is NOT in the "External Zone" in firewall settings A device or devices listed above should be in the "External Zone" [i.e. if the device carries Samba communications on the LAN.] To add a device go to Yast --> Security and Users --> Firewall --> Interfaces. Then highlight the device and "Change" it to the "External" zone. Status: Fail =============================================================================== Check SuSEfirewall2 TCP, UDP and outward Broadcast ports for a Workgroup These TCP ports should be open: 139 (netbios-ssn) 445 (microsoft-ds) These TCP ports are open: These UDP ports should be open: 137 (netbios-ns) 138 (netbios-dgm) These UDP ports are open: These Broadcast ports should be open: 137 (netbios-ns) 138 (netbios-dgm) These Broadcast ports are open: SuSEfirewall2 ports are not properly open for Samba Workgroup traffic GoTo Yast --> Security and Users --> Firewall --> Allowed Services. Click the drop-down list labelled "Service to Allow" and select the item "Samba Server". Click Add to put it in the list of Allowed Services. Then click Next and Finish to exit. Status: Fail =============================================================================== Check SuSEfirewall2 for passage of netbios-ns broadcast replies SuSEfirewall2 is NOT open for receiving netbios-ns broadcast replies. To open the firewall go to Yast --> Security and Users --> Firewall --> Broadcast and click the "Add" button. Clear the Network entry, and enter the string for your Trusted Network: 192.168.1.0/24 Leave the Zone as "External Zone" and the Service as "Samba Browsing". Status: Fail =============================================================================== Each workstation takes a common workgroup/domain name but a unique nebios name. Samba has been configured for workgroup/domain ==> SWERDNA Correction Needed: Samba has not been configured with a netbios name Status: Fail You can correct this situation with Yast: Go to Yast --> Network Services --> Samba Server --> Identity. Edit only the Workgroup and/or Netbios (Host)name. Do not activate for DC or Wins Server =============================================================================== This workstation appears to be configured as a Wins Server. That is for advanced users only, generally with multiple subnets. To revert to Broadcast Name Resolution, goto Yast --> Network Services --> Samba Server --> Identity --> Advanced Settings --> Expert Global Settings: Highlight the line containing "wins support = yes" and click to Delete it; then OK etc to exit. Status: Fail =============================================================================== You have Samba configured as a Domain Controller (PDC/BDC). To reconfigure Samba as a SOHO LAN with a workgroup, go to Yast --> Network Services --> Samba Server --> Identity. Under heading "Domain Controller", select "Not a DC", then Finish. Status: Fail =============================================================================== Recommended name resolve order = bcast host lmhosts wins (leading two mandatory) You have name resolve order = To fix this go to Yast --> Network Services --> Samba Server --> Identity --> Advanced Settings --> Expert Global Settings --> Add --> locate this in the drop-down list: name resolve order. Then click OK. Then enter this in the following blank space: bcast host lmhosts wins --> OK Status: Fail =============================================================================== Checking configuration of Local Master Browser Your workstation is configured as a Local Master Browser. However your Operating System Level for Samba elections is: os level = 20 Please raise the os level. Go to Yast --> Network Services --> Samba Server Identity --> Advanced Settings --> Expert Global Settings. From there use the Add and the Edit buttons to edit or create the line as follows os level = 65 Then run the script again to test the new configuration Status: Fail =============================================================================== Checking status as a Preferred Master Browser for the LAN Your workstation is configured as the Preferred Master Browser for the LAN. However your os level is 20. Please increase it to 65 and then run the script again Status: Fail ------------------- Footnote -------------------------------------------------- You can switch the Local Master on or off and/or alter the os level in Yast --> Network Services --> Samba Server --> Identity --> Advanced --> Expert Global Use the Add/Edit/Delete buttons to modify the settings =============================================================================== Checking the Samba user database The following users exist in the Samba user database: samba john Status: Pass =============================================================================== Incidental (precautionary) checks: Not a "Wins Client" Not a "Windows Domain Member" ===============================================================================