Search Results for 'samba'

[Member PHerrmann]

Hello!
If this may help :
I use Connectshares to mount Samba local network shares (NAS).
I encountered turnoff process halting after the line : “Stopping enhanced syslogd : rsyslogd” during 1 to 2 minutes, then resuming to full stop. This behavior was the same for 32 bit and 64 bit PC, both running antiX 19.2.
I found that, when disconnecting manually the shares using Disconnectshares before turnoff, the turnoff process was very quick, as it should be.
This behavior is reproducible.

[Forum Admin SamK]

olsztyn wrote:

…it looks to me password= and pass= both worked.

OK, moving on to configuring Connectshares.
The config in post #33805 looks generally OK to use as a base.

NAS Server that uses SMB/CIFS v1.0
Edit ~/.config/connectshares/connectshares.conf

Ensure the samba options section looks like the following
SAMBAOPT=vers=1.0,

NAS Server that uses SMB/CIFS v2.1 or greater
Copy connectshares.conf to connectshares2.conf

Edit ~/.config/connectshares/connectshares2.conf

Ensure the correct IP Address is used

Ensure the correct shares are listed

Ensure the samba options section is empty i.e.
SAMBAOPT=

Save the file as connectshares2.conf

Connectshares can be started in various ways.

Manually from
* antiX menu
* Creating launchers in the Personal menu section
* Creating a desktop shortcut
* Added to SpaceFM as shown in the video by dolphin_oracle

In every case the command
* “connectshares” will connect using connectshares.conf
* “connectshares connectshares2.conf” will employ connectshares2.conf

Automatically at boot up (shown in the antiX FAQ)
Control Centre–>Session–>User Desktop-Session–>Startup Tab

To start via connectshares.conf, uncomment the line that contains the command
“connectshares &”

To start via connectshares2.conf, append a line
“connectshares connectshares2.conf &”

[Member olsztyn]

Executed as per your commands and strangely getting:

$ mkdir testmnt
demo@antix1:~
$ sudo su
root@antix1:/home/demo# mount -t cifs //192.168.0.6/Files testmnt –verbose -o user=francis
Password for francis@//192.168.0.6/Files:
mount.cifs kernel mount options: ip=192.168.0.6,unc=\\192.168.0.6\Files,user=francis,pass=********
mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
root@antix1:/home/demo# ls testmnt

No idea why because Findshares has no problem seeing:
root@antix1:/home/demo# findshares
Local Host Name = antix1
Local IP Address = 192.168.0.108 on wlan1

Scanning from 192.168.0.108 on wlan1
Samba/Windows Shares
——————————————————————————–
WORKGROUP
IX2-200B 192.168.0.6 Iomega ix2-200
Backups
Files
Video
Audio
Pics
IPC$ IPC Service (Iomega ix2-200)

root@antix1:/home/demo#

Can you see your files on the remote server share? Yes, from other systems, but not from antiX.
Are there any error messages when running the mount command? No error reported.

Thanks again for your help…

• This reply was modified 3 years, 1 month ago by olsztyn.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member olsztyn]

Thank you samK for elaborate response.

SamK wrote:

f you mean you are prompted for credentials in both cases, the most likely cause is invalid configuration.

No. Prompting for Username/Pass was only in case ‘CREDAUTO=’.

SamK wrote:

Are all the shares on the remote server set up to require username+password?

Yes.

SamK wrote:

If your remote shares are sometimes seen and sometimes not seen, it might indicate an intermittent connection problem somewhere in your local or remote system, or both. If so, Connectshares is not the cause . Connectshares is just like any other app, it requires a stable, reliable connection.

My next testing step will be on wired connection, not WiFi.

SamK wrote:

You have not provided the contents of your connectshares.conf as requested in post #33788. Post it if you want any further help.

The reason I have not provided connectshares.conf was that I was constantly changing parameters. If I know what configuration actually works (whatever is recommended) with security I will work on testing from there.

But if it helps, this is:
$ cat ~/.config/connectshares/connectshares.conf

# ————-
# Remote System
# ————-

# The name or IP address of the remote system serving the share(s)
# Examples
# REMOTE=shareserver
# REMOTE=192.168.1.50
REMOTE=192.168.0.6

# ————
# Samba Shares
# ————

