Как смонтировать виндовую шару? — Хабр Q&A

Build instructions¶

For Linux:

Cifs kernel module parameters¶

These module parameters can be specified or modified either during the time of
module loading or during the runtime by using the interface:

i.e.:

Cifs vfs mount options¶

A partial list of the supported mount options follows:

How to mount windows share on linux system using cifs – oss-it

This article describes how to mount CIFS shares.

English version of this page under construction. You can read automatic translation.


Иногда, при организации совместных сетей между Windwos и Linux системами, в последних может появиться необходимость монтирования расшаренных SMB-ресурсов прямо к файловой системе. Прежде всего такая необходимость появляется при использовании легковесных рабочих сред (XFCE, OpenBox, LXDE и др), файловые менеджеры которых не поддерживают прямой доступ к samba.

Например, в среде Gnome доступ к ресурсу Windows можно получить прямо из файлового менеджера Nautilus, введя в адресной строке путь вида smb://192.168.0.11/ (где вместо необходимого ip-адреса также может быть просто указано сетевое имя windows-системы). Но многие другие файловые менеджеры (к примеру, быстрый и удобный PCMan File Manager до определённой версии) не поддерживают такой возможности, поэтому универсальным решением становится монтирование SMB к конкретному пути вашей файловой системы, в результате вы получите доступ к расшаренному ресурсу удаленной системы точно так же, как вы его получаете к своим дискам. Для этой цели нам потребуется установленный пакет cifs-utils, в Ubuntu и Debian установить его можно командой:

sudo apt-get install cifs-utils

В Fedora, CentOS и других RedHat based дистрибутивах:

sudo yum install cifs-utils

Также, как заметили в комментариях, рекомендуется установить пакеты ntfs-3g и ntfs-config, если они у вас ещё не установлены.

Теперь для начала давайте разберем как монтировать расшаренные папки вручную. Потребуется создать путь куда будем монтировать SMB-папку, пусть это, к примеру, будет /media/sharefolder:

sudo mkdir /media/sharefolder

Вот такой командой можно примонтировать папку, требующую авторизации по логину и паролю:

sudo mount -t cifs //192.168.0.11/share /media/sharefolder -o username=windowsuser,password=windowspass,iocharset=utf8,file_mode=0777,dir_mode=0777

где вместо //192.168.0.11/share – ip-адрес и имя необходимой общей папки (если имя расшаренной папки содержит пробел, то необходимо заключить весь путь в кавычки, как это показано в следующем примере), /media/sharefolder – путь куда будет монтироваться ресурс, windowsuser – имя пользователя с необходимыми правами доступа к этому ресурсу Windows, windowspass – пароль этого пользователя.

Если необходимая папка не требует обязательной авторизации, то подключить ресурс можно такой командой:

sudo mount -t cifs "//192.168.0.11/общие документы" /media/sharefolder -o guest,rw,iocharset=utf8,file_mode=0777,dir_mode=0777

Если гостевой доступ к необходимой папке включен только в режиме чтения, то будет достаточно такой команды:

sudo mount -t cifs //192.168.0.11/общие /media/sharefolder -o guest,iocharset=utf8

При удачном выполнении этих команд не должно произойти никакого уведомления – можете смело проверять как примонтировалась папка перейдя по вашему пути (в нашем примере – /media/sharefolder).
Отмонтируется папка командой:

sudo umount /media/sharefolder

Для того чтобы осуществить автомонтирование таких папок нам придется отредактировать системный файл fstab. Также, если доступ к необходимому windows-ресурсу требует обязательной авторизации, то потребуется предварительно создать файл, в котором будут прописаны логин и пароль доступа (сделать это можно текстовым редактором nano):

sudo nano /root/.smbcredentials

В этот новый файл добавьте две строки:

username=windowsuser
password=windowspass

где, соответственно, windowsuser – имя пользователя с необходимыми правами доступа к ресурсу Windows, windowspass – пароль этого пользователя. Измените права созданного файла так, что редактировать и смотреть его смог только root, то есть сама система:

sudo chmod 700 /root/.smbcredentials

Сохраните изменения и переходите к редактированию файла /etc/fstab:

sudo nano /etc/fstab

И здесь в самом конце добавьте строку типа:

//192.168.0.11/share /media/sharefolder cifs credentials=/root/.smbcredentials,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0

Если авторизации по имени и паролю не требуется, а требуется только гостевой доступ, то создавать файл .smbcredentials не потребуется, этот шаг можно было пропустить и сразу в /etc/fstab добавить строку:

