mount error(22): Invalid argument

Добрый день, монтирую виндовую сетевую папку под debian 9 командой:

нельзя монтировать иерархию каталогов вроде, верным будет

mount -t cifs //192.168.250.30/ExtRep/

а /folder/CB потом забиндить если только.

такая же ошибка:(

Поправка, должно быть так. но все равно не работает. (

попробовал у себя, полет нормальный

sudo mount.cifs //192.168.100.201/1c-base /mnt/servak -o user=user, pass=password

mount -t cifs //192.168.250.30/ExtRep/folder/CB /SHARE -o user=co,domain=CB,password=«Rkbtyn ( 18.10.18 09:59:28 )

у меня тоже так работает на другом серваке, а тут нет=(

verbose добавьте при монтировании, может скажет что-нибудь вразумительное

mount.cifs kernel mount options: ip=192.168.250.30,unc=\\192.168.250.30\ExtRep,vty2019!,iocharset=utf8,user=co,domain=CB,pass=******** mount error(22): Invalid argument

похоже на то, что он воспринимает часть пароля как отдельный параметр

а на другом ПК тот же пароль при монтировании?

unable to access location — failed to mount Windows share: Invalid argument [duplicate]

I’m running Ubuntu 14.04 LTS within a VMware workstation virtual machine and I have managed to setup a network by changing the samba.conf file to the WORKGROUP of my choice. Doing so gave me access to the User folder on the host machine (Win8.1) after providing the proper Username and Password (although I setup a WORKGROUP, here that WORKGROUP was renamed as a Domain for some reason). The problem is that there are several other folder setup on the host machine to be shared (according to windows 8.1) and these folders are displayed in the guest OS (Ubuntu) as expected, however the username and password will be accepted and I cannot gain access to them. In addition, there are other folders in the directory that I have no clue about. They seem to be folders from the host that show up, but I never set up sharing for them to begin with from within Win8.1. Also they have weird syntax that I assume comes from Linux (I am new to Linux) that places a «$» at the end of the folder name, like this:

I messed around with the smb.conf file and some features from the Software Center like tools for mounting and manipulating filesystems, but that just ended up mounting another drive in the virtual guest machine.

The bottom line is that a key folder I am trying to access is seen in the network directory, such as smb://hostpc/folderKEY , but the gives the following error on opening.

The folder belongs to an exFAT partition on an external USB drive attached to the host Machine OS (Win8.1). I can access it no problem from Win8.1, but not Ubuntu in the VM. The other folders belong to the host machine. I would get rid of all passwords to gain access to them, but I do not know how to do that.

Can’t share drive. mounting . /C on /c failed: Invalid argument #646

Comments

devnixs commented Apr 15, 2017

Before I start, this is not a duplicated issue. I’ve read all the other github issues related to that error, and tried every possible fix, and none of them worked.

My firewall is completely disabled for all networks.
If I create the share manually using

And then try to share the driver in docker for windows, the share is deleted.

Something surprising is that I can access the share in windows explorer
But when I try with the command line, it fails :

But it works in explorer!

Of course, I tried rebooting, uninstalling and reinstalling docker many times.

Expected behavior

• I should be able to share a drive in docker for windows

Actual behavior

• After typing my password, the checkbox gets unchecked

Information

The error in the log is :

And the Diagnostic ID is 416D68C3-32DA-4D22-8310-B4729A32B7B8/2017-04-15_11-24-53

I’m on Windows 10 Pro, version 1607 (OS Build 14393.1066 )

Steps to reproduce the behavior

1. Open docker for windows, shared drives tab.
2. Check a drive
3. Hit apply
4. Enter your password
5. The checkbox get unchecked!

Thanks for your help! I’m really getting out of ideas.

The text was updated successfully, but these errors were encountered:

Failed to mount windows share invalid argument

Скачать архив с программой — AsusFlashToolInstaller.zip ( 28,55 МБ )

Распаковать, запустить установку.

Если висит на лого ASUS с вечной загрузкой — пробуйте это.
________________________________________
Дамп прошивки 7.6.0 (app + priv-app + все в zip) — Asus FonePad HD 7 — Прошивка (OS Android 4.х.х-5.х.х ) (Пост evg1394 #44947174)
________________________________________
Дамп прошивки 6.3.6 (app + priv-app) — Asus FonePad HD 7 — Официальная прошивка (OS Android 4.2.х-4.3.х) (Пост #32948734)
________________________________________
Буквенные индексы прошивок.
CN — Китай.
TW — Тайвань.
WW — WorldWide (всемирная).
Отличия в полосе пропускания (baseband), языковой пакет загружается автоматом.

В теме нет куратора. По вопросам наполнения шапки, обращайтесь к модераторам раздела через кнопку под сообщениями, на которые необходимо добавить ссылки.

Сообщение отредактировал Violence Jack — 12.01.19, 16:42

Инструкция по восстановлению слетевшего IMEI. Только для ME372CG!

Метод работает только на х86-системах (32-bit), на х64 — не работает!

1. Скачайте архив с необходимыми файлами, распакуйте. АРХИВ.zipАРХИВ.7z Или скачайте компоненты по отдельности если не имеете программу-архиватор — СКАЧАТЬ.
2. Установите прошивку на Ваш планшет (инструкция по установке RAW прошивок — в шапке темы). Обратите внимание — на карте не должно быть других образов прошивок, если они есть — удалите!
3. Установите драйвера, на всякий случай перезагрузите компьютер.
4. Подключите планшет к ПК и запустите программу Only_ME372CG_Rewrite_IMEI_E0924.
5. После появления окна программы введите номер порта (где взять номер порта: РАЗ и ДВА) и свой номер IMEI.
6. После того, как программа отработает, планшет перезагрузится.
7. Убедитесь, что IMEI восстановлен.
8. Далее установите желаемую прошивку и можете обновляться «по воздуху» или оставляйте нужную Вам версию прошивки и не обновляйтесь.
9. PROFIT!
10. :happy:

Найдено на XDA. Оригинальный ПОСТ.

Сообщение отредактировал evg1394 — 28.07.15, 11:08

Failed to retrieve share list from server: Invalid argument

I have a fresh install of Ubuntu 20.04 with Samba share enabled. When trying to access the share by browsing through the file manager, I get the error «Failed to retrieve share list from server: Invalid argument».

This happens from the pc which is sharing the samba share and also from another Linux box. Browsing from a Windows 10 pc is working fine.

I have seen a lot of solutions posted, but none is suitable for me: I know I can enable the NT1 (SMB1) protocol in the smb.conf but I don’t want to use this because it is insecure. I could access the shares using the ip address (which isn’t working for me) or could mount the share using cifs.

But I want to be able to access the shares by browsing in the file manager. How can I configure the Ubuntu 20.04 box to be able to access SMB2 (or higher) shares?

1 Answer 1

Short Answer: You cannot until this bug is resolved: https://bugs.launchpad.net/gvfs/+bug/1828107

A gvfs backend process ( gvfsd-smb-browse ) drops down to SMB1 ( NT1 ) to get a list of SMB hosts and their shares and then gets stuck there. When it tries to access a SMB server that has disabled SMB1 like Ubuntu 20 it cannot because there is no SMB1 — that is the «invalid argument».

You can still access the host and its share but you cannot browse or discover it. You must access it explicitly by host name and share name in Connect to Server.

Browsing from a Windows 10 pc is working fine.

There are only two ways a Win10 client can discover any Linux samba server:

** You enabled WS-Discovery on your Ubuntu box which you would remember doing since it is somewhat involved.

** Or you enabled client side SMB1 on your Win10 box. You can verify that in Win10 by:

Entering «Windows Features» in Search then expanding SMB 1.0/CIFS File Sharing Support

In this case Win10 will use SMB1 to get the list of shares but then uses SMB2 / SMB3 to make the actual connection. That is the thing an Ubuntu 20 client cannot do.

I have a Win10 machine that has enabled SMB1 on the client side. In Explorer I can see the non-smb1 Ubuntu server using NetBIOS:

If I connect to one of it’s shares I am connecting using SMB3:

Samba version 4.11.6-Ubuntu PID Username Group Machine Protocol Version Encryption Signing
—————————————————————————————————————————————- 1443 nobody nogroup
2605:a601:a1a4:d000:30e3:5dca:a90c:1fea (ipv6:2605:a601:a1a4:d000:30e3:5dca:a90c:1fea:49761) SMB3_11