ATA Gateway Services not starting

Are you able to connect from these machines to the destination machines that ATA fails for using ldp.exe via kerberos? or are you getting the same error there?

It doesn't work.

I already add 3 other DC's to my Ata Center but this one don't work.

Try to restart the GW machine, I wonder if it will change anything.

---

Paulo Silva wrote:

DNS ok and the time in the Ata Gateway is ok too.

Do you have ideia if this problem could be caused by another thing ?

 

Thanks

---

DNS ok and the time in the Ata Gateway is ok too.

Do you have ideia if this problem could be caused by another thing ?

Thanks

The GW is failing to connect to the *AD04 DC.

Error Code 82 suggest:

1. Confirm that the domain controller’s DNS record is configured properly in the DNS server. 
2. Verify that the time of the ATA Gateway is synchronized with the time of the domain controller.

Eli.

Having this problem again in another environment...

I receiving again this error 1067 and I already saw:

- Network connections ok;

- Net framework installation ok;

- WMI library ok;

- enought hardware to run gateway lightweight;

Anyone know what could be ?

I already add another 10 DC's in my Ata center in the same environment, but there's one that is showing this error 1067.

In this case is the deployment of 1.9 version.

Below follow my error.log

2018-04-26 16:49:40.9293 4792 13 Error [DirectoryServicesClient+<CreateLdapConnectionAsync>d__32] Microsoft.Tri.Infrastructure.Utils.ExtendedException: Failed to connect to domain controller [DomainControllerDnsName=XXXXXAD04.XXXXXXXX.corp ErrorCode=82] ---> System.DirectoryServices.Protocols.LdapException: A local error occurred.
 at System.DirectoryServices.Protocols.LdapConnection.BindHelper(NetworkCredential newCredential, Boolean needSetCredential)
 at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.CreateLdapConnectionAsync(?)
 --- End of inner exception stack trace ---
 at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.CreateLdapConnectionAsync(?)
 at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.CreateLdapConnectionAsync(?)
 at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.TryCreateLdapConnectionAsync(?)
2018-04-26 16:49:40.9772 4792 5 Error [DirectoryServicesClient+<OnInitializeAsync>d__14] Microsoft.Tri.Infrastructure.Utils.ExtendedException: Failed to communicate with configured domain controllers
 at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.OnInitializeAsync(?)
 at async Microsoft.Tri.Infrastructure.Framework.Module.InitializeAsync(?)
 at async Microsoft.Tri.Infrastructure.Framework.ModuleManager.OnInitializeAsync(?)
 at async Microsoft.Tri.Infrastructure.Framework.Module.InitializeAsync(?)
 at async Microsoft.Tri.Infrastructure.Framework.Service.OnStartAsync(?)
 at Microsoft.Tri.Infrastructure.Framework.Service.OnStart(String[] args)
2018-04-26 16:49:54.3286 3096 12 Error [DirectoryServicesClient+<CreateLdapConnectionAsync>d__32] Microsoft.Tri.Infrastructure.Utils.ExtendedException: Failed to connect to domain controller [DomainControllerDnsName=XXXXXAD04.XXXXXXXX.corp ErrorCode=82] ---> System.DirectoryServices.Protocols.LdapException: A local error occurred.
 at System.DirectoryServices.Protocols.LdapConnection.BindHelper(NetworkCredential newCredential, Boolean needSetCredential)
 at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.CreateLdapConnectionAsync(?)
 --- End of inner exception stack trace ---
 at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.CreateLdapConnectionAsync(?)
 at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.CreateLdapConnectionAsync(?)
 at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.TryCreateLdapConnectionAsync(?)
2018-04-26 16:49:54.3443 3096 5 Error [DirectoryServicesClient+<OnInitializeAsync>d__14] Microsoft.Tri.Infrastructure.Utils.ExtendedException: Failed to communicate with configured domain controllers
 at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.OnInitializeAsync(?)
 at async Microsoft.Tri.Infrastructure.Framework.Module.InitializeAsync(?)
 at async Microsoft.Tri.Infrastructure.Framework.ModuleManager.OnInitializeAsync(?)
 at async Microsoft.Tri.Infrastructure.Framework.Module.InitializeAsync(?)
 at async Microsoft.Tri.Infrastructure.Framework.Service.OnStartAsync(?)
 at Microsoft.Tri.Infrastructure.Framework.Service.OnStart(String[] args)

In the above case a  rebuild of the WMI Repository solved the problem.

What was the solution as I am experiencing the exact problem.

Eli,

I sent for you a private message with my gateway configuration.

Thanks