Would that I could...

On Fri, Oct 24, 2014 at 10:27 PM, Kurt Buff <[email protected]> wrote:

> I think that's the direction we're heading.
>
> Kurt
>
> On Fri, Oct 24, 2014 at 7:19 PM, Richard Stovall <[email protected]>
> wrote:
> > Time to disable Adobe*?
> >
> > On Fri, Oct 24, 2014 at 4:30 PM, Kurt Buff <[email protected]> wrote:
> >>
> >> I saw a couple of links/articles like that, but even disabling sandbox
> >> protection didn't help. Sigh.
> >>
> >> Kurt
> >>
> >> On Fri, Oct 24, 2014 at 12:32 PM, Susan Bradley <[email protected]>
> >> wrote:
> >> > https://forums.adobe.com/message/6860536#6860536
> >> > You aren't alone.
> >> >
> >> > Susan Bradley
> >> > http://blogs.msmvps.com/bradley
> >> >
> >> >
> >> > On 10/24/2014 12:29 PM, Kurt Buff wrote:
> >> >>
> >> >> On the test machine, I uninstalled Adobe Reader, and replaced it with
> >> >> the free Foxit reader.
> >> >>
> >> >> That opens the document across the WAN just fine.
> >> >>
> >> >> So, for now, that's what I'm going to recommend to the user.
> >> >>
> >> >> Kurt
> >> >>
> >> >> On Thu, Oct 23, 2014 at 4:27 PM, Kurt Buff <[email protected]>
> wrote:
> >> >>>
> >> >>> 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
> >> >>
> >> >>
> >> >>
> >> >
> >> >
> >> >
> >>
> >>
> >
>
>
>

Reply via email to