//192.168.0.11/общие40документы /media/sharefolder cifs guest,rw,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0

Обратите внимание, что здесь если ваша папка содержит пробелы, то вариант аналогичный командной строке – заключении пути в кавычки – не поможет, для того, чтобы fstab понял пробелы – их необходимо заменить на четыре символа: 40
И, соответственно, если требуется только лишь гостевой доступ в режиме чтения к windows-папке, то будет достаточно такой строки:

//192.168.0.11/общие /media/sharefolder cifs guest,iocharset=utf8 0 0

Для того, чтобы проверить корректно ли монтируется shared-папка из fstab без перезагрузки нужно выполнить такую команду:

sudo mount -a

Также к этому стоит добавить, что если вы хотите получать доступ к windows-шаре не через ip-адрес, а через имя машины, то вам потребуется установить winbind, в Debian-based:

sudo apt-get install winbind

Или в RedHat-based системах:

sudo yum install samba-winbind

После этого отредактируйте файл /etc/nsswitch.conf:

sudo nano /etc/nsswitch.conf

Где в строке:

hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4

перед dns добавьте wins, то есть после редактирования она должна выглядеть вот так:

hosts: files mdns4_minimal [NOTFOUND=return] wins dns mdns4

После перезагрузки для получения доступа к windows-ресурсу через CIFS можно будет указывать не только ip, но и сетевое имя windows-ресурса (netbios name). Но мы всеже рекомендуем использовать непосредственно ip-адрес (как было описано в статье) – к нему обращение идет напрямую, быстрее.

