Why would SAMBA server not work in 64-bit os but works 32?

[houndstooth]

If I boot a 32 distro on a 64 machine, I can host SAMBA shares from it. SAMBA is not working in 64 distros. Is that another feature miss or am I missing a setting?

[rockedge]

Which 64 distro is giving problems? I have had probelms in Fossapup64-9.5 but so far F96-CE_1 is performing well as a SAMBA server/client.

[houndstooth]

Which 64 distro is giving problems?

Definitely Fossa64 & I believe back to Xenial at LEAST 2 of 3.

Not sophisticated enough to hone a single release, I've been working-feature hopping.

I was looking at KLV Jammy but can't grasp the bloat, usually running 200-400 MB all in ram.

[Clarity]

I am going to assume you are using @666philb's FossaPup64 posted here on the forum. If so, could you please post what you see when you type this in a terminal

Code: Select all

smbclient -U% -L localhost

I have not had any issues with any WoofCE PUP that come with SAMBA pre-installed, thus far over the past years. Also, what do you see when you type this in the console?

Code: Select all

findsmb

I also am making the assumption that SAMBA is pre-installed as almost EVERY forum disto has SAMBA pre-installed along with a simple activation script in the PUP's Menu .... Menu>Network>SAMBA Sinple Management which allows a simple definition tool as well as a server actuator/de-actuator (namely PUPs/DOGs/EASY/etc as there are only a handful at most which do not have SAMBA server pre-installed).

The PUP developers have made this simpler than anything found in Microsoft/Apple

There is NO installation requirement as SAMBA is an OOTB subsystem service in these forum's distros equally as important as the system kernel is. For many/most of us, its used extensively.

The KL series of forum distros DO NOT have SAMBA buitl-in like the other forum distros. You will notice it does NOT have a "Network' category in its Menu. But, SAMBA in KLV is expected in an upcoming release to avoid installation issues. This has been requested.

Let us know

[houndstooth]

@Clarity I hop, in Xenial now but will post Fossa later. Same malfunction but maybe installation differences?

It's really a game of 'what functionality do I need today' & since I'm just browsing & doing file management Xenial sufficies.

If I needed builtin Android or SD access it would be Fossa. If I needed SAMBA too it would be 32 bit.

Code: Select all

root# smbclient -U% -L localhost
Connection to localhost failed (Error NT_STATUS_UNSUCCESSFUL)
root# 

root# findsmb
bash: findsmb: command not found
root# 

Please quote/mention me so I see your replies.

[bigpup]

Fossapup64 9.5 has this in the bug fixes:

04/07/2021 samba on/off fix ... @rmcellig1 & Clarity

To install bug fixes.

Quickpet icon on desktop.
Quickpet -> Info -> Fossapup updates

May have to reboot, making sure to update the save, so the updates are now being used.

[Clarity]

HI @houndstooth

1. The smbclient response says your SAMBA is NOT running on your PC

2. The 2nd says you are missing some of the expected utilities found in PUPs.

Consider

1. Run just as @bigpup advises.

2. Use the SAMBA Simple Management to start SAMBA and report back here after starting SAMBA with the outcomes.

BTW: MY FossaPUP64 has findsmb command in its system. Are you sure you are running the "official released" version of FossaPup64?

[houndstooth]

Fossapup64 9.5 has this in the bug fixes:

04/07/2021 samba on/off fix ... @rmcellig1 & Clarity

On/off appears to work.

The problem is connecting to shares on the Puppy host.

It's a transparent error.

[houndstooth]

@Clarity I see. When I first issued the commands, I did so outright without SAMBA running.

I'll try it here again still in Xenial64 today (the host can find SAMBA shares on itself):

Code: Select all

root# smbclient -U% -L localhost
Domain=[WORKGROUP] OS=[Windows 6.1] Server=[Samba 4.4.4]

	Sharename       Type      Comment
	---------       ----      -------
	SpotDownloads   Disk      
	IPC$            IPC       IPC Service (Puppy Samba Server)
	CUPS-PDF        Printer   CUPS-PDF
Domain=[WORKGROUP] OS=[Windows 6.1] Server=[Samba 4.4.4]

	Server               Comment
	---------            -------
	SV-XENIAL64JWM       Puppy Samba Server

	Workgroup            Master
	---------            -------
	WORKGROUP            SV-XENIAL64JWM
root# 

findsmb is not in the ppm.

[houndstooth]

@Clarity more information in Fossa:

Code: Select all

root# smbclient -U% -L localhost

	Sharename       Type      Comment
	---------       ----      -------
	HomeSpot        Disk      
	IPC$            IPC       IPC Service (Puppy Samba Server)
	CUPS-PDF        Printer   CUPS-PDF
SMB1 disabled -- no workgroup available
root# 

SMB1 disabled?

Code: Select all

root# findsmb

                                *=DMB
                                +=LMB
IP ADDR         NETBIOS NAME     WORKGROUP/OS/VERSION 
---------------------------------------------------------------------
192.168.1.4     SV-FOSSA64JWM +[	WORKGROUP     ]
192.168.1.237   BRWA8A7955C7362 Unknown Workgroup
root#

[Clarity]

smb1 should not be used. There are some security issues that most all of industry moved on to smb2/smb3 years ago. Most units or NAS or other programs/apps in the world also moved on quite some time ago.

Current PUP-forum versions use the secure current versions of SAMBA.

[houndstooth]

smb1 should not be used. There are some security issues that most all of industry moved on to smb2/smb3 years ago. Most units or NAS or other programs/apps in the world also moved on quite some time ago.

Current PUP-forum versions use the secure current versions of SAMBA.

How do I choose smb2 or smb3 instead?

This is the main 64 Fossa among the newest releases I assume.

[Clarity]

If yyou are referring to th message output by 'smbclient', that is merely a warning that the SAMBA is not configured for SMB1 access. But does work for smb2/smb3. Thus it serves smb2/smb3 requests...not smb1.

Namely, your SAMBA is already built with this in mind.

[houndstooth]

If yyou are referring to th message output by 'smbclient', that is merely a warning that the SAMBA is not configured for SMB1 access. But does work for smb2/smb3. Thus it serves smb2/smb3 requests...not smb1.

Namely, your SAMBA is already built with this in mind.

OK, but bear in mind SAMBA in Fossapup is NOT working as corroborated by Rockedge. If there's a secret to make it work, that's what we need. It appears to work, but clients aren't finding the shares.

If your patch is for something other than on/off it might be the difference, but I assumed that's what it is.

[wizard]

@houndstooth

bear in mind SAMBA in Fossapup is NOT working

I have had Puppy samba file servers running as far back as Puppy 4.12. I've only had one samba issue with Fossapup64 9.5 as a server and that involved connecting with ES File Explorer, an Android file manager. Members @rcrsn51 and @clarity have been a big help in the past.

The method that works best for me is: Keep it simple, first, make it work and then make changes.
If you like, I can walk you through making it work. You'll need two computers on the same LAN running FRESH installs of Fossapup64.

wizard

[houndstooth]

Hello @wizard,

Yes, it's Android to the main Puppy 64 distros.

In this scenario, 2 Android clients can't find the shares while in 32 pups it's cake.

I'm not testing pup:pup because it's not the goal, but SAMBA service is starting & 64 pup hosts can see their own shares.

[wizard]

@houndstooth

My Puppy media server is running Bionic64 and I access with pc, android tablets or phones. My test Puppy is Fossapup64 and can do the same, except with that old version of ES File Explorer. Have had issues with Android streaming on Fossapup64.

Thanks
wizard

[Clarity]

Just a note on my Android use for past years. There are more clients today than when I started, but my current Android apps, installed from the Play Store, I use, WIRELESSLY, via their smb clients are

• Media

  • VLC

• File Managers

  • Solid Explorer ... mostly

  • Total Commander

  • Cx File Explorer

I have never had a reason to connect via USB cable to any LAN PC from my cell phones. In my case, all hotspot as well as all smb and dlna needs for local PC access on my home LAN is not required for any/all of the things I do...currently. Home wireless ethernet bandwidth is more than adequate and uses 2.4/5/6/6e transmits within the home.

Hope this is helpful for things that work with forum distros that come equipped with SAMBA out-of-the-box.

[houndstooth]

I've read about streaming multimedia players but have yet to get one going myself. If VLC can stream on Android from a Linux share that could be useful... or even direct from the Internet itself. I remember playing a file from a share on Android once & it copied to device locally without direction.

One of those three file managers could be the 2nd I tried, but there are at least two others there worth the attempt if Android client compatibility with 64pups is indeed the problem.

I just made a 32pup Android:SAMBA connection easy-peasy. 64 is still elusive.

[wizard]

@houndstooth

If VLC can stream on Android from a Linux share that could be useful.

It can, and even better just connect to the samba share with your file manager, open the media file, most of them (file managers) will ask you what media player you want it to play in, if you have VLC, you can choose it. This is how I use my media files.

wizard

[houndstooth]

@wizard there's the caveat to me about copying the file, but I also wonder about avoiding the Youtube Android client with VLC. I use it out of builtin convenience but it's not my preference.

[houndstooth]

SAMBA is working pup:pup including 64 so my new hypothesis is 64 compatibility with Android clients.

The challenge is it does not appear to be the version of SAMBA because old SAMBAs work in 32, & likewise not the version of the clients installed new from Play Store.

Perhaps there is an esoteric setting in 64 pups.

[wizard]

@houndstooth

Your older apps probably can only use smb1 protocol which is not secure. For that reason newer versions of Samba have it disabled by default. If you find you have a network device or must have app that still needs smb1, and you can't upgrade, you can enable it.

-On the server, open the file: smb.conf
-Add this line in the global section: server min protocol = NT1
-save the file
-turn samba off, then back on

Again, smb1 is not a secure protocol.

wizard

[houndstooth]

@wizard there's a step missing in understanding, humbly my deficiency.

I should assume noarch & check SAMBA versions in the 64 pups to determine if a newer version(s) is/are not using smb1?

this again on the assumption smb1 is what makes 32 pups Android compatible?

My take if this is correct is: there is no way to use SAMBA with newer/upgraded host software unless Android clients support 2/3 protocols.

[Clarity]

Ha! @wizard you just 'may' have shined a light on this.

@houndstooth, which Android version are you running on your phone/tablets?

Reason: I seem to remember that old Android versions and the apps downloaded for those versions from the app store "may" be a cause of the behavior.

I also MUST ask:

1. AFter adding VLC to your phone are you able to see and media that are shared from your FossaPup64?

2. What about the other Android filemanager app I mentioned, are you able to set it up to see all of your LAN PCs that share files?

Curious.

[wizard]

@houndstooth

It's not related to 32 or 64bit OS versions, it's only related to whether smb1 is enabled or disabled

there is no way to use SAMBA with newer/upgraded host software unless Android clients support 2/3 protocols.

Not correct.

Here's an example:
-server is Fossapup64 9.5 (which has smb1 disabled by default)
-Android phone, old version of ES File Explorer that can only use smb1

ES File Explorer can't connect unless I do the following on the Fossapup64 9.5 server:

-On the server, open the file: etc/samba/smb.conf
-Add this line in the global section: server min protocol = NT1
-save the file
-turn samba off, then back on

Now ES File Explorer or any other app that needs smb1 can connect to the server

wizard

[houndstooth]

@Clarity, for network sharing I'm usually in 8.1. When I exhaust the other possibilities I'll report here again.

1st:
your alternate Android clients

2nd:
defaulting to smb1 just to see if any Android:64pup connection works

[Clarity]

Hi @houndstooth. Glad you've got this all sorted.

iS "BRWA8A7955C7362", seen in your findsmb report, have resources shared for your LAN users too? Great it so.

See it via this command (assuming you know your username and password on BRWA8A7955C7362)

Code: Select all

smbclient -L 192.168.1.237

This will ask you for the password to use. if its the same as your PC, to see your resources shared you could merely use

Code: Select all

smbclient -U% -L 192.168.1.237

Enjoy

[houndstooth]

@Clarity 192.168.1.237 is a printer.

I am not sure what I can do with it on a SAMBA. I boot Windows to use it. I saw some arkane Linux drivers on the manufacturer's website, but if it's not as complete as the Windows gui it's another low priority technical hurdle.

I can also print from Android, but that app includes a severe privacy violations, namely location tracking (TO PRINT ON YOUR LOCAL NETWORK!) & access to your printed files uploaded to their servers.

[Clarity]

Never did a print directly from Android. On the many occasions of use, I merely upload to the SAMBA PC and manipulated files there.

Maybe other members have used an Android on their LANs that can help.