Kodi не видит smb windows 10 - Доктор Windows - ваш надежный помощник

Posts: 7

Joined: Jun 2016

Reputation:
0

When I try to access SMB shares on a Windows 10 machine from my FireTV stick, I keep getting «invalid argument» errors. Sometimes it allows me to access the share and it’s fine, but that’s rare and usually it gives me the invalid argument error. I’ve added the share by both selecting browse and choosing the share, and I’ve also added it manually through «select network location». I’ve googled the issue and some sites suggest changing the IRPstacksize in the registry, but I’ve had no luck with that. This is a really irritating issue and I’d love to find a solution.

Posts: 942

Joined: Mar 2014

Reputation:
39

Smb on 17 is causing problems.I have 2 Android boxes that work fine but my Samsung S10.5 T800 fails with a timeout just trying to access windows workgroup. I’ve also had it happen the same way with Ubuntu. I’m trying to figure it out too but no joy. Best I can hope for is that someone figures it out and posts the fix, not a work around. We have a couple of those already that help but don’t fix it. Like you’ve discovered trying to manually enter an IP. Somewhere else it will fail because smb isn’t working as it should on some devices.

Posts: 5

Joined: Feb 2017

Reputation:
0

I have the same problem.

I installed Kodi 17 on my Smart TV,but cannot add shares from my Windows 10 PC’.
I have been able to set up Weather,some official addons,but that’s all.

I googled the problem and looked through some of the forum discussions and even tried chaning a few settings on the Windows PC,but,it still won’t work;won’t even show the folders beoyond «users» in fact.

Thankfully,I access the Windows Folders using Plex,so all is not lost.

Posts: 942

Joined: Mar 2014

Reputation:
39

I solved my smb issue by going to my router’s firewall settings and turning on NETBIOS. All is just fine and dandy now been working as it should for about a week.

Posts: 5

Joined: Feb 2017

Reputation:
0

Doesn’t help me.

I checked my modem/router’s settings and note that netbios is already on.

Posts: 942

Joined: Mar 2014

Reputation:
39

One other suggestion I saw was to turn on netbios on the machine that you are sharing from, the host. This is done via opening Network Sharing Center…

Click on Connections:Ethernet
Click on Properties button (lower left)
Double click internet Protocol Version 4 (TCP/IPv4)
Click Advanced Button lower right
Click the WINS tab
Click the radio button to Enable NetBios over TCP/IP

Might work…

Posts: 97

Joined: Apr 2015

Reputation:
0

Heart

2017-10-17, 01:38

(2017-02-19, 23:17)flhthemi Wrote: One other suggestion I saw was to turn on netbios on the machine that you are sharing from, the host. This is done via opening Network Sharing Center…

Click on Connections:Ethernet
Click on Properties button (lower left)
Double click internet Protocol Version 4 (TCP/IPv4)
Click Advanced Button lower right
Click the WINS tab
Click the radio button to Enable NetBios over TCP/IP

Might work…

DID work! At least for me. And I tried EVERYTHING else!

Yet when I was struggling with this issue earlier,I was told to turn OFF NetBios over TCP/IP! That was very bad advice.

Thanks, flhthemi

Posts: 23

Joined: Jul 2015

Reputation:
0

Interesting. I’ll have to see if net bios is enabled on my windows 10 server as well. I’ve been banging my head on the wall for the same problem for hours today.

Sent from my iPhone

Posts: 1

Joined: Jan 2018

Reputation:
0

2018-01-07, 22:32
(This post was last modified: 2018-01-07, 22:34 by novikorisnik.
Edit Reason: typos
)

Hi guys. I’ve just registered to post solution regarding connecting errors with Kodi using windows 10 SMB shares. (getting timeout error after I upgraded from win7 to win10 few days ago).

In windows 10, you have to enable SMB 1.0 because kodi uses this older version of SMB.

As explained here:

http://kodi.wiki/view/SMB/Windows

Cheers.

Posts: 2

Joined: Jan 2018

Reputation:
0

Thank you for your solution. I came to the same conclusion, that my earlier problem of the so called «invalid argument» had to do with SMB. But I only saw it on the RPi LibreElect version. This version of Kodi implements SMB using all three newer versions. However my version of Windows 10 only provides for SMBv1. So if I wanted to use SMB, I had to set Kodi to SMBv1 max. This was the only way I could connect to shares on my Local Area Network.
Adventures in PC Land should be the title of a best seller.

Posts: 4

Joined: Feb 2018

Reputation:
0

