asked on Ipconfig / Flushdns , successful but not helpful
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
However if I ping by the new IP and with -a switch it will ping successfully.
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
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.
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
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
Windows OSDNS
Last Comment
jskfan
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.
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.
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.
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.
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.
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.
ASKER
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
Though I run ipconfig /registerdns on wondows 7
ASKER
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.
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.
ASKER
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 :
.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
ASKER
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
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
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
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
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.
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.
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).
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)
I suggest you join devices to domain
or make them static
or configure DHCP to register them
or allow insecure DNS updates (not recommended)
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.
Why is this or other computers not members of the domain?
Me,bears of the domain are subject and are centrally managed.
ASKER
it is a LAB
how to do this ?
or allow insecure DNS updates (not recommended)
how to do this ?
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.
Check DNS server, zone properties here you can set what kind of updates are acceptable.
Might be worth checking the hosts file in C:\Windows\System32\driver
ASKER
Thank you
Go to command level, issue "nslookup (whatever)" and see what nslookup says it is using for the DNS server.
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.