In the meantime, I did a zypper up and things are a bit better. Dolphin and Konqueror still give the error, but if I manually enter “smb:/netbios-name” I can connect to main pc. That no longer causes Dolphin and Konqueror to crash. Here is the report.txt but there’s not much to see since I fixed everything.
Analysis of Samba setup for a Workgroup in Version openSUSE 11.0 (i586)
Do NOT use this script if you have a Domain Controller on the LAN or if
workstation is a Domain Member. This script is only for SOHO workgroups.
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: eth0 IP address: 192.168.10.5 MAC address:xx:xx:xx:xx:xx
Your “Trusted Network” is 192.168.10.0/24
Status: Pass
===============================================================================
Report on Samba daemons
The Samba smb daemon is running
The Samba nmb daemon is running
Status: Pass
Check for active firewall
SuSEfirewall2 is running
Status: Pass
===============================================================================
Check devices carrying Samba comms are in the “External Zone” of SuSEfirewall2
Device eth0 [IP=192.168.10.5] is in the “External Zone” in firewall settings
Status: Pass
===============================================================================
Check SuSEfirewall2 TCP, UDP and outward Broadcast ports for a Workgroup
These TCP ports are open: 139 (netbios-ssn) 445 (microsoft-ds)
These UDP ports are open: 137 (netbios-ns) 138 (netbios-dgm)
These Broadcast ports are open: 137 (netbios-ns) 138 (netbios-dgm)
SuSEfirewall2 TCP, UDP and outward Broadcast ports are open for a Workgroup.
Status: Pass
===============================================================================
Check SuSEfirewall2 for passage of netbios-ns broadcast replies
Firewall allows netbios-ns broadcast replies on trusted network 192.168.10.0/24
Status: Pass
===============================================================================
Each workstation takes a common workgroup/domain name but a unique nebios name.
Samba has been configured for workgroup/domain ==> HOMENET
Samba has been configured with netbios name ==> LABRAT
Status: Pass
[Footnote: If you want to modify either name you can do that in 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]
===============================================================================
Recommended name resolve order = bcast host lmhosts wins (leading two mandatory)
You have name resolve order = bcast host lmhosts wins
Status: Pass
===============================================================================
Checking configuration of Local Master Browser
Your workstation is configured as a Local Master Browser with “os level = 33”.
Status: Pass
===============================================================================
Checking status as a Preferred Master Browser for the LAN
Your Local Master Browser is not configured as the “Preferred Master Browser”.
Status: Pass
–Footnote–For Experts: About Preferred Master Browser------------------------
A Preferred Master generally shares community resources; e.g. file/print server.
Do not have more that one Preferred Master on your LAN. This function is mainly
for experts. If in any doubt, just leave it off. That works fine for SOHO LANs.
You can add/delete Preferred Master 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
One user, named prexy, exists in the Samba user database.
Status: Pass
===============================================================================
Incidental (precautionary) checks:
Not a “Wins Server”
Not a “Wins Client”
Not a “Domain Controller”
Not a “Windows Domain Member”
===============================================================================
I’m now inclined to believe this has nothing to do with samba. I didn’t have a chance to try this on the remaining pc.