I'm suddenly unable to access the Internet on my PC?
I'm suddenly unable to access the Internet on my PC?
All DNS ping attempts were unsuccessful. I talked to support at my ISP this evening. They plan to lend me a router to check if the problem is with the device itself. I’m not sure why it’s happening, since it only affects my computer. But I’m not an expert in networking, so I don’t know what to do.
Ping the default gateway. If it doesn't respond, the address might be incorrect or the modem/router is offline.
Another inquiry: Have you ever interacted with DHCP on and off? If yes, please describe how.
= = = =
And following the ping recommendations mentioned earlier, it would also be useful to test the default gateway (192.168.0.1) through other network devices if possible.
= = = =
Out of curiosity, I tested both IP addresses 209.18.47.61 and 209.18.47.62. The outcomes were identical: "Request timed out."
I don’t understand why the Motorola technician would recommend those specific IPs. Generally, I expect technical support to suggest well-known DNS servers that are likely operational.
For example, Google’s addresses 8.8.8.8 and 8.8.4.4 responded successfully. [See below].
Ping results from my computer using Windows PowerShell.
Copyright © Microsoft Corporation. All rights reserved.
Upgrade to the latest PowerShell for new features and improvements!
https://aka.ms/PSWindows
Running ping 209.18.47.62 in PowerShell:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping stats for 209.18.47.62:
Packets sent = 4, received = 0, lost = 4 (100% loss),
PS C:\WINDOWS\system32> ping 209.18.47.61
Results identical to previous test.
Pinging 209.18.47.61 from my machine:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Statistics for 209.18.47.61:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
PS C:\WINDOWS\system32> ping 8.8.8.8
Testing 8.8.8.8 via PowerShell:
Reply from 8.8.8.8: bytes=32 time=18ms TTL=114
Reply from 8.8.8.8: bytes=32 time=18ms TTL=114
Reply from 8.8.8.8: bytes=32 time=17ms TTL=114
Reply from 8.8.8.8: bytes=32 time=16ms TTL=114
Ping stats for 8.8.8.8:
Packets sent = 4, received = 4, lost = 0 (no loss),
Approximate round trip times: Minimum 16ms, Maximum 18ms, Average 17ms
PS C:\WINDOWS\system32> Ping 8.8.4.4
Testing 8.8.4.4 with 32 bytes:
Reply from 8.8.4.4: bytes=32 time=18ms TTL=114
Reply from 8.8.4.4: bytes=32 time=18ms TTL=114
Reply from 8.8.4.4: bytes=32 time=19ms TTL=114
Reply from 8.8.4.4: bytes=32 time=20ms TTL=114
Ping stats for 8.8.4.4:
Packets sent = 4, received = 4, lost = 0 (no loss),
Approximate round trip times: Minimum 18ms, Maximum 20ms, Average 18ms
When you access a network adapter’s Details and double click on IPv4, you can select either automatic IP assignment or manual static address. That’s the toggle.
The system is responding to the IP addresses provided, confirming they point to Charter's DNS servers rather than MIT. Everything appears normal, so there should be no online issues. You can try alternative queries or use different tools to verify connectivity.