TCP/IP Ports of SharePoint 2013


Protocol
Port
Usage
Comment
TCP
80
http
Client to SharePoint web server traffic
(SharePoint – Office Web Apps communication)
TCP
443
https/ssl
Encrypted client to SharePoint web server traffic
(Encrypted SharePoint – Office Web Apps communication)
TCP
1433
SQL Server default communication port.
May be configured to use custom port for increased security
UDP
1434
SQL Server default port used to establish connection
May be configured to use custom port for increased security
TCP
445
SQL Server using named pipes
When 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
TCP
25
SMTP for e-mail integration
Cannot be configured
TCP
16500-16519
Ports used by the search index component
Intra-farm only
Inbound rule Added to Windows firewall by SharePoint
TCP
22233-22236
Ports required for the AppFabric Caching Service
Distributed Cache…
TCP
808
Windows Communication Foundation communication
WCF
TCP
32843
Communication between Web servers and service applications
http (default) To use custom port, see references section
Inbound rule Added to Windows firewall by SharePoint
TCP
32844
Communication between Web servers and service applications
https
Inbound rule Added to Windows firewall by SharePoint
TCP
32845
net.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
TCP
32846
Microsoft 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.
TCP
5725
User 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 + UDP
389
User Profile Synchronization Service(FIM)
LDAP Service
TCP + UDP
88
User Profile Synchronization Service(FIM)
Kerberos
TCP + UDP
53
User Profile Synchronization Service(FIM)
DNS
UDP
464
User Profile Service(FIM)
Kerberos change password
TCP
809
Office Web Apps
Intra-farm Office Web Apps communication.
Plan security hardening for SharePoint 2013
http://technet.microsoft.com/en-us/library/cc262849.aspx
Configure SQL Server security for SharePoint 2013 environments
http://technet.microsoft.com/en-us/library/ff607733.aspx#proc1
TCP/IP Communications (Windows Server AppFabric Caching)
http://msdn.microsoft.com/en-us/library/ee790914(v=azure.10).aspx

Comments

Post a Comment

Popular posts from this blog

"There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word." Office WebApp Error

Problem: When Opening a word document I get the following error when Office Web Apps tries to render the document " There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word. " Initial Hypothesis: Check the ULS logs on the Web Front End (SharePoint Server) as this doesn't tell me much.  I found the following issue in my UL S: WOPI (CheckFile) - Invalid Proof Signature for file SandPit Environment Setup.docx url: http://web-sp2013-uat.demo.dev/Docs/_vti_bin/wopi.ashx/files/6d0f38c0d5554c87a655558da9cedcad?access_token... Resolution: Run the following PS> Update-SPWOPIProofKey -ServerName "wca-uat.demo.dev" More Info: http://technet.microsoft.com/en-us/library/jj219460.aspx
Continue Read

"We’re sorry. We ran into a problem completing your request. Please try that again in few minutes." Excel Service SharePoint

Image
This article explains about Excel related issue in our SharePoint 2013 Environment. Whenever user tries to open excel files uploaded in document library, it launches browser to open the file and then displays below error- " We’re sorry. We ran into a problem completing your request. Please try that again in few minutes." Also see below screenshot- As part of issue analysis, following checks were performed- 1.) Check if Excel Services is running. ( This was running in our case. ) Open Central Administration -> System Settings -> Manage Services on Server -> Excel Calculation Service -> Started 2.) Check if Excel Service Application is associated to Web Application in question. ( This was configured in our case. ) Open Central Administration -> Application Management -> Manage Web Applications -> Select Web Application -> Select Configure Service Associations 3.) Check if Trusted File Location is configured for Excel Service...
Continue Read

Deployment error "The web.config is invalid on this IIS Web Site"

I've developed a webpart that deploys and works properly in my DEV environment. When I attempt to deploy to PROD I get the following error: SOMESERVER : http://acme.com/ : SharePoint - 41981 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\41981\web.config. SOMESERVER : http://acme.com/ : SharePoint - 41981 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\41981\web.config. SOMESERVER1 : http://acme.com/ : SharePoint - 23994 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\23994\web.config. None of these virtual directories exist. Any ideas how to resolve? Solution : In Central Administration-> Operation-> Services on Server, please stop the Windows SharePoint Services Web Application service , SharePoint will remove the sites in IIS. And then start the Windows SharePoint Services Web Application service agai...
Continue Read