Skip to main content

List of ports used by SharePoint 2016

ProtocolPortUsageComment
TCP80httpClient to SharePoint web server traffic
(SharePoint – Office Web Apps communication)
TCP443https/sslEncrypted client to SharePoint web server traffic
(Encrypted SharePoint – Office Web Apps communication)
TCP1433SQL Server default communication port.May be configured to use custom port for increased security
UDP1434SQL Server default port used to establish connectionMay be configured to use custom port for increased security
TCP445SQL Server using named pipesWhen SQL Server is configured to listen for incoming client connections by using named pipes over a NetBIOS session, SQL Server communicates over TCP port 445
TCP25SMTP for e-mail integrationCannot be configured
TCP16500-16519Ports used by the search index componentIntra-farm only
Inbound rule Added to Windows firewall by SharePoint
TCP22233-22236Ports required for the AppFabric Caching ServiceDistributed Cache…
TCP808Windows Communication Foundation communicationWCF
TCP32843Communication between Web servers and service applicationshttp (default) To use custom port, see references section
Inbound rule Added to Windows firewall by SharePoint
TCP32844Communication between Web servers and service applicationshttps
Inbound rule Added to Windows firewall by SharePoint
TCP32845net.tcp binding: TCP 32845 (only if a third party has implemented this option for a service application) Custom Service Applications
Inbound rule Added to Windows firewall by SharePoint
TCP32846Microsoft SharePoint Foundation User Code Service (for sandbox solutions) Inbound on all Web Servers
Inbound rule Added to Windows firewall by SharePoint
Outbound on all Web and App servers with service enabled.
TCP5725User Profile Synchronization Service(FIM)Synchronizing profiles between SharePoint 2013 and Active Directory Domain Services (AD DS) on the server that runs the Forefront Identity Management agent
TCP + UDP389User Profile Synchronization Service(FIM)LDAP Service
TCP + UDP88User Profile Synchronization Service(FIM)Kerberos
TCP + UDP53User Profile Synchronization Service(FIM)DNS
UDP464User Profile Service(FIM)Kerberos change password
TCP809Office Web AppsIntra-farm Office Web Apps communication.

Comments

Popular posts from this blog

How to get SPUser or SPGroup from Person or Group field

You have person or group field in SharePoint list and you want to programmatically get the user or person. The below code to gets SPUser from User or Group field in the list when multiple choice and Groups are not allowed in the field: //get SPUser SPFieldUser userField = (SPFieldUser)item.Fields.GetField("Users"); SPFieldUserValue userFieldValue = (SPFieldUserValue)userField.GetFieldValue(item["Users"].ToString()); SPUser user = userFieldValue.User; This part of code would help you to get SPUser when multiple choice is allowed and groups are not allowed: //Multiple choices are allowed SPFieldUser userField = (SPFieldUser)item.Fields.GetField("Users"); SPFieldUserValueCollection userFieldValueCollection = (SPFieldUserValueCollection)userField.GetFieldValue(item["Users"].ToString()); foreach (SPFieldUserValue userFieldValue in userFieldValueCollection) {     Console.WriteLine("     " + userFieldValue.User.LoginName); } And when group

SharePoint publishing page scheduling

In SharePoint 2010 publishing enabled team site collection is not showing schedule button in publish ribbon. Solution: Here is how to enable it  though the UI: Locate the SharePoint Server Web site on which you want to enable content approval and item scheduling. Click  Site Actions , click  Site Settings , and then click  Modify Pages Library Settings . Under  General Settings , click  Versioning Settings . Click  Yes  next to  Content Approval , and then click  OK . Click  Manage item scheduling .   Click to enable the  Enable scheduling of items in this list  check box, and then click  OK .

Changing Content Type Hub URL

Change the Hub URL through powershell by using: Set-SPMetadataServiceApplication -Identity " " -HubURI " " For Ex: Set-SPMetadataServiceApplication -Identity "Managed Metadata Service" -HubURI "http://contenttype.Domain.Com" When you try to do this you get this rather scary message: This is SharePoint telling you that this is a major thing so be careful! Essentially all your content types that you have published out will be removed if they can, and you have to republish all of your content types out again which can cause some issue.