That's good info. Thanks for that. Kurt
On Mon, Oct 27, 2014 at 8:02 AM, Nash Pherson <[email protected]> wrote: > Note that when you open an FQDN, it will default to the Internet zone for > security settings unless you have explicitly put that domain into the > Intranet zone list. Many files are blocked by default with the Internet zone > (for good reason). You can use Group Policy Preference to push out the zone > map keys for the trusted domain. > > Nash > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Crawford, Scott > Sent: Saturday, October 25, 2014 1:39 AM > To: [email protected] > Subject: RE: [NTSysADM] Adobe Reader can't open PDFs over the WAN > > Is DFS involved? > > We had a similar issue with pdf. Opening from a dfs share - > \\comp.com\dfs\share\pdf.pdf wouldn't open, but \\comp\dfs\share\pdf.pdf did. > (note the missing .com). Also, strangely enough, even with the longer path, > we could make a copy of the file and it opened fine. > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Kurt Buff > Sent: Thursday, October 23, 2014 6:28 PM > To: [email protected] > Subject: [NTSysADM] Adobe Reader can't open PDFs over the WAN > > All, > > A user in our AU office on a Win7 machine is complaining about inability to > open PDFs from our US file server. The error he gets is: > > "There was an error opening this document. The network path was not > found." > > I am able to duplicate this on another Win7 machine in our AU office. > > This started happening after this past weekend, during which we switched from > a Server 2003 VM to a 2012R2 VM. > > I've asked him to verify the version of Reader he's using. I installed > 11.0.09 on my test machine over there. I also turned off "Enable Protected > Mode at startup", per several web sites. > > Interestingly, he can open the PDF if he copies locally, or to a share on the > file server in his office, and I can open it just fine from the US file > server also. It's only across the WAN that it fails. > > Anyone else run into this, and have any insight? > > Kurt > >
