Page 2 of 8

Posted: Mon 07 Feb 2011, 02:25
by rcrsn51
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?

Posted: Mon 07 Feb 2011, 03:54
by rcrsn51
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.

Posted: Mon 07 Feb 2011, 14:30
by marco07
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!

Posted: Mon 07 Feb 2011, 14:41
by rcrsn51
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.

Posted: Tue 08 Feb 2011, 00:01
by marco07
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.

Posted: Tue 08 Feb 2011, 00:06
by rcrsn51
Glad to help.

Posted: Tue 08 Feb 2011, 12:51
by drblock2
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.

Posted: Mon 21 Mar 2011, 15:38
by Lobster
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 8)
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.

Posted: Mon 21 Mar 2011, 22:36
by rcrsn51
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.

Posted: Tue 22 Mar 2011, 02:03
by Lobster
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.

Posted: Sun 27 Mar 2011, 20:29
by smokey01
rcrsn51,

Are you able to offer some advice here please.

http://www.murga-linux.com/puppy/viewto ... 020#508020

Thanks

Posted: Sun 27 Mar 2011, 20:30
by smokey01
rcrsn51,

I would rather use WIFI than ethernet for this type of connection.

I'm not really sure if it's possible though.

Thanks

Posted: Sun 27 Mar 2011, 20:53
by rcrsn51
This all depends on what client software is on the I*P*A*D. You can run a Samba server over Wifi with no problem, but I don't know if an Apple product will recognize a Microsoft protocol.

Posted: Mon 28 Mar 2011, 02:57
by smokey01
I understood WIFI to be a standard protocol that was universal but then I don't know much about networking.

I guess WIFI is just the transport medium. What hangs off each end need to be compatible.

I read your tutorial on Samba which was very interesting but I must admit I didn't fully understand it.

I guess I need to read the basic 101 for networking. Can you suggest a good resource that will be relevant to Puppy.

Thanks

Posted: Mon 28 Mar 2011, 03:23
by rcrsn51
To send files into the I*P*A*D, the easiest way would be to run an HTTP server on the Puppy machine as described here. The I*P*A*D could download the files through its web browser.

Posted: Mon 28 Mar 2011, 06:22
by disciple
I think Apple PCs support SAMBA, but a quick google indicates that maybe I*P*A*D*S don't... but can if you install an app called "FileBrowser" or something. I may have not have that quite straight though...

Posted: Mon 28 Mar 2011, 09:24
by smokey01
I really liked the simplicity of your HTTP solution but unfortunately it didn't work for me.

To access a Windows share from Puppy:

1. Declare a shared folder on the Windows machine.

2. Launch Puppy and run Pnethood or lameSMBxplorer from the Network menu.

---------------------------

To access a Puppy share from a Windows machine or another Puppy:

You need to run a server on the host Puppy machine. This could be a full Samba server or an ftp server, but here is my favourite method.

1. Go here and install the Python PET. Did this

2. Set up a share folder anywhere on your Puppy system and put some files in it. Yes, did this too

3. Open the folder in ROX. Yes

4. Open a terminal window inside the folder by pressing the backtick key (above the Tab key). Yes

5. Type the command
Code:
python -m SimpleHTTPServer This setup the server but it said the address was 0.0.0.0:8000

6. Minimize the terminal window, but don't close it.

7. Identify your Puppy server's IP address with the command
Code:
ifconfig
This gave me 192.168.0.2

8. Go to the client machine and open a web browser.

9. Type in the URL
Code:
http://puppy.server.ip.address:8000
I typed in http://192.168.0.2 and the connection was refused

Now if I typed the above into the sever computer that is connected to the wireless router it displayed the shared directory. When I tried this from a laptop running either puppy or windows the connection was refused. Any ideas?

Posted: Mon 28 Mar 2011, 10:22
by rcrsn51
9. Type in the URL
Code:
http://puppy.server.ip.address:8000
I typed in http://192.168.0.2 and the connection was refused
You need to type

Code: Select all

http://192.168.0.2:8000
Are you forgetting the 8000? Are you running a firewall?

Posted: Mon 28 Mar 2011, 10:54
by smokey01
rcrsn51 wrote:
9. Type in the URL
Code:
http://puppy.server.ip.address:8000
I typed in http://192.168.0.2 and the connection was refused
You need to type

Code: Select all

http://192.168.0.2:8000
Are you forgetting the 8000? Are you running a firewall?
I typed http://192.168.0.2:8000 and it works ok from the host/server computer but I guess that is inside the firewall. I will try a clean install and leave the firewall off.

I just tried a live session of Lupu 5.2.1 without the firewall and it worked great.

Thanks for you help. Much appreciated.

Posted: Mon 28 Mar 2011, 11:59
by rcrsn51
Glad to help. Your next problem is to upload files from the I*P*A*D to Puppy. Like disciple said, you will need to find out what client software is available for it.