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
- 262 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
problem with Server Computer Name
larshaedersdal
Member Posts: 12
Hi Guys
I have the following setup
NAV 2018 CU8, my service tier is running on a server named navserver.domain.local. When I connect to the servicetier from remote I use navserver.domain.com,
and everything is fine. When I from the RTC wants to open the sessions page it comes with a warning saying
You are about to connect to 'Instance name' on server navserver.domain.local which is not your current default connect settings.
This can create a security risk.
I understand the warning is because my default connect settings is navserver.domain.com but why is it not using the default connect settings and is there a fix for this? I have the same problem when using the development client from remote and I want to sync changes.
I have the following setup
NAV 2018 CU8, my service tier is running on a server named navserver.domain.local. When I connect to the servicetier from remote I use navserver.domain.com,
and everything is fine. When I from the RTC wants to open the sessions page it comes with a warning saying
You are about to connect to 'Instance name' on server navserver.domain.local which is not your current default connect settings.
This can create a security risk.
I understand the warning is because my default connect settings is navserver.domain.com but why is it not using the default connect settings and is there a fix for this? I have the same problem when using the development client from remote and I want to sync changes.
0