How to Create a Classic Mode Authentication via ‘Negotiate (Kerberos)’ in SharePoint 2013, Part 2: How to Establish Name Resolution

In this post, I will use two servers: an Active Directory Domain server, and a SharePoint 2013 Web Server that is joined to an Active Directory Domain server (Windows Server 2008 R2).

Make sure that the URL of the Web Application has an A-Record created in DNS. When we create this URL, the SharePoint 2013 Web Server that is joined to an Active Directory Domain will get an A-record created automatically. Also, make sure that an entry for the Web Applications URL has been added to the client's host file.

To create an A-record in DNS, go to the Active Directory Domain server using following steps:

1.       Go to Administrative Tools, open DNS Management.

2.       In DNS Management, expand the Forward Lookup Zones section.

3.       Right-click on the domain name, and click on New Host (A or AAAA)…

4.       Type in the server name of the SharePoint 2013 Web Server; this is the URL of the Web Application.

Note: In this post, I use Kerberos authentication to a SharePoint 2013 site on default port 80 with a single SharePoint Web Server.

5.       Type in the IP address of the SharePoint 2013 Web Server.

6.       Click Add Host, click OK.

7.       You will see this verification dialog with servername.fulldomainname, click OK.

8.       Make sure that the record has been created in the right pane of DNS Management.

9.       To make sure with above steps, do a flush of the DNS cache as follows:

Go to Start, select Command Prompt, select Run as administrator.

Ipconfig -flushdns

Press Enter.

10.   In the Command Prompt, ping the Web Application URL.

For example: ping Chaupso15sql

11.   To add the entry for the Web Applications URL into the Hosts file, go to the Hosts file on your client server in the following path: C:WindowsSystem32Driversetchosts.

 12.   Add server name, domain name, and IP.

Example: 172.16.124.11 chaupso15sql

172.16.124.11 chaupso15sql.huyteam.com       

Part 2 is complete. If you want to continue reading How to Create a Classic Mode Authentication via 'Negotiate (Kerberos)' in SharePoint 2013, check out the rest of our series:

For further reading:    

All SharePoint Versions

The web parts are functional components that extend your SharePoint environment whether it’s hosted, on-premises, or part of Microsoft® Office 365.

SharePoint 2013, 2016, 2019, Online (Office 365)

On-Premises Only

These web parts extend SharePoint beyond its out-of-the-box capabilities by tailoring it to your requirements with Bamboo Solution’s growing portfolio of SharePoint Web Parts.

SharePoint 2013, 2016, 2019

SharePoint

Product Suites

Experience greater power and savings by bundling our SharePoint apps and web parts.


Essentials Suite


Essentials Plus Suite


Bamboo Premier Suite


Project Management Suite


Knowledge Management Suite


External User Manager


 

For more information on our product suites, contact us.

Featured Services

SharePoint Health Check

A SharePoint Health Check will identify the causes of issues and risks associated with your specific environment, and is custom tailored to provide you with the best recommendations to optimize your SharePoint environment.

SQL Health Check

Document recommendations relating to performance, stability, availability, or a specific focus you request of your SQL Server database instances.

My SharePointXperts

The truth is that each SharePoint skill may not be a full time job for many organizations, and it is nearly impossible for one person to do everything you need – so augment your team with SharePointXperts; providing the skill sets you need when you need them!