Can i Access NAV 2009 from internet?

bangswit
Member Posts: 265
as i know. nav 2009 is web based
can i access nav 2009 from the internet?
is it must used RTC?
thanks
can i access nav 2009 from the internet?
is it must used RTC?
thanks
0
Comments
-
NAV 2009 is not web based.There are no bugs - only undocumented features.0
-
bangswit wrote:can i access nav 2009 from the internet?Timo Lässer
Microsoft Dynamics NAV Developer since 1997
MSDynamics.de - German Microsoft Dynamics Community - member of [clip]0 -
You can use Web Services for this...0
-
Can we clarify what we mean? Do we mean accessing the NAV application via a web browser? Or are we talking about accessing NAV database (and maybe business logic) via a HTML based application?
For the first part this has been doable for some time using the Advanced Terminal Server client (or other methods). The second one put you in the realm of Web Services.There are no bugs - only undocumented features.0 -
Timo Lässer wrote:bangswit wrote:can i access nav 2009 from the internet?
But still, it doesn't mean that it is web based or that using RTC over internet will be usable for real usage. New feature in NAV 2009 R2 just mean that "it is possible" but still you need to have good bandwidth to not have performance problems...0 -
so only the NAV 2009 R2 can access NAV (using RTC)?
is it already published?0 -
bangswit wrote:so only the NAV 2009 R2 can access NAV (using RTC)?
is it already published?0 -
All, thanks for the sharing....
any other additional information would be good
thanks0 -
If you have VPN, you do not need to use only Remote Desktop Connection. NAV 2009 is 3 tier application. You can use database server, application server and client (RTC) on different location. This mean that you can use RTC on own PC, while servers is remote. This is access from internet, although NAV 2009 is not classic internet application.0
-
atotovic wrote:If you have VPN, you do not need to use only Remote Desktop Connection. NAV 2009 is 3 tier application. You can use database server, application server and client (RTC) on different location. This mean that you can use RTC on own PC, while servers is remote. This is access from internet, although NAV 2009 is not classic internet application.
This is not supported.There are no bugs - only undocumented features.0 -
But I want to emphasize the word "can". It is same can as in "You can jump from this roof down". It is the "can" you do not want to become reality. It is good only for exceptional access to development or test database, not for Live usage in real company (if the company have more than one user).0
-
bbrown wrote:atotovic wrote:If you have VPN, you do not need to use only Remote Desktop Connection. NAV 2009 is 3 tier application. You can use database server, application server and client (RTC) on different location. This mean that you can use RTC on own PC, while servers is remote. This is access from internet, although NAV 2009 is not classic internet application.
This is not supported.0 -
kine wrote:bbrown wrote:atotovic wrote:If you have VPN, you do not need to use only Remote Desktop Connection. NAV 2009 is 3 tier application. You can use database server, application server and client (RTC) on different location. This mean that you can use RTC on own PC, while servers is remote. This is access from internet, although NAV 2009 is not classic internet application.
This is not supported.
I really don't know where's the "miss-usage" when using VPN as a connection to the NAV server or the DB directly (classic client)? I've been using this kind of connection ever since and as long there is a fairly good internet connection it's working like a charm. I would advise anyone to use the VPN connection instead of ANY terminal (rdp, cytrix,...) one and it's the kind of connectivity that MS itself emphasizes.0 -
problem is the partas long there is a fairly good internet connection it's working like a charm
Because:
1) internet is not reliable
2) You do not have granted bandwidth in most cases
3) If you run more users over the link, and somebody start download, you will kill the performance for others
4) In most cases, the latency is too big
and of course, all depends on what you are doing in NAV. If you are posting, or just running reports, or you are starting the Cost Adjustment batches etc...0 -
bbrown wrote:rhpnt wrote:and it's the kind of connectivity that MS itself emphasizes.
I have never heard or seen anything from MS supporting or promoting this type of connections (pre R2).
Well I've read about it a lot. Start in Security Hardening Guide - page 20+ included in every NAV installation - MS never mentions any terminal access. More to follow...0 -
kine wrote:problem is the partas long there is a fairly good internet connection it's working like a charm
Because:
1) internet is not reliable
2) You do not have granted bandwidth in most cases
3) If you run more users over the link, and somebody start download, you will kill the performance for others
4) In most cases, the latency is too big
and of course, all depends on what you are doing in NAV. If you are posting, or just running reports, or you are starting the Cost Adjustment batches etc...
1-the same applies for terminal access
2-true, but a symmetric 10/10Mb acces is almost standard for companies nowadays
3-the link MUST be reserved for ERP access - no surfing/download allowed
4-if 2 true then "no latency"0 -
rhpnt wrote:bbrown wrote:rhpnt wrote:and it's the kind of connectivity that MS itself emphasizes.
I have never heard or seen anything from MS supporting or promoting this type of connections (pre R2).
Well I've read about it a lot. Start in Security Hardening Guide - page 20+ included in every NAV installation - MS never mentions any terminal access. More to follow...
You are interpreting those statements too broadly and taking them out of the context (security) for which they were intended.There are no bugs - only undocumented features.0 -
rhpnt wrote:bbrown wrote:rhpnt wrote:and it's the kind of connectivity that MS itself emphasizes.
I have never heard or seen anything from MS supporting or promoting this type of connections (pre R2).
Well I've read about it a lot. Start in Security Hardening Guide - page 20+ included in every NAV installation - MS never mentions any terminal access. More to follow...
See Tech Article 874535 on PartnerSource. While this article specifically references version 3.70 Microsoft's stand has not changed. At least not until R2 is released. Then we shall see.There are no bugs - only undocumented features.0 -
rhpnt wrote:2-true, but a symmetric 10/10Mb acces is almost standard for companies nowadays
Yes, and minimum requirement for NAV C/Side client was 10Mbps, optimal 100Mbps (for NAV 2009 the network speed is not described in the system requirements). And this is per client. Thus your "standard" line is only for one user...
My final word - NAV is for LAN, not for WAN. WAN access is only exceptional possibility.0 -
bbrown wrote:See Tech Article 874535 on PartnerSource. While this article specifically references version 3.70 Microsoft's stand has not changed. At least not until R2 is released. Then we shall see.
Well, if I took something out of context then I don't know what to say about your contribution.
Because this doc is marked as confidential I can't quote it, but I would highly suggest that anybody who has access to it reads it and decides if it's still valid. I really can't believe that you are putting up this doc as an argument.
Let me reconcile my statement; I'm not saying that NAV is ready for online 9h-17h work from remote branch offices via VPN and the Internet. For such scenarios there are other tools and products which take care of that.
I'm saying that for every data connection VPN should always be choice over any kind of terminal one and that the terminal connection was NEVER intended for ERP online 9h-17h work. In terms of reliability and security there is NO other choice than VPN. I'm saying that rdp is the lowest most primitive form of remote connection possible and shall be avoided for use in realtime production ERP environments at any cost!0 -
I don't know your scenario but make sure you have a WAN line with a symmetrical speed (10/10Mb min.) reserved exclusive for NAV (no surfing, streaming,...). Set up a solid VPN connection (MS or Cisco) and access the db using the client installed locally on the remote pc.
Consult a local IT system integrator for further details and final implementation.0 -
Best solution is to use VPN and RDP together (RDP could be used as Remote Application). Thus you have security and low bandwidth with high performance together.0
-
kine wrote:Best solution is to use VPN and RDP together (RDP could be used as Remote Application). Thus you have security and low bandwidth with high performance together.
I would argue that the best solution (cost aside) is private line with RDP. In situations where private lines are not practical, either due to cost or availability then I'd say VPN would be the next choice.There are no bugs - only undocumented features.0 -
-
Nav guys finally blogged about this:
http://blogs.msdn.com/b/nav/archive/2010/09/27/hosting-possibilities-for-dynamics-nav-2009-r2.aspx0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions