Linux smb1 disabled no workgroup available

Еще раз про доступ к SMB сетевым ресурсам

Добрый день.
Есть следующая ситуация:
— небольшая одноранговая ЛВС (20 РС)
— есть файловый сервер Синолоджи с подключением к нему по протоколу smb с РС под Вынь
— есть сервер удаленных рабочих столов под ЛИНУКС-рунту16.04 (протокол РДП) для выхода в инет с РС под Вынь + на сервере для каждого пользователя сетевые папки(САМБА) для обмена файлами из почты
все работает как предначертано, в том числе с РДП-сервера есть доступ к сетевым каталогам на СИНОЛОДЖИ

Решил перевести часть пользователей на чистый Линукс-рунту20.04:
— установил ОС на самый простой РС (core duo 2 gb memory)
— установил самба+клиент+кифс (но на РС нет своего сетевого каталога, ненужно, все на файл-сервере)

В результате:
— при подключении к линукс РДП-серверу идет запрос логин-пароль, запоминается, есть доступ к сетевым каталогам
— при подключении к РС(под Вынь или Синолоджи) в сети через тунар(наутилус) видны сетевые каталоги на хосте, но при попытке входа нет запроса на ввод логин-пароль и естественно самого подключения (через 10. 20 сек появляеия сообщение от файл-манагера что ничего путного невышло)
— при подключении через терминал:

sudo smbclient -L \\192.168.0.8 -N

Sharename Type Comment
——— —- ——-
print$ Disk Printer Drivers
sysad Disk
dizzi01 Disk
.
SMB1 disabled — no workgroup available
—————— это подключение к линукс серверу РДП, все работает

sudo smbclient -L \\192.168.0.9 -N
protocol negotiation failed: NT_STATUS_IO_TIMEOUT
—————————- это подключение к ВЫнь, отказ

sudo smbclient -L \\192.168.0.102 -N
protocol negotiation failed: NT_STATUS_CONNECTION_DISCONNECTED
—————————- это подключение к Синолоджи, отказ

в общем постоянно вот это: protocol negotiation failed

Вопрос: что это такое protocol negotiation failed и как его забороть
Заранее всем спасибо

Источник

Arch Linux

You are not logged in.

#1 2017-10-28 11:07:59

[SOLVED] Cant enter samba shares — no workgroup in Samba

I would like to ask for your help. I dont know what i could do much to solve my problem. I just cant enter samba shares via KDE/Dolphin.

This is log from terminal

I start Dolphin > Samba Shares > and in «nSamba Shares» should be at last my home folder or my shares. There is no single one. Folder of my arch is being shown only when i enter ip address of my machine into Dolphin bar, but even when i try to access it, i just cant. I got error about «unknown error in stat file, report bug to KDE».

I have this in my setup of samba:

i have this in /etc/hosts:

and this in /etc/nsswitch.conf

Could somebody help?

Forget about this:

Last edited by firekage (2017-10-29 12:41:55)

#2 2017-10-29 12:39:56

Re: [SOLVED] Cant enter samba shares — no workgroup in Samba

Ok. I now know perfectly that is was not Samba issue, not my samba config issue. but. again, something wrong with updates, linux, KDE, or Dolphin. I’ve been trying to solve it past several days, wasting time. because i was digging in Samba, Samba configuration. my usershares and network configuration.

This was something that solved my problem:

It should be in KDE section, Dolphin section or even Arch Samba section!

Here, what is important:

section of smb.conf there should be placed this:

. Why something like this is not mentioned, explained but solution should be searched everywhere? What is most funny, i made topic on Arch site, while when somebody ask about Manjaro, here, topic is closed! Strange. Strange is something more — i had to use it from last updated. Never used this earlier!

Last edited by firekage (2017-10-29 12:41:35)

#3 2017-10-29 13:10:07

Re: [SOLVED] Cant enter samba shares — no workgroup in Samba

This is actually all over the place in different variants. The cause is that upstream switched the default protocol because SMBv1 had recently rather bad press.

The correct solution is btw. to NOT use dolphin kio-cifs, https://bugs.kde.org/show_bug.cgi?id=339752
I’m not sure about the claimed upstream fix, but a general issue will be that the higher protocol versions do not provide posix extensions, iow: stop using SMB, it’s a crap protocol to begin with (and this is btw. also stance of the SAMBA developers — SAMBA exists because SMB is significant, not because it’s a good choice)

#4 2017-12-05 07:13:10

Re: [SOLVED] Cant enter samba shares — no workgroup in Samba

Don’t understand. Stop using SMB, so use what? There is nothing more that does this kind of job, right?

Last edited by firekage (2017-12-05 07:13:34)

#5 2017-12-05 08:28:16

Re: [SOLVED] Cant enter samba shares — no workgroup in Samba

What is «this kind of job»?
If you’re spellbound to windows, then the answer is (for the moment): «not reasonably».
Otherwise smb is redundant in it’s function as remote filesystem or printer sharing protocol as well as RPC (if you actually want to buy into this)

In a pure POSIX environment, SMB is about the worst choice for every job it does.

#6 2017-12-05 08:35:56

Re: [SOLVED] Cant enter samba shares — no workgroup in Samba

So in other word, if i want to browse my shares under Arch, and using of Samba is a wrong choice, than is there any other choice? I always knew that it is only SMB for linux file sharing across computers.

#7 2017-12-05 08:41:00

Re: [SOLVED] Cant enter samba shares — no workgroup in Samba

if i want to browse my shares

What «shares»? If you want to access windows shares, using NFS et al. under windows is still rather a PITA. If you don’t have a windows system in your network, «man nfs», if your connection is unreliable (because you shutdown systems etc) also have a brief look at https://unix.stackexchange.com/question … -directory

#8 2018-03-24 17:34:12

Re: [SOLVED] Cant enter samba shares — no workgroup in Samba

Firekage, thanks for the suggestion of using:
client max protocol = NT1
in the global section. I was banging my head aginst the wall on this. Share browsing works on my ubuntu machines but not arch. Now it does.

Second, please quit bashing samba. Even in a pure linux environment (like mine) it is still needed and up to date docs are required. There are many IoT devices which use only samba.

Last edited by gearhead (2018-03-24 17:39:38)

#9 2018-03-24 17:42:28

Re: [SOLVED] Cant enter samba shares — no workgroup in Samba

It’s requirement does certainly not relate to its quality (or lack thereof) — and questioning the latter isn’t «bashing».

Please also notice that setting the max protocol to NT1 is a terrible «solution»
NT1 was ditched because of the inherent security flaws that caused the wannacry et al. situation. You should not use it and you should certainly not enforce its usage.

#10 2018-03-24 17:57:24

Re: [SOLVED] Cant enter samba shares — no workgroup in Samba

Even in a pure linux environment (like mine) it is still needed

I’d be interested to know why it’s still needed. What does it do that can’t be achieved with native Linux software?

No, it didn’t «fix» anything. It just shifted the brokeness one space to the right. — jasonwryan
Closing — for deletion; Banning — for muppetry. — jasonwryan

Источник

Thread: Samba problem — no workgroup available

Thread Tools

Display

Samba problem — no workgroup available

I can reach the workstations using smbclient -L and IP adresses, but smbtree does not give any output, and dolphin does not see the workstations (Win 10).

After reading posts on the forum I have read about the /etc/hosts file. I have put in the IP adress of my opensuse server, but I’m not sure if I have done it right:

I get the message above, and wonder if someone can give me a hint about my setup which makes this go wrong.

Re: Samba problem — no workgroup available

Re: Samba problem — no workgroup available

BTW, are all your samba hosts SMB2+ capable?

Re: Samba problem — no workgroup available

SMBv1 appears to be properly disabled.

Your /etc/hosts file entry only describes the machine hostname «opensuse»
Depending on your client connection string, the entry you created might be sufficient to successfully connect but would not likely fix the error you’re seeing.
The Workgroup name is in addition to the hostname, eg opensuse.workgroup where «workgroup» would be whatever your workgroup ;name is.

If you don’t know what your workgroup name should be, perhaps a good place to start would be whatever your SAMbA server is already configured with and so would require.

Inspect your smb.conf and if necessary post for others to view. Offhand, I con’t think there is anything unique or sensitive others shouldn’t see it. Your smb.conf will likely identify your workgroup as a DOMAIN.

Re: Samba problem — no workgroup available

BTW —
I’d direct your attention to the «Sticky post» at the top of this Forum which describes specifically configuring the Workgroup.

Re: Samba problem — no workgroup available

Re: Samba problem — no workgroup available

Here is the output from the windows machine:

Re: Samba problem — no workgroup available

Here is the output from the windows machine:

Ok, that looks as expected. You mentioned that «Dolphin does not see the workstations (Win 10).» That is expected (now that NetBIOS discovery is deprecated and disabled). However, if using Dolpin 20.04.0+, the newer WS-Discovery protocol can be used, assuming the requisite discovery services are turned on in Windows of course.
https://fitzcarraldoblog.wordpress.c. nux-computers/

If not already doing so, you’d need to upgrade using the KDE repos as I already outlined.
https://forums.opensuse.org/showthre. 01#post2955301

Last edited by deano_ferrari; 18-Aug-2020 at 15:19 .

Re: Samba problem — no workgroup available

Here is my /etc/samba/smb.conf:

Some suggestions although I don’t think should affect your current problem.

