HI,
I have a mAP (RBmAPL-2nD). The device responds to ping on the local subnet.
The devices AP is transmitting. Lights look good.
But… Winbox will not detect device.
Any ideas as to why?
Geoff
Check the Discovery Settings under IP Neighbors…
If you cannot get in via any of the network interfaces (including the wireless one), neither using MAC address nor using an IP address, neither using Winbox nor Webfig or SSH, connect the USB OTG adaptor to the mAP, and an USB to serial converter to it, then a null modem cable, then a serial port on your PC or yet another USB to serial converter. Hyperterminal is long gone but PuTTY can use serial ports. Oh, and if the device gives out IP addresses via DHCP, you don’t need neighbor discovery (which can be disabled separately from mac-winbox) to determine its MAC address - look at the gateway IP the PC has got from the device, and the ARP table on the PC will show you the MAC address.
@sindy is a lot easier to suggest a netinstall…
Also the op says “Winbox will not detect device.”
@Zacharias, try to disable neighbor discovery at the device and detect it using Winbox - it won’t find it because disabling of neighbor discovery not only prevents the device from actively sending discovery queries but also from responding them.
And not everyone saves their configuration and exports certificates from the devices, so a netinstall is always the last resort.
All in one tiny box: https://mikrotik.com/product/woobm . Works great!
Yes, another “off the shelf” solution. The difference is where the shelf is, next to your desk or in the local electronics shop 
@sindy read my 2nd post again please…
I suggested to the OP checking his neighbor discovery settings… Never said the word disable…
As for the certificates, you are right only in case that the OP indeed has Certificates…
Netinstall is a 1 minute case… Computer with serial, serial cables and usb to serials i think is a lot more time to find…
My opinion ofcorse…
@Zacharias, we must have some Metaxa together (although I almost don’t drink) to start understanding each other better
I cannot imagine how to check neighbor discovery settings if you cannot break in to the device. So my initial response was based exactly on that assumption, that the OP cannot connect to the device by no means known to him, and the “Winbox doesn’t detect” may have been be just a not-so-precise description. When the detection works, you don’t need to touch the keyboard until you get asked for a login and password, so some people haven’t even noticed that you can enter the IP or MAC manually.
Do you know the phrase “we don’t deliver what you asked for, we deliver what you really wanted”? That’s how I try to read the questions, and it usually helps. If someone knows it all, he’ll be angry for getting a basics answer for a minute; if you tell a beginner to do a netinstall without warning him about the collateral damages, he’ll be sorry for much longer.
@sindy,
As OP said :
But… Winbox will not detect device.
Any ideas as to why?
For me that simply means: i do not see my device in the neighbors. I am based exactly to what i read without any assumption…
The fact that you made an assumption that he can not connect at all, might 100% be right, but that does not change the fact that you were based on an assumption… I do not see nothing on the OPs post saying that he can not login, or he can not configure or anything similar…
if you tell a beginner to do a netinstall without warning him about the collateral damages, he’ll be sorry for much longer.
If the OP search for Netinstall the first result he will get is https://wiki.mikrotik.com/wiki/Manual:Netinstall and at the top of the page he will see a red sign Warning: Netinstall re-formats the system’s drive
In case the OP does not read it or does not follow the procedure from the official manual but from somewhere else where the Warning is not shown as it should then whose fault would be ?