Reply to thread

Message

<blockquote data-quote="globaldonkey" data-source="post: 1208578" data-attributes="member: 49844">It requires credentials, but they are the same credentials as I am using the the MediaPortal system, so it connects without any additional credentials. I think the logs point to it being a name resolution issue.I'd rather not implement a local hosts file. That's just one of those annoying things you forget about in 2 years time when you change your router / static ip addressing and wonder why it's not working. I've just tried (for giggles, because I really shouldn't / don't need it) enabling WOL on all the shares. It's been running for a couple of hours now watching TV, and the shares are still there. So maybe WOL is refreshing the name to IP resolution information somehow. I'll keep an eye on it for a another day or so and report back.One thing I have noticed, and you can see it in the logs, is that the &quot;share discovery&quot; process is very inefficient. It does a name lookup on all 6 shares, even though the hostname for each share is identical. And the name resolution is sequentially taking about a second for each share, leading to a delay in opening the root folder. This code could be much more efficient I think. I did notice there was another post from 2008 about delays in accessing shares.<a href="https://forum.team-mediaportal.com/threads/delay-to-load-my-videos-with-shared-network-folders.45707/" target="_blank">https://forum.team-mediaportal.com/threads/delay-to-load-my-videos-with-shared-network-folders.45707/</a>Maybe someone could take a look at this?</blockquote>

[QUOTE="globaldonkey, post: 1208578, member: 49844"] It requires credentials, but they are the same credentials as I am using the the MediaPortal system, so it connects without any additional credentials. I think the logs point to it being a name resolution issue. I'd rather not implement a local hosts file. That's just one of those annoying things you forget about in 2 years time when you change your router / static ip addressing and wonder why it's not working. I've just tried (for giggles, because I really shouldn't / don't need it) enabling WOL on all the shares. It's been running for a couple of hours now watching TV, and the shares are still there. So maybe WOL is refreshing the name to IP resolution information somehow. I'll keep an eye on it for a another day or so and report back. One thing I have noticed, and you can see it in the logs, is that the "share discovery" process is very inefficient. It does a name lookup on all 6 shares, even though the hostname for each share is identical. And the name resolution is sequentially taking about a second for each share, leading to a delay in opening the root folder. This code could be much more efficient I think. I did notice there was another post from 2008 about delays in accessing shares. [URL]https://forum.team-mediaportal.com/threads/delay-to-load-my-videos-with-shared-network-folders.45707/[/URL] Maybe someone could take a look at this? [/QUOTE]

Verification