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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics NAV (Archived) / Problem with changing ...
Microsoft Dynamics NAV (Archived)

Problem with changing server in RTC for NAV 2017

(0) ShareShare
ReportReport
Posted on by Community Member

Hello there, 

I'm having an issue with using the RTC cross-domain - sort of. We have one domain in our local office and another domain for our Azure servers where we host NAV. 

I've installed the RTC to local machines on the local domain and set the RTC for username type authentication so when launched the RTC prompts and the user enters domain\username and their password for the Azure domain. The funny thing is that this works in connecting to the development environment which was the one I configured on install. The connection is made and the RTC works as expected. 

The problem comes when changing servers. I have the production instance of the NAV100 service up and running and it works locally when opening the RTC on the desktop of the Azure server. I can switch back and forth between dev and prod by selecting "change server" and changing the port number and instance name in the connection string. 

However, when I try this operation on a non-Azure machine, it prompts for the username and password again, and then comes back with a net.tcp server not found error. 

Any ideas as to what I am missing?

Thanks!

*This post is locked for comments

I have the same question (0)
  • ShanAbeywicrema Profile Picture
    ShanAbeywicrema 948 on at

    where is production instance located ?  Is it on same azure or local server ?

  • Community Member Profile Picture
    Community Member on at

    It is on the same Azure server as the development instance - just different port assignments. Both are visible as running in the Admin Console. Firewall rules and endpoints in Azure are set correctly. I can port scan the public IP and port assigned to the Client service and see the opening from the local machine.

  • ShanAbeywicrema Profile Picture
    ShanAbeywicrema 948 on at

    When you open database from development environment. Can you see production instance ? (File -> Database -> Information)

  • Community Member Profile Picture
    Community Member on at

    Yes. I can view information, and open it without issue.

  • ShanAbeywicrema Profile Picture
    ShanAbeywicrema 948 on at

    I just want to know whether you can see Server instance in the information (Last info)?

  • Community Member Profile Picture
    Community Member on at

    Yes, it's there. I can see it. It's in the form servername.domain.local:port/instance-name

  • ShanAbeywicrema Profile Picture
    ShanAbeywicrema 948 on at

    You can do couple of things. Just only for the testing.

    As your dev instance worked. You can assigned production database in dev instance. Just for the testing and you can check whether RTC is opening or not.

    If it is open for you. I guess there is permission problem which is for production database (SQL side)

  • Verified answer
    Community Member Profile Picture
    Community Member on at

    I ended up answering my own question after playing around with it for awhile. I just wanted to resolve this thread. The issue was that because I was connecting cross-domain, I had installed the RTC with UserName authentication specified in the config. The service running on the server was set up for Windows authentication. Somehow, even though mis-matched, this combination of authentication methods still allows for initial login through the RTC, even from the remote domain. I guess it accepts the username of DOMAIN\username as an impersonation of Windows credentials. Anyway, it works to log in to the server from the client on launch. However, when you try to change server, it gives the net.tcp error. Changing the service to use UserName authentication and installing the requisite certificate and setting the thumbprint in the service config solved my issue. Also, it's helpful not to forget to add the DNS identity to the RTC config on install when using this configuration or the connection will not succeed. Everything is running fine now. Thanks for attempting to help me solve the issue!

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans