Windows 10: PDF opened from NAS returns index of parent folder

Hi all,

Lately, when I open a PDF file stored on my NAS, Chrome (the default browser) responds with an index of the parent folder as shown in attached screenshot.

The same file opened from a local disk (ie not a mapped drive) opens correctly, in Chrome.

Any idea why this might be happening?

Thx in anticipation.

:)

 

SEARCH Win 10

If you go to the folder on the NAS, right-click and choose "Include in library", it should become indexed (anything in libraries are indexed by default if they can be). Although the indexing restrictions from Windows Vista/7 still apply.

 

How to add NAS shared folders to Win10 Library

Thanks again, but that doesn't work because network folders and the NAS folders are not available in the Indexing Options dialogue boxes.

 

Hello,

Could you install the following extension for Chrome?

PDF Viewer - Chrome Web Store

After completing, restart Chrome and try again.

Cheers.

 

Ahhh, I already had a chrome extension for this purpose that worked well . . . and loading this one made no difference.

 

Is Chrome PDF viewer disabled or checked when you go to chrome://plugins. If you have added any PDF programs, they can change the default programs for PDF's.

 

I wonder what would happen if you'd copy a random .pdf file from your NAS to your desktop and open it from there.

Also, could you open a Run Dialog with Windows key + R.

1) Type in "control /name Microsoft.DefaultPrograms"
2) Click on "Associate a file type or protocol with a program"






3) Find the .pdf extension. Change the default program to Microsoft Edge and click "OK".
4) Now change the default program for .pdf back to Chrome.





Click close and try again. If the issue still persists, you could consider using Microsoft Edge exclusively for .pdf files. But if you want to use Chrome, we can of course look further into the issue.

 

Asuza I am thinking that the OP is going to their NAS in the web browser through FTP. That in itself can be a part of why it is throwing it off. If they left click on the .pdf, it should be opening in Chrome, if they go to that folder in chrome. If not, we are both on the same page that the default program and plugin settings for chrome are screwed up.

 

Hello,

I forgot about that one ! thanks for the reminder. I thought that he was simply accessing his NAS with Windows Explorer.

 

If he has it set for no login needed ftp, it should still work. I only use Samba on mine and FTP is used for the NVidia Shield and a file program I use with the iPhones.

I moved away from cheap NAS's and went with a Synology. Never had any issues with it, compared to the Lenovo ix2-4 that I had. The Lenovo was just one big headache.

 

I figured out what it was . . . it was hiding in plain site

I had to check the "allow access to file URLs" in PDF viewer at chrome://extensions

Once checked, files open in the viewer has they should. I've never had to enable this before, but there you are.

Thanks for your time guys.

 

That would be an unneeded extension that is causing that problem. You do not need any extension with Chrome, since it has a built in PDF viewer.

 

That's what I thought!

So, what's the point of these PDF extensions . . . extra functionality?

Note: After disabling both PDF extensions I have, PDF files now open correctly in Chrome. However, previously (before I checked the "allow access to file URLs" in the only enabled extension), the original problem was evident even when no extensions were enabled.

 

Nothing really. Some are useful, but now days too many of them are not needed with all of the changes that have been done with modern day browsers. Some of those extensions for Chrome are left over from when Google was still working on the PDF portion in Beta. The only extension that I use that interacts with the OS is the Mailto:, so that when I click on a email address, it goes to Yahoo Webmail, since Chrome does not have the ability to set it to take those links and open Mac Mail.

 

Hmmm . . . I spoke too soon. The original behavior has returned.

Clicking a PDF file in the mapped network drive returns an index of that file's parent folder (as described in my very first post).