I could not get the sc config command (or sc.exe in Powershell) to achieve the result I desired, so I resorted to two registry edits and a reboot. See new steps below. Try this:
1. Run «tasklist /svc»
In the output, you should see something like this: Browser and LanmanServer running in their own svchost processes. *Sample output below is abbreviated for illustration purposes. You will see a longer list.Image Name                     PID Services
========================= ======== ==============
svchost.exe                   2772 LanmanServer
svchost.exe                   2868 Browser
2. Run these two commands to add the SvcHostSplitDisable registry value set to 1.

REG ADD HKLMSYSTEMCurrentControlSetServicesBrowser /v SvcHostSplitDisable /t REG_DWORD /d 1 /f

REG ADD HKLMSYSTEMCurrentControlSetServicesLanmanServer /v SvcHostSplitDisable /t REG_DWORD /d 1 /f

This will reconfigure the Browser service to run in a shared svchost with LanmanServer like in previous versions of Windows.

Posts: 4

Joined: Feb 2018

Reputation:
0

Master Browser not working for NON Windows devices in build 1709 and 1703

DaVu

Team-Kodi Member

Posts: 4,486

Joined: Jan 2011

Reputation:
148

DaVu

Team-Kodi Member
Posts: 4,486

Just to mention it…

Enabling the SMB1 support on Windows 10 is a «last resort» solution. SMB1 was disabled for a very good reason. And I agree, that the wiki page, you are referring to, will need (and receive) an update.

SMB1 on Windows 10 was disabled because of security reasons. Enabling it again will open the security hole, which was closed by disabling SMB1, again.

The recommended way should be, to add SMB sources by using the «Select a network location» in Kodi and use the IP instead of the hostname. Also you have to secure your SMB shares with passwords which you have to enter at the specific window in Kodi as well.

Network browsing (to see a share listed under «Network» in Windows File Explorer) was a SMB1 feature and is not supported by SMB2/3. Same counts for «anonymous login». Therefore you will need a password for your SMB shares.

Posts: 1

Joined: Apr 2018

Reputation:
0

same outcome invalid argument even if you use IP address and browse for a directory….

Posts: 293

Joined: Dec 2015

Reputation:
6

mazey

Senior Member
Posts: 293

2018-04-30, 06:07
(This post was last modified: 2018-04-30, 06:22 by mazey.)

kodi v17 doesnt have smb2/3 support so the only option is to enable smb 1 on a windows 10 machine. turn windows features on/off «Smb 1/Cifs Server» just tick that one. i left automatic removal and client unticked.

browsing hasnt worked for awhile you need to add network location in kodi and put the server name or ip in then you can connect to it.

Источник

Hello reader! I’m back again with yet another troubleshooting procedure for Kodi. And this time, I’ll cover the Kodi SMB not working error.

Habitual SMB users on Kodi need no explanation about SMB. However, for the benefit of the new SMB users, I’ll glance through SMB for Kodi.

Server Message Block (SMB) or Windows File Sharing is a client-server protocol Windows uses to share resources over a local network. All the Windows PCs are equipped with SMB and a home user can easily set it up. What makes SMB the best network protocol is its versatility. It can be accessed by any operating system to stream content on any Network Attached Storage (NAS) or other external remote hardware.

In the following sections, you will learn:

How to access local files on Kodi via SMB?
How to fix the Kodi SMB not working issue?
Bonus Kodi SMB tips
SMB alternatives for Kodi
Frequently Asked Questions About Kodi SMB

How to access local files on Kodi via SMB?

There are two basic ways to add a remote media folder to Kodi via SMB. You need to give the folder containing media files Read/Write permission to add the Source Folder to Kodi.

Note: SMB v1 is no longer supported on Kodi. Make sure you are using SMB v2 or higher.

SMB v1 had security issues on Windows and was thus slashed off Windows. The only available option to access shares was to input the IP address or the device name with the path.

To enable browsing SMB shares again, Kodi v19.1 implemented the WS-Discovery protocol (a multicast delivery protocol to access files on a local network). Follow these steps to add a share to Kodi with Windows Network (SMB).

Step 1:

Go to Settings and select File manager

Step 2:

Select Browse source

Step 3:

Select Browse for new shares

Step 4:

From the list of options, choose Windows Network (SMB)

Step 5:

Now, navigate to the source folder path and select it

Step 6:

Hit OK to add the folder to Kodi

If the Windows Network (SMB) method doesn’t work for you, try adding the source folder with the device’s IP address or name. Here’s how to do it!

To add a source folder using the IP address or device name, follow these steps.

Step 1:

Reserve a static IP address for your hardware.

To create a static IP address, add the MAC address of the device to the router’s Reservation list after logging in.

Step 2:

Under Browse for new shares list in Kodi, select Add network location

Step 3:

In the Add network location window, set the protocol to Windows Network (SMB)

Step 4:

Select Server name and input the reserved static IP address of the hardware or the device name (use any one of the two methods)

Step 5:

