web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics NAV (Archived)

Bandwidth and Latency for MS Dynamics NAV

(0) ShareShare
ReportReport
Posted on by 315

Is there anybody have the experience of testing NAV in a VSAT connectivity?

*This post is locked for comments

I have the same question (0)
  • Hardik Shah Profile Picture
    on at

     Ya...i have experienced of testing NAV in a wireless enviornment...it was working fine..

    But its also depend on User workload and infrastructure...

     

  • Taher Ali Profile Picture
    on at

    Hi Hardik,

    Can you please give a short description of your environment? Is it mandatory to use terminal service or citrix? How many users can connect simultaneously in a VSAT environment? What is the recommened bandwidth and latency for MS Dynamics NAV?

    Do you have any idea for calculating response time?

  • Rex David de chavez Profile Picture
    135 on at

    Currently we are implementing NAV, we have tested it through wireless network and wireless VPN and it is working just fine. The recomended bandwitdh for for you to establsihed a good connection is atleast 256kbps dedicated but not necessarily leased line connection.

    Another way is using a Terminal Server (TS) which will need a lesser bandwitdh.

     This will all depend on the infrastructure that you have.

     Hope this information is of any help to you.

     

  • Daniel Rimmelzwaan Profile Picture
    3,485 on at

    Really? Working fine? posting a single transaction takes 30 minutes to 2 hours, and you feel that is working fine? I'm refering to your recent post here: https://community.dynamics.com/forums/p/14538/20613.aspx 

    Is that for just a few users entering a couple of orders, or is that with full system load testing? Wait what happens when someone decides to take their wireless laptop into the parking lot to post some invoices during his cigarette break, and they lock everyone else out. Wireless direct connections are not recommended for a reason.

  • Rex David de chavez Profile Picture
    135 on at

    i would like to comment on that sir daniel,

     

    1.) if someone decides to take their wireless laptop into the parking lot to post their invoices during his cigarette break.

    - our wireless network is confined with in the work area. how about free to air internet? if they will be using free to air internet or any internet out side network they need to connect to our network via VPN which our infrastrucutre determines the bandwidth of the untrusted user and denied access if the minimum bandwitdh set is not met.

     so your theory of posting transaction outside network could cause locking is not possible.

    2.) We tried 12 users connecting simultaneously over VPN and wireless meeting the prescribed bandwidth. This doesnt gives us any problem where 4 of the user are connected using TS. so i still can say that wireless and VPN connection is a no problem and working just fine.

    3.) We have 36 users simultanesously using the system that if several users tried to post a transaction, thats where we encouter the problem of prolonged posting that takes about 30mins to 2hours. BUT if a single user is the only one using the system we dont see any problem, all posting of transaction is fast.

     Sir daniel, from my explanations i dont see any reason that you wont get my delima here and wont understand where i am coming from.

     Thank you for commenting, just trying to help out and hoping in return someone else would help me.

     PEACE...

  • Daniel Rimmelzwaan Profile Picture
    3,485 on at

    Alright Sir Chavez, let me tell you a story. I was involved with a customer with major performance problems. We spent the better part of about a month tweaking hardware, tuning keys, running routines, upgrading hardware, putting in more RAM, installing more disks, everything we could think of. The problem would not go away.

    Turns out this ONE guy, using the broadband wireless connection, inside the building, but on the other side of the warehouse, was running sales reports during the day. He wasn't even posting anything, but he was blocking all 25 customer service reps. We plugged him into the wall and the problem went away. All the other improvements added to the increase in performance, but this is just to show that one single connection can cause a problem. Having 36 people on wireless direct connection is one of the biggest red flags I've seen so far. You don't have to take my word for it Sir Chavez, ask around. 

    You can call it theory all you want, and dismiss my suggestion. There is a HUGE difference though between a controlled wireless test with 12 people or even 36 people running some scripted or even random tasks, and everyone connecting and working full force. There's likely much more to it than just plugging people in of course, I am by no means suggesting that the whole problem goes away simply by plugging people, Sir Chavez. Connecting to NAV directly over wireless is simply not the right way to connect, not with one person, and certainly not with 36. The very least you should be doing is put in a TS/Citrix connection.

    I bid you good luck Sir Chavezz, you're going to need it if you're not open to advice.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans