NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Nosiu
Jun 07, 2022Aspirant
Can't connect to router 2 - 3 days after every reboot. (NETGEAR R6250)
Hello.
I have a problem with my router. After every router reboot I can connect to it via lan/public for only 2 - 3 days. Then there is no response from it, every service - port forwarding,WiFi, DHCP and stuff are working fine.
I had changed a few firmware's but it does not help. What can be the problem? My PC/PHONES/NAS is free of adware or viruses - checked it.
Please help!
5 Replies
Nosiu wrote:
After every router reboot I can connect to it via lan/public for only 2 - 3 days.
What does "lan/public" mean? Connecting what and how?
What firmware version do you have on the device?
A number is more useful than "the latest". (It may not be by the time people read this.) There can also be newer versions, or "hot fixes", that do not show up if you check for new firmware in the browser interface.
It might also help if you told people what the modem is in front of this router, if there is one. The model number could be useful. Is it, by any chance, also a router, with a set of LAN ports on the back?
The reason for asking is that a lot of people turn up here trying to put a router behind a modem that is also a router. That can complicate troubleshooting.- NosiuAspirant
Hi.
Lan/public - I can't login on router via my browser (192.168.1.1) from my home network or neither from the Internet (remote control). After a reboot it's perfectly working fine for a few days. My previous router did not had the the problem - even if It had approx 6 months of uptime.
The version is V1.0.4.48_10.1.30. Netgear support says it's the leatest version. There is NO modem. Behind the router there is only a bunch of managed switches with SFP (don't know the network map of my ISP but it is delivering Internet to the half of city) and then the fiber going to my ISP's servers few hundred meters away from my home.
However, yesterday I saw on my routers log that I have massive connection attempts per second (bots?) from various IP's all over the world to my NAS's peer-to-peer app on one specific OPEN port. The second problem is every 5 minutes constant there are connection attempts on NAS's admin account. The router says:
[DoS attack: Smurf] attack packets in last 20 sec from ip [192.168.1.10], Tuesday, Jun 07,2022 18:53:13
[DoS attack: TCP Port Scan] attack packets in last 20 sec from ip [83.20.32.56], Tuesday, Jun 07,2022 19:29:50
Maybe this is causing the router to some kind of - 'lock itself' ?
I am attaching the logs.
Nosiu wrote:
There is NO modem. Behind the router there is only a bunch of managed switches with SFP (don't know the network map of my ISP but it is delivering Internet to the half of city) and then the fiber going to my ISP's servers few hundred meters away from my home.
OK. That takes us into exotic network country.
Just about every ISP discussed here has either a modem or an Optical Network Terminal (ONT) in front of the router.
Sometimes people have a building network, and that tracks back to a router somewhere in the basement.
I can't login on router via my browserWhat happens when you try? Sadly "Can't login" does not tell us about any error messages you may see.
This sometimes happens when your router is fighting another router to manage the connection. That's why I asked about the modem.
As to DoS Attacks, Netgear's firmware is great at creating false reports of DoS attacks. Many of them are no such thing.
Use Whois.net to see who is behind some of them and you may find that they are from places like Facebook, Google, even your ISP.
Here is a useful tool for that task:
IPNetInfo: Retrieve IP Address Information from WHOIS servers.
The IP address you mentioned, 83.20.32.56 seems to be Orange Polska S.A. Is that tour ISP? You don't say.
If these events are slowing down your router, that may be because it is using up processor time as it writes the events to your logs. Anything that uses processor power – event logging, QoS management, traffic metering – may cause slowdowns. Disable logging of DoS attacks and see if that reduces the problem. This does not prevent the router from protecting you from the outside world.