OmniOS 5.11 omnios-2fb9a48 | SMB2

[smartie3302]

Hi,

I have OmniOS server serving CIFS to Windows domain users and now most of our users are using Windows 10 and it requires SMB2.

I would like to know if there's a way to enable SMB2 on my OmniOS server?

Here's my SMB information

root@san13:/root# sharectl get smb
system_comment=
max_workers=1024
netbios_scope=
lmauth_level=4
keep_alive=5400
wins_server_1=
wins_server_2=
wins_exclude=
signing_enabled=false
signing_required=false
restrict_anonymous=false
pdc=
ads_site=
ddns_enable=false
autohome_map=/etc
ipv6_enable=false
print_enable=false
traverse_mounts=true
map=
unmap=
disposition=

Thanks in advance
Albert

 

[PD_ZFS-User]

Here are a couple of references that may help.

OmniOS CE r151032 or later supports SMB3 and should probably work.

Topicbox

illumos.topicbox.com

OmniOS r151018 or later supported SMB2.1 but a fix was required to connect from Windows clients with SMB1 disabled. However, I'm not sure in which version of OmniOS this fix was applied. @gea may know the answer. https://forums.servethehome.com/index.php?threads/omnios-and-smbv1.18706/

Best of luck

 

[gea]

It seems you use a very very very old OmniOS 151014 with SMB1 only.

You should update either to latest OmniOS 151038 long term stable or current OmniOS 151040 stable, OmniOS Community Edition. Both support SMB 3.1.1. Only with Windows 11, Windows Server 2022 or OSX v.12 you have problems due the new 256bit ciphers. They are ready in OmniOS but not enabled as defaults, (see Feature #14047: Add support for SMB 3.1.1 AES-256 - illumos gate - illumos).

While it is not impossible to update 151014 to current it is not suggested (many steps, some problems due change of certificates or the move from Sun SSH to OpenSSH or newer compilers that need a deinstall of older ones). I would simply export the pool, install a current OmniOS and import the pool. If you use SMB with local users/groups, re-create SMB groups with same names and users with same UID/GID (not needed with AD).