# Enable/disable the mounting of Samba shares from the remote system
# When disabled, all other entries in “Samba Shares” section are ignored
# Leave empty to disable mounting, add y to enable mounting
# Examples
# SAMBA=
# SAMBA=y
SAMBA=y

# The name of the domain in which the remote system serves Samba shares(s)
# Examples
# WORKGROUP=company
# WORKGROUP=workgroup
WORKGROUP=WORKGROUP

# Samba shares on the remote system that require a user name and password
# Leave empty to disable mounting shares of this type
# Each listed share must include only the share name terminated by a comma
# Multiple shares must be specified as a comma separated list
# A space immediately before or immediately after a comma is not allowed
# Examples
# SHARESUSER=
# SHARESUSER=homes,
# SHARESUSER=accounts,homes,video clips,
SHARESUSER=Files,
#
# Enable/disable automatically supplying user name and password to remote Samba server
# When disabled a request to manually input credentials is displayed
# Leave empty to disable automatic credentials mode, add y to enable automatic credentials mode
# Examples
# CREDAUTO=
# CREDAUTO=y
CREDAUTO=
#
# The name and password to be supplied when automatic credentials mode is enabled
# When automatic credentials mode is disabled, these entries are ignored and may be left empty
# Examples
# CREDNAME=popeye
# CREDPASS=spinach
CREDNAME=
CREDPASS=

# Samba shares on the remote system that do not require a user name and password
# The shares must allow access to guests
# Leave empty to disable mounting shares of this type
# Each listed share must include only the share name terminated by a comma
# Multiple shares must be specified as a comma separated list
# A space immediately before or immediately after a comma is not allowed
# Examples
# SHARESGUEST=
# SHARESGUEST=anyone,
# SHARESGUEST=anyone,guest only,
SHARESGUEST=

# Options to be applied when mounting Samba shares (both with and without a password)
# Leave empty to disable the use of options
# An option must be terminated by a comma
# Multiple options must be specified as a comma separated list
# A space immediately before or immediately after a comma is not allowed
# Examples
# SAMBAOPT=
# SAMBAOPT=nounix,cache=none,
SAMBAOPT=

# ——————–
# NFS Shares (Exports)
# ——————–

# Enable/disable the mounting of NFS shares from the remote system
# When disabled, all other entries in “NFS Shares (Exports)” section are ignored
# Leave empty to disable mounting, add y to enable mounting
# Examples
# NFS=
# NFS=y
NFS=

# NFS shares on the remote system that do not require a user name and password
# The shares must be accessible by a local system that has a vaild IP address or DNS name
# Each listed share must include the full path of the exported directory on the remote system
# Each listed share must be terminated by a comma
# Multiple shares must be specified as a comma separated list
# A space immediately before or immediately after a comma is not allowed
# Examples
# SHARESIPDNS=/home/nfs/backups,
# SHARESIPDNS=/home/nfs/audio clips,/home/nfs/backups,/home/nfs/images,
SHARESIPDNS=

# Options to be applied when mounting NFS shares
# Leave empty to disable the use of options
# An option must be terminated by a comma
# Multiple options must be specified as a comma separated list
# A space immediately before or immediately after a comma is not allowed
# Examples
# NFSOPT=
# NFSOPT=rw,hard,intr,timeo=30,retry=0,
NFSOPT=
demo@antix1:~
$

Thanks again for your help!
Greatly appreciated.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Forum Admin SamK]

olsztyn wrote:

sudo ufw status:
Status: inactive

This eliminates one potential source of your problems. Keep the firewall inactive during all tests.

olsztyn wrote:

$ findshares
Local Host Name = antix1
Local IP Address = 192.168.0.108 on wlan1

Scanning from 192.168.0.108 on wlan1
Samba/Windows Shares
——————————————————————————–
WORKGROUP
IX2-200B 192.168.0.6 Iomega ix2-200
Backups
Files
Video
Audio
Pics
IPC$ IPC Service (Iomega ix2-200)

This eliminates a further potential source of your problem. It indicates your remote shares are known to the system on which Connectshares runs.

olsztyn wrote:

…unlike in videos, seems to me there is some difference now vs. antiX 15 (appears to me the latest antiX version in those videos).

Your assumption is incorrect.