Также стоит отметить, что таким образом можно монтировать только конкретные общие папки (например: //192.168.0.11/share), но не весь windows-ресурс целиком (то есть просто: //192.168.0.11).

Installation instructions¶

If you have built the CIFS vfs as module (successfully) simply
type makemodules_install (or if you prefer, manually copy the file to
the modules directory e.g. /lib/modules/2.4.10-4GB/kernel/fs/cifs/cifs.ko).

If you have built the CIFS vfs into the kernel itself, follow the instructions
for your distribution on how to install a new kernel (usually you
would simply type makeinstall).

If you do not have the utility mount.cifs (in the Samba 4.x source tree and on
the CIFS VFS web site) copy it to the same directory in which mount helpers
reside (usually /sbin). Although the helper software is not
required, mount.cifs is recommended.

Misc /proc/fs/cifs flags and debug info¶

Informational pseudo-files:

Configuration pseudo-files:

SecurityFlags

Flags which control security negotiation and
also packet signing. Authentication (may/must)
flags (e.g. for NTLM and/or NTLMv2) may be combined with
the signing flags. Specifying two different password
hashing mechanisms (as “must use”) on the other hand
does not make much sense. Default flags are:

(NTLM, NTLMv2 and packet signing allowed). The maximum
allowable flags if you want to allow mounts to servers
using weaker password hashes is 0x37037 (lanman,
plaintext, ntlm, ntlmv2, signing allowed). Some
SecurityFlags require the corresponding menuconfig
options to be enabled. Enabling plaintext
authentication currently requires also enabling
lanman authentication in the security flags
because the cifs module only supports sending
laintext passwords using the older lanman dialect
form of the session setup SMB. (e.g. for authentication
using plain text passwords, set the SecurityFlags
to 0x30030):

cifsFYI

If set to non-zero value, additional debug information
will be logged to the system error log. This field
contains three flags controlling different classes of
debugging entries. The maximum value it can be set
to is 7 which enables all debugging points (default 0).
Some debugging statements are not compiled into the
cifs kernel unless CONFIG_CIFS_DEBUG2 is enabled in the
kernel configuration. cifsFYI may be set to one or
nore of the following flags (7 sets them all):

traceSMB

If set to one, debug information is logged to the
system error log with the start of smb requests
and responses (default 0)

LookupCacheEnable

If set to one, inode information is kept cached
for one second improving performance of lookups
(default 1)

LinuxExtensionsEnabled

If set to one then the client will attempt to
use the CIFS “UNIX” extensions which are optional
protocol enhancements that allow CIFS servers
to return accurate UID/GID information as well
as support symbolic links. If you use servers
such as Samba that support the CIFS Unix
extensions but do not want to use symbolic link
support and want to map the uid and gid fields
to values supplied at mount (rather than the
actual values, then set this to zero. (default 1)

dfscache

List the content of the DFS cache.
If set to 0, the client will clear the cache.

Похожее:  Оплата Межрегионгаз Север: коммунальные платежи онлайн

These experimental features and tracing can be enabled by changing flags in
/proc/fs/cifs (after the cifs module has been installed or built into the
kernel, e.g. insmod cifs). To enable a feature set it to 1 e.g. to enable
tracing to the kernel message log type:

cifsFYI functions as a bit mask. Setting it to 1 enables additional kernel
logging of various informational messages. 2 enables logging of non-zero
SMB return codes while 4 enables logging of requests that take longer
than one second to complete (except for byte range lock requests).

Mount.cifs

user=arg

specifies the username to connect as. If
this is not given, then the environment variable USER is used. This option can also take the
form “user%password” or “workgroup/user” or
“workgroup/user%password” to allow the password and workgroup
to be specified as part of the username.

password=arg

specifies the CIFS password. If this
option is not given then the environment variable
PASSWD is used. If the password is not specified
directly or indirectly via an argument to mount, mount.cifs will prompt
for a password, unless the guest option is specified.

Note that a password which contains the delimiter
character (i.e. a comma ‘,’) will fail to be parsed correctly
on the command line. However, the same password defined
in the PASSWD environment variable or via a credentials file (see
below) or entered at the password prompt will be read correctly.

credentials=filename

specifies a file that contains a username
and/or password and optionally the name of the
workgroup. The format of the file is:

		username=value
		password=value
		domain=value

This is preferred over having passwords in plaintext in a
shared file, such as /etc/fstab. Be sure to protect any
credentials file properly.

uid=arg

sets the uid that will own all files or directories on the
mounted filesystem when the server does not provide ownership
information. It may be specified as either a username or a numeric uid.
When not specified, the default is uid 0. The mount.cifs helper must be
at version 1.10 or higher to support specifying the uid in non-numeric
form. See the section on FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS below for more
information.

prefixpath=arg

It’s possible to mount a subdirectory of a share. The preferred way
to do this is to append the path to the UNC when mounting. However,
it’s also possible to do the same by setting this option and
providing the path there.

cifsacl

This option is used to map CIFS/NTFS ACLs to/from Linux permission
bits, map SIDs to/from UIDs and GIDs, and get and set Security
Descriptors.

forceuid

instructs the client to ignore any uid provided by
the server for files and directories and to always assign the owner to
be the value of the uid= option. See the section on FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS below for more information.

gid=arg

sets the gid that will own all files or
directories on the mounted filesystem when the server does not provide
ownership information. It may be specified as either a groupname or a
numeric gid. When not specified, the default is gid 0. The mount.cifs
helper must be at version 1.10 or higher to support specifying the gid
in non-numeric form. See the section on FILE AND DIRECTORY OWNERSHIP AND
PERMISSIONS below for more information.

forcegid

instructs the client to ignore any gid provided by
the server for files and directories and to always assign the owner to
be the value of the gid= option. See the section on FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS below for more information.

port=arg

sets the port number on the server to attempt to contact to negotiate
CIFS support. If the CIFS server is not listening on this port or
if it is not specified, the default ports will be tried i.e.
port 445 is tried and if no response then port 139 is tried.

servernetbiosname=arg

Specify the server netbios name (RFC1001 name) to use
when attempting to setup a session to the server. Although
rarely needed for mounting to newer servers, this option
is needed for mounting to some older servers (such
as OS/2 or Windows 98 and Windows ME) since when connecting
over port 139 they, unlike most newer servers, do not
support a default server name. A server name can be up
to 15 characters long and is usually uppercased.

servern=arg

synonym for servernetbiosname=

netbiosname=arg

When mounting to servers via port 139, specifies the RFC1001
source name to use to represent the client netbios machine
name when doing the RFC1001 netbios session initialize.

file_mode=arg

If the server does not support the CIFS Unix extensions this
overrides the default file mode.

dir_mode=arg

If the server does not support the CIFS Unix extensions this
overrides the default mode for directories.

ip=arg

sets the destination IP address. This option is set automatically if the server name portion of the requested UNC name can be resolved so rarely needs to be specified by the user.

domain=arg

sets the domain (workgroup) of the user

guest

don’t prompt for a password

iocharset

Charset used to convert local path names to and from
Unicode. Unicode is used by default for network path
names if the server supports it. If iocharset is
not specified then the nls_default specified
during the local client kernel build will be used.
If server does not support Unicode, this parameter is
unused.

ro

mount read-only

rw

mount read-write

setuids

If the CIFS Unix extensions are negotiated with the server
the client will attempt to set the effective uid and gid of
the local process on newly created files, directories, and
devices (create, mkdir, mknod). If the CIFS Unix Extensions
are not negotiated, for newly created files and directories
instead of using the default uid and gid specified on the
the mount, cache the new file’s uid and gid locally which means
that the uid for the file can change when the inode is
reloaded (or the user remounts the share).

Похожее:  МУП "Жилищник" - управляющая компания Серпухова
nosetuids

The client will not attempt to set the uid and gid on
on newly created files, directories, and devices (create,
mkdir, mknod) which will result in the server setting the
uid and gid to the default (usually the server uid of the
user who mounted the share). Letting the server (rather than
the client) set the uid and gid is the default.If the CIFS
Unix Extensions are not negotiated then the uid and gid for
new files will appear to be the uid (gid) of the mounter or the
uid (gid) parameter specified on the mount.

perm

Client does permission checks (vfs_permission check of uid
and gid of the file against the mode and desired operation),
Note that this is in addition to the normal ACL check on the
target machine done by the server software.
Client permission checking is enabled by default.

noperm

Client does not do permission checks. This can expose
files on this mount to access by other users on the local
client system. It is typically only needed when the server
supports the CIFS Unix Extensions but the UIDs/GIDs on the
client and server system do not match closely enough to allow
access by the user doing the mount.
Note that this does not affect the normal ACL check on the
target machine done by the server software (of the server
ACL against the user name provided at mount time).

dynperm

Instructs the server to maintain ownership and
permissions in memory that can’t be stored on the server. This information can disappear at any time (whenever the inode is flushed from the cache), so while this may help make some applications work, it’s behavior is somewhat unreliable. See the section below on FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS for more information.

directio

Do not do inode data caching on files opened on this mount.
This precludes mmaping files on this mount. In some cases
with fast networks and little or no caching benefits on the
client (e.g. when the application is doing large sequential
reads bigger than page size without rereading the same data)
this can provide better performance than the default
behavior which caches reads (readahead) and writes
(writebehind) through the local Linux client pagecache
if oplock (caching token) is granted and held. Note that
direct allows write operations larger than page size
to be sent to the server. On some kernels this requires the cifs.ko module
to be built with the CIFS_EXPERIMENTAL configure option.

mapchars

Translate six of the seven reserved characters (not backslash, but including the colon, question mark, pipe, asterik, greater than and less than characters)
to the remap range (above 0xF000), which also
allows the CIFS client to recognize files created with
such characters by Windows’s POSIX emulation. This can
also be useful when mounting to most versions of Samba
(which also forbids creating and opening files
whose names contain any of these seven characters).
This has no effect if the server does not support
Unicode on the wire. Please note that the files created
with mapchars mount option may not be accessible
if the share is mounted without that option.

nomapchars

Do not translate any of these seven characters (default)

intr

currently unimplemented

nointr

(default) currently unimplemented

hard

The program accessing a file on the cifs mounted file system will hang when the
server crashes.

soft

(default) The program accessing a file on the cifs mounted file system will not hang when the server crashes and will return errors to the user application.

noacl

Do not allow POSIX ACL operations even if server would support them.

The CIFS client can get and set POSIX ACLs (getfacl, setfacl) to Samba servers
version 3.0.10 and later. Setting POSIX ACLs requires enabling both XATTR and
then POSIX support in the CIFS configuration options when building the cifs
module. POSIX ACL support can be disabled on a per mount basis by specifying
“noacl” on mount.

nocase

Request case insensitive path name matching (case
sensitive is the default if the server suports it).

ignorecase

Synonym for nocase

sec=

Security mode. Allowed values are:

[NB This [sec parameter] is under development and expected to be available in cifs kernel module 1.40 and later]

nobrl

Do not send byte range lock requests to the server.
This is necessary for certain applications that break
with cifs style mandatory byte range locks (and most
cifs servers do not yet support requesting advisory
byte range locks).

sfu

When the CIFS Unix Extensions are not negotiated, attempt to
create device files and fifos in a format compatible with
Services for Unix (SFU). In addition retrieve bits 10-12
of the mode via the SETFILEBITS extended attribute (as
SFU does). In the future the bottom 9 bits of the mode
mode also will be emulated using queries of the security
descriptor (ACL). [NB: requires version 1.39 or later
of the CIFS VFS. To recognize symlinks and be able
to create symlinks in an SFU interoperable form
requires version 1.40 or later of the CIFS VFS kernel module.

serverino

Use inode numbers (unique persistent file identifiers)
returned by the server instead of automatically generating
temporary inode numbers on the client. Although server inode numbers
make it easier to spot hardlinked files (as they will have
the same inode numbers) and inode numbers may be persistent (which is
userful for some sofware),
the server does not guarantee that the inode numbers
are unique if multiple server side mounts are exported under a
single share (since inode numbers on the servers might not
be unique if multiple filesystems are mounted under the same
shared higher level directory). Note that not all
servers support returning server inode numbers, although
those that support the CIFS Unix Extensions, and Windows 2000 and
later servers typically do support this (although not necessarily
on every local server filesystem). Parameter has no effect if
the server lacks support for returning inode numbers or equivalent.

noserverino

Client generates inode numbers (rather than
using the actual one from the server) by default.

See section INODE NUMBERS for
more information.

nounix

Disable the CIFS Unix Extensions for this mount. This
can be useful in order to turn off multiple settings at once.
This includes POSIX acls, POSIX locks, POSIX paths, symlink
support and retrieving uids/gids/mode from the server. This
can also be useful to work around a bug in a server that
supports Unix Extensions.

Похожее:  HTTP коды ошибок клиента | IT-блог о веб-технологиях, серверах, протоколах, базах данных, СУБД, SQL, компьютерных сетях, языках программирования и создание сайтов.

See section INODE NUMBERS for
more information.

nouser_xattr

(default) Do not allow getfattr/setfattr to get/set xattrs, even if server would support it otherwise.

rsize=arg

default network read size (usually 16K). The client currently
can not use rsize larger than CIFSMaxBufSize. CIFSMaxBufSize
defaults to 16K and may be changed (from 8K to the maximum
kmalloc size allowed by your kernel) at module install time
for cifs.ko. Setting CIFSMaxBufSize to a very large value
will cause cifs to use more memory and may reduce performance
in some cases. To use rsize greater than 127K (the original
cifs protocol maximum) also requires that the server support
a new Unix Capability flag (for very large read) which some
newer servers (e.g. Samba 3.0.26 or later) do. rsize can be
set from a minimum of 2048 to a maximum of 130048 (127K or
CIFSMaxBufSize, whichever is smaller)

wsize=arg

default network write size (default 57344)
maximum wsize currently allowed by CIFS is 57344 (fourteen
4096 byte pages)

noposixpaths

If unix extensions are enabled on a share, then the client will
typically allow filenames to include any character besides ‘/’ in a
pathname component, and will use forward slashes as a pathname
delimiter. This option prevents the client from attempting to
negotiate the use of posix-style pathnames to the server.

posixpaths

Inverse of noposixpaths

–verbose

Print additional debugging information for the mount. Note that this parameter must be specified before the -o. For example:

mount -t cifs //server/share /mnt –verbose -o user=username

Restrictions¶

Servers must support either “pure-TCP” (port 445 TCP/IP CIFS connections) or RFC
1001/1002 support for “Netbios-Over-TCP/IP.” This is not likely to be a
problem as most servers support this.

Valid filenames differ between Windows and Linux. Windows typically restricts
filenames which contain certain reserved characters (e.g.the character :
which is used to delimit the beginning of a stream name by Windows), while
Linux allows a slightly wider set of valid characters in filenames.

Windows
servers can remap such characters when an explicit mapping is specified in
the Server’s registry. Samba starting with version 3.10 will allow such
filenames (ie those which contain valid Linux characters, which normally
would be forbidden for Windows/CIFS semantics) as long as the server is
configured for Unix Extensions (and the client has not disabled
/proc/fs/cifs/LinuxExtensionsEnabled).

In addition the mount option
mapposix can be used on CIFS (vers=1.0) to force the mapping of
illegal Windows/NTFS/SMB characters to a remap range (this mount parameter
is the default for SMB3).

Use instructions¶

Once the CIFS VFS support is built into the kernel or installed as a module
(cifs.ko), you can use mount syntax like the following to access Samba or
Mac or Windows servers:

Before -o the option -v may be specified to make the mount.cifs
mount helper display the mount steps more verbosely.
After -o the following commonly used cifs vfs specific options
are supported:

Other cifs mount options are described below. Use of TCP names (in addition to
ip addresses) is available if the mount helper (mount.cifs) is installed. If
you do not trust the server to which are mounted, or if you do not have
cifs signing enabled (and the physical network is insecure), consider use
of the standard mount options noexec and nosuid to reduce the risk of
running an altered binary on your local system (downloaded from a hostile server
or altered by a hostile router).

Although mounting using format corresponding to the CIFS URL specification is
not possible in mount.cifs yet, it is possible to use an alternate format
for the server and sharename (which is somewhat similar to NFS style mount
syntax) instead of the more widely used UNC format (i.e. servershare):

When using the mount helper mount.cifs, passwords may be specified via alternate
mechanisms, instead of specifying it after -o using the normal pass= syntax
on the command line:
1)

Дополнительно

Монтирование CIFS с пробелом (заменяем пробел на 40):

Как смонтировать виндовую шару?

Доброго дня. Подскажите пожалуйста, что я делаю не так?

Есть виндовая машина 10.20.3.89

Там есть шара OrionBase, доступная всем, даже без пароля.

Пытаюсь смонтировать данную папку.

[root@Srv1CL mnt]# mount -t cifs //10.20.3.89/OrionBase /mnt/win/ -o username=root,password=Integr@tr,vers=1.0
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
[root@Srv1CL mnt]# mount -t cifs //10.20.3.89/OrionBase /mnt/win/ -o username=root,password=Integ@t0r,vers=1.0
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
[root@Srv1CL mnt]# mount -t cifs //10.20.3.89/OrionBase /mnt/win/ -o username=root,password=Integ@t0r,vers=1.0
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
[root@Srv1CL mnt]# mount -t cifs //10.20.3.89/OrionBase /mnt/win/ -o guest
mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
[root@Srv1CL mnt]# cd /
[root@Srv1CL /]# mount -t cifs //10.20.3.89/OrionBase /mnt/win/ -o username=root,password=Integ@t0r,vers=1.0
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
[root@Srv1CL /]# ping 10.20.3.89
PING 10.20.3.89 (10.20.3.89) 56(84) bytes of data.
64 bytes from 10.20.3.89: icmp_seq=1 ttl=255 time=0.301 ms
64 bytes from 10.20.3.89: icmp_seq=2 ttl=255 time=0.335 ms
64 bytes from 10.20.3.89: icmp_seq=3 ttl=255 time=0.324 ms
64 bytes from 10.20.3.89: icmp_seq=4 ttl=255 time=0.327 ms
^C
--- 10.20.3.89 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 0.301/0.321/0.335/0.025 ms

Как видите, я и пытался обособить символы в пароле, и обособить все символы, и подключить под гостем.

Так же пытался изменить аргумент vers=1.0

[root@Srv1CL /]# mount -t cifs //10.20.3.89/OrionBase /mnt/win/ -o username=root,password=Integr@tr,vers=3.0
mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

Мануал читал, но может быть я что то упустил?

Прошу ткнуть пальцем, что я делаю не так?

Заранее, большое спасибо.

Монтирование cifs вручную

Синтаксис:

mount.cifs <путь к папке> <куда монтировать> <-o опции>
или
mount -t cifs <путь к папке> <куда монтировать> <-o опции>

Пример монтирования общей папки public на сервере с IP адресом 10.20.30.40 в локальную папку /mnt:

mount.cifs //10.20.30.40/public /mnt

 Пример монтирования папки share на сервере с IP адресом 10.20.30.40 в локальную папку /mnt от имени пользователя v.pupkin:

Ссылки

Настройка samba сервера Ubuntu и клиента RHEL

Samba на Ubuntu Server в домене Windows

Установка пакета для работы cifs

CentOS:

yum install cifs-utils

Ubuntu:

apt-get install cifs-utils

Recommendations¶

To improve security the SMB2.1 dialect or later (usually will get SMB3) is now
the new default. To use old dialects (e.g. to mount Windows XP) use “vers=1.0”
on mount (or vers=2.0 for Windows Vista). Note that the CIFS (vers=1.0) is
much older and less secure than the default dialect SMB3 which includes
many advanced security features such as downgrade attack detection
and encrypted shares and stronger signing and authentication algorithms.

mfsymlinks and either cifsacl or modefromsid (usually with idsfromsid)

1 Звезда2 Звезды3 Звезды4 Звезды5 Звезд (1 оценок, среднее: 5,00 из 5)
Загрузка...

Добавить комментарий

Ваш адрес email не будет опубликован.

Adblock
detector