[Update] There is a new Samba client package attached to Part A above that contains an updated samba-login tool. This version lets you more easily change the default login settings and keep them from one session to the next.

Note that the files are no longer in /root/my-applications/bin.

The samba-adduser script in samba-tng-rcrsn-admin-1.0 has moved to a new location.

To use the devx file in Fatdog, the devx file has to be in the root of the partition (/mnt/home) and then you have to select the file with the Boot manager, it will not automatically be loaded. I tried to get Samba-tng working as a simple file server a few months ago, but didn't have much luck. I could get Samba 3.x going without too much problems, but it's huge. I have to admit that I don't know squat about Samba, so I may had something screwed up in the conf file. That code looks pretty old too, so I wasn't sure. if one of you guys have success with Samba-tng as a server in Fatdog64, I'd like to know. I'm working on Fatdog64-510 right now and it's about ready.

Posted: Mon 13 Dec 2010, 13:17 Post_subject:
Does it work with Vista and Win 7?

Hello rcrsn51,
many thanks for your always excellent tutorials and solutions. Regarding samba I do have the following question. Does it work with Win 7 and Vista?

because at the Samba-TNG homepage there it states (regarding release canditat 0.5):

Quote:

Known issues:

*
Joining Vista works only by using the Wizard. The dialog way does not work. We worked with helpful people from the MS interop team to analyze the problem. We know the solution, but it requires heavy changes and we decided to adress them after 0.5.
*
Joining Windows 7 does not work at all. The solution for the previously mentioned issue will partly fix this.

Samba-TNG has been tested successfully with Vista and Seven. You may have to edit the smb.conf file in /usr/local/samba/etc and change the workgroup value to match your Windows client machines. The usual name is "workgroup". Otherwise, Windows may not detect the share.

As always, you must restart the Samba server after making this configuration change.

I have also read the comment in the Samba-TNG release notes. I don't know what it means either.Edited_time_total

@ rcrsn51:
I have followed your instructions in post #1 to set up file sharing for my Lupu 5.2 frugal installation.
From puppy box I can use pnethood and connect to the other boxes in my home networking set up (windows as well as linux boxes). However, from these boxes, although I can see and ping the puppy server, when I click on the server's name (Esi puppy Samba-TNG Server) I get the following message:

The process for the smb://esi protocol died unexpectedly

ESI is the netbios name of the puppy server. I have already edited the smb.conf file and replaced the pupserver with ESI and workgroup name with MShome (my network name) but have no success in connecting from any other box to the Lupu server.
Any advise is much appreciated.
TIA

You can boot another computer using your Puppy Live CD and run Pnethood.

I am not familiar with Mepis so I don't know how it is mounting the share. It may be assuming that you have already made an fstab entry for the Puppy server.

Box with Windows 98 - Connects perfect and has access to all shares
Box with Windows XP = Ditto
Box (partition) with Ubuntu 10.4 with Gnome - Ditto
Laptop with Lupu 5.2 Live CD - Ditto
Box (partition) with PCLXOS with KDE 4.5 - Does not connects. Give Time out with the server Esi
Box with Mepis 8.5 with KDE 4.4 - Same as my original post.
It seems problem lies with the linux boxes with KDE WM.