The confirmation of correct working documented in post #33788 above proves Connectshares works as expected on antiX-19.1. Additionally it is in daily use here on antiX-17.4.1. The version of antiX is irrelevant.

olsztyn wrote:

Both with CREDAUTO=y and CREDAUTO= (asked me to enter username and password, afterwards)
Neither made a difference.

If you mean you are prompted for credentials in both cases, the most likely cause is invalid configuration.

Are all the shares on the remote server set up to require username+password?

olsztyn wrote:

With ‘CREDAUTO=’ it comes back prompting for Username and Password.

This is normal and expected behaviour.

olsztyn wrote:

I was suspecting ‘SHARESUSER=Files,’ specification but upon removing ‘Files,’ and leaving just ‘SHARESUSER=’ […] I am getting message ‘Config incomplete’, so it seems required now…

Again you are making an incorrect assumption.

Whether SHARESUSER requires a value depends on how you set up the share on the remote server system. If the remote share requires authenication before granting access, SHARESUSER needs a value. If the remote share has been set up to grant access without requiring authentication, SHARESUSER does not need a value.

olsztyn wrote:

…sometimes comes back with ‘Not found’.

If your remote shares are sometimes seen and sometimes not seen, it might indicate an intermittent connection problem somewhere in your local or remote system, or both. If so, Connectshares is not the cause . Connectshares is just like any other app, it requires a stable, reliable connection.

olsztyn wrote:

Regardless of trying various options I am getting ‘Did not mount Files on 192.168.0.6’…
[…]
I tried all kinds of config combinations in attempt to make it work…

You have not provided the contents of your connectshares.conf as requested in post #33788. Post it if you want any further help.

You have made multiple references to following videos but have you looked at the Connectshares FAQ? It contains guidance and a worked example that might assist you if you decide to troubleshoot by yourself.

[Member olsztyn]

Anti, samK – thanks for confirmation.

anticapitalista wrote:

Are you running live? If so do not use disable=lx boot cheat.

I am running Live. Boot default parameters are ‘quiet splasht disable=F’.

SamK wrote:

s the firewall interfering?
Post the output of the command
sudo ufw status

I was testing first with default firewall on, then disabled: sudo ufw status:
Status: inactive
”
$ findshares
Local Host Name = antix1
Local IP Address = 192.168.0.108 on wlan1

Scanning from 192.168.0.108 on wlan1
Samba/Windows Shares
——————————————————————————–
WORKGROUP
IX2-200B 192.168.0.6 Iomega ix2-200
Backups
Files
Video
Audio
Pics
IPC$ IPC Service (Iomega ix2-200)
”
Also:
Both with CREDAUTO=y and CREDAUTO= (asked me to enter username and password, afterwards)
Neither made a difference. This was with ‘SHARESUSER=Files,’.
‘Files’ is the Share Name on CIFS/SMB NAS server 192.168.0.6, correctly reported by Findshares.
I was suspecting ‘SHARESUSER=Files,’ specification but upon removing ‘Files,’ and leaving just ‘SHARESUSER=’ as I saw in multiple videos by DelphinOracle, I am getting message ‘Config incomplete’, so it seems required now, unlike in those videos…
In effect: Regardless of trying various options I am getting ‘Did not mount Files on 192.168.0.6’…
I will continue to try to figure this out but at this point I may have run out of options and the fact that ‘SHARESUSER=’ is reported as incomplete now, unlike in videos, seems to me there is some difference now vs. antiX 15 (appears to me the latest antiX version in those videos).

• This reply was modified 3 years, 1 month ago by olsztyn.
• This reply was modified 3 years, 1 month ago by olsztyn.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member seaken64]

These are the apps that I use regularly, and are already on the Popular Apps of the Package Installer:

Audacious
Kodi
SMPlayer
SMTube

Netsurf
SeaMonkey

SpaceFM
VirtualBox
Samba

These are apps I use regularly that are not on the Package Installer

Remmina – allows remote connection to other computers, uses VNC or RDP, even NX.
Streamtuner2 – browse internet streaming music services, internet radio

I think it may be hard for a newbie to find the Package Installer. It is on the Control Centre but on the second tab (System). If there was a tab or icon titled “Software” or “Software Manager” that might make it easier. It is also on the menu under Applications|System Tools|Package Installer. Again, maybe the word “Software” would be easier for many to understand, or “Software Installer”. And a note at the top telling the newbie that this is only a partial list of the software available. For full software management, and a full list of available software, use Synaptic.

