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
- 267 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 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 2009 R2 - Connection Error Mystery
llegrand
Member Posts: 9
Hello everybody,
I need help from people who have already installed NAV 2009 R2 with RTC on customer site.
I meet this message when trying to connect with RTC on NAV service from a computer included in the same LAN (including mine):
“A server was not found at "net.tcp://[myserver]:7046/DynamicsNAV/Service". Either the URL is incorrect or the server is currently not available.”
When I try to connect with the same path directly from the server through RTC, it works properly!.
Classic client connection to the database works on server and other same LAN computers.
Server and Database server are on the same machine.
Database was installed on “SQL Server 2005 Express” (auto-installed by NAV Setup).
The server is the only one server of the company (DNS, DHCP, AD, IIS).
Check 1: Firewall
Windows Firewall is off.
Symantec Firewall is off.
Physical Firewall (only for WAN) is rightly configured.
Check 2: User rights
Services user (domain account) has been granted to be “Administrators” group member (only during tests).
Check 3: Install a second service
Installing a second service doesn’t change anything. Still available from server, but not from other computers in LAN.
Check 4: Delegation
Setting delegation as explained in manual hasn’t changed anything.
Check 5: NAV License
Tried with Partner and Customer licenses
Check 6: Uninstall, Reinstall
… nothing better…
Check 7: Try another fully operational port
Port 80 was accessible with IIS. I saw an IIS start page when browsing server from every computer in the LAN.
I’ve changed the NAV service port from 7046 to 80.
I’ve stopped IIS.
Connecting RTC directly from server works, but still doesn’t work from other computer in the LAN.
Conclusion: port doesn’t seems to be blocked; but NAV service seems to be.
Check 8: Running the Best Practice Analyzer for Microsoft Dynamics NAV 2009
Everything was good.
Check 9: Reverse Installation
I’ve installed the NAV Service and “SQL Server Express” on a Laptop, and tried to connect with the RTC installed on server… and it works!
Problem:
The NAV service on server seems to be blocked for external TCP communication.
Is somebody already met this situation? ](*,)
Anybody has another step-to-try for me?
Can this problem coming from the fact that server is also DNS server?
Who has a clue for me?
Thanks in advance!
I need help from people who have already installed NAV 2009 R2 with RTC on customer site.
I meet this message when trying to connect with RTC on NAV service from a computer included in the same LAN (including mine):
“A server was not found at "net.tcp://[myserver]:7046/DynamicsNAV/Service". Either the URL is incorrect or the server is currently not available.”
When I try to connect with the same path directly from the server through RTC, it works properly!.
Classic client connection to the database works on server and other same LAN computers.
Server and Database server are on the same machine.
Database was installed on “SQL Server 2005 Express” (auto-installed by NAV Setup).
The server is the only one server of the company (DNS, DHCP, AD, IIS).
Check 1: Firewall
Windows Firewall is off.
Symantec Firewall is off.
Physical Firewall (only for WAN) is rightly configured.
Check 2: User rights
Services user (domain account) has been granted to be “Administrators” group member (only during tests).
Check 3: Install a second service
Installing a second service doesn’t change anything. Still available from server, but not from other computers in LAN.
Check 4: Delegation
Setting delegation as explained in manual hasn’t changed anything.
Check 5: NAV License
Tried with Partner and Customer licenses
Check 6: Uninstall, Reinstall
… nothing better…
Check 7: Try another fully operational port
Port 80 was accessible with IIS. I saw an IIS start page when browsing server from every computer in the LAN.
I’ve changed the NAV service port from 7046 to 80.
I’ve stopped IIS.
Connecting RTC directly from server works, but still doesn’t work from other computer in the LAN.
Conclusion: port doesn’t seems to be blocked; but NAV service seems to be.
Check 8: Running the Best Practice Analyzer for Microsoft Dynamics NAV 2009
Everything was good.
Check 9: Reverse Installation
I’ve installed the NAV Service and “SQL Server Express” on a Laptop, and tried to connect with the RTC installed on server… and it works!
Problem:
The NAV service on server seems to be blocked for external TCP communication.
Is somebody already met this situation? ](*,)
Anybody has another step-to-try for me?
Can this problem coming from the fact that server is also DNS server?
Who has a clue for me?
Thanks in advance!
0
Answers
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
It works properly when I start the RTC Client on the Server.
But I also can't telnet a fully functional server locally on my laptop
I'm not a telnet master :whistle:
Start a command prompt.
Type telnet servername 7046
If you are running a Navision server on your local computer, then try:
telnet localhost 7046
Both should give a blank screen... If telnet cannot connect, you get an error that it was impossible to connect...
Web Services and Telnet were working good.
The problem come from the fact that the login used to install RTC on Laptop was not in the same AD Domain than the Server.
In addition, I was misled by the error message which says that there is no server instead of saying there is an login authentication error.
I've used RTC Over WAN to solve the problem.
Thanks for the help