I've just got our new Fedora Core 5 box up and running on our home network, and I can use File Browser to get to shares on our WinXP boxes. Now, I want to define shares on the FC5 box, and access them from a WinXP box.

I've used Add/Remove Software to download and install Windows File Server (aka Samba). As a demo, I want to define the home directory of a FC5 user as a share. From the "Samba Server Configuration" dialog, I've set the workgroup name the same as our WinXP workgroup name, and Authentication Mode to "User". Then I've added a Samba user from the list of Linux accounts, specified the WinXP Username, and specified a Samba user password. I've added a share by browsing to the home directory for the Linux account. Finaly, Samba has been added to the list of trusted servers in the "Security Level Configuration" dialog. I can see what appear to be valid related entries in /etc/samba files smb.conf and smbusers.

Back on the WinXP box defining the shares I can see from the FC5 box, My Network Places lists "Samba Server (Localhost)" under our workgroup name. But attempting to access it results in "\\Localhost is not accessable... The network path was not found." (I haven't changed the FC5 box's network name from Localhost.localdomain, yet.)

What else do I need to do to get this working?

TIA,
Jon

This isn't the answer you are looking for, but I've used Samba enough to guide you to the best palce to start, the Samba docs. Samba is one of the best documented projects. Start with this example and go from there. This should get you a working server, then add the "homes" share.

http://us2.samba.org/samba/docs/man/...html#id2557577

Thanks, mmaki - I'll check that out shortly.

Now back to it...

Following the doco mmaki pointed me to, smbclient -L localhost
responds "Error connecting to 127.0.0.1 (Connection refused)"
I take it I'm supposed to have processes nmbd and smbd running, but ps -ef shows I've only got nmbd running.

Can anyone help me advance this?

TIA

Make sure that you have set the permissions to the shares properly. Since WinXP sees the share, but can not access it, this would most likely be the reason.