Hi and please excuse my ignorance.
I'm new to RouterOS and the Routerboard hardware.
I have a new Routerboard 2011L and after many failed attempts to configure for a simple DSL setup, I have resorted to doing a factory reset (from within Winbox).

Now I am unable to connect via any ethernet port.
Winbox no longer detects an IP or MAC address.
(no longer 192.168.88.1)

I have tried doing all the hardware reset combinations but still no luck.

How can I find out if there is an IP address present on any of the ports?

I'm not convinced that the reset button / solder pad method of resetting is actually doing anything.
The green leds briefly flash when powered-up but no differently to pre-reset.

Many Thanks for any advice.

Make sure you hold the button/screwdriver before power is applied, keep holding it while you apply power, then wait for some 10 seconds and only then release.

also with the button you can trigger netinstall - open Netinstall in a computer which is directly connected to the first port on the RB2011L. Then boot the device while holding the button. Hold the button for longer, for 20 seconds, only then release. Netinstall should then find the device, and will show it in it's device list. You will be able to reinstall the device. In case reset is not helping, reinstalling should definitely help.

Many Thanks.

I have already tried all those options (on numerous occasions), with no success.
I will try again later today on a different PC.

Did you also try Netinstall? That should work in any case.

Yes I did.

It never "found" the routerboard.

Finally... after many days of trying... I have managed to connect using another laptop to the routerboard.
I have reflashed with both 4.17 and 5.18.

However... after rebooting I cannot access the router on any IP on any Eth port
(does a reflash default to 192.168.88.1 ?)
Also, winbox still does NOT find the MAC address (even though the router LED flashes each time I click the "..." button in winbox.)

The last thing I notice is that the incorrect LED is illuminated for each ethernet port.
e.g. If a CAT5 lead is plugged into ETH2.... the LED for 7 is illuminated... etc etc.

Does this give any clues?
Thanks

OK, maybe I should rephrase the questions:

1. After reinstalling the OS via netinstall I am unable to connect to the routerboard via winbox or any other method.
Should the default IP address now be 192.168.88.1 OR do I need to apply an additional config via netinstall?

2. I can determine the MAC address (from netinstall) but do NOT know what IP settings are now on the routerboard.
Is there a method?

Many thanks.... I'm confused

We have a new RouterOS version which fixes this issue on RB2011 devices. To boot the device, plug it in, wait a few seconds, then quickly unplug/plug the power jack (just so that the LED blinks for a fraction of a second), and it should come up. If not, try a few times. Once RouterOS starts, you will be able to install v5.19. Please email support to get access to this version.

This issue only affects a very small part of devices (one percent). Once we release v5.19, we suggest all RB2011 users to upgrade to it. Factories will also have this version by default, so you will not see this for devices you get in the future.

Thank you again.

However, no matter how many times I do a quick-power-off-on.... the router is still inaccessible via anything other than netinstall.

I have emailed support for ver 5.19.

Please could you remind them as this is now taking me an age to rectify.

(or could you PM me the file ?)

Thanks
Tim

Thank you again.

However, no matter how many times I do a quick-power-off-on.... the router is still inaccessible via anything other than netinstall.

I have emailed support for ver 5.19.

Please could you remind them as this is now taking me an age to rectify.

(or could you PM me the file ?)

Thanks
Tim

If netinstall works, it means the device can be restored to RouterOS v5.19.

I have similar situation with 711GA. It seems that the router doesn't boot up - there are no startup beeps indicating that. However netinstall works. It finds the device, partitions and reinstalls it, but after reboot nothing more happens. Should I return it to RMA?

Thank you again.

However, no matter how many times I do a quick-power-off-on.... the router is still inaccessible via anything other than netinstall.

I have emailed support for ver 5.19.

Please could you remind them as this is now taking me an age to rectify.

(or could you PM me the file ?)

Thanks
Tim

If netinstall works, it means the device can be restored to RouterOS v5.19.

Great.... so if you or Support could send me v5.19.... maybe I could try it !

Tim, I have sent you an email! Let me know if you need help

Any word on when 5.19 will be available?

I am getting random issues on my RB2011LS-IN where sometimes the ports do not come up properly and the port light doesn't light up when a cable is plugged in.
None of the ports (whether they light up or not) are contactable.

It would be great to see if 5.19 will solve my problems.

Unfortunately this version did NOT fix the problem either (still unable to connect via Winbox.)

Interestingly, this version DID temporarily fix the problem of the wrong LEDs showing, but after a re-boot the problem returns.
(I think the routerboard sees a crossover cable... even when it isn't ??)

I am now going to RMA this product to the supplier as I have wasted too many days on it.

Thanks for you efforts.

Hello, I've been having a similar problem with an RB2011LS-IN

While I am able to log on with winbox, upgrade to v6.0rc7 and even downgrade to v5.23, I am not able to use netinstall to install v5.23. Everytime I reboot the device (while keeping reset presed) I am able to pick the installation package but as soon as I hit "install" nothing happens. The progess bar is not shown and a few seconds later the status changes to "ready". However nothing has changed on the OS.

I also noticed the wrong led lighting up while it is looking for the net boot server (eth6 instead of eth1) and I cannot log on winbox using the MAC on eth2.

Might it be this is one of the faulty boards or am I doing something wrong?

Hello, I've been having a similar problem with an RB2011LS-IN

While I am able to log on with winbox, upgrade to v6.0rc7 and even downgrade to v5.23, I am not able to use netinstall to install v5.23. Everytime I reboot the device (while keeping reset presed) I am able to pick the installation package but as soon as I hit "install" nothing happens. The progess bar is not shown and a few seconds later the status changes to "ready". However nothing has changed on the OS.

I also noticed the wrong led lighting up while it is looking for the net boot server (eth6 instead of eth1) and I cannot log on winbox using the MAC on eth2.

Might it be this is one of the faulty boards or am I doing something wrong?

Please contact your supplier for an RMA as the board might be defective. Include the detailed problem description in your RMA request.

Finally... after many days of trying... I have managed to connect using another laptop to the routerboard.
I have reflashed with both 4.17 and 5.18.

However... after rebooting I cannot access the router on any IP on any Eth port
(does a reflash default to 192.168.88.1 ?)
Also, winbox still does NOT find the MAC address (even though the router LED flashes each time I click the "..." button in winbox.)

The last thing I notice is that the incorrect LED is illuminated for each ethernet port.
e.g. If a CAT5 lead is plugged into ETH2.... the LED for 7 is illuminated... etc etc.

Does this give any clues?
Thanks

Just curious to know if you know what differences there was between your computers that would not allow you to access the router using Netinstall and BOOTP. I am having the same issue with 2 PC's that are not seeing the router in the MAC display screen yet the router appears to be trying very hard to talk to the PC and get assigned the temp IP address. I have firewalls off, antivirus off, tried both a striaght and crossover cable, not sure what the issue is with either of my 2 PC's not being able to act as a BOOTP server. I have to believe something in WIN7??? I might try an XP machine next