(old)Puppy Linux Discussion Forum

READ-ONLY Archive
https://oldforum.puppylinux.com/

Puppy 528 unable to access Samba share

https://oldforum.puppylinux.com/viewtopic.php?t=84322

Page 1 of 1

Puppy 528 unable to access Samba share

Posted: Mon 11 Feb 2013, 12:22
by rmcellig
I set up Samba on my Laptop. I installed Samba-Full 3.6.3-s. I am using Puppy Linux 5.2.8. When I go to my other computer, I can see the share but when I open it, I receive the following window. What should I do?

Posted: Mon 11 Feb 2013, 13:46
by rcrsn51
What operating system is running on the "other computer"? What tool did you use on it to mount the share?

Posted: Mon 11 Feb 2013, 14:26
by rmcellig
I am running Mint 14 xfce. All of my other shares work except for this one. All I do is click on the network icon in my sidebar and mount it that way. Should I try smb://the ip address?

Posted: Mon 11 Feb 2013, 14:33
by rcrsn51
rmcellig wrote:All of my other shares work except for this one.
Do you mean other shares on the Puppy machine or shares on other machines?

Is JUJU the name of the Puppy server or the name of the share?

Posted: Mon 11 Feb 2013, 14:45
by rmcellig
Shares on my other machines work fine. The server name is juju. The share name is puppyshare.

This is what I get:

Code: Select all

randy@hprandymint ~ $  /usr/bin/smbclient -L 192.168.2.13
Enter randy's password: 
Connection to 192.168.2.13 failed (Error NT_STATUS_CONNECTION_REFUSED)

Posted: Mon 11 Feb 2013, 15:00
by rcrsn51
Try this command instead

Code: Select all

/usr/bin/smbclient -NL 192.168.2.13
Does that see the share?

If the Puppy server is set up in "security=user" mode, then it requires authentication. But I'm assuming that the "randy" password you are entering is for Randy on the Mint machine.

No such Randy user exists on the Puppy Samba server. So you will need to create it.

What happens if you login to the Puppy server using "root-woofwoof"?

Try running a Puppy client machine and accessing the share through Pnethood or YASSM.

Posted: Mon 11 Feb 2013, 15:14
by rmcellig
No. That didn't work. Here are the contents of my smb.conf file.

I cannot see 192.168.2.13 (juju) at all when I start up pnethood. I see all of my other shares.

Code: Select all

#this is a very simple smb.conf to get you started
#coutesy rcrsn51 and gcmartin
[global]
	workgroup = Workgroup
	 
	server string = Puppy Samba Server
	security = user
	map to guest = Bad Password
	printing = cups
	printcap name = cups
	load printers = yes
	max protocol = smb2

[puppyshare]
	path = /root/my-documents
	writable = yes

[printers]
	comment = All Printers
	path = /var/spool/samba
	browseable = no
	guest ok = yes
	writable = no
	printable = yes

Posted: Mon 11 Feb 2013, 15:31
by rcrsn51
Your smb.conf should have a line like

Code: Select all

netbios name = juju

Posted: Mon 11 Feb 2013, 16:05
by rcrsn51
Samba-Full 3.6.3-s
Is this a Slacko package? Is it compatible with Lupu?

Run "ps". Are the "smbd" and "nmbd" processes running?

Posted: Mon 11 Feb 2013, 16:47
by gcmartin
If the JUJU name was set at firstrun, the netbios line is probably not the problem because the system name is already JUJU.

You share that the other systems cannot "see" your JUJU machine on your LAN.

Could you do the following and post back. Open an terminal on JUJU and exactly type

Code: Select all

ip addr
smbclient -U% -L localhost
The ip addr command will return your LAN IP address. Assuming you do NOT get any errors on the smbclient line, I would like you to run one other command on the JUJU machine in the terminal. Using your real IP address (instead of "theJUJUipAddress"), Run

Code: Select all

smbclient -U% -L theJUJUipAddress
If you get the same answer (no errors) when you run the last command, post them back here.

Finally, at any other LAN PC (not the JUJU SAMBA PC), open a terminal and type (exact same command you used on the JUJU PC...no difference!)

Code: Select all

smbclient -U% -L theJUJUipAddress
If you get ANY OTHER ANSWER OTHER THAN what you got on the JUJU machine, post the answer back here.

Here to help.

Posted: Mon 11 Feb 2013, 17:05
by rmcellig

Code: Select all

sh-4.1# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:1d:72:67:38:0e brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.13/24 brd 192.168.2.255 scope global eth0
sh-4.1# smbclient -U% -L localhost 

Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.6.3]

	Sharename       Type      Comment
	---------       ----      -------
	puppyshare      Disk      
	IPC$            IPC       IPC Service (Puppy Samba Server)
	CUPS-PDF        Printer   CUPS-PDF
	pdf_writer      Printer   PDF
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.6.3]

	Server               Comment
	---------            -------
	JUJU                 Puppy Samba Server

	Workgroup            Master
	---------            -------
	WORKGROUP            JUJU
