When you work in a local area network, especially in domain environments, and when you try to access the objects and/or resources that the remote computers in the same subnet have, it is the DNS server that helps resolving the names of the target computers. Because of this you can easily locate the remote computers and the resources that they contain.
If configured correctly, the entire network runs smoothly and flawlessly. However the latency in accessing the resources on remote computers in a local area network might be because of the incorrect DNS configuration that the computers may have either by the DHCP server or manually.
The key point in the entire problem resolution process is that the IP address of the local DNS server (the DNS server that resides within the local area network and has been configured and managed by the system administrator) must be set as the primary DNS server, and the IP address of the DNS server of the ISP must be set as the alternate DNS server on the client computers.
Once the above configurations are done, and a computer initiates communication with any other computer in the network, the DNS query is first sent to the local DNS server for name resolution. Since the destination computer resides within the local area network, the local DNS server instantaneously resolves the name and the two computers in a LAN start communicating with each other. In case the destination computer does not reside within the local area network (and is present somewhere else), the local DNS server fails to resolve the DNS query, and the query is then forwarded to the alternate DNS server (which is the DNS server of the ISP) for the resolution.
How to Resolve the Latency Issue in the Local Area Network?
Note: This section explains how you can configure the client computers manually to rectify the latency issue that your organization might be facing due to improper DNS address assignment. The following steps are to be performed individually on each participating computer in the local area network. However if the IP addresses are being automatically assigned by the DHCP server, your systems administrator must change the DHCP server settings which requires a completely different set of steps to be performed on the DHCP server.
- Log on to the Windows using administrator’s username and password.
- Press Windows + R keys simultaneously to initiate the Run command box.
- In the available field in the Run command box, type NCPA.CPL command and hit Enter key.
- The opened Network Connections window, right-click the corresponding network interface card (NIC).
- From the displayed context menu, click Properties.
- On the NIC properties box, from the displayed list, double-click the Internet Protocol Version 4 (TCP/IPv4) entry.
- On the opened Internet Protocol Version 4 (TCP/IPv4) Properties box, provide the IP address for the local DNS server in the Preferred DNS server field.
- Also, provide the IP address for the DNS server of the ISP in the Alternate DNS server field.
- Once done, click OK on the opened boxes and windows to save the configurations that you have made.
Related resources
- Issue while accessing to local server from another network via Wireless router Forum
- Unidentified Network (No Internet Access) on Local Area Connection Forum
- SolvedI have a problem configuring a local area network using a switch with windows 8 Pc’s Forum
- SolvedMy laptops' wireless network will not show up when i go to network connections , only the local area connection shows up . Usu Forum
- How to change local area connection network number? Forum