Morning SP- People
I have taken the FE(01) out of NLB as this was causing the Main intranet portal not to render the sites correctly. Running on FE(02) the pages all render correctly and has better performance.
However….
My end users are getting a http404 error when trying to access a particular web app through FE(02) – I have noticed the IIS bindings are different across the two web FE’s.
So I ….
I stopped the web app in IIS on both WFE and changed the Bindings to so they are replicated (as on FE(02) it was defo incorrect for the web app concerned)
I have not changed any AAMÂ
I have restarted IIS on both WFE. when I type the host name into Url on the FE(02) I get taken to the IIS7 landing page. When i add /default.aspx to the url I get a page that has not rendered correctly and http 404 if i click a hyperlink.
Now When i access the web app on the FE(01) -out of NLB – and add /default.aspx I get the site in all its glory although some links give a http404.
Can anyone provide any suggestions as to what i can do to get this working ??
Do i need to do anything with AAM even though it looks to be set up correctly in CentralAdmin and worked prior to FE (01) going down?
Hi Mark there is no SSL on the web app that is giving the issue
Are you using host headers? Is the host header bound correctly to the binding in the web application? I have seen similar issues when the web application is not bound to the host header or host header is not used in the web application. It appears that you are being directed to the default web application in IIS and not going to the SharePoint web application because no host header or port is in the bindings. Just a suggestion I could be wrong…
You haven’t mentioned whether SSL is in use here. If so and your certificate bindings aren’t in order then IIS won’t know which site the incoming request is for. You can use netsh on the command line to check them.
Your AAM needs to have the URL that you are accessing your site with in there.Â
For example:
Default URL: http://intranet.company.com
URL you are accesing it with: http://portal.company.comÂ
you will need to add portal.company.com to the AAM.Â
Furthemore, you need to make sure to add http://portal.company.com to the bindings of the IIS Site “intranet.company.com.Â
Check out some tutorials:
http://blog.blksthl.com/2012/12/03/a-guide-to-alternate-access-mappings-basics-in-sharepoint-2013/
https://technet.microsoft.com/en-us/library/cc262366.aspxÂ