sh-4.1# 
sh-4.1# smbclient -U% -L 192.168.2.13    
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.6.3]

	Sharename       Type      Comment
	---------       ----      -------
	puppyshare      Disk      
	IPC$            IPC       IPC Service (Puppy Samba Server)
	CUPS-PDF        Printer   CUPS-PDF
	pdf_writer      Printer   PDF
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.6.3]

	Server               Comment
	---------            -------
	JUJU                 Puppy Samba Server

	Workgroup            Master
	---------            -------
	WORKGROUP            JUJU
sh-4.1#

Posted: Mon 11 Feb 2013, 17:06
by rmcellig
Here is what the other machine says:

Code: Select all

randy@hprandymint ~ $ smbclient -U% -L 192.168.2.13
Connection to 192.168.2.13 failed (Error NT_STATUS_CONNECTION_REFUSED)
randy@hprandymint ~ $

Posted: Mon 11 Feb 2013, 17:34
by rcrsn51
Do you have the Puppy firewall turned on?

Posted: Mon 11 Feb 2013, 17:52
by rmcellig
Yes I do even though I am able to ping 192.168.2.13 no problem or is that something else?

That worked! I am able to connect but it is asking me for a user/password. Where do I set this up?

Posted: Mon 11 Feb 2013, 17:58
by rcrsn51
rmcellig wrote:Yes I do even though I am able to ping 192.168.2.13 no problem or is that something else? That worked! I am able to connect but it is asking me for a user/password. Where do I set this up?
From which client machine? Try from a Puppy client and see what login credentials work - probably root:woofwoof.

Posted: Mon 11 Feb 2013, 18:04
by rmcellig
That worked. Those credentials worked fine Phew! Now it works!! Thanks so much for the help.

Is there a way to get around the firewall issue, and am I able to change the login credentials to something else?

Posted: Mon 11 Feb 2013, 18:09
by rcrsn51
rmcellig wrote:Is there a way to get around the firewall issue
You would need to do a custom firewall install that opens the Samba-related ports. They are something like 135/tcp 137/udp 138/udp 139/tcp 445/tcp.
Am I able to change the login credentials to something else?
Run smbpasswd. I don't know the exact syntax.

Posted: Mon 11 Feb 2013, 18:13
by rmcellig
Thanks again!!

Posted: Mon 11 Feb 2013, 18:15
by gcmartin
OPPS! Nevermind these instructions. I am late!

There is a manual that was done about a year ago that covers all on this to make it easy. Click this link Any contribution or comments you can make to that guide will help others.

That password is a gotcha with the simple way that SAMBA sets up. The manual explains that, though, to keep users out of trouble. You may want to glance at it when you have a moment.

Here to help
GCMartin wrote:OK, I need you to do 2 more things. One from JUJU and the other from that other LAN PC where you get the error.

At JUJU
Exit the desktop to the console and do the following command. They are going to allow you to set JUJU system's passwords (yes that's plural). I recommend that you use the same password for EACH COMMAND. At the console, type

Code: Select all

# passwd
# smbpasswd -a
# logout
# xwin
When back on desktop, Open a terminal and do the following (DO NOT USE THE "-U" parameter this time)

Code: Select all

# smbclient -L localhost
You will see the same thing you saw before

Next at your LAN PC,
Open a terminal and do

Code: Select all

# mkdir /mnt/JUJU-puppyshare
# mount -o username=root  //192.168.2.13/puppyshare  /mnt/JUJU-puppyshare
Report back your connection

Posted: Mon 11 Feb 2013, 18:41
by rmcellig
These are the results:

Code: Select all

randy@hprandymint ~ $ mkdir /mnt/JUJU-puppyshare
mkdir: cannot create directory `/mnt/JUJU-puppyshare': Permission denied
randy@hprandymint ~ $ sudo mkdir /mnt/JUJU-puppyshare
[sudo] password for randy: 
randy@hprandymint ~ $ mount -o username=root //192.168.2.13/puppyshare  /mnt/JUJU-puppyshare
mount: only root can do that
randy@hprandymint ~ $ sudo mount -o username=root //192.168.2.13/puppyshare  /mnt/JUJU-puppyshare
mount: wrong fs type, bad option, bad superblock on //192.168.2.13/puppyshare,
       missing codepage or helper program, or other error
       (for several filesystems (e.g. nfs, cifs) you might
       need a /sbin/mount.<type> helper program)
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

randy@hprandymint ~ $
All times are UTC
Page 1 of 1

Powered by phpBB® Forum Software © phpBB Limited