I have a very easy to replicate problem that I hope someone has an idea on now to resolve. After I log into a new router (any new HEX router) via Winbox, layer 3 and remove the configuration, I cannot log in via the MAC address which I see and am able to populate in the winbox neighbors tab and populate the discovered mac address in the connect to field. Details follow below:
This is a Brand new out of the box HEX. This happens on ANY new HEX; I don’t believe this is specific to the HEX however.
-The firewall is turned off on my Windows 10 computer.
-I run Winbox as administrator.
-I will initially log in via the 192.168.88.XXX/24 subnet using layer 3 and remove the configuration.
-I then cannot log in using Winbox via layer 2 using the discovered mac address after the configuration is removed.
-I try all 5 ports on the HEX. The only thing plugged into it is my Windows 10 computer.
Winbox indicates logging in and the very briefly downloading descriptors. Winbox disconnects but allows me to reconnect which starts the same failed process over again.
Winbox 3.2 is what is being run.
Because this doesn’t work, I must spend 5 minutes removing all of the default configuration that I do not need to allow me continued access to the router.
When I am setting several of these up per day, this becomes very time consuming and inefficient.
This has been an ongoing issue for the last two years or so.
When I first log in via layer 3, Winbox gives me the option upon login to remove configuration. Are you saying that removing the default configuration via the system/reset configuration/check no default configuration/ is the way to achieve the desired result?
It should work. Have you tested if your L2 connection is stable when the inital configuration is still there. (Before you remove it).
It is not because you have L3 connectivity that you also have (stable) L2 connectivity. L2 is broadcast based, L3 is unicast based.
Resetting the configuration by navigating to System/Reset Configuration/, checking the “No default configuration” and selecting reset configuration does it. The remove configuration script button when you initially log in should be removed from future releases of routeros. It has cost me HOURS!
Unfortunately after more testing, I am having the same issue. I will try another computer over the weekend. Maybe I need to uninstall Winbox and try it again. Winbox disconnects just as the “Downloading Descriptors” banner appears and just before it should open the Winbox GUI.
Winbox v3.27 hangs up on “Downloading Descriptors” when attempting remote connection. Winbox connects ok when on LAN.
This has been happening on several Mikrotik routers and I can’t find any support of fixes to date, although it seems to be a common problem. Any wisdom?