Puppy 528 unable to access Samba share
Puppy 528 unable to access Samba share
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?
- Attachments
-
- juju.png
- (12.07 KiB) Downloaded 324 times
Shares on my other machines work fine. The server name is juju. The share name is puppyshare.
This is what I get:
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)
Try this command instead
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.
Code: Select all
/usr/bin/smbclient -NL 192.168.2.13
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.
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.
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
- Attachments
-
- setup.png
- (33.43 KiB) Downloaded 319 times
Your smb.conf should have a line like
Code: Select all
netbios name = juju
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 typeThe 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"), RunIf 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!)If you get ANY OTHER ANSWER OTHER THAN what you got on the JUJU machine, post the answer back here.
Here to help.
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
Code: Select all
smbclient -U% -L theJUJUipAddress
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
Here to help.
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#
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 ~ $
From which client machine? Try from a Puppy client and see what login credentials work - probably root:woofwoof.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?
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.rmcellig wrote:Is there a way to get around the firewall issue
Run smbpasswd. I don't know the exact syntax.Am I able to change the login credentials to something else?
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
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, typeWhen back on desktop, Open a terminal and do the following (DO NOT USE THE "-U" parameter this time)Code: Select all
# passwd # smbpasswd -a # logout # xwin
You will see the same thing you saw beforeCode: Select all
# smbclient -L localhost
Next at your LAN PC,
Open a terminal and doReport back your connectionCode: Select all
# mkdir /mnt/JUJU-puppyshare # mount -o username=root //192.168.2.13/puppyshare /mnt/JUJU-puppyshare
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 ~ $