Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 3 subscribers
  • Views 11708 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sharepoint publishing?

Louis-M

Hi, I'm trying to get sharepoint working through WAF. I can reach the IIS server http://mysharepointserver no problem. However, when i try to reach http://mysharepointserver/Pages/Home.aspx, I get a 404 (from the server) saying it can't be found.

Obviously, externally I have to go to http://mydomain.com/Pages/Home.aspx which should then allow me to go to http://mysharepointserver/Pages/Home.aspx

Not sure what the issue is here as I can get other web servers to work no problem and I'm sure the 404 is coming from Sharepoint itself.
Can anyone point me in the right direction with this?

Thank you, louis



This thread was automatically locked due to age.
Parents
  • 0

    Hi Louis,

    Check the Webserver protection logs at the time of the 404 error and you will be able to tell if it's coming from the UTM (defines an error itself) or from the sharepoint (receives the error).

    Also could you share a screenshot and snippet of the logs at the time of the error?

    Cheers,

    Emile

  • 0 in reply to Emile Belcourt

    Not 100% sure what's going on with it.

    If my internal sharepoint server is at http://mysharepointserver which then redirects me to http://mysharepointserver/Pages/Home.aspx as the home page, I'm getting lost on how to publish https://mysharepointserver.mydomain.com/Pages/Home.aspx

    I've got the external dns published which points me towards the UTM. As mentioned, If I do this with a normal webserver eg Centos & apache, I can connect as I would expect. It's just this sharepoint server which is returning the 404

    Logs on the UTM are:

    2016:04:11-18:31:06 gw1-1 reverseproxy: id="0299" srcip="127.0.0.1" localip="127.0.0.1" size="52" user="-" host="127.0.0.1" method="GET" statuscode="200" reason="-" extra="-" exceptions="-" time="200" url="/lb-status" server="localhost" referer="-" cookie="-" set-cookie="-"
    2016:04:11-18:31:07 gw1-1 reverseproxy: id="0299" srcip="127.0.0.1" localip="127.0.0.1" size="52" user="-" host="127.0.0.1" method="GET" statuscode="200" reason="-" extra="-" exceptions="-" time="210" url="/lb-status" server="localhost" referer="-" cookie="-" set-cookie="-"
    2016:04:11-18:31:17 gw1-1 reverseproxy: id="0299" srcip="127.0.0.1" localip="127.0.0.1" size="52" user="-" host="127.0.0.1" method="GET" statuscode="200" reason="-" extra="-" exceptions="-" time="196" url="/lb-status" server="localhost" referer="-" cookie="-" set-cookie="-"
    2016:04:11-18:31:17 gw1-1 reverseproxy: id="0299" srcip="127.0.0.1" localip="127.0.0.1" size="52" user="-" host="127.0.0.1" method="GET" statuscode="200" reason="-" extra="-" exceptions="-" time="207" url="/lb-status" server="localhost" referer="-" cookie="-" set-cookie="-"
    2016:04:11-18:31:21 gw1-1 reverseproxy: id="0299" srcip="100.200.31.42" localip="85.167.100.2" size="678" user="jbloggs" host="100.200.31.42" method="GET" statuscode="404" reason="-" extra="-" exceptions="-" time="4797" url="/Pages/Home.aspx" server="mysharepointserver.mydomain.com" referer="-" cookie="-" set-cookie="-"
    2016:04:11-18:31:31 gw1-1 reverseproxy: id="0299" srcip="100.200.31.42" localip="85.167.100.2" size="678" user="jbloggs" host="100.200.31.42" method="GET" statuscode="404" reason="-" extra="-" exceptions="-" time="4998" url="/Pages/Home.aspx" server="mysharepointserver.mydomain.com" referer="-" cookie="-" set-cookie="-"
    2016:04:11-18:31:38 gw1-1 reverseproxy: id="0299" srcip="100.200.31.42" localip="85.167.100.2" size="678" user="jbloggs" host="100.200.31.42" method="GET" statuscode="404" reason="-" extra="-" exceptions="-" time="4494" url="/Pages/Home.aspx" server="mysharepointserver.mydomain.com" referer="-" cookie="-" set-cookie="-"
    2016:04:11-18:31:43 gw1-1 reverseproxy: id="0299" srcip="127.0.0.1" localip="127.0.0.1" size="52" user="-" host="127.0.0.1" method="GET" statuscode="200" reason="-" extra="-" exceptions="-" time="217" url="/lb-status" server="localhost" referer="-" cookie="-" set-cookie="-"
    2016:04:11-18:31:47 gw1-1 reverseproxy: [Mon Apr 11 18:31:47.885793 2016] [mpm_worker:notice] [pid 12958:tid 4147615424] AH00295: caught SIGTERM, shutting down
    2016:04:11-18:31:47 gw1-2 reverseproxy: [Mon Apr 11 18:31:47.925593 2016] [mpm_worker:notice] [pid 24117:tid 4147242688] AH00295: caught SIGTERM, shutting down

    I'm wondering if the sharepoint server needs to have the full external URL binded to it eg http://mysharepointserver.mydomain.com as well as the internal http://mysharepointserver

  • 0 in reply to Louis-M

    Could anybody give me an idea of how to do this here. I'm sure I've got the right settings but just need to check.

    I can reach the IIS homepage on the server but trying to get to a sharepoint page is proving difficult. Any pointers would be appreciated.

  • 0 in reply to Louis-M

    It would be helpful if you post screenshots of your Real and Virtual web server object settings.

  • 0 in reply to Louis-M

    Also, Louis, please clarify what URL you requested when you got the 404 error above. Is this a rewrite URL issue?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    I believe this may be an issue with the internal URL as I hadn't set this up at the time or set the public URL in sharepoint.

    I haven't had time to go back to this yet but I believe once I set this up so it can be reached from outside (without WAF & just port forwarding on https for testing), I can then disable the port forwarding and then configure WAF

Reply
  • 0 in reply to BAlfson

    I believe this may be an issue with the internal URL as I hadn't set this up at the time or set the public URL in sharepoint.

    I haven't had time to go back to this yet but I believe once I set this up so it can be reached from outside (without WAF & just port forwarding on https for testing), I can then disable the port forwarding and then configure WAF

Children
No Data
Unfiltered HTML