web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Answered

[Heads UP]: Microsoft is working on a delegation scenario with MSDyn365BC v19 and Windows authentication

(0) ShareShare
ReportReport
Posted on by Microsoft Employee

Hello,

If your customer does not operate his business OnPrem in a three tier or four tier environment, you can stop reading. Otherwise, we are looking into an issue where kerberos authentication is preventing logon to WebClient. 

Despite correctly configured SPN's that used work fine in previous setup, the errors we see could be like this. 

Exception:

Microsoft.Dynamics.Nav.Types.NavServerNotFoundException: A server was not found at "net.tcp://bc:7046/BC/Service". Either the URL is incorrect or the server is currently not available.

---> System.IO.IOException: The read operation failed, see inner exception.

---> System.ServiceModel.CommunicationException: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:00:59.9910000'.

---> System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host.

-------------------------

CSS is already working and we will post more information in this forum as soon as we have it.

Thanks.

I have the same question (0)
  • Suggested answer
    Marga Profile Picture
    575 on at

    Thank you for sharing!

  • Verified answer
    Marco Mels Profile Picture
    Microsoft Employee on at

    Dear all,

    We found the problem. The issue is not related to the OS. The issue is a regression due to moving to newest version of WCF libraries build for .NET 5. We will add new manual tests for this so that it will not regress again.

    The fix is scheduled to be included with 19.2 release. As a workaround, the WebClient components can be installed on NST server (which we understand you do not want to do) or use NavUserPassword / Azure AD authentication type for the time being till we release 19.2.

    Constrained delegation is only used for windows auth and when NST and WebServer are on separate machines

    Thank you. 

  • Jake Edwards Profile Picture
    on at

    We're still getting no connection from 19.2 -- we're going to try redeploying to see if anything changes.

    Was this fix definitely included in 19.2?

    Regards,

    Jake

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 1,821 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,122 Super User 2026 Season 1

#3
Dhiren Nagar Profile Picture

Dhiren Nagar 959 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans