Skip to main content

NAV 2013 Web Client Access on Local Area Network From Different Machine.

Hi all,

Today's discussion is on Using Navision 2013 Web client on Local Area Network.

I found out that many of us facing issues while trying to access web client from another machine.

First we need to check that is web client is working on the machine where we have deployed/installed it.



As shown below i have tested on my machine localhost. So it confirms that everything is correctly configured.


Now when i try to run this web client from a another machine, i normally end up with multiple error message.

Let's try to resolve them.

Cause of Error -
The Error Occurs because of Windows Firewall (Main Cause, It may not be true for all the cases but for most of the cases).

ERROR - Why ?
When we are trying to access the URL that is hosted on a different machine, the incoming connection to that URL (Port) should be allowed.

How to Allow Incoming Connection ?

1. Open Control Panel.

2. Open Windows Firewall.

3. From Left Hand Panel, select Advanced settings.


4. From Windows Firewall with Advanced Security Window, Select Inbound Rules from Left Panel and Select New Role from Right Panel.

5. A new Inbound Rule Wizard window will open as shown.

6. Select Type of Rule as Port.


7. Now you need to specify the port on which web client is hosted, by default it is hosted on port 82.


8. Click Next, From Next window select Allow the connection.


9. Click Next, From Next Window Select Domain (as you only want to provide access to Local Area Network).


10. Click Next, Provide a Name and Description for the Rule.


11. The New Inbound Rule is created and will be display as shown below.


12. Now try to access the URL from different machine.

13. If the Windows Login exist is the database, you will be able to see the Microsoft Dynamics NAV Web Client.


I hope this resolve issues related to access of Web client on Local Area Network.

Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.