- Thread Author
- #1
I use an ASUS RT-AX88U router for my home network which is set to always use a specific IP address (i.e., 192.168.1.111) for my primary computer which has always worked fine for years.
More than two months ago, the original ASUS motherboard in my 10+ year-old self-built PC, running Windows 10 Pro, finally died, forcing me to purchase a new high-end HP computer. When I set up the new computer, I first renamed it to my previous name and, as expected, it had no problem setting the IP address to the 192.168.1.111 specified by my router. Unfortunately, over the next month, I had continuos keyboard problems with five different sets of wired "and" wireless keyboard/mouse combinations that forced me to return the computer to HP. It was replaced by a new custom-built version of the exact same computer I just returned.
When setting up the second new computer, at some point during setup I renamed this computer once again to the one I've been using for years. At first, I thought everything was okay until I noticed that the IP address was NOT the 192.168.1.111 that my router was supposed to set it to. Instead it was set to 192.168.1.230 which is not what it was supposed to be.
I was not sure what happened but I figured that I would just have to reset it in the router. No such luck! When I tried to reset it, I was told that 192.168.1.111 already existed.
Sure enough! When I "ping" for it, here's what I get:
======================================================
PS C:\Users\XXXXX> ping 192.168.1.111
Pinging 192.168.1.111 with 32 bytes of data:
Reply from 192.168.1.230: Destination host unreachable.
Reply from 192.168.1.230: Destination host unreachable.
Reply from 192.168.1.230: Destination host unreachable.
Reply from 192.168.1.230: Destination host unreachable.
Ping statistics for 192.168.1.111:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
======================================================
Needless to say, if I ping the "supposed" actual address,
that works just fine:
======================================================
PS C:\Users\XXXXX> ping 192.168.1.230
Pinging 192.168.1.230 with 32 bytes of data:
Reply from 192.168.1.230: bytes=32 time<1ms TTL=128
Reply from 192.168.1.230: bytes=32 time<1ms TTL=128
Reply from 192.168.1.230: bytes=32 time<1ms TTL=128
Reply from 192.168.1.230: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.230:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
======================================================
I have wasted hours-and-hours trying to fix this without any success. How do I find what's causing this "ghost" IP address (i.e., 192,168.1.111) to exist and, more importantly, how do I get rid of it so that I can once again assign it to my newest PC?
Any help on resolving this issue would be GREATLY appreciated.
THANK YOU.
More than two months ago, the original ASUS motherboard in my 10+ year-old self-built PC, running Windows 10 Pro, finally died, forcing me to purchase a new high-end HP computer. When I set up the new computer, I first renamed it to my previous name and, as expected, it had no problem setting the IP address to the 192.168.1.111 specified by my router. Unfortunately, over the next month, I had continuos keyboard problems with five different sets of wired "and" wireless keyboard/mouse combinations that forced me to return the computer to HP. It was replaced by a new custom-built version of the exact same computer I just returned.
When setting up the second new computer, at some point during setup I renamed this computer once again to the one I've been using for years. At first, I thought everything was okay until I noticed that the IP address was NOT the 192.168.1.111 that my router was supposed to set it to. Instead it was set to 192.168.1.230 which is not what it was supposed to be.
I was not sure what happened but I figured that I would just have to reset it in the router. No such luck! When I tried to reset it, I was told that 192.168.1.111 already existed.
Sure enough! When I "ping" for it, here's what I get:
======================================================
PS C:\Users\XXXXX> ping 192.168.1.111
Pinging 192.168.1.111 with 32 bytes of data:
Reply from 192.168.1.230: Destination host unreachable.
Reply from 192.168.1.230: Destination host unreachable.
Reply from 192.168.1.230: Destination host unreachable.
Reply from 192.168.1.230: Destination host unreachable.
Ping statistics for 192.168.1.111:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
======================================================
Needless to say, if I ping the "supposed" actual address,
that works just fine:
======================================================
PS C:\Users\XXXXX> ping 192.168.1.230
Pinging 192.168.1.230 with 32 bytes of data:
Reply from 192.168.1.230: bytes=32 time<1ms TTL=128
Reply from 192.168.1.230: bytes=32 time<1ms TTL=128
Reply from 192.168.1.230: bytes=32 time<1ms TTL=128
Reply from 192.168.1.230: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.230:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
======================================================
I have wasted hours-and-hours trying to fix this without any success. How do I find what's causing this "ghost" IP address (i.e., 192,168.1.111) to exist and, more importantly, how do I get rid of it so that I can once again assign it to my newest PC?
Any help on resolving this issue would be GREATLY appreciated.
THANK YOU.