Failed to mount windows share invalid argument

A very similar question has been asked before by robazefa, but no one answered it.
For the last month or so, my Ubuntu 14.04 LTS box has been been unable to open a couple of folders shared from external drives on a PC running Win 8.1 on a home network.

Through Files on the Unity desktop, I can browse the network, access the workgoup, access the Win 8.1 box, see and access its shares except the folders on its external drives. They appear on the list and I could access them without a problem a couple of months ago, but now I get a dialogue box with Unable to access location - failed to mount Windows share: Invalid argument message, with only the option to click OK.

These folders are readily accessible now from other Win 7 and 8 PCs on the network, but the same Invalid argument error now appears on the only other Linux box on the network which runs Mint Cinnamon.

My question is which argument is in invalid and how can I validate it?

A very similar question has been asked before by robazefa, but no one answered it.
For the last month or so, my Ubuntu 14.04 LTS box has been been unable to open a couple of folders shared from external drives on a PC running Win 8.1 on a home network.

Through Files on the Unity desktop, I can browse the network, access the workgoup, access the Win 8.1 box, see and access its shares except the folders on its external drives. They appear on the list and I could access them without a problem a couple of months ago, but now I get a dialogue box with Unable to access location - failed to mount Windows share: Invalid argument message, with only the option to click OK.

These folders are readily accessible now from other Win 7 and 8 PCs on the network, but the same Invalid argument error now appears on the only other Linux box on the network which runs Mint Cinnamon.

My question is which argument is in invalid and how can I validate it?

Hi,
When trying to connect to samba share with nautilus where password is needed, I get

Unhandled error message: Failed to retrieve share list from server: Invalid argument

I just installed my system yesterday, so I didn’t do anything that could mess up with config. I installed samba, smbclient, polkit, gvfs, gvfs-smb. And used default samba config as my config.

Running nautilus from command line didn’t show any errors or warnings.

In journalctl I only see this error:

Kerberos auth with 'adrian@WORKGROUP' (WORKGROUP\adrian) to access '(IP)' not possible

I can connect to the share with smbclient using the same name and workgroup without any issue. On ubuntu connecting to samba share with nautilus worked out of the box.

Mounting with cifs also works without any issue, but I don’t want to mount share on startup or mount it everytime from command line

I also tried

client min protocol = CORE
server min protocol = CORE

but it also didn’t work out.

Samba and smbclient version:

Nautilus version:

Anyone could help?

EDIT: connecting to sftp share with nautilus works flawless. I’m getting prompt for password and share mounts without any issue. So it must be something with samba or gvfs-smb

Last edited by Arko (2022-03-28 12:54:27)

Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.

Frederick Turner

Failed to mount Windows share: Invalid argument

I have problems to connect to the server ( Windows share ) at my workplace. The IT department have no experience with Linux Mint and therefore cannot help me how to connect from home.

They instructed me that the address is smb://abc.defg.hi/<SHARE>

<SHARE> = Name of the Windows share

They said that I’m then prompted to enter my username, which I would have to do as follows:

DEFG/username

After then entering my password I get the following error message: «Failed to mount Windows share: Invalid argument»

What am I doing wrong? I’m using the Linux Mint 17.2 with Cinnamon. Nemo is the file manager. I accessed the GUI via File >> Connect to Server

Do I have to enter the name of the Windows share right behind the server address as in smb://abc.defg.hi/<SHARE> or should the server address be just smb://abc.defg.hi/ ?

As I don’t get a prompt but have to insert my User Details straight away, do I also have to fill in the Domain name (probably with DEFG)?

Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.

Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.

Cosmo.

Level 24
Level 24
Posts: 22968
Joined: Sat Dec 06, 2014 7:34 am

Re: Failed to mount Windows share: Invalid argument

Post

by Cosmo. »

Frederick Turner wrote:Do I have to enter the name of the Windows share right behind the server address as in smb://abc.defg.hi/<SHARE> or should the server address be just smb://abc.defg.hi/ ?

That shouldn’t matter in regard of connectivity.

To make it work you might try one of the following:

1. instead of abc.defg.hi enter abc.defg.hi.local

2. instead of abc.defg.hi enter the IP-address

3. Edit /etc/samba/smb.conf, find the line

Code: Select all

name resolve order = lmhosts host wins bcast

and place lmhosts behind bcast

Regarding the username: I don’t think that you have to enter DEFG/username, but only username (but I don’t know anything about your network of course). If DEFG is the domain name, enter it into the respective field.

Frederick Turner

Re: Failed to mount Windows share: Invalid argument

Post

by Frederick Turner »

