This is a post for Adobe Acrobat, not Adobe Reader as it is a functionality issue with Acrobat. It is peculiar, I am having the same problem when I save the file to a local Windows Home Server.
I have a link called file://whsservername/foldername and it becomes file://whsservername/foldernamewherepdfislocated////whsservername/foldername which is totally convoluted. I am trying to research a solution for this but if anyone else knows what settings to change in Acrobat that would be a great help to post.
It appears when testing on a local server it does not function properly but placing a link in an MS Word document such as http://www.google.com and converting to Acrobat PDF from MS Word 2007 and then using dreamweaver to create a hyperlink to that PDF file will open the PDF file with the http link in it. Clicking on that link from the open PDF within the web browser will indeed take you to google's homepage website. It's just that when using file://servername it gets confused.
Okay. Got a solution. But it's not a happy one. You have to choose either one or the other type of link.
if you create a PDF with a hyperlink /////servername/foldername and view this PDF within a web browser, it will take you to \\servername\foldername in Windows. . However the http://www.sitename.domain/path declaration still works. However if you open this PDF and try to click on the link /////servername/foldername in Acrobat it will not resolve properly, so you have to choose which method your users will use to view the PDF with the link in question--either within a web browser or within a standalone Adobe Acrobat / Adobe Reader product. The two don't work well together except if it is an http:// declaration.
Don't know if this is the same issue but I am trying to load a PDF price list on my root domain http://easytosellgold.com and when anyone accesses it all they get is a 404 error even though I can actually the file in my root. I have found that doing a 301 redirect to this from another file actually will automatically load the page just like its intended.
Thanks. That may help.
I am fairly new to supporting Reader and our users insist that this used to work. But I've tried all kinds of back level combinations and I can't get it to work the way they have the file link coded.
Any other ideas or comments would be appreciated. There doesn't seem to be any way of opening a problem with Adobe for an issue like this, unless we purchase an enterprise support agreement.