locked
Want to use DNS Alias without a port number at the end in MOSS 2007 RRS feed

  • Question

  • Hi all,

    I have created a web application with a port number other than 80, say, 4444.

    So the public URL for this application is http://servername:4444.

    Now I went to Alternate Access Mapping section in Central Admin and added Internal URLs, like, http://somename.mydomain.com and http://somename.

    I added these internal URLs so that internal users can just type in "http://somename" or "http://somename.mydomain.com".

    Now, the web site is accessible with the following addresses

    http://servername:4444
    http://somename:4444
    http://somename.mydomain.com:4444

    but NOT with the following addresses

    http://somename
    http://somename.mydomain.com

    I do not know why, but if I type in either http://somename or http://somename.mydomain.com,
    I get HTTP 404 Not Found The webpage cannot be found error on IE.

    Does anyone know the real issue behind this?

    I cannot find the solution for this issue anywhere else.

    Please help.

    Clark

    Thursday, December 23, 2010 9:51 PM

Answers

  • Hi Clark,

    as far as I know this will not work since the http protocol uses port 80 by default. So if you try to browse http://somename wihtout adding a port to the url your IIS application on port 4444 will not answer.

    To achieve your goal you would have to use a proxy or a reverse proxy which would redirect the client to the non standard http port. Another solution would be to add a binding to the IIS web site with your IP address, port 80 and the host header value of somename. For a description see here http://support.microsoft.com/kb/324287/en-us

    As long as you use host header you can have multiple sites on one IP address and port 80.

    • Marked as answer by clark_ussr Sunday, December 26, 2010 7:08 PM
    Friday, December 24, 2010 9:08 AM

All replies

  • Hi Clark,

    as far as I know this will not work since the http protocol uses port 80 by default. So if you try to browse http://somename wihtout adding a port to the url your IIS application on port 4444 will not answer.

    To achieve your goal you would have to use a proxy or a reverse proxy which would redirect the client to the non standard http port. Another solution would be to add a binding to the IIS web site with your IP address, port 80 and the host header value of somename. For a description see here http://support.microsoft.com/kb/324287/en-us

    As long as you use host header you can have multiple sites on one IP address and port 80.

    • Marked as answer by clark_ussr Sunday, December 26, 2010 7:08 PM
    Friday, December 24, 2010 9:08 AM
  • Clark -

    Make sure the DNS entry points to the SharePoint server IP (or load-balanced IP).
    Configure your IIS Host Headers (or Site Bindings in IIS7) for the IIS Web App (the one that corresponds to the SP Web App).

    For example, a new binding would be Type=http, IP Address=All Unassigned, Port=444, Host name=somename.mydomain.com .

    Hope this helps!


    SharePoint Solution Architect, Developer
    Sunday, December 26, 2010 1:26 PM
  • as far as I know this will not work since the http protocol uses port 80 by default.


    Thank you!!!

    I have been trying with the binding to the IIS web site with port 4444, not 80.

    As soon as I applied 80, voila!

    So it looks like once the SharePoint server must answer any client request through port 80 first, and then redirect the client to any non standard http port.

    Happy New Year to you!!!

    • Edited by Mike Walsh FIN Monday, December 27, 2010 8:32 AM do not waste screen space by using full quote
    Sunday, December 26, 2010 7:12 PM
  • Thank you for your help MossDev.

    The trick was to apply port 80, not the port that I used for the web application.

    What is kind of strange is that I had got this working without specifying another binding with the port 80 before...

    Sunday, December 26, 2010 7:14 PM