NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Nighthawk M1
Dear support:
I am using a Nighthawk MR1100 (firmware NTG9X50C_12.05.05.14) and am having an odd problem.
The mobile router will suddenly stop allowing the internet connection to devices. The router still shows an LTE connection, and phones' data still works on LTE connection (not through the router), but it does not work. The router shows that the 1 device is connected (connects to a Netgear router, which is not the issue as it works flawlessly with DSL and cable modems), and the devices show they are connected, but no internet.
I am hoping this is a setting which can be corrected! I found that if I turn off the mobile router, wait a few minutes and restart it, I 'may' get internet connection on my devices.
I found this thread that seems like my exact issue. The last reply from Mexoh1To7k asks if the user can connect to http://212.129.20.209/ when the internet isn't working, but that's as far as they got before giving up. I can confirm that I CANNOT reach this address when the internet isn't working but CAN when the internet works. No idea what that means, but since they asked I tested it.
I have tried factory reset, changing which bands it connects to and just about every other setting in the menu that seems potentially related.
Overview of settings:
WiFi off
DNS mode has been Auto, but I have also manually set it to OpenDNS. Both exhibit the issue
IP Passthrough is ON
DHCP is OFF
USB port is set to Charge + tether
Ethernet standby is disabled (since that's what my router is plugged into of course)
Client privacy is off
Cellular Data & Roaming Data on
Band region: LTE All
APN: broadband
If this cannot be solved quickly I'll be returning the device and switching back to DSL, which I would hate to do! It's much slower, but more reliable.
Any thoughts would be appreciated.
4 Replies
I think I know what is happening. It happened to me, and I figured it out with a little investigating.
Let the problem return (where the connection is not working). DO NOT REBOOT OR FIX IT. While the problem is still present, do the following tests:
1. Can you ping, still? (yes/no)
ping portquiz.net
2. Can you access portquiz.net on port 80? (yes/no)
3. Can you access portquiz.net on port 443? (yes/no)
4. Can you access portquiz.net on port 666? (yes/no)
5. Which VPN were you using that worked? ______________________
6. What port # do you connect to this VPN server on? _______
7. Are you on an AT&T Connect Car Plan or an AT&T Ipad plan? _______
This will help you figure things out. I suspect you will be able to ping and will be able to connect to 666, but you will not have connectivity to 80 or 443, and I suspect your VPN is not using 80 or 443.
Configure DNS server on your device manually, instead of MR1100, it (MR1100) will always assign itself to connected devices as DNS server regardless you are making it as AUTO or MANUAL when devices are getting IP address from MR1100. Sometimes it just stuck on MR1100 for DNS service and that is causing problem to prevent you going out as expected.
- DNS is not the problem.
He said he could not connect to a web server by its IP address: http://212.129.20.209/
DNS is used to look up IP addresses using its friendly name (such as www.google.com). But if you specify the IP address in the address bar, this bypasses DNS completely. There is no "friendly name" that needs to be converted to an IP address.
DNS is like a phone book. You can look up a person's NAME to find out their PHONE NUMBER. But if you already know the phone number, why do you need the phone book? Even if your phone book was damaged, you'd still be able to dial the phone number that you already knew.
icaruspony wrote:
DNS is not the problem.
He said he could not connect to a web server by its IP address: http://212.129.20.209/
DNS is used to look up IP addresses using its friendly name (such as www.google.com). But if you specify the IP address in the address bar, this bypasses DNS completely. There is no "friendly name" that needs to be converted to an IP address.
DNS is like a phone book. You can look up a person's NAME to find out their PHONE NUMBER. But if you already know the phone number, why do you need the phone book? Even if your phone book was damaged, you'd still be able to dial the phone number that you already knew.Yes, wan't noticed that, you are right about this.