In the Shared folder field, type in the name of the folder you would like to add as it is saved in the device along with the drive location letter (for IP address method) or just type in the folder name without drive location letter (for device name method)

Step 6:

Type in the username and password if prompted in the same window

Step 7:

Hit OK to complete adding the source media folder

Your share will appear in the Browse for new shares list. Depending on the method you used, you would either see the IP address or the device name for the share.

Before we get started with troubleshooting, make sure you are using SMBv2 or higher. These steps might help you fix the SMB not working error on Kodi 19.

Step 1:

Open Kodi on your PC and go to Settings

Step 2:

Go to Services

Step 3:

On the left pane, select SMB client. If you don’t see the SMB client option on the left pane, make sure you have enabled the Expert settings.

Step 4:

Under SMB client, set the Minimum protocol version to SMB v1 if it is set as None or other

Step 5:

Check the Maximum protocol version and change it to SMB v3. Some Kodi users suggest using SMBv1 for maximum requirement but it is considered to be not as secure as the SMBv3.

Step 6:

Go back to the Library to update the share path

Step 7:

Select a media type and go to files

Step 8:

If you have an existing path in the selected media type, click and hold and select Edit source. Otherwise, select the Add [media type] option

Step 9:

In the Add [media type source] window, click on Browse

Step 10:

If you have the shares added to Kodi, select one. Otherwise, go to Add network location.

Step 11:

Follow the above steps to add a share using the IP address or device name. Make sure to use the same username and password as that of your computer.

This will resolve the ‘Operation not permitted’ error and SMB will be up and running on Kodi in no time. You can now easily access old SMB network locations with the set username and password.

Bonus Kodi SMB Tips

If the above troubleshooting method doesn’t fix the Kodi SMB not working issue, try these fixes.

Turn on the Use legacy security option under SMB client and restart the system and check the folder you are looking for.
Change the WINS server under SMB client to the same IP address as your router and retry
If all the above methods fail, downgrade to Kodi v18. Go to Settings > File manager > Add source > Windows Network (SMB) > WORKGROUP. Under WORKGROUP, you’ll see all the SMB compliant devices connected to your network. Select a device and add the share. You might have to compromise on the new features though.

If you are an avid Kodi streamer, you might want to check out the Best Kodi tips.

SMB alternatives

SMB has been the standard client-server protocol on Windows and DOS since 1992. However, there are quite a few SMB alternatives you might want to consider to enable sharing local files to Kodi. Check them out!

Univention Corporate Server

UCS is an integrated identity and infrastructure management system used to administer users and applications. It is compatible with Windows, Mac OS X, and Linux. It uses Extensive Directory functions to allow integration in Windows.

NQE

NQE is one of the best embedded implementations of the SMB protocol. It is also known as Common Internet File System (CIFS) which is a network file system protocol for providing shared access to files and printers between devices on the same network. With the help of CIFS, you can edit, add, and remove files from the Kodi library.

FAQs

To add a share on Kodi, go to Settings > File manager > Browse source > Browse for new shares > Windows Network (SMB). Finally, navigate to the folder path and hit OK.

Which is better: SMB or NFS?

SMB and NFS are network protocols used to access files over a network. With NFS, every user on an authenticated system can access a specific share as it uses the host-based authentication system. This is not possible with SMB as it uses user-based authentication, by which it is possible to separate multiple users from a single authenticated machine and enable file and printer sharing to all users at once. SMB is the ideal solution for Windows servers, whereas unencrypted NFS is the first-choice protocol for the Linux OS.

Does Windows 10 use SMB?

Currently, SMBv1, SMBv2, and SMBv3 work with Windows. However, the configuration requirements might vary from server to server.

Fix ‘Kodi SMB not working’ error

SMB not working has been a pressing issue on Kodi recently, especially after the release of Kodi 19. Kodi 18 didn’t have any issues with SMB but a lot of Kodi 19 users had trouble with using Kodi for folder share.

The above troubleshooting method should help you fix this burning issue. If not, contact Kodi support. Let us know in the comments section down below if this method worked for you.

Источник

03.10.2016, 14:49

Member

Регистрация: 14.12.2014

Адрес: Москва

Сообщений: 36

KODI не видит расшаренные файлы

Коллеги, подскажите (Виндовс 10 — расшаренная папка films, KODI 16-17 на андроид ТВ боксе). Сеть кое как настроил — но КОДИ не видит файлы лежащие в папке films — только один-два файла появляются при загрузке. Остальные фильмы (их больше 30) не видны хоть убейся. Было у кого такое? На компе все расшарено. В коди добавлен источник по самбе. Все ОК. Но файлы не видны — медиатеку обновлял и тд.. На том же боксе в ES проводнике все видно. Фильмы через ЕС проводник запускаются на КОДИ (он стоит по умолчанию для запуска фильмов). Только КОДИ глючит таким образом!

