locked
Page Viewer Web Part RRS feed

  • Question

  • Running WSS 3.0. I have setup a Page Viewer Web Part that displays a folder from a shared folder. It works internally. Externally, we get "unable to display web page". How can I troubleshoot this?

    Thanks, Chris

    Tuesday, May 15, 2012 3:58 PM

Answers

All replies

  • Hi Chris,

    Could you please kindly check if it is external URL used by the Page Viewer Web Part in External site?

    Thanks & Regards,
    Emir Liu
    TechNet Subscriber Support in forum
    If you have any feedback on our support, please contact
    tnmff@microsoft.com.


    Emir Liu

    TechNet Community Support

    Wednesday, May 16, 2012 10:43 AM
  • Thank you for the reply. The Page Viewer URL is pointed towards an internal server - \\InternalServerName\Shared

    Thanks, Chris

    Wednesday, May 16, 2012 1:45 PM
  • Hi Chris,

    Can you access this location by clicking the test link in Edit Web Part pane? Will it ask for validation? After type the user certificate, can you access it now?

    I would like suggest you to use a Shared location instead.

    Thanks & Regards,
    Emir


    Emir Liu

    TechNet Community Support

    Thursday, May 17, 2012 12:39 PM
  • If I click on the 'Test Link', nothing happens.

    What do you mean by Shared Location instead?


    Thanks, Chris

    Thursday, May 17, 2012 1:22 PM
  • Hi Chris,

    I believe that what you're experiencing is expected behavior.  Check this post out:

    http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/e96c3c23-5128-4aba-9a98-77fe7d8d2b93

    It looks like the web part basically doesn't know how to pass the current users credentials to the internal location.  I would bet that if the external user accessed the share first, then accessed the page viewer web part, that it would work.  It's as if the web part doesn't know who the user is.  In the thread above, the recommendation is to create a custom web part, but depending on your requirements (and programming skills), have you considered any alternatives to exposing this content?

    This post has a similar theme, but I would think that Network Monitor would log the attempt at the port level on SharePoint:

    http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/b55af1bd-fd9a-459a-8cb4-f140d46fdde4

    Are the external users authenticated to the domain where the share is located?  How about this for a solution:

    http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/c842102e-39ce-4dd4-9f76-74a535f3a659/

    Hopefully some part of this has been useful to you.  My apologies that the web part doesn't seem to be capable of what you need it to do out of the box.

    Best Regards,

    Bob

    Friday, May 18, 2012 9:48 PM
  • This is pretty much going to be a DNS issue.  As your \\InternalServerName is not known to the outside world, an external client will never know how to find the server or the share.

    When you load your page externally, all the elements are rendered by your browser and the name resolution is handled by whichever DNS provider you're currently using.  Your browser will see the page viewer web part as an iFrame and try to resolve the name InternalServerName to provide the content.  It wont even get to the point of passing credentials.


    Paul Turner http://redmanta.co.uk/blog Twitter: @RedMantaUK MCTS:WSS,MOSS,2010 MCITP:2010.
    Please remember to click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if it was useful.

    Saturday, May 19, 2012 8:51 PM
  • I did find a solution to this issue. Since the Page Viewer web part will not display the internal files, while accessing from outside the comapny, i found a product that does -

    http://www.amrein.com/apps/page.asp?Q=5821


    Thanks, Chris

    Tuesday, May 22, 2012 2:44 PM