none
"hostname is invalid" when accessing internal web site from the internet RRS feed

  • Question

  • This worked before the Sharepoint 2010 re-install into SBS 2011.

    This continues to work correctly from inside the network.

    I'm trying to get an understanding about "binding" and virtual directories.

    https://www.<Domain>.org:987/    fails with the "HTTP Error 400. The request hostname is invalid" error. This is the SBS Sharepoint site.

    https://www.<Domain>.org:/REMOTE   succeeds in bringing me to the Remote Web Access page. From there, OWA and Shared Folders work fine. The Internal Web Site fails with the http 400 error. That URL is:

    https://www.<domain>.org/Remote/internalwebsite

    Question #1
    I see no "REMOTE" as the name of a virtual directory. How does the URL get directed to the Remote Web Access page?

    Question #2
    I see a physical path of     C:\Program Files\Windows Small Business Server\Bin\webapp\InternalWebsite.      
    I don't see a virtual path for     internalwebsite.   I tried to create one but that didn't solve the problem.

    What URL do I need to use to access the internal site externally? If a binding entry is necessary, what would it look like?

    Thanks for any help,
    Mike 

    Saturday, November 19, 2011 5:47 AM

Answers

All replies

  • Have you added alternate access mappings for companyweb?
    Saturday, November 19, 2011 5:53 AM
  • JKazama pointed me in the right direction. The problem is not quite solved yet but there has been progress. The video was the next step:

    http://technet.microsoft.com/en-us/sharepoint/Video/ff679917

    Because of these seemingly disconnected pieces, I needed to have some sort of debugging steps. I'm doc-ing them here in the event others might find what I've learned so far, useful.

    I needed to confirm that I was at least getting through the firewall. First test with:

             telent www.<domain>.org 987

    This succeeded but I needed to see exactly which site was being accessed. I created 3 simple "test.html" docs. 

     

    <html>
      <body>
        <h1>HTML Test Page for [SITE] </h1>
      </body>
    </html>

    SITE = "Default Web Site" and "Companyweb" and "SBS Sharepoint". 3 html files each was placed in the root of the respective site.  How do we identify the root? In IIS, highlight the site and then choose "Explore".

    In each of those site's root, I placed the appropriate test.html.

    In IIS, for the SBS Sharepoint site I added "http"  "<domain name>.org"   "80" to the binding.

    Externally, I attempted accessed http://<domain name>.org:987    and this failed after taking a long time. 
    The Event Log had SChannel errors. Research indicated this error was related to the digital certificate.
    I returned to the SBS Sharepoint bindings and deleted the "https" that invoked the certificate and created a new binding without SSL. 

    Tested the external URL and the test.html doc came up and identified the SBS Sharepoint site. Further testing also indicated that I was able to reach the internal Companyweb site.

    So we identified the certificate as the cause of the problem. Replacing the certificate allowed things to work correctly.

    However, based on the video mentioned earlier, this is not the best way to configure access. My next attempt will be through Alternate Access Mappings of Sharepoint. 

    To those who have a clue, all of the above is obvious. To one who is trying to get the whole SBS 2011 thing understood, this was a learning experience (another one!).

    Thanks again to JKazama for getting me on the correct path.

    Mike

    Saturday, November 19, 2011 9:43 PM
  • One final question please...

    When I used Alternate Access Mapping from Sharepoint, I expected to see the change flow through to the Bindings dialog in IIS. I don't see that happening. Should this happen this way?

    Thanks, Mike

    Monday, November 21, 2011 3:35 PM
  • You have to enter alternate access mappings manually.

    It will not change anything in IIS.You have to manually add the bindings.

    Refer to final section of the following blog post for AMM [its for 2008 but AMM is same]:

    http://blogs.technet.com/b/sbs/archive/2009/05/07/event-2436-for-sharepoint-services-3-search.aspx

    in IIS put 2 bindings for SBS Sharepoint[http=port 80,host header companyweb;https=987 and with right cert]

    • Marked as answer by MRowe31 Tuesday, November 22, 2011 12:27 AM
    Monday, November 21, 2011 4:02 PM