03.10.2016, 22:57

Member

Регистрация: 14.12.2014

Адрес: Москва

Сообщений: 36

Ради бога чуток поподробней. Где это менять?

04.10.2016, 00:26

Senior Member

Регистрация: 12.12.2009

Адрес: Моск.обл.

Сообщений: 4,469

Цитата:

Сообщение от folegozon

Ради бога чуток поподробней. Где это менять?

На тв боксе с коди примерно по такому пути:
/storage/emulated/0/Android/data/org.xbmc.kodi/fles/.kodi/userdata/advancedsettings.xml
Если такого файла ещё нет, то нужно создать. Может быть Вам более нужна не вторая строка времени ожидание по самба, а первая codepages по использованию имён файлов. Может быть у Вас кириллица с латынью переплелись. А что интересного в kodilog есть? Что пишет?

__________________
Ubuntu 20.0.х, Kodi next

Последний раз редактировалось bigbax; 04.10.2016 в 07:26.

04.10.2016, 09:27

Member

Регистрация: 14.12.2014

Адрес: Москва

Сообщений: 36

В общем подключил другой винт все заработало! Нельзя где система стоит шарить

16.06.2018, 18:38

Senior Member

Регистрация: 21.10.2017

Адрес: Доступно

Сообщений: 882

Вот и у меня аналогичная проблема. Комп и медиаплеер в одной локальной сети, которая активна (могу перебрасывать файлы в обоих направлениях через MyPhoneExplorer). Ho Коди не может проиграть медиафайлы потому, что не видит их. Захожу в папку с видео и фото, но там почему-то пусто, хотя реально там есть файлы. Общий доступ к расшариваемой папке открыт (это папка Videos по умолчанию). Пытался подключить папки и с других локальных дисков. В закладке Сеть компа (после того как открываю к ним Общий доступ) они видны. Коди папки тоже видит, но не видит находящиеся внутри файлы. Причем, предварительно просит у меня логин и пароль (по умолчанию: kodi и пароля нет). Ни так ни сяк не пропускает и я не имею доступа к медиафайлам. Почему в Коди все так усложнено и я не могу просмотреть видео, фото и музыку? (непосредственно с пульта плеера)

17.06.2018, 09:08

Senior Member

Регистрация: 29.11.2010

Адрес: Минск

Сообщений: 1,513

На винде учетка Гость активирована ?
Чтобы винда пускала без ввода пароля в шару .
Нужно либо активировать Гостя, либо и на винде и на удаленной системе должны существоавть одинаковые учетки пользователей с одинаковыми паролями !
Например и на винде и на подключающейся системе должен существовать пользователь kodi и пароль и там и там одинаковый.
Без активированой учетки Гость, виндовс в шару без пароля не пустит без изменений в реестре !

Всё правильно

Цитата:

В закладке Сеть компа (после того как открываю к ним Общий доступ) они видны.

Это вход с локальной машины хоть и по сети . Для локальной машины другие правила безопастности .
Коди к настройкам безопасности операционок никакакого отношения не имеет .

Ну и как бы

Последний раз редактировалось sovaby; 17.06.2018 в 09:26.

17.06.2018, 14:26

Senior Member

Регистрация: 21.10.2017

Адрес: Доступно

Сообщений: 882

Цитата:

Сообщение от sovaby

Да, я знаю это правило с галками в Центре управления сетями и у меня именно так и стоит. Теперь что мне делать? Никакого логина и пароля комп не имеет. Есть лишь имя компа.

17.06.2018, 16:07

Senior Member

Регистрация: 29.11.2010

Адрес: Минск

Сообщений: 1,513

Чтобы винда пускала без ввода пароля в шару .
Нужно активировать Гостя

17.06.2018, 19:55

#10

Senior Member

Регистрация: 21.10.2017

Адрес: Доступно

Сообщений: 882

Цитата:

Сообщение от sovaby

Чтобы винда пускала без ввода пароля в шару .
Нужно активировать Гостя

Активировал Гостя, но это не помогло.

Последний раз редактировалось Lotas; 20.06.2018 в 00:31.

Источник

Содержание

Kodi не видит сеть windows smb
Kodi не видит сеть windows smb
Kodi не видит сеть windows smb
Kodi 18.0 and 18.1 Won’t connect to SMB Network Drive #15544
Comments
TBNRerebus commented Feb 17, 2019 •
Kodi 18 no longer connects properly to SMB network drive
Encounters “Error: Operation Timed Out” / “Remote share: Couldn’t connect to network server»
Expected Behavior
Actual Behavior
Possible Fix
To Reproduce
Debuglog
Screenshots
Additional context or screenshots (if appropriate)
Kodi не видит сеть windows smb

