Need help setting up samba client

[Member noordinaryspider]

Hello, I’m new to “Heather Heyer” and probably haven’t even virtualized antiX in a good five years. I’m absolutely loving what you’ve been up to except for the troubles I’m having with Samba. I didn’t have much luck with Connectshares, so I tried just using Spacefm, which would have been ideal, with the address smb://username@ip-address-of-server/share instead of my accustomed smb://ip-address-of-share and/or smb://network/workgroup/hostname-of-server from pcmanfm.

After much grumping and grumbling and shaking my fist at the sky, I finally opened a terminal and realized that it was no big deal to use my words like a big boy/girl and and sudo apt-get install pcmanfm gvs-backends gvs-fuse but I still can’t access my home network. I had the same problem with Devuan on the same Thinkpad T43 I am using for the install, but was under the impression that it was not a hardware issue, just my own inexperience and sloppiness.

I rarely actually need to connect to a windows machine, so samba may just be a bad habit. My current antiX machine(s) are old and I have a brand new hard drive install on a 12 gig IDE drive. I want to access configuration files that are stored on the server and, when all the customizing, learning, and “moving in” is done, edit and access files for word processing, .pdf and .epub books, streaming media, etc.

tia, and this is a question, not an emergency. 🙂

Gnu/Linux user #387554 (since 2005-4-17) with old thinkpads and a strong preference for free-as-in-freedom over proprietary software.

Having loved and dabbled in antiX for a long time, I find that I still have so very much to learn and that learning is so very enjoyable.

[Forum Admin rokytnji]

Helpful

Up

0

::

When in doubt. I go fishing for D.O. So. I run with the dolphin. Then all is good again. Just teaching you how to fish also.

https://www.youtube.com/results?search_query=connect+shares+antix+linux

https://www.youtube.com/results?search_query=samba+antix+linux

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems

[Forum Admin SamK]

Helpful

Up

0

::

noordinaryspider wrote:

I didn’t have much luck with Connectshares…

In antiX-17, Connectshares works fine. It is in daily use here on various hardware from a range of manufacturers. In fact it has been in constant use since antiX-13 on systems manufactured circa 1999 onwards.

You mention you have had similar problems with Devuan and are similarly unable to access your home network with antiX. This may point to a wider problem.

To help you diagnose the problem we need more information than “I didn’t have much luck with Connectshares…”

Are you using antiX Stable? An inxi report will help here. In a terminal enter inxi -Frz and let us see the output.

You mention virtualized antiX. What does this mean. Are you installing antiX to a virtual machine (VM) and wanting to access a share on a remote Windows system from within the VM? If yes can you access the share directly from the system on which the VM is installed?

What does Findshares report? In a terminal enter findshares to scan the LAN for available shares.

Have you followed the guidance in the antiX-FAQ? Many users successfully set up share access with it.
http://download.tuxfamily.org/antix/docs-antiX-17/FAQ/connectshares.html

Have you tried the advice given in the Connectshares video?
https://www.youtube.com/watch?v=pp95SzXLp7Q

How have you configured Connectshares? Post the contents of ~/.config/connectshares/connectshares.conf
Note: If you are using this file to automatically supply a username+password for share access you might want to remove those before posting.

[Member noordinaryspider]

Helpful

Up

0

::

Thank you.

I can see the shares just fine in step 1, but in step 2, I get an error message saying that “Either the file already exists or the name is invalid”. I get the same error message when I try to create a new configuration file.

