Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
NAV Server Accessible Via IP But Not Name?
thunt
Member Posts: 5
Working on an environment setup for a customer, I came across an odd issue and I'm wondering if anyone else has seen it or has any explanation for it.
I set up a NAV server and a SQL server on the same box, and set the NAV server to look at the SQL server. When I try to access the NAV server via the RTC, I could not get to it when I entered the server name. This held true whether I used the simple server name (testserver) or the fully-qualified domain name (testserver.mycustomer.mycustomersdomain.net).
I received an error saying “A server was not found at ‘net.[url=tcp://testserver:7046/DynamicsNAV/Service]tcp://testserver:7046/DynamicsNAV/Service[/url]’. Either the URL is incorrect or the server is currently not available.”
However, once I tried to access the server by using the IP address instead of the name, it worked just fine.
I have seen this happen once before, on the same customer’s network, and I resolved it the same way. Has anyone else encountered this? Does anyone have an explanation as to why this would happen?
I set up a NAV server and a SQL server on the same box, and set the NAV server to look at the SQL server. When I try to access the NAV server via the RTC, I could not get to it when I entered the server name. This held true whether I used the simple server name (testserver) or the fully-qualified domain name (testserver.mycustomer.mycustomersdomain.net).
I received an error saying “A server was not found at ‘net.[url=tcp://testserver:7046/DynamicsNAV/Service]tcp://testserver:7046/DynamicsNAV/Service[/url]’. Either the URL is incorrect or the server is currently not available.”
However, once I tried to access the server by using the IP address instead of the name, it worked just fine.
I have seen this happen once before, on the same customer’s network, and I resolved it the same way. Has anyone else encountered this? Does anyone have an explanation as to why this would happen?
0
Comments
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
Your environemen was a 2 macine setup using a Virtual environment for you Service Tier and Database components. Your clients connect via a Virtual Server and when connection initiaolly connect fine, however you were not able to connect to the environment in the RTC without using the ip address. We removed and reinstalled the client and found that you could not setup the RTC to connect via FQDN. We removed and reinstalled the clinet and entered the RTC Settinsg using the ip address and were able to connect, but again are not able to reconnect from the RTC using the FQDN.
Upon further investigation you were using a Domain account with Domain Admin priviledges for your service tier account and a domain account for your SQL environment. We looked at the SPN's for the user account for ther Service Tier and there was no SPN Setup.
When using at 2 machine setup and a domain account you will have to create the SPN's for the domain account as described in the nav walkthrough for the 2 machine setup"
"However, the Network Service account is less secure because it is a shared account. Users who have rights to this account have rights to all services run by this account. Running the Microsoft Dynamics NAV Server service under a dedicated domain user account is the more secure option, although it requires additional configuration by a domain administrator. For more information, see the section about Configuring for a Domain User Account in Walkthrough: Installing the Three Tiers on Three Computers."
We switched your Service Account back to Network Service and the SQL server service accout back to Network Service and were able to connect to the environment using FQDN.
Base on this resolution we are closing this incident.