Apologies to those who are annoyed by the fact that I still haven't got this working. I had attempted to configure Samba server with YaST, with direct file editing, and with SWAT, and was not able to get the client (also SUSE 10) to even see the server. At Ken's suggestion I tried configuring Samba from the KDE Control Center. That had never occurred to me. Thank you. When I used KDE Control Center > Internet & Network > Samba, I simplified to share-based security in Base Settings. This causes any users to disappear from the "Users" tab (which I suppose is partly a correct action). But here's what happens now, on my client machine. Using Konq to browse smb://ourhouse, I see an icon/folder for "thatbox (Samba 3.0.20.4 -SUS)" Inside that are icons/folders: groups profiles shared Unnamed users When I try to select ANY of them, I get an authentication dialog: "Please enter authentication information for server = thatbox share = shared Username [ ] Password [ ] " The exception is if I click "profiles", then I see the contents of the "kshared" shared directory on the server user that matches the user I've got open on the client. So, I seem to have achieved a mish-mash of User-level samba share security and share-level samba security. There's nothing in smbusers on my server, which sorta matches with what happened when I selected "share" as the security level... Anybody explain what I'm seeing now (why do I get a remote directory when I browse "profiles")? What I want is for my user (the one who can remotely see "kshared" on his doppelganger user space on the server) to also be able to see "mshared" (the wife's share on the server) as well as /home/shared, which should be a generally-available-to-anybody share on the server. Also my wife should be able to see all of them as well. Kevin