Twonky Forum

My twonky server is installed on a XP client working as a server. I had my media files on a file server which is not identical with the first.
My problem is that twonky didn't find the files on that other server.
I can see that on the twonky server statuspage:

Letzte Änderung: Läuft...
[-unc share name]...

but no indexing happens.
Did anyone has an idea?

Tom

On the sharing page use the IP address of the file server not its name i.e. for me I use \\192.168.2.150\Music instead of \\WILMA\Music and that works.

PB

PeeBee wrote:On the sharing page use the IP address of the file server not its name i.e. for me I use \\192.168.2.150\Music instead of \\WILMA\Music and that works.

PB

I don't know why but it didn't work, too. During the last hours I've tried the version \\10.10.200.200\music\parents and file://10.10.200.200/music/parents with no result. I am sure that the client with the Twonky Server had propper rights for crawling the fileserver.

Tom

riethmueller wrote:

PeeBee wrote:On the sharing page use the IP address of the file server not its name i.e. for me I use \\192.168.2.150\Music instead of \\WILMA\Music and that works.

PB

I don't know why but it didn't work, too. During the last hours I've tried the version \\10.10.200.200\music\parents and file://10.10.200.200/music/parents with no result. I am sure that the client with the Twonky Server had propper rights for crawling the fileserver.

Tom

file:// anything won't work. Windows does not recognise that. If you are running Twonky on Windows XP I don't know of any way for the Twonky server to recognise network shares. It is not a Twonky restriction but rather just the way Windows networking security works. A Windows service process usually does not have sufficient privileges to access network resources. And it definitely cannot access mapped drives. They only exist in the context of a logon session.

Yeah parnott thank you, thats it ..., sometimes I didn't see the forrest ...,

that was the necessary hint for me.

>Windows service process usually does not have sufficient privileges to access network resources
If you start the service with administrator rights it works!

Just give the Twonky service the admin rights it works. I'm sure I can customize a user with the propper rights for this service without using an admin account.

Thank you all
for your help

Tom

parnott wrote:file:// anything won't work. Windows does not recognise that. If you are running Twonky on Windows XP I don't know of any way for the Twonky server to recognise network shares.

I have 2 instances of Twonky 6.0.30 running: one on my Linkstation Pro and the other on my Windows 7 PC. Both of them share the same files located on my LS Pro. On the LS Pro itself I share them as the actual filesystem locations on the NAS (/mnt/disk1/Music) and on the PC I use the URL as I described above (\\192.168.2.150\Music). Both work fine for me.

People have had the issue before of not being able to use a server name in the URL but the IP address has always seemed to work for them so far.

Are you saying that Twonky on XP and Win7 are handling shares differently? I could install Twonky 6.0.30 on my son's PC running XP and try it.

PB

PeeBee wrote:

parnott wrote:Are you saying that Twonky on XP and Win7 are handling shares differently? I could install Twonky 6.0.30 on my son's PC running XP and try it.

PB

No. Sorry, I wasn't very clear.

What I intended to say is that when Twonky runs as a service (i.e. it runs even when no user is logged in), that services usually don't have sufficient privileges to access network resources (i.e. shares). It has been basically this way since day one with Win NT and its successors W2K, XP, Vista, Win7 and all the server versions.

I have been told that there are ways of tweaking the security credentials of a service to allow it to access network resources. But, I have never found one that is reliable and secure. Now this was in the context of a corporate network, so in a home network there are probably ways to loosen up the security without too much risk.