In the end, I had to enter DEFG.HI as the domain name and my user name as user name. The server address had to be set abc.defg.hi without smb:// .

Cosmo, Thanks for your help!

Solution 1

I resolved this by using the IP address instead of the server name.

Solution 2

This sounds like a regression. An Ubuntu bug report and upstream bug report has already been made for it. It might be best to set yourself as «affected» and ask what information is needed. also clearly state that this is a regression. Regressions get fixed faster.

Workaround #1

You can try manually opening the share with nautilus (the file manager)

nautilus smb://ServernameOrIp

Workaround #2

You can try mounting it with smbclient. Example:

smbclient –L geekmini –U geek

Where geekmini is pc and geek is username.

Create mountpoint:

sudo mkdir /media/Video

Actually mounting the drive:

mount –t cifs –o username=geek,password=thepass //geekmini/root /media/Video

Good luck and let me know what works!

Solution 3

edit /etc/samba/smb.conf

and Disable SMBv1 and use SMBv2 works for me

like min protocol = SMB2

Solution 4

My samba share has started to produce this same error after the group the shared directory had, and was shared to, has been erroneously deleted.

It got back to work OK after the situation with the disappeared group was resolved.

One could resolve it giving the share another group in the smb.conf file, but I just recreated it on the system level.

Hope this will help.

Related videos on Youtube

How to fix Failed to mount '/data' (Invalid argument) (100% working method)

03 : 21

How to fix Failed to mount ‘/data’ (Invalid argument) (100% working method)

[ How to fix  ] [ recovery mode  ] E:failed to mount /efs (Invalid argument)

03 : 51

[ How to fix ] [ recovery mode ] E:failed to mount /efs (Invalid argument)

How to Fix E:failed to mount /cache (Invalid argument) on ZenFone 5 (Asus T00F) ?

02 : 14

How to Fix E:failed to mount /cache (Invalid argument) on ZenFone 5 (Asus T00F) ?

E:failed To mount /efs (invalid Argument  (Any Samsung )

01 : 58

E:failed To mount /efs (invalid Argument (Any Samsung )

How to Mount a Windows Share on Linux Video Tutorial

09 : 17

How to Mount a Windows Share on Linux Video Tutorial

How to fix E:failed to mount /efs (Invalid argument) in recovery mode EFS

09 : 07

How to fix E:failed to mount /efs (Invalid argument) in recovery mode EFS

Ubuntu: Failed to mount Windows share: Invalid argument (2 Solutions!!)

02 : 27

Ubuntu: Failed to mount Windows share: Invalid argument (2 Solutions!!)

Comments

  • A very similar question has been asked before by robazefa, but no one answered it.
    For the last month or so, my Ubuntu 14.04 LTS box has been been unable to open a couple of folders shared from external drives on a PC running Win 8.1 on a home network.

    Through Files on the Unity desktop, I can browse the network, access the workgoup, access the Win 8.1 box, see and access its shares except the folders on its external drives. They appear on the list and I could access them without a problem a couple of months ago, but now I get a dialogue box with Unable to access location - failed to mount Windows share: Invalid argument message, with only the option to click OK.

    These folders are readily accessible now from other Win 7 and 8 PCs on the network, but the same Invalid argument error now appears on the only other Linux box on the network which runs Mint Cinnamon.

    My question is which argument is in invalid and how can I validate it?

    • I had this start happening «suddenly» too. I wonder which of the Linux updates broke things…

    • 1st attempt: You get this notice when Windows system’s firewalling does not allow remote file accessing.

    • 2nd attempt: please tell us the filesystems these are on and check if your system supports it (exFat might need installing a driver).

  • Sorry, I should have posted earlier. Nothing I tried worked when I first encountered the problem. A couple of months ago, I found a workaround by accident. Cleaning up, I unplugged all the peripherals from the PC. Reconnecting them, I inadvertently plugged the old external HDD into a USB3 port. Only later did I discover the invalid argument problem had gone away, but it no longer mattered because I had already moved all the files I wanted to other drives.

  • and how did you obtain the IP address? … How wuold you get it if you only know the server name?

  • @S.A.Ping the server name.

  • Walk over to the windows computer, open up Command Prompt, and type in ipconfig.

  • This is what worked for me. I had forgotten that I have created a group for samba users. Thanks!!!

Recents

Related

  • Failed to initialize battleye service windows test signing mode not supported как исправить
  • Facecam 315 драйвер для windows 10
  • Failed to initialize windows socket
  • Facecam 1320 драйвер windows 10
  • Failed to initialize battleye service windows test signing mode not supported pubg