marshallcaleb26 Posted November 10, 2017 Posted November 10, 2017 Cant connect to interface. Always says "192.168.88.1 took too long to respond"
Netduma Staff Netduma Jack Posted November 10, 2017 Netduma Staff Posted November 10, 2017 Cant connect to interface. Always says "192.168.88.1 took too long to respond" Hi, welcome to the forum! Try unplugging both your Modem and the Netduma. Wait for a minute before plugging in the Modem again, wait for a minute and then plug the Netduma. This should allow the Modem and the Netduma to properly communicate and allow access to the Interface. If this doesn't work, can you access the Netduma interface when you unplug the Modem, plug the Netduma into a PC and use 192.168.88.1 or http://r1?If you can, access the Netduma Miscellaneous settings and click on 'Factory Reset'.
marshallcaleb26 Posted November 10, 2017 Author Posted November 10, 2017 I did everything as instructed. Still says both sites take too long to respond or DNS server could not be found
Administrators Netduma Fraser Posted November 11, 2017 Administrators Posted November 11, 2017 Hey, welcome to the forum! Please follow this guide to see if you're able to access the interface: http://support.netduma.com/support/solutions/articles/16000022375-i-unticked-preserve-settings-when-upgrading-can-t-access-my-router-help
marshallcaleb26 Posted November 12, 2017 Author Posted November 12, 2017 Ive had 3 people tell me to do the same thing. THIS DOESNT WORK. This is very frustrating. Anytime that i try to connect to 192.168.1.1 or 88.1 it says, took too long to respond. It will not connect to this interface
Administrators Netduma Fraser Posted November 12, 2017 Administrators Posted November 12, 2017 Connect directly via ethernet. Open up a command prompt and enter 'ipconfig'. Screenshot the results and post here please.
marshallcaleb26 Posted November 13, 2017 Author Posted November 13, 2017 Microsoft Windows [Version 10.0.15063] © 2017 Microsoft Corporation. All rights reserved. C:\Users\Josh>ipconfig Windows IP Configuration Ethernet adapter Ethernet: Connection-specific DNS Suffix . : neo.rr.com IPv6 Address. . . . . . . . . . . : 2607:fcc8:654f:4600::2 IPv6 Address. . . . . . . . . . . : 2607:fcc8:654f:4600:f5a4:1917:a2c3:69f1 Temporary IPv6 Address. . . . . . : 2607:fcc8:654f:4600:2535:2111:9f2c:301c Temporary IPv6 Address. . . . . . : 2607:fcc8:654f:4600:5856:8b2c:83ff:4af2 Temporary IPv6 Address. . . . . . : 2607:fcc8:654f:4600:f9b9:196b:e7be:8c91 Link-local IPv6 Address . . . . . : fe80::f5a4:1917:a2c3:69f1%9 IPv4 Address. . . . . . . . . . . : 192.168.0.2 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : fe80::da0f:99ff:fefa:7f96%9 192.168.0.1 Ethernet adapter Bluetooth Network Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 13: Connection-specific DNS Suffix . : IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fb:2470:3b3e:52a6:a364 Link-local IPv6 Address . . . . . : fe80::2470:3b3e:52a6:a364%5 Default Gateway . . . . . . . . . : C:\Users\Josh>
Administrators Netduma Fraser Posted November 13, 2017 Administrators Posted November 13, 2017 It doesn't look like you're connected to the R1 at all but instead directly connected to the hub itself. Can you confirm this? Setup should be: Hub port 1 R1 port 1 R1 port 2 PC
marshallcaleb26 Posted November 13, 2017 Author Posted November 13, 2017 Microsoft Windows [Version 10.0.15063] © 2017 Microsoft Corporation. All rights reserved. C:\Users\Josh>ipconfig Windows IP Configuration Ethernet adapter Ethernet: Connection-specific DNS Suffix . : lan IPv6 Address. . . . . . . . . . . : 2607:fcc8:654f:46f0::17c IPv6 Address. . . . . . . . . . . : 2607:fcc8:654f:46f0:f5a4:1917:a2c3:69f1 IPv6 Address. . . . . . . . . . . : fdea:6e70:50b8::17c IPv6 Address. . . . . . . . . . . : fdea:6e70:50b8:0:f5a4:1917:a2c3:69f1 Temporary IPv6 Address. . . . . . : 2607:fcc8:654f:46f0:fcfe:995d:8d71:9f5 Temporary IPv6 Address. . . . . . : fdea:6e70:50b8:0:fcfe:995d:8d71:9f5 Link-local IPv6 Address . . . . . : fe80::f5a4:1917:a2c3:69f1%9 IPv4 Address. . . . . . . . . . . : 192.168.88.154 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : fe80::e68d:8cff:fe46:5635%9 192.168.88.1 Ethernet adapter Bluetooth Network Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 13: Connection-specific DNS Suffix . : IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fb:4a2:2fc4:52a6:a364 Link-local IPv6 Address . . . . . : fe80::4a2:2fc4:52a6:a364%5 Default Gateway . . . . . . . . . : C:\Users\Josh>
Administrators Netduma Fraser Posted November 13, 2017 Administrators Posted November 13, 2017 That's much better, now try accessing the Netduma interface using 192.168.88.1 please
marshallcaleb26 Posted November 13, 2017 Author Posted November 13, 2017 says 192.168.88.1 took too long to respond
marshallcaleb26 Posted November 13, 2017 Author Posted November 13, 2017 wait....i did the R1 instead of the 192 address and it let me factory reset the netduma. now can you link the guide again for setup? my friend cant join my party on PS4 and he lives 4 miles form me
Administrators Netduma Fraser Posted November 13, 2017 Administrators Posted November 13, 2017 Great to hear you've got access again. Guide: http://support.netduma.com/support/solutions/articles/16000023979-optimal-settings-guide
Recommended Posts
Archived
This topic is now archived and is closed to further replies.