SharePoint Server Search Administration Medium Could not find or connect to host controller on server
Introduction
SharePoint Server Search Administration Medium Could not find or connect to host controller on server
Issue
After we configure everything related to search, when we try to find the search we see the error “A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond”
Event
0x0BD8 SharePoint Server Search Administration Medium Could not find or connect to host controller on server SERVER. Exception: Could not connect to net.tcp://SERVER/ceres/hostcontroller/nettcp. The connection attempt lasted for a time span of 00:00:21.0369864. TCP error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.181.14.21:808. Server stack trace: at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout) at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout) at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout) at System.ServiceModel.Channels.ClientFramingDupl… ff78fc9b-4b6c-b08b-52a2-ff7745f71f1f
Resolution
After going through the Events and running traces we see the issue is related to the network. Deep diving on the issue shows something is blocking the search.
- Check the firewall settings.
- Stop the firewall and search. This will work but is not recommended on production servers.
- Create a new rule allowing Inbound traffic on TCP Port 808 on all SharePoint Servers. Go to Windows firewall with advanced security->click on Inbound->create a new rule to allow.
See more at SharePoint Server Search Administration Medium Could not find or connect to host controller on server
Note: If you find a different solution, please report it as a comment to this post. This will be useful to the SharePoint Community. Be sure to double-verify it: undo your solution and verify that the problem comes back, then redo it and verify that the problem goes away.