Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

eConnect client and Dynamics GP server hosted in different AD domains

(0) ShareShare
ReportReport
Posted on by

Hi,

    We currently have some C# console applications that use eConnect to push data to GP db which works fine on our local network which have same domain.

The problem is we wanted to move the GP db to the cloud which will have a different domain (ex. CLOUD1) and that the server were the application is hosted is under a different domain (ex. LOCAL1). The 2 servers are able to ping each other because we have a VPN setup.

How do I get both the app to work with this setup? I assume eConnect only uses windows authentication to connect. Thanks in advance.

*This post is locked for comments

  • Rob Klaproth Profile Picture
    1,730 on at
    RE: eConnect client and Dynamics GP server hosted in different AD domains

    We have a one way trust.  When I install econnect on the new VDI machine that is on the different domain, we can't get past the first screen that asks for a domain user and password for the service account it just says invalid credentials.  I am trying to use the "Service account" from the other domain, maybe I need to create a new service account in the new domain and enter it, and then let the installer add the permissions in SQL, or do I also need to manually go into SQL and add the permissions?

  • Community Member Profile Picture
    on at
    RE: eConnect client and Dynamics GP server hosted in different AD domains

    Thanks Lyn for the suggestion, this worked for us as well. The network folks setup a one way trust for the domains and that resolved our issue.

    Thanks also to everyone who gave their suggestions. 

  • Community Member Profile Picture
    on at
    RE: eConnect client and Dynamics GP server hosted in different AD domains

    I differ with soma on the usage of sa.  sa is generally not preferred to be used in application, as this an in-built power user.  You have the risk where your security can be exposed.  Also, this may come as a point in the System Audits.  I prefer to use an alternative power user.

  • Suggested answer
    soma Profile Picture
    24,410 on at
    RE: eConnect client and Dynamics GP server hosted in different AD domains

    1. Make sure the eConnect is installed on the new cloud server(Where the current GP database available).

    2. Then try to connect the SQL server(Cloud server GP instance) from local domain SSMS.

    3. eConnect also use sa to connect the database(not only windows authentication). While installing you can specify eConnect connection in either SQL server authentication or Windows authentication.

    Better you can use "sa" (SQL server authentication) for eConnect connectivity to avoid the cross-domain problems.

    Hope this helps!!!

  • Verified answer
    Lyn Barr Profile Picture
    on at
    RE: eConnect client and Dynamics GP server hosted in different AD domains

    I'm not a network person, so by no means am I an expert.  However, I did have a circumstance once, where the Management Reporter was installed on a server under one domain, and the users were all in a different domain.  The network folks set up a trust between the two domains, and everything worked!

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

Jainam Kothari – Community Spotlight

We are honored to recognize Jainam Kothari as our June 2025 Community…

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard >

Featured topics

Product updates

Dynamics 365 release plans