Kodi / documented application workflow · Publisher-documented application guidance; UK IPTV account compatibility not tested. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Separate discovery and access
Begin with the server identity, intended shared folder and the exact Kodi environment. Not seeing a server in a browse list and failing to open a known authorised share are different observations. Record which one occurs. Avoid publishing a share password or private network path, and do not reset a viewing-service account to diagnose a local file-sharing problem.
Inspect the allowed protocol range
Kodi’s official SMB client page provides minimum and maximum protocol controls and a separate WS-Discovery option. The page, marked for version 22, explicitly discourages SMBv1 because of serious security weaknesses. A tutorial recommending v1 should not be followed simply because it makes an older screenshot match. Identify what the server and client currently support and use their documented compatible arrangement.
Keep legacy compatibility separate
The same page describes a legacy-security option for particular older sharing devices. Its existence is not a recommendation to enable it on every network or a guarantee that it solves a browsing issue. If the server only supports an obsolete arrangement, establish that limitation and consider the server’s supported update or replacement route. Do not change unrelated router features or expose a local share to the public internet.
Retain a controlled comparison
After a documented change, test the same authorised path and sample, then record the result and the chosen protocol settings. Do not modify several controls at once and call the outcome proof of one specific cause. Throughput tuning is a later question after access works; a chunk-size option does not resolve incorrect credentials or unsupported negotiation. No UK IPTV network-share configuration is asserted here.