Extending a web application to port 80

Hello -
I have a web application running on port 80.  The associated IIS site is http://sharepoint
I want to extend the web application to port 80 and use a different URL:  http://isharepoint
The authentication schema will stay the same (classic NTLM).
I assume I enter http://isharepoint as the host header and use port 80, correct?
Do I need a new IP address and a new DNS entry, or do I just set up a CNAME that points to an existing name?
thanks

Assuming that sharepoint is the current host header then yes you can extend to isharepoint on port 80 with isharepoint being the new host header.  You don't need a new IP address, but will need a new DNS entry and it should be an A record not a CNAME.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Similar Messages

  • Help needed for Extending ISA Web applications

    Hi All,
    I am working on CRM 5.0. Need some kind of step by step guide to enhance standard Web applications. For example,
    Adding a new field. Changing the Layout etc.
    If some one has already done this kind of modifications, please share the same with me.
    It will be of immense  help to me
    Please mail the same to [email protected]
    Regards,
    Eureka.

    Hi,
    You need to get the development and extension guide.
    Have a look at this posting for details of how to find it.
    How to modify Webshop's layout, style and so on...
    Hope this helps,
    Gareth.

  • Extending Web Application - File Not Found

    A quick search with no results and a ton of frustration are leading me here...I am attempting to use the very basic "Extend" functionality for a Web Application. We are trying to at the least add SSL/443 to SharePoint, if not convert entirely to
    443.
    I have tried simply extending the Web Application, or deleting the IIS Site (from Manage Web Applications -> Delete -> Remove SharePoint from IIS Web Site) and then extending the Web Application. Both are failing with the same error "File not
    found." A review of the ULS logs shows that the site is failing to find the web.config for the brand new IIS site it should be creating...which I guess makes sense, but shouldn't it be creating this file?
    I am tempted to mess around with the newly created site in IIS to make it work, but we are doing this in Dev as a proof of concept to do this in production. Needless to say, this needs to become much more reproducible before we'd even consider doing it in
    production.
    Some things I've tried:
    Extending a Web Application with an existing site
    Extending a Web Application without an existing site
    Creating a new Web Application and extending existing port 80 site
    Creating a new Web Application and extending after deleting existing port 80 site
    I haven't tried creating a site 443 out of the gate mainly because I am afraid this functionality failing could be an indication of something wrong with the farm and want to fix this correctly, rather than deleting a Web Application and creating it 443 from
    the get-go. Also, this method would obviously involve downtime.
    System.IO.FileNotFoundException: Could not find file 'C:\inetpub\wwwroot\wss\VirtualDirectories\ConstructionProjectsDev.agoc.com443\web.config'.
    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
    at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
    at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
    at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize)
    at System.Xml.XmlUrlResolver.GetEntity(Uri absoluteUri, String role, Type ofObjectToReturn)
    at System.Xml.XmlTextReaderImpl.OpenUrlDelegate(Object xmlResolver)
    at System.Threading.CompressedStack.runTryCode(Object userData)
    at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
    at System.Threading.CompressedStack.Run(CompressedStack compressedStack, ContextCallback callback, Object state)
    at System.Xml.XmlTextReaderImpl.OpenUrl()
    at System.Xml.XmlTextReaderImpl.Read()
    at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
    at System.Xml.XmlDocument.Load(XmlReader reader)
    at System.Xml.XmlDocument.Load(String filename)
    at Microsoft.SharePoint.Administration.SPAspConfigurationFile.ApplyZoneSettingsToWebConfig(Uri responseUri, SPIisSettings settings)
    at Microsoft.SharePoint.Administration.SPWebApplication.Provision()
    at Microsoft.SharePoint.ApplicationPages.ExtendWebFarmPage.BtnSubmit_Click(Object sender, EventArgs e)
    at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
    at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    Thanks,
    Chris P.

    A quick search with no results and a ton of frustration are leading me here...I am attempting to use the very basic "Extend" functionality for a Web Application. We are trying to at the least add SSL/443 to SharePoint, if not convert entirely to
    443.
    I have tried simply extending the Web Application, or deleting the IIS Site (from Manage Web Applications -> Delete -> Remove SharePoint from IIS Web Site) and then extending the Web Application. Both are failing with the same error "File not
    found." A review of the ULS logs shows that the site is failing to find the web.config for the brand new IIS site it should be creating...which I guess makes sense, but shouldn't it be creating this file?
    I am tempted to mess around with the newly created site in IIS to make it work, but we are doing this in Dev as a proof of concept to do this in production. Needless to say, this needs to become much more reproducible before we'd even consider doing it in
    production.
    Some things I've tried:
    Extending a Web Application with an existing site
    Extending a Web Application without an existing site
    Creating a new Web Application and extending existing port 80 site
    Creating a new Web Application and extending after deleting existing port 80 site
    I haven't tried creating a site 443 out of the gate mainly because I am afraid this functionality failing could be an indication of something wrong with the farm and want to fix this correctly, rather than deleting a Web Application and creating it 443 from
    the get-go. Also, this method would obviously involve downtime.
    System.IO.FileNotFoundException: Could not find file 'C:\inetpub\wwwroot\wss\VirtualDirectories\ConstructionProjectsDev.agoc.com443\web.config'.
    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
    at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
    at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
    at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize)
    at System.Xml.XmlUrlResolver.GetEntity(Uri absoluteUri, String role, Type ofObjectToReturn)
    at System.Xml.XmlTextReaderImpl.OpenUrlDelegate(Object xmlResolver)
    at System.Threading.CompressedStack.runTryCode(Object userData)
    at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
    at System.Threading.CompressedStack.Run(CompressedStack compressedStack, ContextCallback callback, Object state)
    at System.Xml.XmlTextReaderImpl.OpenUrl()
    at System.Xml.XmlTextReaderImpl.Read()
    at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
    at System.Xml.XmlDocument.Load(XmlReader reader)
    at System.Xml.XmlDocument.Load(String filename)
    at Microsoft.SharePoint.Administration.SPAspConfigurationFile.ApplyZoneSettingsToWebConfig(Uri responseUri, SPIisSettings settings)
    at Microsoft.SharePoint.Administration.SPWebApplication.Provision()
    at Microsoft.SharePoint.ApplicationPages.ExtendWebFarmPage.BtnSubmit_Click(Object sender, EventArgs e)
    at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
    at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    Thanks,
    Chris P.

  • How to upgrade the extended web application for FBA from MOSS 2007 to SharePoint 2010?

    Hi All,
    Currently my farm version is MOSS 2007 with SP3.
    I have a web application on port 80, and is based on windows authentication, and i extend it on the port 90, and the authentication is FBA with SqlServer.
    I know that SharePoint 2010 has a new claims based authentication, and in a single web application you can do both windows authentication and FBA.
    Now i want to know, when i migrate the MOSS 2007 port 80 and port 90, which method should i choose?
    1. in SharePoint 2010 farm, Create  a classic based web application on port 80, and extend it on port 90, enable FBA on port 90. It is the same as MOSS 2007.
    2. in SharePoint 2010 farm, Create a claims based web application, and enable both windows authentication and FBA.
    Thanks.

    FBA requires claims so you'll need to create a claims based web application. Whilst you might extend the site to give you a FBA portal the web application itself will have to be claims based.
    I would definitely be looking at using a database attach upgrade path in your case to give you the opportunity for testing as moving between authentication providers can be painful.

  • Extended web application pointing to root site collection, Can point to another site collection?

    I have a web application running on port 443 https with windows authentication, machine name is "localspdev" I have following site collections
    / (Root site collection)
    site1.dev (HNSC)
    site2.dev (HNSC)
    If I browse "https://localspdev" I get root site collection, which is fine. I can browse site1 and site2 as well
    I am extending web application to extranet zone with forms and windows authentication enabled, port is 443, https and host header is "extranet.dev"
    when I browse "https://extranet.dev", root site collection comes up, which I don't want, I can create 1 more extranet
    HNSC but how can I configure "https://extranet.dev" to open/link new extranet site collection?

    Hi Shafaqat,
    When we extend the web application to extranet zone, then the root site collection should be accessed by default with extranet zone URL.
    If you want to configure the URL https://extranet.dev to open the Host named site collection, then you need to set the URL to be the extranet zone URL for the Host named sites collection instead of extending the web application.
    http://falakmahmood.blogspot.jp/2013/08/sharepoint-2013-setting-up-host-named.html
    Thanks,
    Victoria
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • What is the correct way to set a web application to use HTTP or HTTPS?

    In the past I've always created an HTTP web application as the default zone. Then extended the web app, creating a new IIS website on port 443 and enabled SSL. This seems to have worked fine, but I recently read an article stating that it is not good to
    extend a web app unless absolutely necessary. So can someone tell me what the proper way is to configure a single web application to work with HTTP and HTTPS?

    Extending the web application to support both HTTP and HTTPS is a perfectly good method and in fact is the only way to have a web application support both so what you've done is fine.
    If the web application will only use HTTPS, you can set this up when you first create the web application. Specify port 443 and the SSL option (and ensure the URL has an https://) when creating the web application. You'll need to install the certificate
    in IIS once the web application has been created.
    Jason Warren
    Infrastructure Architect
    Habanero Consulting Group
    habaneroconsulting.com/blog

  • Restore the deleted extended IIS web site into Virtual directories

    Hi,
    i deleted the IIS site from virtual directories and as well from IIS. But still i can see the extended web site zone in the Central administration, General Settings from the remove SharePoint from IIS web site. now question is there any way i can restore
    the deleted iis site zone any how?
    Thanks

    Hi Trevor,
    Thanks for your answer. i need some suggestion regarding on going issue. First i have created a web application at port 80 when it was in singer server and then i extended to 443 and 80 in multi-tier farm as you can see in the below image
    And then i deleted IIS site from IIS itself and from Virtual directories as you can see in the below picture. Then i blinded the "SharePointDemo-80" site with host header at port 443 With default zone AAM. now i can access the site well but problem
    is if i want to deploy any custom solution, getting error "The web.config is invalid on this IIS web site: "C:\inetpub\wwwroot\wss\VirtualDirectories\demoportal.bbcat.local80\web.config. " and also crawler is not crawling any items. my
    understanding is, as there is no IIS site into virtual directories obviously will throwing error. Usually first i create web application at different port (example 8080) and then extend the application to 80 or 443.  As i have already place this web application
    and did customization, what will be the best way to handle this situation?
    Thanks in advanced!!

  • On SharePoint side - other than enabling Kerberos at web application level - is there any other step needed? What?

    Hi there
    My Network guy says that he has taken all necessary steps to roll out Kerberos.
    In the scope of SharePoint - I have extended our web application and this has Kerberos enabled (instead of NTLM). <-- Other than this any more steps are needed on SharePoint side? Which ones?
    Thank you so much.

    Microsoft has released the Kerberos configuration guide : http://www.microsoft.com/en-us/download/details.aspx?id=23176
    note: it's long... 100 pages long.
    Scott Brickey
    MCTS, MCPD, MCITP
    www.sbrickey.com
    Strategic Data Systems - for all your SharePoint needs

  • Web Application with NetBeans 4.0 & JDK 1.5

    I am currently working on a web application using NetBeans 4.0.
    I have a piece of code that works perfectly in a General application which works on jdk 1.5.
    However, when i created a web application and port all existing code to this new project, the compiler gives me an error:
    javac: invalid target release 1.5
    So wat do i have to do to get the code work under Web Project in NetBeans 4.0?

    In NetBeans 4.0, General Java Apps seem to work fine with jdk 1.5 so NetBeans 4.0 does support jdk 1.5 to an extent.
    However, the same code does not work in the Web Application.
    Okay, when you first create a Web Project in NetBeans 4.0, it asks you the 'J2EE Specification Level' and it gives you only 2 options: J2EE 1.3 or J2EE 1.4. I think this is wat giving me the problem.
    The reason why i chosed NetBeans 4.0 because I want to work with Web Services and Tomcat. There are 'none' online resource for NetBeans 4.1 WS and Tomcat (only App Server).
    The worst case is i'll get rid of Generics in my code.

  • Can you enable both Windows Based Authentication and Forms Based Authenication for the same web application?

    Hello Community
        In WS2012 and SharePoint 2013 Server is it possible when creating a
    web application to enable both Windows Based Authentication/Negotiate
    (Kerberos) and enable Forms Based Authentication or does the web application
    use either one or the other?
        Thank you
        Shabeaut 

    Yes , you can use dual authentication on same web application. You can use same web application , at OOB login page you will have option to use windows or form login.
    Or you can extend your web application to a new web app and configure extended web application to use Form Based Authentication(Note extended web application will also show same content database , so the content will same only url will be different)
    http://blogs.technet.com/b/ptsblog/archive/2013/09/20/configuring-sharepoint-2013-forms-based-authentication-with-sqlmembershipprovider.aspx
    http://gj80blogtech.blogspot.in/2013/11/forms-based-authentication-fba-in.html
    Thanks
    Ganesh Jat [My Blog |
    LinkedIn | Twitter ]
    Please click 'Mark As Answer' if a post solves your problem or 'Vote As Helpful' if it was useful.

  • Nested web applications directory.

    I recently design the jsp development structure in my company.
    It is basically contain two webapps which is productionLine webapp and developmentLine webapp.
    In my developmentLine webapp contain several programmers. Each of them has their own user directory in developmentLine webapp but i face a trouble which is each subdirectory cannot run their servlet in WEB-INF.
    In http://localhost/developmentLine/servlet/servletname is running fine but once i move the webapp into user directory then it cause the problem like http://localhost/development/John/servlet/servletname. It is not working. Any idea about it?
    design jsp development structure based.
    root
    -> productionLine
    \t -> HR
    \t -> Admin
    -> developmentLine
    -> John
    -> HR
    -> webster
    -> Admin
    Is the tomcat support nested webapplication? else i think i need put entire servlet in the common library to shared among each web applications.
    Edited by: webster on Nov 15, 2008 12:30 PM

    Because my company didn't install the any Java Tools before. I need to install entire java development Tools and assigned each particular directories in Tomcat web server for each developer. what's mean of "hacked"?
    I intent to put assigned each developer a userId directory in developmentLine directory. what i trying to do is allow each userId subdirectory in web application directory (i.e. ROOT, webdav, balancer and etc) to have their own servlet classes in WEB-INF directory.
    cause my company required put all the source code into a single server. Their think it is much more easier to maintain.
    so I am trying to install two tomcat in a server. I had change my http port, shutdown port and AJP port to 80, 89 and 85. When i try install a new Tomcat with same version into server, it pop up an error msg.
    Failed to install Tomcat5 service.
    Check your settings and permissions
    Ignore and continue anyway (not recommended)
    I choose ignore it, and continue install. Afterward my web application in port 80 change to 8080. I think it is replace the old tomcat server instead of running both tomcat together.
    Any idea?
    p/s: previous tomcat installation path is C:\Program Files\Apache Software Foundation\Tomcat 5.5 and another tomcat server installation path is C:\Program Files\Apache Software Foundation\Tomcat 5.52.
    Edited by: webster on Nov 17, 2008 10:39 AM

  • SharePoint 2013 Central Admin says port 80 for three web applications, but IIS says they have different ports

    Hello,
    I have three web applications on a SharePoint 2013 servers.  In Central Administrators on the Application Management page where it lists all of the web applications, it shows Port 80 being used 2 3 sites.  When I go to IIS, 2 of the 3 are using
    different ports, 81 and 82.  So, only one site IIS says is using port 80. Why is this?  The host file has no entries in it.  Where these web applications extended?
    Thanks,
    Paul
    Paul

    Hi Paul,
    From the URL of the web application in Central Administration in the image, you have configured the Alternate Access Mapping for the web applications.
    And the URL configured is by default using port 80 if you don’t 
    assign other ports for the web application, so the port is changed to 80 in Central Administration.
    To be able to access the web application, you need to add binging for the web application in IIS(please make sure that you have added the host name in DNS).
    For example, SharePoint – 32298, you need to create the binding for the web application in IIS as the image below:
    Best regards.
    Thanks
    Victoria Xia
    TechNet Community Support

  • Portal Port to Publish in Portal via Query Designer and Web Application

    Hello Gurus,
    Recently we change the port from 50000 to 80 to do federated portal connection more transparent.
    After this change I open for example the web application designer and open a web template and try to execute it.
    This action pop up the web browser to show the web template, but there is a problem, the web application designer still openning the web template with the 50000 port.
    The question is:
    Where I change the port used for BEx Web Applications to execute the web templates or the BEx Web querys?
    thansk for your help.
    Jose

    Solve with SAP Note: 947148

  • Office Web App error in extended web application

    I have a web application that has been extended in intranet zone. While all feature works in the application in the default zone of office web app, creating new document from site it self does not work in intranet zone. Error I am getting is sorry, there
    was a problem and we can't open this document. If this happens again, try opening document in microsoft word. I was not able to find anything regarding this.
    My extended web application is using FBA and default zone uses windows. 
    Thanks,
    Errors in ULS logs
    WOPI ProcessRequest - Unhandled Exception in WOPI app layer  [e: System.InvalidOperationException: Operation is not valid due to the current state of the object.    
     at Microsoft.SharePoint.SPUserToken.GetClaimsUserLoginName()    
     at Microsoft.SharePoint.IdentityModel.SPIdentityContext.Create(SPUserToken token, Boolean isShareByLinkGuestUser)    
     at Microsoft.SharePoint.IdentityModel.SPIdentityContext.Create(SPUser user)    
     at Microsoft.SharePoint.IdentityModel.OAuth2.SPOAuth2SecurityTokenManager.IssueLoopbackTokenString(Uri endpointAddress, SPUser user, String applicationContext, DateTime& validTo)    
     at Microsoft.SharePoint.Utilities.SPWOPIHost.GetAccessToken(SPWeb web, Guid uniqueId, String proofKeyId, SPUrlZone zone, SPBasePermissions perms, Boolean hasEditLicense, Int64& ttl)    
     at Microsoft.SharePoint.Utilities.SPWOPIHost.GetAccessToken(SPFile file, WopiTokenContext tokenContext, Int64& ttl)    
     at Microsoft.SharePoint.SoapServer.Wopi.RunCobalt(HttpContext context, CommonRequestData requestData, CommonResponseData responseData)    
     at Microsoft.SharePoint.SoapServer.Wopi.ProcessRequestCore(HttpContext context, CommonRequestData requestData, CommonResponseData responseData)]
    WOPI - CopyRequestBodyToStream throw exception [exception System.ObjectDisposedException: Cannot access a disposed object.  Object name: 'Microsoft.SharePoint.CoordinatedStreamBuffer.SPCoordinatedMemoryStream'.    
     at Microsoft.SharePoint.Utilities.SPChunkedStream.get_Length()    
     at Microsoft.SharePoint.SoapServer.Wopi.CopyRequestBodyToStream(HttpContext context)]
    WOPI cobalt - Failed to read entire request body, url
    sachin

    Hi sachin,
    According to your description, my understanding is that you got an error when you created a new document using OWA in the extended zone with FBA.
    The issue stems from SharePoint and is due to an error in the access token generation when a user tries to load a document in the Office Web Apps.
    The current workaround is to configure FBA authentication in the Default zone of the effected web application.
    More information, please refer to the link:
    http://blogs.technet.com/b/office_web_apps_server_2013_support_blog/archive/2014/03/20/office-web-apps-2013-errors-previewing-viewing-editing-documents-when-using-fba-in-the-extended-zone-but-not-the-default-zone.aspx
    I hope this helps.
    Thanks,
    Wendy
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Wendy Li
    TechNet Community Support

  • How to change port for deployed web application on IAS10g(from 7778 to 80)

    I have deployed an application on IAS Application Server. The default link to my application is:
    http:/my_sever_ip_address:7778/my_app
    Can any one tell me how to change the port that my_app run on from 7778 to 80.
    So that the link to my_app will be:
    http:/my_sever_ip_address/my_app (run on default port 80)
    Very urgent!
    Thx

    You need to read the Oracle® Application Server 10g Administrator's Guide of your installation, which is also available online. In particular, for 9.0.4, you need to read the chapter Managing ports. Basically you need to change your web-cache listener port if web-cache is installed; otherwise you need to change Oracle HTTP Server Port.
    Also note tht port 80 requires extra steps since it is a restricted port.

Maybe you are looking for