Seaken64

[Moderator christophe]

I see that smbclient is available in Debian Stretch. So I don’t know why you can’t see it. Have you changed your repos?

Also (and maybe this is of more help) at the debian site, https://packages.debian.org/stretch/smbclient, it mentions this:
“Utilities for mounting shares locally are found in the package cifs-utils.”

See if this may be helpful: https://www.raspberrypi.org/documentation/remote-access/samba.md

• This reply was modified 3 years, 3 months ago by christophe. Reason: bad answer
• This reply was modified 3 years, 3 months ago by christophe.
• This reply was modified 3 years, 3 months ago by christophe.

confirmed antiX frugaler, since 2019

[Member Speedyg869]

I followed the thread “antiX 13.2 / SAMBA” you referred to and tried the same things the OP did.

sudo apt-get update && sudo apt-get dist-upgrade

sudo apt-get remove --purge samba
	Package 'samba' is not installed, so not removed
sudo apt-get remove --purge smbclient libsmbclient
	Package 'smbclient' is not installed, so not removed

sudo apt-get install samba
Package samba is not available, but is referred to by another package.
...
However the following packages replace it:
	samba-common samba-libs

sudo apt-get install samba-client
...
E: Unable to locate package samba-client ?

sudo apt-get install smbclient
...
E: Unable to locate package smbclient ?

The conlusion was that smbclient is not available in the antiX repo.
Your last post in that thread talks about getting the package from debian. But then you say “OK, thanks. If push comes to shove I’ll look into that.”. So I don’t know what you ended up doing.

If smbclient or samba-client aren’t in the antiX repo, then what?
Should I add the deb http://ftp.us.debian.org/debian/ stretch main contrib non-free to my sources.list and install it from there?
Does smbclient require/use systemd?
I have never added package from another distro before. Can someone confirm?

• This reply was modified 3 years, 3 months ago by Speedyg869. Reason: Fix code tag

[Anonymous]

https://www.antixforum.com/forums/search/samba/page/2/
+
https://www.youtube.com/user/runwiththedolphin/search?query=samba

antiX 17.4 Live USB w/persistence.
How do I start the Samba Server in antiX 17.4?
The package manager shows that samba-common, samba-libs, libwbclient0, libsmbclient are installed and are the latest. No other packages are available matching “samba”. There is no Samba service running. When I search for documentation, I find old entries from 2013 and none of those commands seem to work. The commands from Debian don’t seem to work either.
Connectshares seems to apply only to remote systems, not shares on the local system. Maybe I’m wrong about that.
Can someone tell me how to start the Samba server?

Thanks in advance.

• This topic was modified 3 years, 3 months ago by Speedyg869. Reason: Marking [Solved]

[Member 3guesses]

anticapitalista wrote:

Yes.
If you want samba, install it while running live and then run the installer or do it after installation.

That’s what I’d love to do! But the SAMBA Server package/software doesn’t seem to be available for antiX 13.2…

[Forum Admin anticapitalista]

Yes.
If you want samba, install it while running live and then run the installer or do it after installation.

• This reply was modified 3 years, 4 months ago by anticapitalista.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member 3guesses]

I have re-run the antiX 13.2 installation, and at stage 6 (“Computer Network Names”) there is an option “SaMBa Server for MS Networking” – BUT IT IS GREYED OUT! So it would appear that the intention was for the SAMBA Server software to be an option for the user to include during installation, but it was never implemented.

This is also the case for the antiX 19 installer…

[Member 3guesses]

Anonymous wrote:

I couldn’t recall, had to go lookitup –} antiX 13.2 was based on debian 7(aka “Wheezy”)

a websearch “debian wheezy install samba” led me to the following

https://www.howtoforge.com/samba-server-install-on-debian-7-wheezy

To install samba:
apt-get install samba samba-common libcups2

Thanks. I’ve already tried installing the samba and samba-common packages and I think libcups2 will handle printing 8-(

seaken64 wrote:

I am running antiX-16 and antiX-17 on similarly powered computers. One is a P-III with 384MB RAM. Have you tried one of the Jessie versions?

Seaken64

I might have a go at running antiX-17 on it then if there are all dead ends where antiX-13 is concerned.