I'm having issues with my shares again. This time it seems to be MS Office in particular.
I can open any file over the network with any other peace of software, but multiple users have complained that office opens files on the share really slow and in protected view. I've added the share to trusted locations, have enabled "Trust files from the network" but still, office opens file in protected view and downloads the files first(this is a very big issues when working with 100mb+ powerpoints over WiFi). Based on the error message Office thinks the files come from the internet and can't be trusted. My guess is that Office is downloading the files for a virus scan or validation or something. I have turned all the settings I can think of or find through google that might cause this behavior.
Considering that the old QNAP office NAS wasn't getting these issues, I'm going to guess that some features or option of samba isn't setup correctly. QNAP is also running a UNIX-based system, and uses Samba for its shares.
Anyone else have similar issues in the past and managed to get a fix for them?
I can open any file over the network with any other peace of software, but multiple users have complained that office opens files on the share really slow and in protected view. I've added the share to trusted locations, have enabled "Trust files from the network" but still, office opens file in protected view and downloads the files first(this is a very big issues when working with 100mb+ powerpoints over WiFi). Based on the error message Office thinks the files come from the internet and can't be trusted. My guess is that Office is downloading the files for a virus scan or validation or something. I have turned all the settings I can think of or find through google that might cause this behavior.
Considering that the old QNAP office NAS wasn't getting these issues, I'm going to guess that some features or option of samba isn't setup correctly. QNAP is also running a UNIX-based system, and uses Samba for its shares.
Anyone else have similar issues in the past and managed to get a fix for them?
Last edited: