Beiträge von sudosudoo

Zitat von Steuko

Hi,

I just reinstalled my WIN 10 desktop and I cannot see any of my shares on my OMV server (v3.2.0-6-amd64). I tried:
- same workgroup, also changed from my own to WIN default.
- ping to server still works fine
- my linux mint laptop CAN see all shares properly
- in OMV SMB/CIFS I added Extra Options:
client min protocol = SMB2
client max protocol = SMB3
- in WIN 10 samba entries was added to registers according thread "HOW-TO-Connect-to-OMV-SMB-shares-with-Windows-10..."
- in WIN 10, I use MSA credential (this was not in previous WIN 10 install) - I tried also add my OMV users to local win credentials for server IP and separately for server name
- when I try to connect manually to server I receive error reffering that connection is not safe and uses SMB1, see picture. Why windows thinks of that? Do I do something wrong?

Do you have any ideas what else should I try? I spent many hours with this and I'm confused. I just used brand new install of win 10 pro, activated by original key, iso image was from microsoft.

Thanks a lot for suggestions.

EDIT:
I just find, that I used wrong string: "server min protocol = SMB2". I tried as mentioned above "client min protocol = SMB2", but I get result in Diagnostics>Services>SMB/CIFS:
Ignoring unknown parameter "client min protocol"
Unknown parameter encountered: "client max protocol"
Ignoring unknown parameter "client max protocol"
I just added this to shares as well, but result is still unknown parameters

EDIT2:
Only one thing helped - enable SMB1 in WIN 10, but this is not what I'm looking for due to safety reasons. How can I force SMB2 on both sides? Why does OMV's samba ignore my client min protocol value?

Code

# cat /etc/samba/smb.conf
#======================= Global Settings =======================
[global]
workgroup = WORKGROUP
server string = %h server
dns proxy = no
log level = 2
syslog = 2
log file = /var/log/samba/log.%m
max log size = 1000
syslog only = yes
panic action = /usr/share/samba/panic-action %d
encrypt passwords = true
passdb backend = tdbsam
obey pam restrictions = yes
unix password sync = no
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
pam password change = yes
socket options = TCP_NODELAY IPTOS_LOWDELAY
guest account = nobody
load printers = no
disable spoolss = yes
printing = bsd
printcap name = /dev/null
unix extensions = yes
wide links = no
create mask = 0777
directory mask = 0777
use sendfile = yes
aio read size = 16384
aio write size = 16384
null passwords = no
local master = yes
time server = no
wins support = yes
client min protocol = SMB2
client max protocol = SMB3


#======================= Share Definitions =======================
[Foto]
path = /media/307C1DF37C1DB516/02 - Foto/
guest ok = no
read only = no
browseable = yes
inherit acls = yes
inherit permissions = no
ea support = no
store dos attributes = no
printable = no
create mask = 0755
force create mode = 0644
directory mask = 0755
force directory mode = 0755
hide dot files = yes
valid users = "user1","user0"
invalid users =
read list = "user1"
write list = "user0"

Alles anzeigen

Alles anzeigen

its been a while but i only fixed it by upgrading to OMV 4.x

Hi All!
the following is my current omv build mainly used for plexmediaserver and easier access to the files that plexmediaserver uses
https://imgur.com/a/mbd8CpC (i uploaded the images to imgur because they were too big)

Specs:
Core 2 Duo E6550 (2.33GHz)
3 GB RAM
230GB Drive for storage
Toshiba 16GB usb for the OMV install

Zitat von flmaxey

Well, from a support point of view (as in trying to provide it) I didn't see that one coming. I have to ask, why did you think shares would show up for users who don't have access to them?
And as a rule of thumb, electronics don't like water. Building on storage media that has been damaged is, generally, not a good idea.

i didnt think the shares themselves would show up for users who cant access them but i did think the nas would show up in Network but it would ask for a password to view the shares. it asks for a password to view the shares as long as users and other is set to read only.

Zitat von raulfg3

perhaps your win10 try to use NTLM1 that is not supported by SAMBA, so you need to instruct Windows to use SMB3 that is more efficient , this can be done using " Client max protocol":

see smb.conf rules: https://www.samba.org/samba/do…anpages-3/smb.conf.5.html

eg: copy & paste from smb.conf rules:

Spoiler anzeigen

client max protocol (G)

The value of the parameter (a string) is the highest protocol level that will be supported by the client.
Possible values are :
CORE: Earliest version. No concept of user names.
COREPLUS: Slight improvements on CORE for efficiency.
LANMAN1: First modern version of the protocol. Long filename support.
LANMAN2: Updates to Lanman1 protocol.
NT1: Current up to date version of the protocol. Used by Windows NT. Known as CIFS.
SMB2: Re-implementation of the SMB protocol. Used by Windows Vista and later versions of Windows. SMB2 has sub protocols available.
SMB2_02: The earliest SMB2 version.
SMB2_10: Windows 7 SMB2 version.
SMB2_22: Early Windows 8 SMB2 version.
SMB2_24: Windows 8 beta SMB2 version.
By default SMB2 selects the SMB2_10 variant.
SMB3: The same as SMB2. Used by Windows 8. SMB3 has sub protocols available.

• SMB3_00: Windows 8 SMB3 version. (mostly the same as SMB2_24)

