Reply to thread

Message

<blockquote data-quote="Jay_UK" data-source="post: 733139" data-attributes="member: 98509">Hi there,A better way than using RunAs is to load up the services control panel (start/run/services.msc), double click the iPimp service, and select the Logon tab. From there change the Local System Account to be the account that can access the NAS.Restart the HTPC or the service and try that.J.Cheezey,Amongst the 1000000 of other features/changes you are working on, have you remembered anything around how the Clientcontroller &quot;pings&quot; the server? I still get dropped frames on my HTPC (single seat) when this currently happens <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown&nbsp; &nbsp; :(" loading="lazy" data-shortname=":(" />I have tried different network drivers with no joy. I am about to try a different NIC.Thanks,J.</blockquote>

[QUOTE="Jay_UK, post: 733139, member: 98509"] Hi there, A better way than using RunAs is to load up the services control panel (start/run/services.msc), double click the iPimp service, and select the Logon tab. From there change the Local System Account to be the account that can access the NAS. Restart the HTPC or the service and try that. J. Cheezey, Amongst the 1000000 of other features/changes you are working on, have you remembered anything around how the Clientcontroller "pings" the server? I still get dropped frames on my HTPC (single seat) when this currently happens :( I have tried different network drivers with no joy. I am about to try a different NIC. Thanks, J. [/QUOTE]

Verification