NAV 2013 RTC not connecting over VPN

afarrafarr Member Posts: 287
edited 2013-10-09 in NAV Three Tier
We have installed NAV 2013 (build 35201) and SQL Server 2008 R2 on a virtual server (Win 2008 R2) where it works fine.
RTC connects to the default MyServer:7046/DynamicsNAV70

We also installed NAV 2013 (client only) on a PC in the same domain. The PC can connect to the VPN, and then telnet to MyServer on port 7046, but RTC cannot connect to MyServer:7046/DynamicsNAV70 – we get the standard message “A server was not found at net.[url=tcp://MyServer:7046/DynamicsNAV70/Service]tcp://MyServer:7046/DynamicsNAV70/Service[/url]”

Event Viewer doesn’t show any relevant error messages.

We set the NAV 2013 service to run with Administrator credentials, just to rule out permission problems, and restarted MyServer, but the problem remained the same.

The forum posts that mention VPN and RTC didn’t provide a solution either.

Have you encountered this before?
Alastair Farrugia

Answers

  • bbrownbbrown Member Posts: 3,268
    What are you ultimately trying to accomplish?
    There are no bugs - only undocumented features.
  • afarrafarr Member Posts: 287
    The client wants to connect to RTC without using Remote Desktop.

    It's a standard 2-tier setup, with the SQL and NAV server on one machine, and the NAV client(s) on other machines.

    We tried using the IP address as server name (both external and internal IPs), but still got the same error.
    Alastair Farrugia
  • bbrownbbrown Member Posts: 3,268
    This may provide you some insight: http://msdn.microsoft.com/en-us/library/gg502476.aspx

    Also, be sure both you and your client review and understand the "Performance Considerations" before proceeding with this configuration. You'll avoid disappointment.
    There are no bugs - only undocumented features.
  • afarrafarr Member Posts: 287
    I discussed this again with the client today, and found that the server is still in a workgroup, while the PCs are in a Windows domain.

    They are now trying to join the server to the domain, and that should solve the problem.

    I'm sorry that I posted about this problem with incomplete information.
    I will mark it as solved.
    Alastair Farrugia
Sign In or Register to comment.