A TP-Link modem used to give me access to what ipconfig in CMD says is its default gateway : 192.168.1.1 After years of use it would no longer accept credentials of admin/admin. Now it will no longer give access to 192.168.1.1 - it times out - and does that in 7 different browsers.
My ISP examined the issue and recommended a new modem. That new modem (D-Link) would not accept those credentials either; and also no longer allows access to 192.168.1.1 The ISP then recommended a second new modem - same model D-Link. It would not even let me reach 192.168.1.1
My internet is quite good most of the time, so that is not an issue. There are rare times when the internet is missing - and THEN I look around at what I can tweak to get it back, but I have no access to 192.168.1.1 The problem is the same on my laptop - connected through WiFi.
My ethernet-connected desktop is an upgrade of Win7 Ultimate 32bit to Win10 v1511; my laptop is a fresh install of Win10 v1607 - also 32bit
That can take a few minutes to complete, come back and past the result in a message here.
If you are on a machine with no network connection, use a floppy, USB disk, or a CD-RW disk to transfer a text file with the information to allow pasting it here.
I pasted Old Rick's entire code into the 'DOS" window - don't know how long I have to wait - the title of the window changed, but IN the window, nothing.
ECHO is on.
Pinging 192.168.1.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Pinging 216.58.199.174 with 32 bytes of data:
Reply from 216.58.199.174: bytes=32 time=380ms TTL=54
Reply from 216.58.199.174: bytes=32 time=408ms TTL=54
Reply from 216.58.199.174: bytes=32 time=269ms TTL=54
Reply from 216.58.199.174: bytes=32 time=296ms TTL=54
Ping statistics for 216.58.199.174:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 269ms, Maximum = 408ms, Average = 338ms
Pinging google.com [74.125.206.100] with 32 bytes of data:
Reply from 74.125.206.100: bytes=32 time=310ms TTL=43
Reply from 74.125.206.100: bytes=32 time=321ms TTL=43
Reply from 74.125.206.100: bytes=32 time=338ms TTL=43
Reply from 74.125.206.100: bytes=32 time=331ms TTL=43
Ping statistics for 74.125.206.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 310ms, Maximum = 338ms, Average = 325ms
Tracing route to google.com [74.125.206.100]
over a maximum of 30 hops:
1 <1 ms <1 ms 1 ms 192.168.1.1
2 13 ms 12 ms 12 ms 203-23-237-1-cpe.spintel.net.au [203.23.237.1]
3 96 ms 80 ms 12 ms vl104.core01.syd.spintel.net.au [203.23.236.53]
4 95 ms 85 ms 82 ms 72.14.211.170
5 37 ms 26 ms 13 ms 209.85.242.124
6 222 ms 151 ms 149 ms 72.14.238.186
7 175 ms 255 ms 233 ms 216.239.49.15
8 188 ms 187 ms 232 ms 209.85.251.138
9 271 ms 196 ms 195 ms 72.14.232.71
10 210 ms 269 ms 330 ms 108.170.236.240
11 380 ms 287 ms 287 ms 209.85.249.61
12 292 ms 319 ms 290 ms 216.239.51.110
13 291 ms 291 ms 383 ms 209.85.242.165
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 937 ms * 1157 ms wk-in-f100.1e100.net [74.125.206.100]
Yes, internet access is mostly excellent. No, I have not tried a different ethernet cable. All 4 ethertnet ports are connected some or other device. I COULD try another port. But I don't think I will bother, because even the wifi connected laptop fails to access the default gateway, so it is not an ethernet issue. Moreover, the same with the other two brand new modems which connected by their new cables.
Being open to hacking the router may have been set to not respond to ping.
Older and even some newer routers have vulnerabilities that make them accessible from the outside.
I would hit the reset button on the router as you power it up to set it back to defaults. Then try your access again. Sometimes it takes a couple of resets for it to take.
There doesn't appear to be anything wrong with your pc since tracert showed the router and it uses icmp just like ping does. Appears the router has been configured to not respond to ping
'I would hit the reset button on the router as you power it up to set it back to defaults.' that was done several times during the sessions with the ISP consultants.
' Appears the router has been configured to not respond to ping' : ' Appears the router has been configured to NO LONGER respond to ping, because previously it did.
Hi, go to start search and type:- cmd right click on the returned cmd.exe and select "run as administrator" at the prompt copy paste:- (cmd's for you are highlighted in red)
netsh int ip reset (press enter)
Next, still at cmd prompt:-
netsh winsock reset (press enter)
Restart computer. Open a cmd prompt again as admin and at the prompt type:-
Ping 192.168.1.1 > 0 & notepad 0 (press enter)
If this fails still at command prompt copy paste:-
That's exactly the point SEBASTIAN42, the configuration changed. Now that can be due to age/failed component/impending failure or its been changed from the outside.
You say you did the reset. I take it there was no change
"Now that can be due to age/failed component/impending failure or its been changed from the outside." The two brand new modems can likewise not access Default Gateway. For over a year, when I turn on my Android tablet, it warns about the modem being insecure.
"You say you did the reset. I take it there was no change" It did not fix the problem.
"try to access the router(192.168.1.1) using IE." - Same result with 7 different browsers.
The connection still times out when attempting to access 192.168.1.1
*****************************************************************
ECHO is on.
===========================================================================
Interface List
4...00 25 22 f5 39 b0 ......NVIDIA nForce Networking Controller
1...........................Software Loopback Interface 1
6...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
===========================================================================
SEBASTIAN42 just quoting and agreeing with the aforementioned conclusion really isn't helping you.
What antivirus are you using? what firewall software?
if you are proposing that three modem/router combo units all exhibit the same behavior [we can only go upon your unbiased observations] of no access then the conclusion has to be something with your pc.
Hi, well you have internet and the route table identify's 192.168.1.1. I asked you to use IE as it is more likely to not give security problems. GentleArrow is correct we would normally suggest a power cycle of router and computer and if this fails a reset, you say both have been tried, it would help to look at your AV and firewall, although it is not blocking access as you have internet, very odd, at this stage i suggest you open a cmd prompt (as admin) and type :-
netsh interface ip delete arpcache (press enter). Try now, let us know how you get on.
In regards to the AV have you at any time had another AV program (maybe a trial) of an AV installed? Same goes for firewall.
'netsh interface ip delete arpcache (press enter)' resulted in 'OK'
192.168.1.1 prompted : 'Problem loading page' 'The connection has timed out' 'The server at 192.168.1.1 is taking too long to respond.'
"Can you access the router from another computer? "
I had written that a laptop with Win10 v1607 can get WiFi to from the same modem/router
Would there be sense in trying any of these tests on one (or both) of the brand new modems ? involving a different PC - two different desktops have Win10 v1607, and Win8.1 or I can run Win7 Ultimate in THIS PC - all done with some, but manageable, effort.
Hi, I meant on another computer, typing 192.168.1.1 into the browsers address bar, does it access the router? Well if you cannot access the router how are you going to use the new one's?
I mounted the new modem and connected it to a PC different from this one; All went well.
Then I connected it to just THIS PC, and NO internet was available. I didn't bother typing the Default Gateway, because unless I have internet, the rest is immaterial.
So now this PC is again connected to the old modem - I have internet, but no access to Default Gateway.
On the other PC I could access the Default Gateway of the new modem, but not internet. Reconnecting to the old modem restored internet to that other PC.
When I wrote 'all went well' - I was referring to accessing the Default Gateway and getting the admin credentials accepted. It did not occur to me at the time to ALSO test for internet, as that had not been an issue. But when I did it was lacking.
A forum community dedicated to tech experts and enthusiasts. Come join the discussion about articles, computer security, Mac, Microsoft, Linux, hardware, networking, gaming, reviews, accessories, and more!