Here is my `/.config/connectshares/connectshares.conf file:

# ————-
# 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.10.169

# ————
# 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=

# 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,
noordinaryspider=homes,
#
# 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

# 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=

Here is the inixi report:

System: Host: antix1 Kernel: 4.14.2-gnu.nonpae i686 bits: 32
Desktop: Fluxbox 1.3.5
Distro: antiX-17_386-full Heather Heyer 24 October 2017
Machine: Device: laptop System: IBM product: 18714PU v: ThinkPad T43 serial: N/A
Mobo: IBM model: 18714PU serial: N/A
BIOS: IBM v: 70ET64WW (1.24 ) date: 02/13/2006
Battery BAT0: charge: 60.4 Wh 99.9% condition: 60.4/71.3 Wh (85%)
CPU: Single core Intel Pentium M (-UP-) cache: 2048 KB speed: 1866 MHz (max)
Graphics: Card: Intel Mobile 915GM/GMS/910GML Express Graphics Controller
Display Server: X.Org 1.19.2
drivers: intel (unloaded: modesetting,fbdev,vesa)
Resolution: 1024×768@60.00hz
OpenGL: renderer: Mesa DRI Intel 915GM x86/MMX/SSE2
version: 2.1 Mesa 13.0.6
Audio: Card Intel 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC’97 Audio Controller
driver: snd_intel8x0
Sound: Advanced Linux Sound Architecture v: k4.14.2-gnu.nonpae
Network: Card-1: Broadcom Limited NetXtreme BCM5751M Gigabit Ethernet PCIE
driver: tg3
IF: eth0 state: down mac: <filter>
Card-2: Qualcomm Atheros AR5212 802.11abg NIC driver: ath5k
IF: wlan0 state: up mac: <filter>
Drives: HDD Total Size: 12.1GB (38.9% used)
ID-1: /dev/sda model: HITACHI_DK23AA size: 12.1GB
Partition: ID-1: / size: 10G used: 3.5G (37%) fs: ext4 dev: /dev/sda1
ID-2: swap-1 size: 1.07GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 48.0C mobo: 42.0C
Fan Speeds (in rpm): cpu: 3949
Repos: Active apt sources in file: /etc/apt/sources.list
deb http://linux-libre.fsfla.org/pub/linux-libre/freesh/ freesh main
Active apt sources in file: /etc/apt/sources.list.d/antix.list
deb http://repo.antixlinux.com/stretch stretch main nosystemd
Active apt sources in file: /etc/apt/sources.list.d/debian-stable-updates.list
deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
Active apt sources in file: /etc/apt/sources.list.d/debian.list
deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
deb http://security.debian.org/ stretch/updates main contrib non-free
Info: Processes: 143 Uptime: 8:26 Memory: 1075.5/1972.5MB
Client: Shell (bash) inxi: 2.3.40

and findshares:

findshares
Local Host Name = antix1
Local IP Address = 192.168.10.179 on wlan0

Scanning from 192.168.10.179 on wlan0
Samba/Windows Shares
——————————————————————————–
WORKGROUP
DEVUAN 192.168.10.169 Samba 4.2.14-Debian
print$ Printer Drivers
noordinaryspider
IPC$ IPC Service (Samba 4.2.14-Debian)
Benjamin_Franklin HP Deskjet 1050 J410 series
MFCJ480DW MFCJ480DW
HP_DeskJet_940C HP DeskJet 940C

WORKGROUP
ANTIX1 192.168.10.179 Samba 4.5.12-Debian
print$ Printer Drivers
IPC$ IPC Service (Samba 4.5.12-Debian)

NFS Exports
——————————————————————————–
Server IP Address = 192.168.10.169
Exported Location Allowable Clients
/home
192.168.10.121
192.168.10.205
192.168.10.115
192.168.10.111
192.168.10.255
192.168.10.114
192.168.10.179

Gnu/Linux user #387554 (since 2005-4-17) with old thinkpads and a strong preference for free-as-in-freedom over proprietary software.

Having loved and dabbled in antiX for a long time, I find that I still have so very much to learn and that learning is so very enjoyable.

[Forum Admin SamK]

Helpful

Up

0

::

Kernel and Repos

noordinaryspider wrote:

Here is the inixi report:

System: Host: antix1 Kernel: 4.14.2-gnu.nonpae i686 bits: 32

You are using a kernel which I have no experience of, so the following is based on the premise that it does not adversely affect the issue.

The use of the stable (stretch) repos with antiX-17-Full is good as it reduces the number of potential sources of the problem. If you have not already done it, follow the standard update and upgrade routines to ensure the system is fully up to date.

Connectshares Configuration

noordinaryspider wrote:

…in step 2, I get an error message saying that “Either the file already exists or the name is invalid”. I get the same error message when I try to create a new configuration file.

This is highly likely to be due to the way in which you are using the inbuilt selection and editing tools.

The previously linked video provides relevant info. Start times approximately:

• 3:00 connectshares configuration
• 4:00 how to select and edit connectshares.conf
• 5:15 alternative method of configuring connectshares.conf

There are errors in the details you have entered into the connectshares.conf file.
It will be beneficial for you to read the FAQ Connectshares guide section entitled, Setting Up Connectshares. This section includes an example configuration. Pay particular attention to the entries, WORKGROUP and SHARESUSER, both of which require a value and are currently invalid in your configuration.

Findshares Report
It looks like you are trying to connect to a remote Samba server (192.168.10.169) and mount a homes share (usually password protected) in the local system (192.168.10.179). The Findshares report does not contain a reference to any homes shares which suggests homes shares are not set up on the remote Samba server or the remote system might be blocking them in some way.

Is the remote Samba server correctly configured to serve homes shares? This would also explain the difficulties you reported when using Devuan to connect to the Samba server. Note, Samba homes shares usually require name and password to be supplied during the connection process. There are plenty of reference guides on this available on the net.

The Findshares report shows you are also running a Samba server on the local system (192.168.10.179). This is not needed to access shares on a remote Samba server. If you do not intend to serve shares from 192.168.10.179 to other client systems on the LAN, it is probably a good idea to switch off (and eventually uninstall) this Samba server. Doing so will make more resources available to 192.168.10.179 and reduce the complications you face while troubleshooting.

An unusual entry in Findshares is reported as 192.168.10.255. Is this the IP address of one of your systems? xxx.xxx.xxx.255 is normally reserved for the broadcast address of the LAN and as such is not used as an actual host address. This might be adding to the problems you are experiencing.

[Forum Admin SamK]

Helpful

Up

0

::

This overview of Connectshares might be useful.
https://www.antixforum.com/forums/topic/remote-share-access-connectshares-v-file-manager/#post-3631

[Member noordinaryspider]

Helpful

Up

0

::

Thank you again, SamK. 🙂

I have multiple problems with the video streaming site that are irrelevant to the discussion, but the only problem with the text documentation is lack of time on my part. This is temporary and has nothing to do with antiX.

I’ll post an update when I get this figured out and/or reinstall. A fresh start with a c/p of the configuration file seems like a sensible next step at the moment.

Everything else is working out of the box on extremely old hardware with extremely limited time and energy for learning a whole new OS. My compliments to the chefs. 🙂

Gnu/Linux user #387554 (since 2005-4-17) with old thinkpads and a strong preference for free-as-in-freedom over proprietary software.

Having loved and dabbled in antiX for a long time, I find that I still have so very much to learn and that learning is so very enjoyable.

[Member 1040STE]

Helpful

Up

0

::

I encounter difficulties in mounting my NAS with Sambashare.
The problem is : Antix tries to establish an SMB1 connection, and the Synology denies this.
No, I don’t want to allow SMB1 connections 🙂
How can I force SMB2 or 3 in Antix ? I find here and there solutions implying modifying smb.conf, but I understand Samba isn’t “really” installed on Antix (no smb.conf nor related folder).
And apparently installing samba fails because some dependencies can’t be installed.
Thanks for your help!

[Member olsztyn]

Helpful

Up

0

::

1040STE wrote:

I encounter difficulties in mounting my NAS with Sambashare.
The problem is : Antix tries to establish an SMB1 connection, and the Synology denies this.
No, I don’t want to allow SMB1 connections

What version of antiX is that? Since long time it has been the other way round – default protocol is SMB2 and it has been more difficult to set up access to SMB1 NAS.
If you are using any antiX later than antiX 17 then it should be pretty simple to access SMB2 NAS. Choice of options:
– Connectshares
– FSTAB definitions
– directly from default file manager (zzzFM)
– SMBmap script developed by PPC.

The last method (smbmap) is very easy to use and works with SMB2 and up NAS servers. It is a particularly useful utility, however it has not been made available separately but only as bundled with FT10 antiX transformation script. It is a pity that you would be forced to install the FT10 in order to perform smbmap connection to NAS SMB2, but this is what it is, unless PPC would be willing to make smbmap script separately, not forcing FT10 installation.
Connectshares (developed by SamK) has been with antiXfor a long time and works just fine.
I have used all the above methods and currently am connecting to multiple NAS servers, both SMB2 and SMB1 with no issues.

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

[Member 1040STE]

Helpful

Up

0

::

Thank you @olsztyn ! I’m on Antix 22, more precisely “Distro: antiX-22_386-full Grup Yorum 18 October 2022”.
I’ll check the SMBmap/FT10 solution, I guess 🙂

[Member olsztyn]

Helpful

Up

0

::

1040STE wrote:

I’ll check the SMBmap/FT10 solution, I guess

SMBmap is the name when I was testing it some time ago. I am not sure it is still called that name within the FT10 bundle, but should be easy to find. Otherwise PPC will be of help how to locate it. I am familiar with just this utility but not the entire FT10.

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

[Member PPC]

Helpful

Up

1

::

Hi. there is no need to install FT10 to use the samba2 shared folder GUI script- it’s available here in the forum. For your convinience, I attached it below. Unzip and run the script – it tries to install any missing dependencies, at first run.

How it works:
Run the script and it tries to install any missing dependencies (asks user’s authorization first); then it scans the network for shared folders. If a shared folder is found, it’s shown on a list. Click the shared folder you want to connect to. If you need to enter credentials, do so on the window that pops up (if not, just don’t enter anything in the credentials window). The shared folder should pop up in zzzfm.
If no network shared folder is found a “notification” will pop up, on the lower right corner of the screen.

Limitations of the GUI script:
It works only on samba2 shared folders (not in previous versions) and it’s been reported to fail if the “share” includes spaces in it’s name.

Personal opinion:
Since there are lots of people that do have to user their computers with shared folders (specially in a work envirnoment), I do think this script, and it’s .desktop file should be included, by default in antiX. The script and it’s .desktop file take about 11kb of disk space (since it only installs the very small dependencies when people want to use it).

P.

• This reply was modified 2 months ago by PPC.

Attachments:

1. my_network_neighborwood.zip

[Member olsztyn]

Helpful

Up

0

::

PPC wrote:

Hi. there is no need to install FT10 to use the samba2 shared folder GUI script- it’s available here in the forum.

Thank you PPC for sharing this useful tool independently from FT10…

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

[Member 1040STE]

Helpful

Up

0

::

@PPC : thank you very much ! I’ll try this, as the installation of FT10 appears to have somewhat failed here (?)
@olsztyn : I’m afraid I was wrong when I wrote Antix tried to connect the NAS via SMB1. It wasn’t my eeePC with Antix but my less old large Asus with Ubuntu.

[Member 1040STE]

Helpful

Up

0

::

The installation fails : “dependencies not installed”. The terminal window closes too quickly to see what’s wrong, but it might be a repository issue?

[Author]

Posts