Porteus-V5.0 - SMB broken after RC3 ?
Porteus-V5.0 - SMB broken after RC3 ?
What changed in the SMB department between RC3 and 'Final' v5.0 ? I can no longer access my SMB shares on old XP machine
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
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
- ncmprhnsbl
- DEV Team
- Posts: 3939
- Joined: 20 Mar 2012, 03:42
- Distribution: v5.0-64bit
- Location: australia
- Contact:
Porteus-V5.0 - SMB broken after RC3 ?
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
so, to test this, either getpkg perl or activate 05-devel.xzm
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44
- AcnapyxoB
- Samurai
- Posts: 191
- Joined: 24 Dec 2014, 10:15
- Distribution: Porteus 5.01
- Location: Planet Earth
Porteus-V5.0 - SMB broken after RC3 ?
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
- ncmprhnsbl
- DEV Team
- Posts: 3939
- Joined: 20 Mar 2012, 03:42
- Distribution: v5.0-64bit
- Location: australia
- Contact:
Porteus-V5.0 - SMB broken after RC3 ?
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
- AcnapyxoB
- Samurai
- Posts: 191
- Joined: 24 Dec 2014, 10:15
- Distribution: Porteus 5.01
- Location: Planet Earth
Porteus-V5.0 - SMB broken after RC3 ?
I noticed something strange (it is discussed in another topic) I could access shares from Porteus 5.0rc3 XFCE after adding blueman module !?ncmprhnsbl wrote: ↑18 Jul 2022, 06:07so you could try adding (any of) those in case they're needed run time..
Porteus v5.01 KDE x86_64
- ncmprhnsbl
- DEV Team
- Posts: 3939
- Joined: 20 Mar 2012, 03:42
- Distribution: v5.0-64bit
- Location: australia
- Contact:
Porteus-V5.0 - SMB broken after RC3 ?
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
- AcnapyxoB
- Samurai
- Posts: 191
- Joined: 24 Dec 2014, 10:15
- Distribution: Porteus 5.01
- Location: Planet Earth
Porteus-V5.0 - SMB broken after RC3 ?
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
Porteus-V5.0 - SMB broken after RC3 ?
not sure why AcnapyxoB would hijack my thread .. but cifs not even working for me
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
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:
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)
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)
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.
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)
- AcnapyxoB
- Samurai
- Posts: 191
- Joined: 24 Dec 2014, 10:15
- Distribution: Porteus 5.01
- Location: Planet Earth
Porteus-V5.0 - SMB broken after RC3 ?
Sorry, Buurman,
I'm not trying to "hijack", I'm trying to find a solution.
Porteus v5.01 KDE x86_64
-
- Ronin
- Posts: 1
- Joined: 27 Aug 2022, 18:20
- Distribution: 5.0 gnome
Porteus-V5.0 - SMB broken after RC3 ?
I'm struggling with the same problem. cifs isn't working as well. Same error. Have any solutions turned up lately?