DNS stands for Domain Name System, which is a network service that translates hostnames to IP addresses. Hostnames are human-readable names that identify devices or services on the Internet, such as www.google.com or mail.yahoo.com. IP addresses are numerical identifiers that specify the location of devices or services on the Internet, such as 172.217.14.206 or
98.137.11.163. DNS allows users to access websites or services by using hostnames instead of IP addresses, which are easier to remember and type. DNS also allows hostnames to change their IP addresses without affecting the users, which can improve performance and security.

Looking at the network configurations and outputs from both PCs and servers, here are the possible issues and solutions:
1. PC 1
* Issue: The IP address for PC1 is 192.168.1.1, which conflicts with Server 1 (which also uses
192.168.1.1).
* Solution: Change the IP address on PC1 to a unique one within the range, like 192.168.1.3.
2. PC 2
* Issue: PC 2 is configured with 192.168.1.2, which conflicts with Server 2 that has the same IP address.
* Solution: Update the IP address on PC 2 to something unique, like 192.168.1.4.
3. Server 1
* Issue: The IP address for Server 1 is 192.168.1.1, which conflicts with PC1.
* Solution: Since Server 1 and PC1 are using the same IP address, change one of them. For Server 1, you could change the IP address to 192.168.1.5.
4. Server 2
* Issue: Server 2 is using the IP address 192.168.1.2, which conflicts with PC2.
* Solution: Update Server 2 to use a different IP address, such as 192.168.1.6.
General Remediation:
The primary problem here is overlapping IP addresses, leading to connectivity issues. Each device on the network must have a unique IP address. After making these changes, ensure that all devices can communicate properly by testing the connection between devices and verifying they can access shared resources.

See the answer below in explanation part.
Explanation:
Answer of both steps below.
A picture containing text, screenshot, indoor Description automatically generated

Diagram Description automatically generated with medium confidence

If an application was previously running in a virtualized environment and is not launching after being installed directly on the base operating system, it's possible that the technician did not account for dependencies or configurations specific to the virtualized environment that are not present or are incompatible with the base operating system. This mismatch can prevent the application from launching properly.