All my Kontakt libraries are on a WD NAS drive. Using Windows 10 it finds the libraries and adds them but then I get Library Content Not Found. I try to manually add it by browsing to the folder and it will not.

I have to look under NETWORK. It does not see my mapped drives. I also tried creating a symbolic link to a folder and that did not work.

I tried 5.6.8, upgrading from there, and a couple other version to 5.8.1. Did not try portable. Tried deleting, cleaning, reinstalling.

Any ideas would be greatly appreciated. It used to work before switching computers due to a crash.
Mike

 

I think Kontakt needs to see the mapped drives, not sure 100%. What I mean is that Kontakt needs to see a drive in general. Perhaps I'll try.
Probably won't help but have you tried to resave the instruments?

 

I tried and it worked for me. Clearly something is different on your current computer but I'm sure you can tweak it to work.

 

I think the best way is to set up an iSCSI drive. With us it works very well with all libraries. Depending on the formatting, it can even be connected to multiple systems at the same time. For us it is a Mac and two Windows 7 x64 computers.

 

Thanks, what version are you running? I have a second system also on Windows 10. I'll load it up and see if I get the same results.

 

Windows 10 v1709 (RS3?) b16299 x64 Pro
Kontakt no install v5.8.1 (it also works with older versions, I tried with v5.6.8)
Pretty standard Ethernet 1GB LAN.

I don't use a NAS, I just connect my laptop to my desktop computer. But it should be similar.

I think the key is to tweak the network settings until Kontakt sees the mapped drives.

 

Perhaps this can help you with the symlink approach:
https://answers.microsoft.com/en-us...rk-drive/61250cc3-8daf-43e2-b942-472cf9ff4f0a

 

You mean exFAT or a more advanced concept?

 

No .... https://support.wdc.com/knowledgebase/answer.aspx?ID=13116 or https://support.wdc.com/knowledgebase/answer.aspx?ID=13111

 

Very cool. I think Daemon has a tool for this iSCSI set-ups.

 

Tried building a Symlink, I'll read through all these docs tonight, clean out the registry and system, then try again. It seems to run fine but does not want to see attached drives from my NAS for from fileshares on another WIN10 box. Just doesn't like anything on the network.

Maybe it's using something other than standard fileshare ports 137-139, 445. I'll try disabling the firewall and see if that helps as well.

 

Only had time to skim before work. This looks interesting. I'll try this tonight!