Search Results for 'samba'

[Member ahoppin]

Sam, again, many thanks for your patience and support. That’s an interesting table. I’ve saved a copy for future reference.

I wouldn’t have thought to compare Connectshares with a file manager, but I see the reasoning.

Maybe some of my Thunar preference is just familiarity. I’ve used it in Puppy for a decade. It’s also non-standard there, and integrating it requires more manual tweaking than in antiX.

The way Puppy handles mounting and unmounting, all Thunar has to do is display the mounted shares and drives, so I never noticed its limitations.

In antiX, I’m fine with Thunar’s handling of removeable drives. It can’t unmount them without root permission, but that’s OK. The panel icon does it nicely.

Samba shares, I’m not so sure, but I’m not connecting to any Samba shares from antiX at the moment. If I need to connect to Samba shares from antiX later, I’ll revisit the situation.

Smb4k’s mass is why, after testing it on antiX live, I haven’t added it to my antiX installation. It’s needlessly complex and, dare I say it, kind of clunky. I may go back to it, but it’ll be as a last resort.

As for the choice of an operating system, you might choose a lightweight one like antiX to keep old hardware going – a good deed for the environment, IMO. Or you might choose it just because you like things lighter. I drive a small car and live in a small (by US standards) house, so I tend to go for lightweight hardware and software too.

Others have different preferences and needs. Some folks drive big muscular pickups and SUVs. Some run Ubuntu and Fedora. To each his own.

Linux gives us the choice, and thank goodness for that. Windows doesn’t.

I have antiX-21 64 bit, version 4 kernel, installed on a 13 year old Thinkpad T400 with 4 gb of memory. It’s remarkably responsive. With a modern SSD in place of the old spinning platters, it boots from Grub to desktop in less than 20 seconds, and a push of the power button shuts it down in 5 seconds. What other modern OS can match that?

[Member PPC]

