RB951Ui-2Hnd Automatic Restart and Error Log View

Why my mikrotik RB951Ui-2Hnd routers automatically restart 3 or 5 times in a day?
Why shows this log error always?
How to get rid from this problem?

Dec/18/2016 15:03:56 memory system, error, critical login failure for user root from 187.205.53.2 via telnet
Dec/18/2016 15:03:56 memory system, error, critical login failure for user admin from 123.254.65.169 via telnet
Dec/18/2016 15:03:56 memory system, error, critical login failure for user root from 187.205.53.2 via telnet
Dec/18/2016 15:03:56 memory system, error, critical login failure for user admin from 123.254.65.169 via telnet
Dec/18/2016 15:03:56 memory system, error, critical login failure for user root from 187.205.53.2 via telnet
Dec/18/2016 15:03:56 memory system, error, critical login failure for user admin from 123.254.65.169 via telnet
Dec/18/2016 15:03:56 memory system, error, critical login failure for user root from 187.205.53.2 via telnet
Dec/18/2016 15:03:56 memory system, error, critical login failure for user admin from 123.254.65.169 via telnet
Dec/18/2016 15:03:56 memory system, error, critical login failure for user root from 187.205.53.2 via telnet
Dec/18/2016 15:03:56 memory system, error, critical login failure for user admin from 123.254.65.169 via telnet
Dec/18/2016 15:03:56 memory system, error, critical login failure for user root from 187.205.53.2 via telnet
Dec/18/2016 15:03:56 memory system, error, critical login failure for user admin from 123.254.65.169 via telnet

Telnet is available on your WAN interface…that is not a good idea. Please configure VPN for any administration on your MikroTik router (and the rest of the network if required).

VPN created but problem not solved.VPN created from this way.
http://forum.mikrotik.com/t/vpn-configure-step-by-step/92121/1

In IP > Firewall > Filter Rules you should have a default deny for the INPUT chain to deny all connections to your wan IP that don’t match any of the rules above.

Default out of box config should have this. Chain=Input, in-interface=ether1-gateway, action=drop. Move rule to bottom.

As for reboots, does the log say why? Go to System > Watch Dog Timer, is that enabled? Sometimes the Mikrotik will power cycle ether ports if there are packet errors, like collisions.

  1. yes, bro may be my first problem has been solved. its working good now . Is this configure impact any where like my gateway-Wan or somewhere?
  2. No brother my watch Dog Timer is not enable? So, What to do now?

in System > Log, set it to save to disk. When saving to memory, the logs are lost on reboot.

If there is still no evidence on why it’s rebooting, do a backup of config. Reset to factory defaults and change minimal settings just to make it work on your network. Does it still reboot on its own?

In Winbox you can click Make Support.rif, It’ll create a file under Files. Email that file to support@mikrotik.com with an explanation of the problem.