Ipconfig / Flushdns , successful but not helpful

jskfan
jskfan used Ask the Experts™
on
Ipconfig / Flushdns , successful but not helpful

I have windows7 computer [not joined to he domain] that has changed the IP address.
 from my computer if I ping Windows7 computer it will still try to reach the old IP Address
C:\Users\Administrator.TEST>ping windows7

Pinging windows7.Test.local [192.168.254.166] with 32 bytes of data:
Reply from 192.168.254.129: Destination host unreachable.
Reply from 192.168.254.129: Destination host unreachable.
Reply from 192.168.254.129: Destination host unreachable.
Reply from 192.168.254.129: Destination host unreachable.

Open in new window


However if I ping by the new IP and with -a  switch it will ping successfully.
C:\Users\Administrator.TEST>ping -a 192.168.254.167

Pinging Windows7 [192.168.254.167] with 32 bytes of data:
Reply from 192.168.254.167: bytes=32 time<1ms TTL=128
Reply from 192.168.254.167: bytes=32 time=1ms TTL=128
Reply from 192.168.254.167: bytes=32 time<1ms TTL=128
Reply from 192.168.254.167: bytes=32 time<1ms TTL=128

Open in new window



I have restarted DNS client service on my computer, I have run Ipconfig/Flushdns , but still did not resolve the issue. ...
I do not have anything configured on my host file


Any help?

Thank you
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Dr. KlahnPrincipal Software Engineer

Commented:
Find out what the primary and secondary DNS servers on that network connection are.  The system may be falling back to a secondary DNS server (e.g., firewall or router).

Go to command level, issue "nslookup (whatever)" and see what nslookup says it is using for the DNS server.

nslookup
If this fails to clear things up and you are not using Microsoft Networking, consider disabling it for testing purposes so that the system does not look there for IP address information.
Qlemo"Batchelor", Developer and EE Topic Advisor
Top Expert 2015

Commented:
The wrong IP is coming from DNS (visible as the ping displays the full DNS name). The ping -a is using broadcasts / WINS = NetBIOS, and is correct.
Checking for the correct DNS server as stated above is one thing to do. If you are sure both (!) clents use the same DNS server. and it is your own internal DNS server allowing updates, force an update by runnign ipconfig /registerdns on Windows7.
MASEE Solution Guide - Technical Dept Head
Most Valuable Expert 2017

Commented:
Type nslookup and find out what DNS servers in use..
Please open DNS lookup zones make sure Windows7 A record created and PTR record for 192.168.254.167
If not registered try to run ipconfig /registerdns from windows7 PC.
Distinguished Expert 2017

Commented:
A system that is not joined to the domain usually would not have rights to update the DNS record, registerdns.
Thus would mean the host registration was handled by the DHCP server when the ip was allocated.
The ipconfig /flushdns clears the local cached data on the system where the command ran.

Ipconfig /all on the system in question to determine whether the ip it now has is statically ir dynamically assigned.

Updating the DNS record on the server is fastest way to correct.

Author

Commented:
RIght..I check DNS server... Forward lookup zone still has the record for windows 7 ping to old IP address.
Though I run ipconfig /registerdns   on wondows 7

Author

Commented:
C:\Windows\system32> ipconfig /registerdns

Windows IP Configuration

Registration of the DNS resource records for all adapters of this computer has b
een initiated. Any errors will be reported in the Event Viewer in 15 minutes.

Author

Commented:
Reverse lookup zone has 2 old IP addresses point to Windows 7
.165
and
.166

the current one and the correct one is .167 as shown below
I am not sure even where this reply is coming from :

C:\Users\Administrator.TEST>ping -a 192.168.254.167

Pinging WINDOWS7 [192.168.254.167] with 32 bytes of data:
Reply from 192.168.254.167: bytes=32 time<1ms TTL=128
Reply from 192.168.254.167: bytes=32 time<1ms TTL=128
Reply from 192.168.254.167: bytes=32 time<1ms TTL=128
Reply from 192.168.254.167: bytes=32 time=1ms TTL=128

Open in new window

Author

Commented:
if I run the nslookup for IP it does not it resolve it but if I ping with -a  it replies...not sure why

C:\Users\Administrator.TEST>nslookup 19.168.254.167
Server:  dc1.test.local
Address:  192.168.254.128

*** dc1.test.local can't find 19.168.254.167: Non-existent domain

Open in new window


C:\Users\Administrator.TEST>ping -a 192.168.254.167

Pinging WINDOWS7 [192.168.254.167] with 32 bytes of data:
Reply from 192.168.254.167: bytes=32 time<1ms TTL=128
Reply from 192.168.254.167: bytes=32 time<1ms TTL=128
Reply from 192.168.254.167: bytes=32 time=1ms TTL=128
Reply from 192.168.254.167: bytes=32 time=1ms TTL=128

Open in new window


C:\Users\Administrator.TEST>ping -a 192.168.254.167

Pinging WINDOWS7 [192.168.254.167] with 32 bytes of data:
Reply from 192.168.254.167: bytes=32 time<1ms TTL=128
Reply from 192.168.254.167: bytes=32 time<1ms TTL=128
Reply from 192.168.254.167: bytes=32 time=1ms TTL=128
Reply from 192.168.254.167: bytes=32 time=1ms TTL=128

Open in new window

Distinguished Expert 2017
Commented:
The ipconfig /registerdns sends the update reord updates.
The DNS server says, thanks, but you are not authorized to make these requests and discards them.

Much depends on your setup. Commonly, the DHCP server that registers records commonly deletes them when the lease expires.
DNS scavenging process also us used to maintain DNS records.

Based on your description, it is possible that the record in question was likely manually added or you do not have DNS scavenging setup that deals with clearing DNS zones of "temporary" records such as those registered by DHCP server or local systems.
When a person adds a host record, it is permanent and DNS scavenging does not delete it.


Potentially, that ip was either reserved/statically set and was so configured on the server. Since, it may have changed......

Beyond speculating ......
Only way to fix, delete the record on the DNS server.

Author

Commented:
Probably because WIndows7 is in Work Group and the DNS server is on the Domain Controller.

So From Windows7 cannot register DNS in the domain Controller

I know i can just manually updates on the DNS server....  but if I add many windows 7 computers as work group then it will be manual process.
Qlemo"Batchelor", Developer and EE Topic Advisor
Top Expert 2015

Commented:
Is the IP address static? Then you have no choice then to manually edit DNS. If DHCP is used, then the DHCP server needs to be allowed and enabled to update DNS (check DHCP server options).
kevinhsiehNetwork Engineer

Commented:
Is you have a domain, why are there devices in workgroup and not part of the domain?

I suggest you join devices to domain

or make them static

or configure DHCP to register them

or allow insecure DNS updates (not recommended)
Distinguished Expert 2017

Commented:
Not sure I understand your setup. DNS server can be modified to accept unsecure requests meaning anything on the L?aN can make requests.
Why is this or other computers not members of the domain?
Me,bears of the domain are subject and are centrally managed.

Author

Commented:
it is a LAB

or allow insecure DNS updates (not recommended)

how to do this ?
Distinguished Expert 2017

Commented:
A lab can also have a DC .on a separate network/segment

Check DNS server, zone properties here you can set what kind of updates are acceptable.
Mike SunSenior Systems Engineer (IBM - retired)

Commented:
Might be worth checking the hosts file in C:\Windows\System32\drivers\etc just in case there is an overriding manual entry in there.

Author

Commented:
Thank you

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial