Porteus-V5.0 - SMB broken after RC3 ?

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
Buurman
White ninja
White ninja
Posts: 25
Joined: 28 Oct 2019, 18:00
Distribution: ver5

Porteus-V5.0 - SMB broken after RC3 ?

Post#1 by Buurman » 16 Jul 2022, 19:34

What changed in the SMB department between RC3 and 'Final' v5.0 ? I can no longer access my SMB shares on old XP machine :cry:
smb.conf still has a line about min = NT1

I can see the windows shares but not access
if I connect to smb://1.2.3.4 (ip is example)
I see the windows computer (listing e.g. C$, D$, the shares)
but when trying to access the actual shares I get:

Failed to mount Windows Share: Invalid argument [OK]
...than
The specific location is not mounted [OK]

-edit, looks like samba not being the culprit directly but rather mount.cifs ? adding vers=1.0 (trying to manually mount it ..instead of through pcmanf) no change, still not working

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 3924
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

Porteus-V5.0 - SMB broken after RC3 ?

Post#2 by ncmprhnsbl » 18 Jul 2022, 00:07

one thing that changed that might be the problem: perl was moved to 05-devel ..
so, to test this, either getpkg perl or activate 05-devel.xzm
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
AcnapyxoB
Samurai
Samurai
Posts: 191
Joined: 24 Dec 2014, 10:15
Distribution: Porteus 5.01
Location: Planet Earth

Porteus-V5.0 - SMB broken after RC3 ?

Post#3 by AcnapyxoB » 18 Jul 2022, 04:56

ncmprhnsbl wrote:
18 Jul 2022, 00:07
either getpkg perl or activate 05-devel.xzm
Already tested (with 05-devel) would not be of that.
By the way with cifs I can access my shares on NAS:

Code: Select all

su
toor
mkdir /mnt/smb
mount -t cifs -o username="USER" //IP_ADDRESS/STORAGE /mnt/smb
Porteus v5.01 KDE x86_64

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 3924
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

Porteus-V5.0 - SMB broken after RC3 ?

Post#4 by ncmprhnsbl » 18 Jul 2022, 06:07

AcnapyxoB wrote:
18 Jul 2022, 04:56
Already tested (with 05-devel) would not be of that.
ah thanks, scratch that idea then..
something else to try would be to pull the standard samba package from slackware 15.0 and see if that makes any difference ..
the reason we decided to build our own was to avoid messing with kerberos..
there's also some other packages i've interpreted as make deps: python-dnspython, python-markdown, rpcsvc-proto
so you could try adding (any of) those in case they're needed run time..
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
AcnapyxoB
Samurai
Samurai
Posts: 191
Joined: 24 Dec 2014, 10:15
Distribution: Porteus 5.01
Location: Planet Earth

Porteus-V5.0 - SMB broken after RC3 ?

Post#5 by AcnapyxoB » 18 Jul 2022, 16:01

ncmprhnsbl wrote:
18 Jul 2022, 06:07
so you could try adding (any of) those in case they're needed run time..
I noticed something strange (it is discussed in another topic) I could access shares from Porteus 5.0rc3 XFCE after adding blueman module !?
Porteus v5.01 KDE x86_64

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 3924
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

Porteus-V5.0 - SMB broken after RC3 ?

Post#6 by ncmprhnsbl » 18 Jul 2022, 23:22

AcnapyxoB wrote:
18 Jul 2022, 16:01
I could access shares from Porteus 5.0rc3 XFCE after adding blueman module !?
yeah, that is strange..
here's something that might be relevent: https://www.linuxquestions.org/question ... 175714661/
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
AcnapyxoB
Samurai
Samurai
Posts: 191
Joined: 24 Dec 2014, 10:15
Distribution: Porteus 5.01
Location: Planet Earth

Porteus-V5.0 - SMB broken after RC3 ?

Post#7 by AcnapyxoB » 19 Jul 2022, 05:02

ncmprhnsbl wrote:
18 Jul 2022, 23:22
here's something that might be relevent
Upgraded GVFS to gvfs-1.50.2-x86_64-1.txz. No success (can't access samba shares) - Porteus 5.0 KDE x86_64.
Porteus v5.01 KDE x86_64

Buurman
White ninja
White ninja
Posts: 25
Joined: 28 Oct 2019, 18:00
Distribution: ver5

Porteus-V5.0 - SMB broken after RC3 ?

Post#8 by Buurman » 11 Aug 2022, 05:40

not sure why AcnapyxoB would hijack my thread .. but cifs not even working for me

Code: Select all

mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
haven´t really found enough time to track this either .. sigh (05-devel is already inplace .. no change indeed)
only thing dmesg gives after cifs

Code: Select all

[ 2176.879593] Malformed UNC in devname

edit--

tried to mount the (different) windows-folders directly (not just the whole share)
either it just waits endlessly on connect (ctrl-c) or it gives:

Code: Select all

[ 2324.574643] CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount.
edit2--

sigh .. the vers=1.0 thingie is a pickle too .. for gods sake =username=bladiebla,vers=1.0
not --vers=1.0 or -vers=1.0 or plain vers=1.0 .. no .. ,vers=1.0

so .. now got something mounted (like the thread hijacker)

User avatar
AcnapyxoB
Samurai
Samurai
Posts: 191
Joined: 24 Dec 2014, 10:15
Distribution: Porteus 5.01
Location: Planet Earth

Porteus-V5.0 - SMB broken after RC3 ?

Post#9 by AcnapyxoB » 11 Aug 2022, 08:27

Buurman wrote:
11 Aug 2022, 05:40
not sure why AcnapyxoB would hijack my thread
Sorry, Buurman,
I'm not trying to "hijack", I'm trying to find a solution.
Porteus v5.01 KDE x86_64

syntaxerror
Ronin
Ronin
Posts: 1
Joined: 27 Aug 2022, 18:20
Distribution: 5.0 gnome

Porteus-V5.0 - SMB broken after RC3 ?

Post#10 by syntaxerror » 27 Aug 2022, 18:56

I'm struggling with the same problem. cifs isn't working as well. Same error. Have any solutions turned up lately?

Post Reply