New
#31
Tell you what. Looks like you ain't interested in dealing with this. It's been over an hour since your last response. You could look over the diags I suggested and go to a good machine and report back. I gotta go though
regards
These are the logs from when I pinged my nic after the connection was lost.
- C:\Users\Jared>ping -n 100 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Request timed out.
Reply from 192.168.1.105: Destination host unreachable.
Request timed out.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 192.168.1.105: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 192.168.1.105: Destination host unreachable.
Request timed out.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Request timed out.
Reply from 192.168.1.105: Destination host unreachable.
Request timed out.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.105: Destination host unreachable.
Request timed out.
Reply from 192.168.1.105: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 192.168.1.105: Destination host unreachable.
Request timed out.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Request timed out.
Reply from 192.168.1.105: Destination host unreachable.
Request timed out.
Reply from 192.168.1.105: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 192.168.1.105: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 192.168.1.105: Destination host unreachable.
Request timed out.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Reply from 192.168.1.105: Destination host unreachable.
Ping statistics for 192.168.1.1:
Packets: Sent = 100, Received = 66, Lost = 34 (34% loss),
C:\Users\Jared>ping 192.168.1.105
Pinging 192.168.1.105 with 32 bytes of data:
Reply from 192.168.1.105: bytes=32 time 1ms TTL=128
Reply from 192.168.1.105: bytes=32 time 1ms TTL=128
Reply from 192.168.1.105: bytes=32 time 1ms TTL=128
Reply from 192.168.1.105: bytes=32 time 1ms TTL=128
Ping statistics for 192.168.1.105:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Users\Jared>
Later today, I'll see if the problem occurs when I use a different but unsecure network
If .105 is your nic, then you are not able to ping your own ip address..You can have multiple IP addresses on your computer.. they just have to be on different subnets. i.e. you wireless is 192.168.1.05 and your ethernet is 192.168.2.105
right click on your network icon then left click on network properties and sharing and tell me what you see..I'll be back in an hour and we'll walk through this. this should be easy
The full map is jared's PC to chastoy to the internet. When the connection stops, I can't confirm what happens because network and sharing center no longer operates after my computer enters limited access mode. However, I'm assuming the break is between my PC and chastoy, even though the computer still says it's connected to chastoy;because of the fact my other devices still work on that router.
So is chastoy the name of the router?
And yesterday, I didnt get an answer about how far away is the router from your PC?
Your last ping doesnt make sense. How can you ping your router but it says its coming from 1.105
Your PC is obtaining an IP address from the router, correct?
12 feet should be OK, How's the signal strength on your task bar?
Right click on your network icon, left click on "open network and sharing center". In the top left left click on change adapter settings properties. right click on your wireless network connection. left click on properties. left click on internet protocol ver 4 TCP/IP protocol. Check and make sure obtain address automatically is filled. ON the dns you can either put in a manual one like google's 8.8.8.8 or either obtain automatically
Also, go into manage wireless and chose your chastoy router. Go into properties and make sure it sez connect to this machine when in range or automatically or words to that effect
It is my bed time, but before I go;
windows - Pinging a machine on my local network gets an 'unreachable' response from my own IP address? - Super User
This question is now the top google result when searching for 'destination host unreachable from my own ip address'. If that's how you got here, then you should know that my problem was a silly one probably caused by temperamental hardware, so don't bother reading through the walls of text below. The sole piece of information that's probably useful to you comes from Harry Johnston's comment below:
Getting a "destination unreachable" message from your own machine is normal behaviour in recent Windows versions. It just means that the arp failed, i.e., the IP address couldn't be located on the LANTo confirm this, try running arp -a on your machine, and you'll see a list of all the IP addresses that could be found on your LAN. If you don't see the IP address that you're trying to ping, then that explains why your pings are returning 'unreachable' from your own machine. As for how to fix that problem, it could be caused by anything. Try resetting your router, resetting your network adapters, fiddling with static/dynamic IP addresses etc etc.