My 411u is not recognized by the network adapter and the winbox. I plug it in the network adapter and nothing is happening. My router does not cointain the device in it's arp table.

I can connect to the device from the putty via the serial com1.

If my device faulty?

If you can connect from the console, what troubleshooting have you done? Does the interface show as up? Is the correct IP address applied to the interface?

I connected to the console. I restored the file configuration that i was using before the winbox problem. The file was restored fine. I checked the configuration and it was restored corectly. I don't now what else should i do. The ip adress is set.

I enter the network adapter the ip setting manually but also the router was not identified by the winbox or the browser.

[admin@MikroTik] /interface> print
Flags: D - dynamic, X - disabled, R - running, S - slave
# NAME TYPE MTU L2MTU
0 ether1 ether 1500 1526
1 R bridge bridge 1500 65535

[admin@MikroTik] /ip address> print
Flags: X - disabled, I - invalid, D - dynamic
# ADDRESS NETWORK BROADCAST INTERFACE
0 192.168.1.30/24 192.168.1.0 192.168.1.255 bridge
1 192.168.1.30/24 192.168.1.0 192.168.1.255 ether1

also i tried to ping my router and my pc from the console. I have the utp cable connected but none of them responded.

I have also done : check-installation and check-disk and get no report message at all. ( to see if something was wrong or ok)


I press the reset button during booting. Then i connect the com and try to connect. I get those messages:

Ethernet link absent...
trying bootp protocol........................................................................................................................................................................................................... failed
kernel loading failed
loading kernel from nand... OK
setting up elf image... OK
jumping to kernel code

I think is a ethernet port problem :
I tried : [admin@MikroTik] > interface ethernet blink ether1
the ethernet port should be blinking but nothing.

You've got the same IP address on a physical interface and a bridge. Why? Are you trying to bridge traffic? What interfaces are you trying to bridge? The interface list only shows two interfaces - a bridge, and ether1. Did you edit that list? What happened to the wireless interface?

What are you trying to ping? Are you sure that whatever you're trying to ping doesn't have a host firewall that blocks ICMP?

I bridged the interfaces becauses this router was used for a wireless ap.

I reseted the configuration added 192.168.1.30/24 adress on the ether1. because 192.168.1.0 is my network. So with only one interface active I am also having problem with ether1. See my previous msg..

Ethernet link absent...

[admin@MikroTik] > interface ethernet blink ether1
the ethernet port should be blinking but instead nothing.

Then you may have a faulty Ethernet port. Try and contact your reseller.

is there a way to save my routers configuration file in my pc? because in case that they will replace the router my config file will be lost!

Sure. Run "/export" via the console port and copy and paste the resulting configuration to your PC and save it as a text file. Edit it to make sure unique information (such as MAC addresses) are taken out. Then you can paste it into the replacement router when you get it.

done! many thanks!

You have to connect ethernet cable and have ethernet link up running (link led on) to blink command able to blink. Your interface print shows that ethernet is not running, so it can't blink.

Are you disabled auto-negoation on ethernet interface? That could cause problems.

/interface ethernet print detail

Getting interface running is first thing. And you have tried with another ethernet cable?

If these don't help it could be faulty ethernet port.

that means that i have a problem right?

It's ok. Normally it is enabled like yours.

But if it is manually set to disabled then it could cause problems if not set correctly in both sides of link.

Did you try other cable? Sometimes problem could be bad or broken cable.

After that it is more and more likely faulty ethernet chip.

Finally i have send the device for rma a couple of months again. the deviced replaced with a new one.

SOLVED.