If Kodi cannot open an SMB share, separate three questions: can the device reach the server, can the account access the folder, and can Kodi open the exact share? A missing server in a browsing list is not the same as a failed direct connection.
This guide assumes a home network and media you are authorised to access. Do not expose a file-sharing service to the public internet as a troubleshooting shortcut.
Check the share outside Kodi
From another device on the same network, open the intended share with the same account. Use a small, non-private test file. If that fails, investigate the server or account first.
Check whether the player and server are on the same usable local network. A guest Wi-Fi network may behave differently from the network used by the NAS. Record the network names rather than assuming two nearby devices can communicate.
Use a precise network location
Kodi’s SMB documentation describes adding a network location using a server name or IP address, a shared folder and credentials where required. It specifies SMB version 2 or higher.
- Identify the server. Confirm its current local address or device name through your own network’s management tools.
- Confirm the share name. Use the published share, not an arbitrary folder path copied from the server’s local file browser.
- Add the location in Kodi. Select the SMB protocol and enter the server, share and required account details in the appropriate fields.
- Open one file. Establish access before configuring library scraping or testing a large collection.
Distinguish credentials from discovery
If browsing shows no server but a direct address works, focus on discovery or name resolution. If Kodi reaches the share but refuses the account, check the credentials and that account’s access to the specific folder.
A test using a different administrator account is not proof that the normal account has permission. Grant only the access your use requires; do not broadly open private folders to make one media file play.
Watch for changing addresses
A source pointing to an old server address can stop working after a network change. Kodi’s documentation recommends a reserved address when using the IP-based approach. Follow your router’s instructions and preserve existing reservations rather than assigning an arbitrary address.
After fixing access, test again following a normal restart. Record the working server identifier and share name, keeping passwords out of public notes.
Frequently asked questions
Should I enable SMB1?
Do not use an old-protocol downgrade as the default fix. Configure a supported SMB2-or-higher connection and check the server’s documentation.
The file opens but stutters. What next?
Access and playback performance are separate issues. Compare a local copy using our video stutter workflow. For persistent access errors, capture a reviewed debug log.