If not, then follow the below steps to update in the host file. (optional) In Command Prompt, ping the web application URL and check if it’s working fine.Verify that the A Record is created in the right pane with correct Host name and IP address.You will see the confirmation dialog box.If you have 2 WFE Servers within the same farm, you need to make 2 entries - one for each WFE Server with the same Host Name and with respective WFE’s IP address. Enter your Host Name - this is the URL of the web application (minus the domain part in a FQDN) and type in the IP address of WFE Server.

You will see the below screen for entering the new Host details.Right click on your domain and click on 'New Host (A or AAAA)'.Expand 'Forward Lookup Zones' container.Open DNS Management in Administrative Tools on a DNS Server.This section to be execute ONLY on DNS Server. Note - This section is to be executed by Windows Server Administrator for reliable configuration. Click OK button to create new web application with Kerberos Authentication type.However, you need to use the port number too during the execution of Service Principal Name commands (Section 3). Note - You can use the default name with port number given by SharePoint. Change the public URL to a specified URL.Specify the type of Authentication to 'Negotiate (Kerberos)' in Claims Authentication Type section.

Specify the name for web application, such as “webapplication name” in IIS web site section.

Create new web application in the dialog box.

Click on 'Manage web application' in 'Application Management' section.

This article will help the SharePoint administrators who want to configure the Kerberos Authentication in their SharePoint web applications.Ĭreating new web application with Kerberos Authentication We have captured step by step process of how to configure Kerberos Authentication in SharePoint 2013. My team recently configured Kerberos Authentication in SharePoint 2013 web application.