NAV 2009 RTC Error

chandrurec

Hi all,

Hi all,

I have configured domain in a centralised location in a seperate system and I have NAV 2009 RTC and SQl installed and configured in another system.

When I try to run the RTC from the centralised location using domain login , its showing me the error

"MICROSOFT DYNAMICS NAV SERVER CANNOT CONNECT THE CHANGE LISTNER BECAUSE OF THE FOLLOWING ERROR LOGIN FAILED FOR THE NTAUTHORITY\ANONYMOUS LOGON"

If anybody already come across this error, Kindly give solution to overcome this error.

Thanks in advance.

Regards,
Chandru.

kriki

[Topic moved from 'NAV/Navision Classic Client' forum to 'NAV Three Tier' forum]

alok_dida

chandrurec wrote:

"MICROSOFT DYNAMICS NAV SERVER CANNOT CONNECT THE CHANGE LISTNER BECAUSE OF THE FOLLOWING ERROR LOGIN FAILED FOR THE NTAUTHORITY\ANONYMOUS LOGON"

Add "NT AUTHORITY\NETWORK SERVICE " and "NT AUTHORITY\SYSTEM" users in ur SQL Server.

For do that connect to Database Server .. than go to Object Explorer than select Security and than select Logins and that add above two users.

It might be solve this problem.

mostle

Hi Chandru,

Anonymous Logon always looks like an authentication / delegation problem. And I would never give Anonymous Logon access to anything in my domain :shock:
Is your NAV database on another server than the Service Tier? Does the 3 Tier Architecture works?

kine

chandrurec wrote:

Hi all,

Hi all,

I have configured domain in a centralised location in a seperate system and I have NAV 2009 RTC and SQl installed and configured in another system.

When I try to run the RTC from the centralised location using domain login , its showing me the error

"MICROSOFT DYNAMICS NAV SERVER CANNOT CONNECT THE CHANGE LISTNER BECAUSE OF THE FOLLOWING ERROR LOGIN FAILED FOR THE NTAUTHORITY\ANONYMOUS LOGON"

If anybody already come across this error, Kindly give solution to overcome this error.

Thanks in advance.

Regards,
Chandru.

Yes, it is common error, and if you use search functionality, you will find the solution easily yourself... ;-)

You can search on google and on Microsoft MSDN documentation too...

TonyH

Delegation using dsa.msc and delgate the <MachineName>$ directly to the 1433 account using Kerberos...

http://msdn.microsoft.com/en-us/library ... x#delegate

t