samba 2

[john.mcmstr]

Hi
I am having a strange problem.
Just found Antix and I love it
However I am unable to mount a windows10 share from the 64 bit version
I get an error(22) invalid argument
Checking the kernel log I see that the vers=2.0 argument is unknown
This works from the 32 bit version ?
tried on several different machines and vmplayer and Virtualbox with the same results
Any ideas?

[Jerry3904]

Hi, and welcome. I'm going to move this to the antiX Forum.

[dolphin_oracle]

often with windows10 you must specify a username and password, even if the share is not password protected.

I've got a windows10 share at home. I'll try out antiX on it tonight and see if it works, but I've done this in the past without issue. I use the "connectshares" utility in antiX for this.

if you want to post the command you were using to mount the share I can try that too.

one more option: spacefm in antiX can be configured to mount samba shares as well.

[john.mcmstr]

Hi
Thanks for the response
I am using the username and password variables on the mount line
I can use the exact same mount line on 32 bit version and it works
I tried "connectshares" but cannot find a way to change to samba version 2 or higher
Windows has stopped using samba 1

[john.mcmstr]

Hi
Command is
mount -t cifs //192.168.1.10/stuff /mnt -o username=XXXXX,pasworrd=XXXXXX,vers=2.0
Thanks

[dolphin_oracle]

Hi
Command is
mount -t cifs //192.168.1.10/stuff /mnt -o username=XXXXX,pasworrd=XXXXXX,vers=2.0
Thanks

Ok thanks. I'll investigate when I get home tonight, unless someone else gets to it first.

[john.mcmstr]

Hi to all.
Any help / update ?
Am out of ideas
Thanks
John

[paul1149]

Not a direct answer, but you can activate smb 1 in Windows.

[john.mcmstr]

Anyone?
smbclient works fine with the -m SMB3 option
Thanks

[dolphin_oracle]

right now I can't duplicate your problem.

here's the output of "findshares", which finds my shares OK

Code: Select all

demo@antix1:~
$ findshares
Local Host Name  = antix1
Local IP Address = 192.168.1.133 on wlan0

Scanning from 192.168.1.133 on wlan0
Samba/Windows Shares
--------------------------------------------------------------------------------
WORKGROUP
    LINKSYS16521     192.168.1.100     Samba 3.0.28a
	IPC$                           IPC Service (Samba 3.0.28a)

WORKGROUP
    MX               192.168.1.104     Samba 4.5.16-Debian
	print$                         Printer Drivers
	IPC$                           IPC Service (Samba 4.5.16-Debian)
	HP_LaserJet_Pro_MFP_M225dw     HP_LaserJet_Pro_MFP_M225dw

HOME
    DESKTOP-8HGT9DD  192.168.1.110     

HOME
    MEDIAPC          192.168.1.142     
	ADMIN$                         Remote Admin
	baritone play along            
	C$                             Default share
	E$                             Default share
	IPC$                           Remote IPC
	media                          
	print$                         Printer Drivers
	scans                          
	Users                          


Server          Remote Resource        Local Mount Point
--------------------------------------------------------------------------------
192.168.1.142   media                  /mnt/mediapc/media\040on\040mediapc

and using the connectshares tool it connects OK too. (you can see the mount point). The mount command connectshares uses doesn't specify a type of samba share at all.

a manual mount with this also works

Code: Select all

sudo mount -t cifs //mediapc/media /mnt/test

the share is hosted by a windows 10 PC. I've done no special configuration to it.


this also works (modification of your mount command...in your post password is spelled wrong but I figure thats just a typo in your post.

Code: Select all

sudo mount -t cifs //mediapc/media /mnt/test -o username=fred,password=fred

So I'm not sure where your problem actually lies. Unfortunately network issues aren't my speciality but I was really hopping to find an issue with my antiX setup since I have the windows server, but I haven't found the problem.