Change or shorten your WORKGROUP name,
Although the current hame is supportd by hostname resolution (aka using DNS, /etc/hosts), it’s unusable by any systems that try to convert or read it as a NetBIOS name which has a limit of 8 characters without spaces and special characters.
Remove lmhosts and winds, that’s the NetBIOS name resolution system which would be screwed up by your current WORKGROUP name and shouldn’t be used nowadays. It’s a relic of the old MSWindows NT4 architecture no one should be using anymore without good reason.

Restart, or better yet just reboot your system after making the above changes and test. Maybe that’ll fix the WORKGROUP error although it’ll still make a diff how you create your connection string.

Are you using YaST to set up your server and clients or are you handcrafting connections?
Auto discovery is nice, but you wouldn’t need that if you simply use a valid connection string.

BTW — After you fix your workgroup name, you can set up both the FQDN and simple name entries in your /etc/hosts file.
And your connection string might be something like the following (adjust as necessary)

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

[solved] accessing windows 10 machines from linux

[solved] accessing windows 10 machines from linux

Post by callmejoe » Mon Apr 09, 2018 11:30 am

so from what i’ve read so far since MS has disabled SMB version 1 in their last update this breaks sharing access from linux. I can’t connect from linux mint or from raspbian any longer.

re-enabling SMBv1 on windows 10 brings share access back, but i know there are security issues with SMBv1. i’ve tried other fixes i’ve found in various posts around, but none have worked for me.

i came across this post from altair4, viewtopic.php?f=42&t=249758, but as I read through i can’t tell exactly what I need to do.

Re: accessing windows 10 machines from linux

Post by altair4 » Mon Apr 09, 2018 12:44 pm

[1] On the smbclient end you edit /etc/samba/smb.conf and add the following line — right under the workgroup = WORKGROUP line:

Restart your file manager and access the Win10 machine by name or ip address. So in nemo run smb://win10-host-name or smb://win10-ip-address .

Just keep in mind the Bad News:

Samba client host browsing ( the Computer Browsing Service in Windows ) and SMB1 are linked. You can not have one without the other. When you set the client max protocol to anything other than SMB1 ( called NT1 in Samba ) going to Nemo > Network > Windows Network results in an empty space.

Re: accessing windows 10 machines from linux

Post by callmejoe » Mon Apr 09, 2018 6:52 pm

client max protocol = SMB3

i tried to add that line to my raspberry pi machine, but it didn’t work. i figured since they are both based on debian it would work. oh well

Re: accessing windows 10 machines from linux

Post by callmejoe » Tue Apr 10, 2018 1:45 pm

can i open up this thread again? i am having the same trouble accessing shares on my windows 10 machine from my raspberry pi. i know this is a linux mint fourm. but i came across altair4’s thread here and i might be on to something

so here is a screenshot after running smbclient

so i see the shared folders but the connection still fails.

Re: accessing windows 10 machines from linux

Post by AZgl1500 » Tue Apr 10, 2018 1:46 pm

Install Teamviewer on both machines.

works for me, TV offers «file transfer mode»

Re: accessing windows 10 machines from linux

Post by altair4 » Tue Apr 10, 2018 3:49 pm

I don’t know if I can help you with the raspberry pi since I do not know anything about it.

But I can tell you that the output you posted and the error message that came with is unfortunately standard these days. For example:

$ smbclient -L 192.168.1.208 -m SMB3 -U smbuser
Enter smbuser’s password:
Domain=[VWIN10] OS=[] Server=[]

Sharename Type Comment
——— —- ——-
ADMIN$ Disk Remote Admin
C$ Disk Default share
Documents Disk
IPC$ IPC Remote IPC
print$ Disk Printer Drivers
Shared Disk
Users Disk
Connection to 192.168.1.208 failed (Error NT_STATUS_RESOURCE_NAME_NOT_FOUND)
NetBIOS over TCP disabled — no workgroup available

$ smbclient // 192.168.1.208/documents -m SMB3 -U smbuser
Enter smbuser’s password:
Domain=[VWIN10] OS=[] Server=[]
smb: \> ls
. DR 0 Tue Apr 10 15:23:50 2018
.. DR 0 Tue Apr 10 15:23:50 2018
desktop.ini AHS 402 Tue Apr 10 15:23:50 2018
FromLin.txt A 0 Thu Nov 26 18:44:27 2015
gedit.txt A 1 Mon Sep 11 14:48:05 2017
My Music DHS 0 Mon Apr 2 11:16:57 2018
My Pictures DHS 0 Mon Apr 2 11:16:57 2018
My Videos DHS 0 Mon Apr 2 11:16:57 2018
OnWIn.txt.txt A 5 Tue Apr 19 16:05:23 2016
Untitled Document.txt A 6 Sun Jun 26 19:03:15 2016

8183295 blocks of size 4096. 3989657 blocks available
smb: \> quit
altair@xub1404:

Источник