Ocena wątku:
  • 0 głosów - średnia: 0
  • 1
  • 2
  • 3
  • 4
  • 5
Rozwiązane Montowanie udziału sieciowego z routera na Mint/Ubuntu
#1
0
Witam

Mam problem z zamontowaniem (odpaleniem) udostępnionego urządzenia USB wpiętego w port routera.
Bez problemu wchodzę tam z Win 7/10, ponadto mogę podpiąć się w Mint poprzez domyślnego managera plików (wpisuję np smb://IP_serwera) i pokazuje się "folder z zawartością USB.
Natomiast każda próba zamontowania z konsoli kończy się błędem.
Kod:
sudo mount -t cifs -o user=guest //IP_Servera /home/marcin/mnt
Kod:
sudo mount.cifs -o user=guest //IP_Servera /home/marcin/mnt

Dodam, że domyślnie mam na routerze ustawiony folder dostępny dla każdego (public) nie pomaga nawet wprowadzenie userów i hasła.

W odpowiedzi dostaję pytanie o hasło dla "sudo", a następnie dla zasobu, choć nie mam tam hasła. Z Win wchodzę bez problemu, z managera plików w Mint, też, daję anonimowo i wyświetla zasób.
W odpowiedzi na w/w polecenia otrzymuję

Kod:
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

Z góry wielkie dzięki.
pozdrawiam
M.
#2
0
Pokaż co widać:
smbclient -L //IP_Servera -U guest
#3
0
(18-05-2020, 17:26)dedito napisał(a): Pokaż co widać:
smbclient -L //IP_Servera -U guest
Kod:
protocol negotiation failed: NT_STATUS_CONNECTION_DISCONNECTED

Takie info mam na routerze w USB Storage:
Cytat:Note:
1. Storage Sharing function is based upon the NetBIOS/SMB protocol supported by Windows OS and some additional operating systems.
2. Anonymous: All active volume(s) will be shared with no authentication required.
3. You will be able to access the shared folders by the following methods:
    For Windows OS:Open the "Run" window within the Start menu and enter \\(IP Address) or \\(IP Address)\(Share Name)
e.g. \192.168.1.1 or \192.168.1.1photo;
    For Mac OS:Open the "Connect to Server" window within the Go menu and enter smb://(IP Address) or smb://(IP Address)/(Share Name).
e.g. smb://192.168.1.1 or smb://192.168.1.1/photo.
#4
0
Pokaż swoje smb.conf
i spróbuj tak: smbclient -L //IP_Servera/ --option='client min protocol=NT1'
#5
0
smb.conf, nie mam jak pokazać, bo tj na tp link ustawiony zasób.
po wklepaniu polecenia w terminal, otrzymałem zapytanie o hasło do WORKGROUP\marcin's - jakie hasło, nie mam bladego pojęcia.
Dobra po podaniu błędnego hasła mam :
Kod:
Server requested LANMAN password (share-level security) but 'client lanman auth          = no' or 'client ntlmv2 auth = yes'
tree connect failed: NT_STATUS_ACCESS_DENIED

Ale gdy dam ENTER:
Kod:
Sharename       Type      Comment
        ---------       ----      -------
        volume(sda1)    Disk
        IPC$            IPC       IPC Service (Samba Server)
        ADMIN$          IPC       IPC Service (Samba Server)
Reconnecting with SMB1 for workgroup listing.

        Server               Comment
        ---------            -------

        Workgroup            Master
        ---------            -------
#6
0
Ja pisałem o twoim smb.conf czyli cat /etc/samba/smb.conf
Dopisz sobie tą opcję do swojego smb.conf i zrestartuj sambę lub komputer.
#7
0
(18-05-2020, 17:56)dedito napisał(a): Ja pisałem o twoim smb.conf czyli cat /etc/samba/smb.conf
Dopisz sobie tą opcję do swojego smb.conf i zrestartuj sambę lub komputer.

Którą opcję?? Bo się pogubiłem.
smb.conf mam domyślny po instalce, nic tam nie grzebałem.
Kod:
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
   server string = %h server (Samba, Ubuntu)

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# We want Samba to only log to /var/log/samba/log.{smbd,nmbd}.
# Append syslog@1 if you want important messages to be sent to syslog too.
   logging = file

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone server" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
   server role = standalone server

   obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<[email protected]> for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
   pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user

########## Domains ###########

#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or 'domain logons' is set
#

# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /home/samba/etc/smb.conf.%m

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap config * :              backend = tdb
;   idmap config * :              range   = 3000-7999
;   idmap config YOURDOMAINHERE : backend = tdb
;   idmap config YOURDOMAINHERE : range   = 100000-999999
;   template shell = /bin/bash

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 means that usershare is disabled.
#   usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests = yes

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
;   comment = Home Directories
;   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
;   read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
;   create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
;   directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only "username"
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
;   valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin
#8
0
Tą którą dodawałaś do smbclienta.
Przykładowo, przed linijką #======================= Share Definitions =======================
Dopisz sobie jako root np. takie coś:
Kod:
#client min protocol (G)
#This setting controls the minimum protocol version that the client will attempt to use.
client min protocol=NT1
Więcej: https://www.samba.org/samba/docs/current...INPROTOCOL
#9
0
A mnie coś się wydaje, że po //IP_Servera/ jeszcze coś może być w ścieżce Smile

U mnie, np. pendrive przedstawia się jako "a", czyli mam //IP_Servera/a
#10
0
Kod:
#client min protocol (G)
#This setting controls the minimum protocol version that the client will attempt to use.
client min protocol=NT1
Dopisałem.
Zresetowałem sambę
Kod:
sudo service smbd restart

próba montowania:
Kod:
sudo mount -o user=guest //IP_servera /home/marcin/mnt/
Password for guest@//IP_servera:
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

Kod:
sudo mount.cifs -o user=guest //IP_servera/volume/ /home/marcin/mnt/
Password for guest@//IP_servera/volume/:
mount error(2): No such file or directory
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
Tak, teoretycznie ma volume, ale w manager jak dam samo IP to podmontuje mi to bez problemu, a w terminalu za nic...


Skocz do:




Użytkownicy przeglądający ten wątek: 1 gości