(old)Puppy Linux Discussion Forum

I have the devx file in the right place and the boot manager detects it. It just won't load at bootup.

In any case, if you can get samba-tng compiled, we should be able to pull the necessary files out of the 32 bit version to get it working as described in the how-to.

Rcrsn,

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.

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):

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.

kind regards
emil

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.

@kirk:

I have now tried fd64-510 with the fd64-32bit-libs-3.sfs compatibility package. Under this combination, the original samba-tng-rcrsn 32-bit version works fine.

@ 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

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

Where are you getting this message - from Windows or from another Linux?

when I click on the server's name (Esi puppy Samba-TNG Server) I get the following message:

Please be more specific.

Can another Puppy client see the server using Pnethood?

The reference to smb:// suggests that you are trying to connect using the smbfs protocol. You should be using cifs.

rcrsn51 wrote: Where are you getting this message - from Windows or from another Linux?

Iget this message from a linux (Mepis) box.

Can another Puppy client see the server using Pnethood?

I do not have any other Puppy to use it as a client. Only Lupu which I am trying to access it as a server.

The reference to smb:// suggests that you are trying to connect using the smbfs protocol. You should be using cifs.

How could I use the cifs. smb:// is in dolphine file manager of the Mepis linux.
Thank you!

What do you get from a Windows box?

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.

rcrsn51 wrote:What do you get from a Windows box?

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.

KDE 4.x is capable of authenticating aganist Samba shares. You just have to either pre-provide credentials ( set them in System Settings > Sharing ) or provide them in the URL ( smb://user@server/share )

Is this useful?

As a test, I downloaded Mepis 8.5.03.

I started the Samba-TNG server on a Quirky machine with the default smb.conf.

I booted another machine off the Mepis CD. I started Dolphin and browsed to pupserver and pupshare. It asked for authentication and accepted root:woofwoof. The share was visible. Everything worked correctly.

I couldn't duplicate your error.

rcrsn51 wrote:As a test, I downloaded Mepis 8.5.03.

I started the Samba-TNG server on a Quirky machine with the default smb.conf.

I booted another machine off the Mepis CD. I started Dolphin and browsed to pupserver and pupshare. It asked for authentication and accepted root:woofwoof. The share was visible. Everything worked correctly.

I couldn't duplicate your error.

Thanks!
I have edited mepis's smb.cfg in order to access all the boxes and various partitions on them in my LAN and has had no probelm sharing files, except with Lupu 5.2 as we have been discussing above. My editing of original mepis's smb.conf has been changing the Security form user to share and adding force user = marco under each of shared folders listed in smb.conf. Therefore, as is, when i connect to shared items in other boxes using mepis, there is no authentication required.It connects right away. I wonder, if this could be the cause of problem with Lupu. I keep on workin on this and see how I can resolve this. Will report back when I have some result. In the mean time I appreciate any other ideas you may have on my editing of mepis's smb.conf.
Thanks again!

The Samba-TNG tutorial explains how to set up no-login access. Maybe your Mepis would be happier with that configuration.

Remember to restart the Samba server after changing the smb.conf.

Or maybe you need to create a "marco" user on the Samba-TNG server.

rcrsn51 wrote: Or maybe you need to create a "marco" user on the Samba-TNG server.

This did it. I have now access to ESI server and all its shared folders.
Thanks for your patience with me. Your guidance is well appreciated.

Glad to help.

I have a Windows-based LAN with a file and printer server running XP and Puppy frugal installs on several different machines in different parts of the house. I have no need for multiple user accounts (cat has refused my generous offer many times), guests just use my (W)LAN to go on line.

The major difficulty with this setup is that machines running Puppy see the server, but not each other. The Windows server doesn't see the Puppy machines either. For direct file transfer between Puppy machines, I have always relied on FTP. This is not very satisfactory because FTP does not allow you to open files on the remote drive.

With Samba-TNG, I was able to set up the network so that all the various boxes talk to each other in minutes!

1. Downloaded and installed the Samba-TNG server pet.

2. Typed samba-start in a terminal window and confirmed that Samba was indeed running.

3. Rescanned the network from another machine with Pnethood and behold - my PUPSERVER was found. Log in as described and had instant kennel to kennel contact.

4. Rescanned the network from the Windows server by clicking on network neighborhood. The PUPPYGROUP was instantly recognized.

5. Only hitch was encountered when installing the Samba-TNG server on the other Puppy machine. I initially forgot to provide a different netbios name for the new server. This was easily fixed by changing the entry in /usr/local/samba/etc/smb.conf.

rcsn51 does it again!

My next project: getting rid of the Windows server entirely.

Thanks rcrsn51, guys,

Installed on one machine that has a frugal install of a beta of Lucid 5.2.1
and accessed and transferred a file by click and dragging from another machine
with the latest 5.2.1 beta . . .

A lot easier than I expected. Many thanks for your efforts
A Windows XP machine I could not work out how to connect. I may try with Xandros or even a MAC.

Can a samba server be made available on the internet?
That is really what I want.

Lobster wrote:A Windows XP machine I could not work out how to connect.

Is the XP machine running a firewall? It will interfere with your connection to the Puppy Samba server.

Also, change the server's workgroup name to match that of the XP machine.

What procedure are you using on the XP machine? I have found the easiest way is to make a desktop shortcut directly to the server.

Is the XP machine running a firewall?

Yes. That would be it.

It is not my machine
and to be honest I would not advise the turn off.
The same may be true of the Mac.
- on Puppy I am quite happy with a router firewall.

Many thanks.