Kodi не видит сеть windows smb

Новые темы необходимо создавать только в корневом разделе! В дальнейшем они будут обработаны модераторами.

Если Вы выложили новую версию программы, пожалуйста, сообщите об этом модератору нажав на вашем сообщении кнопку «Жалоба».

Последнее обновление программы в шапке: 11.10.2022

6486566

6486568

6486570

Краткое описание:
Кросс-платформенный медиацентр XBMC.

Бесплатный кроссплатформенный медиаплеер и программное обеспечение для организации HTPC с открытым исходным кодом. Графический интерфейс программы позволяет легко управлять видеофайлами, фотографиями и музыкой, находящимися на компьютере, оптическом диске, в интернете или в локальной сети. Может управляться с помощью ПДУ.

Android 4.2+:
версия: 16.1 Jarvis for Windows Kodi (Пост _SERGEYX_ #56018605)
версия: 16.0 Jarvis Kodi (Пост fack1900 #47300196)
версия: 16.0 Jarvis x86 Kodi (Пост ROMANFIONOV #47315630)
версия: 15.2 final Kodi (Пост grey684 #43824098)
версия: 15.2 + кэш Kodi (Пост fack1900 #44038040)
версия: 14.2 (x86) Stable kodi-14.2-Helix-x86.apk ( 61,12 МБ )

версия: 14.2 (windows) Stable kodi-14.2-Helix.exe ( 67,82 МБ )

версия: 15.1.1 Kodi (Пост grey684 #42405075)
версия: 15.1 + кэш Kodi (Пост fack1900 #42280136)
версия: 15 + кэш Kodi (Пост fack1900 #41793816)
версия: 15.0 + кэш KODI (XBMC) (Пост fack1900 #41260543)
версия: 14.2 (arm) Stable kodi-14.2-Helix-armeabi-v7a.apk ( 59,74 МБ )

версия: 13 Stable XBMC (Пост #31290789)
версия: 13 XBMC (Пост #31210770)
версия: 12.2 https://4pda.to/forum/dl/post/2915114/xbmc-12.2-Frodo-armeabi-v7a.apk
версия: 12.1 xbmc-12.1-Frodo-armeabi-v7a.apk
версия: 12.0 http://mirrors.xbmc.org/releases/android/x. armeabi-v7a.apk
NEON Devices (Nexus 7 / Tegra3 / Newer Samsung Devices): xbmcapp-armeabi-v7a-debug-08-22-full-neon.apk
Non-NEON Devices (Tegra2 / A500 / A100 / Thrive): xbmcapp-armeabi-v7a-debug-08-22-no-neon.apk
версия: n/axbmcapp_armeabi_v7a_debug_20120714.apk ( 39,01 МБ )

Источник

Kodi не видит сеть windows smb

Последнее обновление программы в шапке: 11.10.2022

6486566

6486568

6486570

Краткое описание:
Кросс-платформенный медиацентр XBMC.

версия: 14.2 (windows) Stable kodi-14.2-Helix.exe ( 67,82 МБ )

Источник

Kodi не видит сеть windows smb

(2015-03-05, 05:42) guyonphone Wrote: 1. Can you access the smb shares from just windows, outside of Kodi on the same machine Kodi is installed on?
2. Have you tried mapping a drive, and setting up the mapped drive in Kodi?
3. Have you performed a full uninstall and fresh install of Kodi?

Theron
Member

(2015-03-05, 08:16) Fry7 Wrote: Have you ruled out that the Win firewall blocks the kodi.exe from accessing your LAN?

Disabled windows firewall for all connection types, that does not work.

For debugging, I turned that on along with component specific debugging and enabled it for SMB library as well. I then closed the program, deleted the debug log. Started it back up an tried to map a my «Videos» share. From looking at the debug, it is completely useless, it does not show much for SMB.

I feel like I should add some additional information here, and this is where it will get confusing. If I do a direct SMB share (without browsing) from Kodi, for example, smb://10.10.2.20/Videos/Movies-HD (not actual path). Kodi will map the folder and show a single movie that I added in my library a few days ago and not the other ones. But when I browse and open the Videos folder, the Movies-HD folder does now show up, like it is hidden? Or possibly an ACL issue? But if this were an ACL issue, why would it work on 13.2 and prior version as well as Windows, but not Kodi. This is part of the reason I am stuck. I have also done packet captures with a side by side comparison. There are obvious difference but I cannot tell for the life of me where in the SMB exchange things are going wrong.

Here is the SMB Browsing Debug (expires in two weeks):
http://pastebin.com/Rd4cup0z

For the Direct SMB Debug (expires in two weeks):
http://pastebin.com/knLje8YD

Here are some screenshots:

[edited] Did major edits to provide additional information and logs

— stop Kodi
— go to your %appdata%Kodiuserdata folder
— edit your sources.xml:

I am not sure I understand your request. The path «smb://192.168.60.25/Movies-HD/» does not exist. I will try your suggestion because I may not be getting something, but I think it should be «smb://192.168.60.25/Video/Movies-HD/». I will try both and let you know the outcome. Also I do not have a passwords.xml file. SMB is doing NTLM automatically (user creds are the same on the NAS and the windows machine). I have manually entered in different credentials to no avail. Ill update this post with the results.

UPDATE:
These are the same results as doing the direct SMB share. I had to update the path provided to include «Video».

Thank you for you help so far.

I don’t know if this helps at all, but I find windows smb can be a flaky. This is what works for me:

1. On all windows machines, in «network and sharing center» in «advanced sharing settings» I have «Turn off password protected sharing» (I’m not particularly worried about attacks from inside my LAN).

2. On all windows machines, for folder shares on that machine I set the folder/file permissions for «Everyone» to have full control. Then I set sharing to «Everyone».

3. I force my most reliable Win 7 machine (don’t have enough experience with Win 8 to comment) to take master browser by shutting down all other systems on my LAN and powering up that system first.

(After doing this, I can reliably browse my local network in windows file explorer from all windows machines. Note that if you have network browser problems often if a system isn’t shown in the network browser, you can still access shares by using the IP addr as computer name.)

4. I don’t ever map shares to local drive letters.

5. On my Synology running DS 4 I have accounts for all machines and use «xbmc» as the user name for each shared folder.

6. I know when windows systems access shared folders, windows can store «credentials» (on first access) and I’m not sure how to clear that store (I assume it’s buried somewhere in your HKLM current control set).

Again this has security implications but as I said, seems to work for me.

(2015-03-05, 22:43) scott967 Wrote: I don’t know if this helps at all, but I find windows smb can be a flaky. This is what works for me:

2. On all windows machines, for folder shares on that machine I set the folder/file permissions for «Everyone» to have full control. Then I set sharing to «Everyone».

3. I force my most reliable Win 7 machine (don’t have enough experience with Win 8 to comment) to take master browser by shutting down all other systems on my LAN and powering up that system first.

4. I don’t ever map shares to local drive letters.

5. On my Synology running DS 4 I have accounts for all machines and use «xbmc» as the user name for each shared folder.

Again this has security implications but as I said, seems to work for me.

You are of course right concerning your SMB path, simply missed to write down your folder ‘Video’.

Anyway, if Kodi can access your NAS using its IP but not when using its name ‘NASBOX’ the only things I could think of would be missing DNS and/or WINS resolution.

You also said that you didn’t have a sources.xml, maybe you take a look at the wiki: http://kodi.wiki/view/sources.xml and try to create one completely on your own.

(2015-03-06, 08:14) Fry7 Wrote: You are of course right concerning your SMB path, simply missed to write down your folder ‘Video’.

Anyway, if Kodi can access your NAS using its IP but not when using its name ‘NASBOX’ the only things I could think of would be missing DNS and/or WINS resolution.

You also said that you didn’t have a sources.xml, maybe you take a look at the wiki: http://kodi.wiki/view/sources.xml and try to create one completely on your own.

I do not have an issues with using a host name VS an IP. It is when I choose to do the windows share browsing VS a direct connect. When I browse my network for available shares, I see the top level folder but nothing underneath it. When direct connect, I can traverse to a lower level directory, but when I do, only a single movie shows up and not my entire library. Kodi does not appear to be listing my shares.

I am probably doing a terrible job at explaining this. The problem is not connecting to the NAS. It is when I connect to my share via Kodi, none of my folders show up. When I connect to the share via windows on the same machine, I can see all my folders just fine. So from the upgrade from 13 to 14, I had my sources, but none of the directories in my defined sources appeared.

Источник

Kodi 18.0 and 18.1 Won’t connect to SMB Network Drive #15544

Kodi 18 no longer connects properly to SMB network drive

Encounters “Error: Operation Timed Out” / “Remote share: Couldn’t connect to network server»

Here is a clear and concise description of what the problem is:
I store my movie files on a 1 Terabyte Apple AirPort Time Capsule (3rd Generation) drive and access them through the SMBv1 share on Kodi and have never had a problem with it on Krypton v17.6. However, when I upgraded from v17.6 to v18.0 and 18.1, the SMB share doesn’t work much anymore. Leia will sometimes connect to my SMB drive for a short thirty seconds or so immediately when you open the program but after that minute it will give you a “Error: Operation timed out” message, even if I try to re-add the remote path under “add videos”. I have tried re-installing the program, tried using another device with a different OS, and tried hard wiring my devices to eliminate any network issues. Kodi v17.6 has no problems even when I uninstall v18 and then immediately install v17.6. This issue only occurs in v18/v18.1.

Expected Behavior

Here is a clear and concise description of what was expected to happen:
Kodi connects to SMBv1 share and streams video files from network drive without any errors or issues.

Actual Behavior

Kodi connects to share for the first thirty seconds after program launch, then displays an Error: Operation timed out” / “Remote share: Couldn’t connect to network server” forever after when trying to access files on the share from Videos>Files.

Possible Fix

Revert the SMB protocol back to what it was in v17.6

To Reproduce

Steps to reproduce the behavior:

Debuglog

The debuglog can be found here:
kodi.log

Screenshots

Here are some screenshots to help explain the problem:

Additional context or screenshots (if appropriate)

Here is some additional context or explanation that might help:

note: Once the issue is made we require you to update it with new information or Kodi versions should that be required.
Team Kodi will consider your problem report however, we will not make any promises the problem will be solved.

The text was updated successfully, but these errors were encountered:

Источник

Kodi не видит сеть windows smb

Последнее обновление программы в шапке: 11.10.2022

6486566

6486568

6486570

Краткое описание:
Кросс-платформенный медиацентр XBMC.

версия: 14.2 (windows) Stable kodi-14.2-Helix.exe ( 67,82 МБ )

Источник

Does your Kodi return this message, “Kodi SMB operation not permitted” when accessing your media?

You are not alone! Kodi can be a great way to enjoy your favorite movies, podcasts, TV shows, and music.

However, Kodi users may find that they are experiencing interference with their networks.

Read on if this is the case for you and find out how to fix this error.

To clear the “Kodi SMB Operation Not permitted” message, first ensure that the SMB protocol is correct. Set SMB V1 as the minimum protocol and the maximum to SMB V3. If this doesn’t work, you can add a username and password if you haven’t already done that.

The following are some of the major causes of your Kodi error message. We’ll also take a close look at the solutions for fixing the error.

Reasons Your Kodi SMB Operations Are Not Permitted

Many reasons may cause the “Kodi SMB Operations Are Not Permitted” message.

Here are some reasons:

You have set the maximum SMB protocol to SMB V1.
You have not set up your username and password.
The password protection for sharing is on.
Media streaming is off.
The source path is incorrect or doesn’t exist.
The VPN setting is restricting performance.

How to Fix SMB Operation Not Permitted Error on Your Kodi

It’s now easier to fix this error successfully after troubleshooting and identifying the source of the problem. Here are some quick fixes you can try:

Solution #1: Check the SMB Protocol Settings

Setting the SMB protocol correctly is fundamental if you want your Kodi to function without issues.

So, check the SMB settings first before trying any other solution. Kodi version 19 doesn’t support SMB V1for security purposes, so change the setting to a higher version.

Ensure that the minimum protocol version is set to SMB V1 and the maximum protocol version to SMB V3.

To check or change the SMB settings, follow these few steps:

Open Kodi from your device
Select services under the settings menu
Click the SMB client and ensure you set the protocols to SMB V1 for minimum and SMB V2 for maximum.

Solution #2: Turn the Media Streaming Option to On

After installing or upgrading Kodi software, you may find that the media streaming option is automatically set to off.

So, ensure to check this setting and set it to on.

Open Network and Sharing Center;
Go to advanced sharing settings under the “All Networks tab” and click on change on your Kodi.
You’ll find a “media streaming option” and click on the “Choose media streaming options” link.
When you click the link, you’ll see “Media streaming is not turned on.”
Click on the “turn on media streaming” option and click OK.

Solution #3: Set a Username and Password

The earlier Kodi versions did require a username and password. So, if you have upgraded your Kodi to version 19, Kodi likely needs you to set up your user account.

Also, this version does not support network browsing, requiring a username and password.

Go to libraries and select your source.
Select the file option, and you’ll see a list of sources.
Scroll down and choose “Add network location.”
From there, you can add your username and password.

Solution #4: Turn off Password Protected for Sharing

The password protection for sharing can sometimes cause the Kodi SMB Operation Not permitted error.

If this password is set to ON, turn it off and see if your Kodi will clear this error.

From your Kodi’s Network and Sharing Center, select the “All Networks tab.”
Scroll down to “password protected sharing.”
The default option is set to “Turn on password protected sharing.”
Turn it off by selecting the “Turn off password protected sharing” and save changes.

Your Kodi should now be able to access your media sources without any errors.

An incorrect source path can result in the Kodi Operation Not permitted SMB message.

If you used the source path before, confirm that the address is correct.

This is because you might have changed your media source on your device without knowing.

Select your source from the library, for example, music
Select file option
Click and hold on the existing path and then select edit source
You’ll see a list of your sources on the browse for share window
Browse the list to locate your source and select OK after editing the path

If the error is still there, you can also add a new source manually or use the device name or IP address.

Step #1: Scroll down the list of your sources on the browse for share window

Step #2: Select “Add a network location.”

Step #3: Select server name and key in the IP address or the device name

Step #4: Your new path should now reflect on the browse for share window

Solution #6: Turn off the VPN

Sometimes your VPN settings can interfere with Kodi’s performance. This can happen, especially if you install it or change its settings.

However, VPN is a good protection tool against threats and cybercrimes.

It helps encrypt your data on internet traffic and hide your location and Ip address. So, it’s good to have one installed.

But in this case, you don’t need to enable the VPN when using Kodi. Also, check other protection settings that may hinder your Kodi’s performance.

Do the above solutions fix your problem? If not, it’s always good to try all-purpose solutions for software.

Solution #7: Reboot Your Device or Unplug from Power

Sometimes it can only take a quick reboot to your system to quickly fix your problems. So, reboot your device to allow the Kodi program to refresh.

Rebooting can also help clear some load in the cache, thereby improving the functionality of the Kodi.

Instead of rebooting, you can also prefer unplugging your device’s power cord from the wall outlet. Wait for 10 to 15 seconds for you to plug in your power cable.

Solution #8: Uninstall and Reinstall the Kodi Software

If you’re still receiving the SMB operation not permitted error, it’s time to uninstall the software.

Sometimes bugs can mess up with the normal functioning of programs. So, try the uninstall and reinstall option and fix your problem once and for all.

When you uninstall the software, the system will clear the cache too. This means that if there were a bug causing the error, it would be removed from the device.

When reinstalling the software, ensure you have the updated version. This helps your software to improve performance and provides you with enhanced features.

Ensure to install updates regularly to keep your software updated to eliminate and patch issues with your Kodi.

Solution #9: The Last Resort- Reach out to Kodi Customer Care

If all these solutions haven’t cleared the error message, contact Kodi Customer Care.

According to Kodi, the best way to seek help from Kodi support is by using their active community support forum.

You will receive solutions from other Kodi users and the Kodi support team on the forum.

A remedy for the "SMB operation not permitted" problem on Kodi can't be the same for everyone.

Therefore, it’s a good idea to experiment with different options to determine what works best for you.

To fix the “SMB operation not permitted error,” change the SMB protocol to SMB V1 and SMB V3 for minimum and maximum protocols, respectively. Also, set the media streaming option on and turn off the “password protected for sharing.” You can also update your media source and add a username and password.

Read Next: Can You Put Kodi on Xbox 360?

Bottom Line

The “Kodi SMB operation not permitted” error is a common complaint among its users. The good thing is that you can fix this error quickly.

We hope that these quick fixes will clear the error and allow you to continue enjoying your music, videos, or movies.

Kevin has over five years of experience working in various Tech startups and providing Technical solutions. He has contributed to many Tech publications and websites.

Источник

Kodi is continually going from strength-to-strength. Kodi team is currently working extremely hard to bring Kodi 18 Leia into the public domain with an official release, but, in the meantime, more and more users are onboarding themselves with Kodi 17.6 Krypton, which invariably means that a subset of those users is going to have some teething issues.

For some, those issues are relatively trivial and don’t take much effort to fix or resolve. Others, however, are slightly more complex and actually involve looking at that whole media player infrastructure in order to troubleshoot and fix.

One such issue revolves around content no longer being accessible to a Kodi installation on Android which has been shared via the Windows-based SMB protocol in Windows 10. Naturally, this can be extremely frustrating for anyone accessing content on multiple machines but, thankfully, it can be fixed with a little bit of Registry tinkering.

It is worth mentioning that anything to do with the Windows Registry should be handled and treat with care as editing the wrong areas can cause larger issues throughout the whole system. If you feel comfortable, then carry on reading and let’s dive right in.

Step 1: On your Windows 10 PC, enter into the Registry by entering the Start Menu and typing “regedit” in the Run box and hitting Enter.

Step 2: Once the Registry is opened, find the following key: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesNetBTParameters. Add the following information to it:

Value Name: AllowNBToInternet
Type: DWORD
Value: 1

Step 3: Make sure that all of the above information is saved successfully in the Registry and exit.

Step 4: Now, fully reboot the Windows system to ensure that the changes made in the registry propagate and take effect. Once the system boots, you should find that those changes have taken effect and the issues with the Windows-based SMB protocol have been resolved.

Hopefully, those steps should resolve the SMB sharing issues that you may be experiencing when trying to access shared content via a Kodi installation which is hosted and shared via a Windows machine. Obviously, if Kodi is unable to see and interact with these shares then it makes the whole installation fairly pointless, which makes it even more important to get the issues fixed as soon as is possible.