By default SMB3 selects the SMB3_00 variant.
Normally this option should not be set as the automatic negotiation phase in the SMB protocol takes care of choosing the appropriate protocol.
Default: client max protocol = SMB3[/i]
Example: client max protocol = LANMAN1[/i]
client min protocol (G)

This setting controls the minimum protocol version that the client will attempt to use.
Normally this option should not be set as the automatic negotiation phase in the SMB protocol takes care of choosing the appropriate protocol.
Default: client min protocol = CORE[/i]
Example: client min protocol = NT1[/i]
client NTLMv2 auth (G)

This parameter determines whether or not smbclient(8) will attempt to authenticate itself to servers using the NTLMv2 encrypted password response.
If enabled, only an NTLMv2 and LMv2 response (both much more secure than earlier versions) will be sent. Older servers (including NT4 < SP4, Win9x and Samba 2.2) are not compatible with NTLMv2 when not in an NTLMv2 supporting domain
Similarly, if enabled, NTLMv1, client lanman auth and client plaintext auth authentication will be disabled. This also disables share-level authentication.
If disabled, an NTLM response (and possibly a LANMAN response) will be sent by the client, depending on the value of client lanman auth.
Note that Windows Vista and later versions already use NTLMv2 by default, and some sites (particularly those following 'best practice' security polices) only allow NTLMv2 responses, and not the weaker LM or NTLM.
Default: client NTLMv2 auth = yes[/i]
client plaintext auth (G)

Specifies whether a client should send a plaintext password if the server does not support encrypted passwords.
Default: client plaintext auth = no[/i]

Alles anzeigen

Zitat von flmaxey

The Samba protocol does an auto-negotiate that works most of the time but, as it is with anything "auto", there can be problems.
Win10 can be problematic in that its' preferred protocol (depending on the installation) can be at the top end of the 3.XX range.

The client "max" and "min" protocol settings restrict the negotiation process on the OMV side. Hopefully, you can find something to "bracket" what you need, with the info @raulfg3 provided to you, above.

For instance:
client min protocol = SMB2
client max protocol = SMB2
might work for you.

You can try these parameters here:
forum.openmediavault.org/wsc/index.php?attachment/8059/

On the Win10 end of it, as it seems, there are command lines for power shell to turn SMB levels on and off. Since I don't have a Win10 client, I can't test them but I image they work. Nailing it down to SMB2 only, on both ends (OMV and Windows), would be an approach I might try.

Alles anzeigen

i did get the shares to work, having users set to not being able to access the share at all caused it to not show up, users needed to have read only access. also i think i had a currupt install of omv because the usb i was using had heaps of water damage and it works like only 10% of the time.

Zitat von raulfg3

revise SMB MaxServer & Client on OMV, NTLM is not supported anymore by SAMBA/CIFS

i dont understand, please explain

Zitat von macom

In your other post you write, that you are installing now OMV4. So this post is obsolete?

yes it will be unless i have the same problem. havent successfully installed OMV4 yet.

Zitat von geaves

I've dropped M/S, but that error would suggest that file and print sharing needs to be turned on in W10....this explains how.

it already is enabled.

Hello,
my samba share is not showing up on windows 10 at all, i am running windows 10 build 17017.rs_prerelease.171010-1400. is there any configs i need to provide at all?
when i try \\192.168.0.15 in windows explorer and i goto troubleshooting when it says it fails it reports back this error The device or resource (192.168.0.15) is not set up to accept connections on port "The File and printer sharing (SMB)".
Thank You.

UPDATE: i just downloaded and and now in the process of installing omv 4.0.14

Please Help,
when i try to update i get the following error here:

>>> *************** Error ***************
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; export DEBIAN_FRONTEND=noninteractive; apt-get --yes --force-yes --fix-missing --auto-remove --allow-unauthenticated --show-upgraded --option DPkg::Options::="--force-confold" install base-files bind9-host firmware-adi firmware-amd-graphics firmware-atheros firmware-bnx2 firmware-bnx2x firmware-brcm80211 firmware-intelwimax firmware-ipw2x00 firmware-ivtv firmware-iwlwifi firmware-libertas firmware-linux firmware-linux-nonfree firmware-misc-nonfree firmware-myricom firmware-netxen firmware-qlogic firmware-ralink firmware-realtek firmware-samsung firmware-ti-connectivity gnupg gpgv iucode-tool libbind9-90 libcups2 libcurl3-gnutls libdb5.3 libdbi1 libdns-export100 libdns100 libgd3 libgssapi-krb5-2 libicu52 libirs-export91 libisc-export95 libisc95 libisccc90 libisccfg-export90 libisccfg90 libk5crypto3 libkrb5-3 libkrb5support0 liblwres90 libncurses5 libncursesw5 libperl5.20 libssl1.0.0 libtinfo5 libwbclient0 libx11-6 libx11-data libxml2 ncurses-base ncurses-bin openssh-client openssh-server openssh-sftp-server openssl perl perl-base perl-modules rsync tzdata wget wpasupplicant 2>&1' with exit code '100': Reading package lists...


Building dependency tree...


Reading state information...


firmware-adi is already the newest version.
firmware-ralink is already the newest version.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:


The following packages have unmet dependencies:
 firmware-misc-nonfree : Breaks: firmware-adi
                         Breaks: firmware-ralink
E: Unable to correct problems, you have held broken packages.
<<< *************************************

my update settings are set to pre-release as i saw in another forum post to resolve this error but it did not make any difference
i am running version 3.0.94