Skip to main content

Outdated entry in the DNS cache

I always experience this error during the remote desktop connection and the great reason behind this Outdated entry in the DNS cache is most often due to "The Remote Desktop Initiator, Does Not Restarted computer since so long". I am writing this to help you people with easy solution. Once you tried Remote Desktop which is obviously working for someone else but you are getting this error;
The connection cannot be completed because the remote computer that was reached is not the one you specified. This could be caused by an outdated entry in the DNS cache. Try using the IP address of the computer instead of the name.

Outdated entry in the DNS cache

This error also can be seen in below screenshot because I want to make it clear that you are facing this exactly the same issue, which I am talking about. Please have a review on below image;

Outdated DNS Cache Error

Before you proceed to solve the issue, I think being a good IT Professional or even the best end user, you must first make sure the "prerequisites" before struggling with solutions available over the internet. Please check these before solutions;
  1. If both Computers are on the same Network, Please make sure that Clock (Yes) is correct on both network nodes (client machine , the remote machine)
  2. The Remote Desktop Computer , Target Computer is Power UP and Running. If possible, please double check with someone else;
  3. Client Computer (the Remote Desktop Initiator) must make sure that his computer is recently updated with DNS Server.

Solutions:

  1. If you consider your self and IT Professional, you need to make sure that your DNS settings are pointing to Internal DNS Server.
  2. You need to flush DNS Cache on the client computer, where you are facing the issue. For this, you can use ipconfig /flushdns command in CMD with Administrator.
  3. Once you are able to flush DNS cache, just register the DNS Server again with ipconfig /registerdns in CMD with Administrator.
  4. Sometimes, deleting the object from DNS Server also helps but, its highly depends on the scenarios.
  5. If you face any kind of issue while using these commands, simply go for the master trick "Restart your Computer" and check the issue again.

ipconfig /registerdns The requested operation requires elevation.

Some of you, might face that when you try ipconfig /registerdns command is not working and you might be facing this error,
ipconfig /registerdns
The requested operation requires elevation.

To solve this issue, please Type CMD in Start Menu and before clicking it to open, just right click on command prompt and run as administrator. Then type again ipconfig /registerdns and this will work perfectly. You are expert Now !

This Blog Post is moved on my Website,  Outdated Entry in the DNS Cache Error

Comments

Popular posts from this blog

Setting up per connection Limit Bandwidth on MikroTik Router

Generally, I do not prefer to add any unwanted restriction on the network user until its required due to some Administration reason. I know, there are more ways to tackle this setting up per connection Limit Bandwidth on MikroTik Router question comes into one’s mind but I resolve my concern while using MikroTik PCQs feature in MikroTik Queue Type and then calling this Queue Type to Simple Queue. There are more options for setting up per connection Limit Bandwidth on MikroTik Router but please share your concern to add anything else in this article. Let’s start to add our configurations; I am using WinBox for this Article but you can use anything you are convenient to use. Let’s start Step by Step procedure for Setting up per connection Limit Bandwidth on MikroTik Router, any version.  Setup Queue Types After Successful Login, click on Queues menu. Navigate to Queue Types and Press Add + (Plus Sign) to add a new Queue Type. Type a Name like in my scenario,...

DsReplicaGetInfo failed with status 8453 0x2105 on Windows Server 2008

I have two Domain Controller in my envorinment, Primary Domain Controller is Windows Server 2003 based and Additional domain controller is Windows Server 2008 based. When I Installed New 2008 ADC and after some time, when I check with repadmin /showreps found the error.... DsReplicaGetInfo() failed with status 8453 (0x2105):Replication access was denied. I really worried about Solutions: [ DsReplicaGetInfo failed with status 8453 ]

Event ID: 14158 Source: Microsoft Forefront TMG Firewall - How to change intra-array address in TMG 2010

In my organization, we are privious using Microsoft ISA Server 2006 ENT for proxy and gateway purpose. There are two website published on ISA 2006 Server and I install Microsoft TMG 2010, this morning. When I was making installations and configurations of my New Microsoft TMG 2010 Firewall Server with 192.168.10.17 but when I replace server with my existing Microsoft ISA Server 2006 and change Internal IP to my privous gateway IP, Microsoft TMG 2010 start showing events with ID 14158  and Configurations Error with "Description : The IP address specified for communication between this Forefront TMG computer (192.168.10.17) and other array members is not bound to a network adapter installed on this computer. The IP address specified for intra-array communication must be bound to a network adapter installed on the computer." Event ID 14158 Solution - 1: (Easy One)  Management Console : Start > All Programs > Microsoft Forefront TMG > Micr...