I can’t speak for everybody else that contributes to antiX’s Development, but I’ve been creating scripts that add functionality to antiX (like this one https://www.antixforum.com/forums/topic/script-to-automagically-mount-a-samba-shared-folder-in-antix/#post-78786). As soon as I think that the script I’m working on is production ready, I usually send anticapitalista a PM, explaining what the script does and why it could be a nice addiction antiX. All of those scripts are usually incorporated into the FT10 package latest beta version. The the final, non beta version Ft10 is available in the antiX repository under the name “ft10-transformation” – as far as I know, compiled by anticapitalista himself from the original compressed source code – so, in a way at least those contributions to antiX’s development are getting included in a official although optional package – that anyone can install and have some extra features available (no need to enable FT10 toolbar and menu – most applications, like Debinstaller, Translator, Cloud, Weather, News, Clock – with GUI World Clock, Alarms, Timers and a basic Stopwatch, and the beta includes already the Shared Folders Script) are available from the menu, once you install ft10-transformation.
People can contribute to antiX’s development and not post over at the Development sub forum…
I do miss Xecure and Skidoo, as far as I know, both departed from the forum for completely different reasons- that’s life – people come, people go- no one stays in the same place forever, I guess… fortunately new users drop in quite often, particularly from Brazil – how long do you think new users will take to start contributing to antiX’s Development?
I also take it as a good sign, that there is not so much missing from antiX as it was some 4 years ago, when I started using it – antiX is more feature rich, friendlier to use and much better themed – all nice characteristics that help acquire and keep new users- and still is the best full fledged OS for using on low spec hardware…

P.

[Member ahoppin]

Again I’m far from an expert on this, but I think that the command line flag that should work is -m, and the value would be either NT1 or SMB2.

smbclient -m SMB2

However, that doesn’t work for me. It may be related to this bug :

https://bugzilla.samba.org/show_bug.cgi?id=14939

This command did the job :

smbclient --option="client min protocol = CORE" --option="client max protocol = SMB2"

If that fails, you might try replacing SMB2 with SMB3 or NT1.

You may find it easier to enter the options that you find are successful in the [global] section of /etc/samba/smb.conf – for example

[global]
client min protocol = CORE
client max protocol = SMB2

FWIW, with the CORE / SMB2 options above, I can connect successfully to both Windows 2000 and Windows 98 servers.

[Member olsztyn]

ahoppin wrote:

I’ll need to tweak it a bit, since I presently have no machines aside from the antiX box that support anything past SMB1.

I was myself looking for SAMBA option parameter to specify SMB 1.0 in this script. On antiX Connectshares the parameter to specify SMB version is SAMBAOPT=vers=1.0 in Connectshares.cfg. And this worked great accessing my SMB 1.0 NAS servers.
However for smbclient used in the script developed by PPC I am still not clear what is the syntax for corresponding parameter.

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

[Member PPC]

Just another perspective on the problem of connecting to a shared folder – I’ve been developing a script that scans the network for shared folders and allows you to select to which one you want to connect to. For now it only works for shares that use smb > v.1. , it’s available here: https://www.antixforum.com/forums/topic/script-to-automagically-mount-a-samba-shared-folder-in-antix/page/2/#post-79130
I consider this script to be connectshare’s younger, fully GUI brother- it works more like what I remember from accessing a shared folder on Windows. For now, users have to always enter the credentials to access the shares, future versions may save the credentials and allow automatic log-in to the chosen share… It’s not what you want, but it may be an alternative way to get similar results…

P.

[Member PPC]

I just found an “one size fits all” solution to unmouting samba shares here: http://devplant.net/2016/02/29/unmounting-samba-shares-after-network-disconnect/comment-page-1/
Running this command solves the problem:
sudo umount -a -t cifs -l

So, a GUI to close zzzfm, unmount all shares and restart zzzfm will probably look something like this (untested):

pkill zzzfm & pkill spacefm & sleep 1 && sudo umount -a -t cifs - && sleep 1 && zzzfm

Edit1: why the “spacefm” part? Funny thing, when working on the script that configures zzzfm, I needed to close zzzfm to perform editions to it’s config file (manual changes to that file are overwritten automatically if zzfm is running)- and sometimes, those editions would not stick- I found out why after some frustrating hours- when zzzfm is killed, it can sometimes respawn as the process spacefm- nice, right?

Edit2: I was thinking how to implement this – probably on the part of the script that displays the “notification” that no network/shares are detected- I could create a function with this contents:
– check if zzzfm is running
– If zzz is running, kill it.
– Display a warning to save locally any open shared documents
– Perform the umount command and
– if zzz was running, launch it again

This implies no buttons, nothing more than this function- simply launching the script from the cli or the menu (using the provided .desktop file) can solve the problem… This approach has only one problem – it unmounts all shares- most people probably are not connected to shares hosted on more than one device, but just in case they are, they’ll have to remount the share that was not off-line… This solution, as everything in live has pros and cons…
All feedback is, as always, welcome!

P.

• This reply was modified 1 year, 1 month ago by PPC.
• This reply was modified 1 year, 1 month ago by PPC.
• This reply was modified 1 year, 1 month ago by PPC.

[Member Robin]

PPC wrote:

I literally learned from scratch how to create and manage samba shared folders, and then dug around to discover the perfect way to scan and mount those shared folders… Lots of time went to this script, already…

I do know exactly what you mean, I had to research on this very thing some years ago myself and remember quite well there were many pitfalls…
Maybe you could have saved some time when hanging around in IRC antiX translators channel occassionally, possibly I could have given you some hints. But as I’ve learned from your other thread, you have managed to research everything very well on your own already. Great job, PPC!

So many thanks also for your SAMBA tutorial tailored for antiX! This updates also my recollection of the needed steps on SAMBA.

Don’t bother if the force disconnect button(s) don’t make their way into the upcoming final version. Let’s implement it in the next update, e.g. along with the translations.

Windows is like a submarine. Open a window and serious problems will start.

[Member madibi]

I’ve just finished the test of the 1.4.b4 version, on a fresh install. All was fast and with no problems at all.

I followed your tips in order to install also your samba utility to “automagically mount samba shares” and in my private lan with antix shares + (old) LXLE shares, everything was fine.

In the next few days I’ll try some more experiment and I’ll let you know.

As always. thx for your precious job 🙂
m

• This reply was modified 1 year, 1 month ago by madibi.

[Member madibi]

Many thx for the tireless work you do for all of us.

This kind of guide on Samba is quite easy to find on the internet, not in the antix world where there was another strategy to have a samba connection.

The one suggested in this post is the “traditional” one.

I would like to highlight the great usefulness of the contents of point 4. In fact this removes all the problems that are very easy to encounter when trying to make the Samba network work.

On some occasions I find useful the testparm command to verify that I have not made any type of error and to have a dump of my service definitions (simply open the terminal and type: “testparm”).

[Member PPC]

@Robin – I tested the situation you described and you are right – zzzfm just freezes, when it loses contact with the shared folder.
I was thinking of a simple script to disable the network shares and restart zzzfm, if it’s running… But I’m not sure I can do more work on the script before launching the final Ft10 1.4… I literally learned from scratch how to create and manage samba shared folders, and then dug around to discover the perfect way to scan and mount those shared folders… Lots of time went to this script, already…

@olsztyn – I like your idea- but that implies changing the script…

Any takers on helping adapt the script? 🙂

P.

I recently discovered the joys of using a shared folder to move files between my computers. It was a pain to set the shared folder because I did not find, in the repository any GUI that I was able to use to configure samba. I did eventually find a real nice GUI (not yet available in the repository), but, what really allowed me to first configure and use a network shared folder was the excellent YouTube channel “learnlinux.tv”. I jotted down a few notes that I used to create this “How to”. Following it will allow anyone to create a network shared public folder.

How to create a public shared folder on your local network:
(Adapted from https://www.learnlinux.tv/setting-up-simple-samba-file-shares/)

1-Install samba with all it’s dependencies, Open a terminal and run this commands, enter your password if asked to:
sudo apt update && sudo apt install samba

2- Make sure samba is not being executed, on the terminal, run this command:
sudo service smbd stop

and then back up the default Samba configuration, just to be on the safe side (optional step)
sudo mv /etc/samba/smb.conf /etc/samba/smb.confBAK

3- Open samba configuration file for edition:
sudo geany /etc/samba/smb.conf

4- Edit the smb.conf file:
Delete any of the file’s contents and replace it with the text below, making sure that you replace the capitalized text with the appropriate values. FILESERVER and WORKGROUP do not have to be replaced, unless you what to and SHARED-FOLDER can/should be replaced with the name of the folder you want to be displayed (do not use spaces or special characters). The only value you have to adapt when editing this config file is /FULL/PATH/OF/FOLDER/TO/BE/SHARED that has to be replaced with the full path of the folder you want to be shared: for example- /home/ppc/PublicFiles
Optionally you can also replace the smbuser and smbgroup values with any values you select, but you’ll have to apply those exact values on the terminal commands that you’ll have to enter after editing the smb.conf file…

[global]
server string = FILESERVER
workgroup = WORKGROUP
security = user
map to guest = Bad User
name resolve order = bcast host

[SHARED-FOLDER]
path = /FULL/PATH/OF/FOLDER/TO/BE/SHARED
force user = smbuser
force group = smbgroup
create mask = 0664
force create mode = 0664
directory mask = 0775
force directory mode = 0775
public = yes
writable = yes

5- Save the config file and close geany and, on the terminal run this commands to create the required and group and user:

sudo groupadd --system smbgroup
sudo useradd --system --no-create-home --group smbgroup -s /bin/false smbuser

IMPORTANT: make really sure that the folder you what to share already exists and DO NOT SHARE YOUR HOME FOLDER!!! (but you can share any sub-folder inside your home- example: /home/ppc/downloads

6- Change ownership/permissions of the shared folder (replace /FULL/PATH/OF/FOLDER/TO/BE/SHARED with the appropriate address to your shared folder):
sudo chown -R smbuser:smbgroup /FULL/PATH/OF/FOLDER/TO/BE/SHARED
sudo chmod -R g+w /FULL/PATH/OF/FOLDER/TO/BE/SHARED

7- Make sure that samba is started:
sudo service smbd restart

That’s all.

How to access your shared folder from another device connected to your network:
You can now access your shared folder from any other computer connected to the same local network by entering, on the address bar of your file manager:
//IP.of.host.computer/SHARED-FOLDER
(replacing, of course, the “IP.of.host.computer” part with the real IP of the computer that is sharing the folder(s) and “SHARED-FOLDER” with the name you choose, for example //192.123.4.5/PublicFolder
How do you get the IP of the computer that is hosting the shared file? On that computer open the terminal and run this command:
ifconfig
On the line just below you network connection (ex: “eth0” if you are using a network cable or “wlan0” if you are using wi-fi) is a line staring with “inet”- the long string of four numbers separated by dots- that’s the IP you want.

Extra tip- sharing more folders/sharing protected folders:

You can add as many shared folders as you want, to the smb.conf file, taking care to remember to:
-always disable samba before editing the config file:
sudo service smbd stop

-edit the samba config file, adding and adapting the [SHARED-FOLDER] part included above. If you want to make it so the users accessing your shared folder can’t change it, make sure to change the last line “writable = yes” to “writable = no”:

Example:
[PROTECTED-SHARED-FOLDER]
path = /FULL/PATH/OF/FOLDER/TO/BE/SHARED/NUMBER/2
force user = smbuser
force group = smbgroup
create mask = 0664
force create mode = 0664
directory mask = 0775
force directory mode = 0775
public = yes
writable = no

-Save your editions to the config file
-Don’t forget to change ownership of the newly shared folder(s), adapting the commands from step 6.
-Restart samba:
sudo service smbd restart

Troubleshooting:
-Don’t forget- you are sharing the folder over your local network. You can’t access a shared folder over the internet (well, there are ways to do it, but it’s DANGEROUS. If you want to access your local files via the Internet, you’ll be better off using FTP)
-You can’t obviously access a shared folder if the device that hosts the shared folder is off or off-line… If the host of the shared folder is on-line but you can’t access the shared folder, make sure to run (on the host computer);
sudo service smbd restart
-Some File Managers get “frozen” if they lose connection to a mounted shared folder – zzzfm is one of such file manager- if that happens you’ll either have to re-enable the shared folder on the host computer and then unmount it on the remote computer or you’ll have to kill zzzfm and forcibly unmount the mount point… Yeah… it’s not pretty… You’ll have to force zzzfm to “let it go, let it go” (yes, it’s a “Frozen” joke)

P.

• This topic was modified 1 year, 1 month ago by PPC.
• This topic was modified 1 year, 1 month ago by PPC.
• This topic was modified 1 year, 1 month ago by PPC.

[Forum Admin SamK]

Connectshares does not provide a name resolution service (DNS), one must already exist in order that Connectshares can make use of it.

Simplified Overview of a Domestic Set Up
LAN system names do not appear in a global DNS. To overcome this, both global and local name resolution services are needed.

A global DNS handles everything on the outside of the router/firewall/switch (R/F/S) i.e. the world.
Because the R/F/S unit it always powered up, world name resolution is always available via a global DNS. The R/F/S often defaults to using the DNS specified by the ISP. Some offer the ability to specify a global DNS of the user’s choice.

A local DNS handles everything on the inside of the R/F/S i.e. the LAN.
Many home units do not provide a DNS for the LAN and therefore name resolution is unavailable within it.

A Potential Way Forward
An often used method of providing name resolution for LAN systems is to install a DNS package on a system that is always powered up and running (usually some form of server hardware). In that way the LAN name resolution service is always available. One benefit of this method is the local name resolution service is available to Windows and Linux systems in the LAN and is independent of the configuration of apps such as Samba and NFS. It is available to all programs that can utilize a name resolution service.

It might be worth looking at an app named dnsmasq. It is a tiny download from the repo. Additionally is uses negligible amounts of CPU/RAM/disk-space. It is is easy to set up via a single config file. It is good fit with the antiX philosophy.

Outcome
The result is Connectshares is able to make use of the LAN name resolution service and thereby works with either a server ip address or a server name.

If wanted Connectshares can also:
• Automatically mount remote shares at antiX login or on request,
• Automatically unmount shares at logout or on request,
• Make shares available to all apps and file managers without being tied to a specific file manager,
• Make shares available in both GUI and Console (text only) environments,
• Connect to shares on remote servers that use versions 1.0 and 2.1 or higher of the CIFS/SMB protocol,
all without the cumbersome error prone method of editing fstab or typing commands.

As always, it’s your system, your choice.

[Member madibi]

Many thanks @PPC
I’ll try later in the afternoon the new version, included facility for the samba shares.
I’ll have to handle my grandpa’s job first 🙂
m

[Member PPC]

Last night I finished the latest FT10 beta. It’s available here: https://gitlab.com/antix-contribs/ft10-transformation/-/raw/main/packages/ft10-transformation_1.4.b4_all.deb
Changes:
-includes some bug fixes on the update reminder and the zzzfm configuration script
-a “Shared Folders” script, with a .desktop, already added to zzzfm bookmarks – at first run, this script offers to install the needed dependencies- you’ll have to rerun the script for it to start after that. If the dependencies are already installed, the script scans your network and displays all shared folders (if they use samba > v.1). click the shared folder that you want to connect to and a window to enter the credentials (user and password) will be displayed. If you shared folder does not require any password, simply click the “ok” button (or press enter) to ignore that step – the selected shared folder will be instantly displayed in zzzfm (I hope this works for you madibi 🙂
P.S.- please note that this script DOES NOT allow you create shared folders, only to access already existing shared folder on your local network. This script can be considered the connectshares younger and fully GUI brother…

To do’s:
– improve localization – but I probably won’t include the automatic translations Robin so kindly provided- I don’t have time to test them…
– improve some details, and after that, the final v. 1,4 will be made available…

P.

[Member ahoppin]

Thanks again to all who posted here. I found a simple solution to this problem – let Antix be the Samba hub for the other machines.

Adding the lines

server min protocol = CORE
server max protocol = SMB2
client min protocol = CORE
client max protocol = SMB2

to /etc/samba/smb.conf allowed every machine on the LAN, Windows and old Linux, to browse Samba shares on Antix.

Note that I’m using only Windows 98 and Windows 2000, nothing later. The above fix might cause problems with later versions of Windows, or at least compromise security with them. Use at your own risk.

I’m far from a networking expert, but my guess is that Samba 4.13.13 in Antix couldn’t negotiate a protocol with the old clients until it was limited by the protocol statements. Smbclient on the old Puppy 5 box reported that “protocol negotiation failed.”

I suspect that Samba’s developers didn’t test with old Windows versions, maybe because they’re not commonly available any more, and hardly anyone still uses them anyway.

CUPS PRINTING BONUS: The Win98 machine hosts a couple of ancient printers. Adding the above client protocol lines to /etc/samba/smb.conf also got Antix CUPS working with those printers.