DNS problems

Many remote desktop connectivity problems can be traced to DNS issues. If an admin changed a host's IP address, then clients might not be able to connect to the host until the client's DNS resolver cache expires. To expire a DNS resolver cache, follow these steps:

1. Open an elevated Command Prompt window by entering the CMD command at the Windows Run prompt.
2. Enter the IPConfig /FlushDNS command.

?

Clients may also have trouble connecting to a host if they use an external DNS server that is unable to resolve hosts on the organization's private network. The fix for this problem is to modify the client's IP address settings so it uses one of the organization's DNS servers rather than an external DNS.

As an alternative, you may be able to connect to a remote system by specifying its IP address rather than a host name. To determine whether an endpoint is connected to the correct DNS server, complete the following steps:

1. Open a Command Prompt window by entering the CMD command at the Windows Run prompt
2. Enter the IPConfig /all command
3. Verify that the correct DNS server is being used with the Preferred network adapter. If the DNS server listed is incorrect, then you can manually specify a different DNS server in the PC's IP address properties or configure the PC to use a DHCP server