Hi,

i have 133c client board which will not boot so i tried using the console side to enter but this is the message that came up

RouterBOOT booter 2.11

RouterBoard 133C3

CPU frequency: 175 MHz
Memory size: 16 MB

Press any key within 2 seconds to enter setup..
loading kernel from nand... OK
setting up elf image... OK
jumping to kernel code
Starting...
Starting services...


Shutting down...
Stopping services...

Demo license expired!System halted.

Please reinstall the router.

and when i try to enter by making the ethernet port to boot this is what i get
and i can enter with netinstall as well

RouterBOOT booter 2.11

RouterBoard 133C3

CPU frequency: 175 MHz
Memory size: 16 MB

Press any key within 2 seconds to enter setup..
trying bootp protocol...........................................................
................................................................................
................................................................ failed
kernel loading failed
€€

what should i do?

attached is the screen shot of the netinstall

1. enable net booting
2. plug in the cable from router->windows pc
3. disable all antivirus and firewalls that might block this

its still the same thing

is there a way u can come into this pc and look at it?

ummm, no, i'm far away

you can try to use the XMODEM transfer protocol in your Hyperterminal program to send new BIOS to the routerboard. Use this file:

http://www.routerboard.com/files/rb-2.1 ... 0-2.18.fwf

same thing Sir

Please try a different ethernet cable, or a different port on the RouterBOARD and PC. Make sure you disable the firewall on this ethernet port in your Windows, and disable any other network cards. This error clearly indicates that there is no Netinstall program running at the other end of the cable.

Did the Bootloader version change to 2.18 in the Hyperterminal screen?

yes i got the 2.18 alright. but i still dont see why it will not open the netinstall after changing cable and ports

ok the problem has been solved but a new one is bothering me.

the rb has become very slow and keeps rebooting every 40mins after i upgraded the firmware and loaded new OS

what can this be?

1. how did you solve the problem? please share, others will be able to benefit from this info.
2. in what way you mean slow? slow traffic, slow console response, slow something else? what features do you use in it, how many rules do you have?

i used the upgraded from the hyper terminal and load the boot file again.
so i had ver. 2.18 then i was able to run the netinstall program to load the new version of routerOS then i went into my account server on www.mikrotik.com to request for the key which was provided in minutes. the board came back to life but it is very very slow.

It take too long to start and when u issue a command it take forever. After some time i saw it keeps rebooting every 20 minutes

what can this new problem be?

what ROS Version are you using ? 133c don't like Version3. used 2.9.51.

What was the CPU load?
Package install?

the Version is 3.xx alright but i cant get into the board now to look at the cpu load so i guess i have to clear everything now right?

please give me the proccedure to erase everything off the board and where i can get the version 2.9.51 so i can reload it well

Thank you

duh, http://www.mikrotik.com/download.html

First you need local access to fix this. You cannot do this with only remote access.

Clear the config... from the cli "system reset-config" then reboot.

If you carried an old config from ROS version 2.9.x to 3.x then this might be causing the slowness. Mikrotik does not always keep the same config registers between major versions and that could be making it slow.

If it still runs slow after clearing the config, downgrade to 2.9.51. You can do this by copying the 2.9.51 ROS image to the files area and under 'system packages' select downgrade.

Don't forget to clear the config after downgrading.

If all else fails, use Netinstall to downgrade the ROS version.

Tom

First you need local access to fix this. You cannot do this with only remote access.

Actually you can do it remotely. I've done many that way.
In case anybody needs to do this, these are the steps I used.


Step by step to downgrade rb133c/rb112 to 2.9.51

The only problem that I've seen with the downgrade is the wireless settings are defaulted. ie, disabled and all settings lost.
And on some downgrades the dhcp server on ether1 would lose the gateway and dns entries. About 10 of 40 had this happen...weird.

I've done about 40 this way. Only one failed and it was using antenna b. I don't know why it was hooked up that way
but it was. Document your settings!!!!

This is for basic routed connection. Wlan to tower, Ether1 to customer. Nat'd.
Security settings are maintained during downgrade but wireless setting to use it must be re-entered.
Wireless settings go to default and disables the wireless card, so if you don't re-enable it and
enter some settings via script you'll be doing a truck roll.

1-login to device to be downgraded with winbox
2-copy os 2.9.51 to file
3-record ssid, authentication, band and antenna of wireless -or minimum requirements to connect on your system
and enter that info in the script part A
4-copy and paste part A in terminal
5-close winbox and wait 3 minutes
6-login with winbox
7-check dhcp servers gateway and dns settings if using dhcp. They tend to dissappear.
8-rename wireless name in wireless settings if you do that. ie, customer name
9-copy and paste part B. system reboots
10-login with winbox and check everything. Remove all files and backup.
11-Move on to the next device to be downgraded.


### Copy RouterOs 2.9.51 to the RB133C

### Don't panic during the downgrade. It takes 60 seconds before the connection drops
### and another 120 seconds before it reconnects. Total of 3 minutes after applying part A.

### You may lose your dhcp servers gateway and dns settings after the downgrade. Some do, some don't.
### You will have to rename your wireless name after the downgrade.


#### Part A ####


### --- Working wireless settings---###
### Copy and paste the settings for the AP you're working with.

### /interface wireless set wlan1 band=2.4ghz-b ssid="RWGALVA-SW"
### insert the ssid between the " and \ like this -- ssid=\"ssid goes here\""


### Put your wirless settings in the script

### Check to see if wireless is using antenna B antenna-mode=ant-b


#### Copy and paste the following ####


# Removing the auto-upgrade config. Don't need that anymore. My upgrade script was named "upgrade".
# and my schedule for the upgrade was named "sched_upgrade". If you didn't have anything like that, remove this.

/system upgrade upgrade-package-source remove [find]
/system script remove upgrade
/system scheduler remove sched_upgrade


# Disable supout file creation It causes the units to hang at times and I don't like it.

/system watchdog
set auto-send-supout=no automatic-supout=no no-ping-delay=5m watch-address=none watchdog-timer=no


# Making the new backup Always a good idea. Name it what you want.

/system backup save name=os_downgrade

# Making the script to re-enable the wireless This will reconfigure the wireless. I put 60 second
# delay to make sure system was up and running.

/system script
add name=reload source=\
":delay 60\r\
\n/interface wireless set wlan1 disabled=no band=2.4ghz-b ssid=\"Your_SSID\""

# Scheduling the script. Scheduled to run at startup

/system scheduler
add disabled=no interval=0s name=reload on-event=reload start-time=startup

# Downgrading the O/S. Scary part, but it works if you entered the correct wireless settings, so relax.
# You did enter the correct settings, didn't you!!!

/system package downgrade
y


#### Part B ####

### Log back in and clean up

## check this ##
## / ip dhcp-server network export

## should look like this

## add address=192.168.10.0/24 gateway=192.168.10.1 dns-server=205.171.3.65
## -- Watch the ether ip address -- could be 192.168.0.1


#### Copy and paste the following


# Removing the downgrade scripts

/system script remove reload
/system scheduler remove reload

# Getting rid of unused packages. Edit as necessary

/system package
uninstall hotspot
uninstall ppp
uninstall routing
uninstall rstp-bridge-test
uninstall webproxy-test
uninstall wireless-crd
uninstall wireless-legacy

# Rebooting the system

/system reboot
y

Hi,
I have same problem with more than 10 of them.
I sent a email to support and never answered.
All 133 board have same problem.
AsDsL

where can i get RouterOs 2.9.51 for the RB133C ?

http://www.mikrotik.com/download.html

1. select 100 series
2. select legacy

i always cant figure out which folder i should unzip files into for the netinstall to load

can u hep?

netinstall has a browse button, so unzip them wherever you want, just make sure to click on the "router MAC" BEFORE you browse for the packages.

i do this most of the time and it does not work.
i will have to hustle with it

Hey no one replied to this
help is needed here ASAp

Hi everyone,

I think i have it all confused again.

After the re installation of the 133c rb i got it working but is was slow so i did a downgrade but after that see what the winbox looks like.
No wireless button to configure the wireless card

here is screenshots and i hope we can get a quick solution to this


Please advice

Hi everyone,
No wireless button to configure the wireless card
Please advice

did you installed wireless package? can you post

/system package pr.

i cant post anything again. the mac id will not even resolve when i try to run the netinstall.
is there a way i can redo everything again?

please advice

i cant post anything again. the mac id will not even resolve when i try to run the netinstall.
is there a way i can redo everything again?

please advice

can you just winbox the RB. no need to use netinstall.

yes i can winbox the rb. so what next?

please help here

this is the message i get trying to load netinstall to 133c


Press any key within 2 seconds to enter setup..
trying bootp protocol..... OK
Got IP address: 192.168.0.111
resolved mac address 00:1B:24:AC:4F:15
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
falling back to small packet size
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
kernel loading failed
€€

RouterBOOT booter 2.18

RouterBoard 133C3

CPU frequency: 175 MHz
Memory size: 16 MB

Press any key within 2 seconds to enter setup..
trying bootp protocol...........................................................

********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
********************************************************************************
****************************************************************************

PLEASE HELP

change LAN cable or try from another PC. also make sure that PC doesn't have firewall or antivirus turned on

yes i can winbox the rb. so what next?

please help here

why are you still playing with netinstall.

from winbox.
/sys package pr

and then what next Sir?

i still cant get this rb to work
can we make this work?

I don't understand you. You said that you can connect with winbox. Where is the problem then ???

i can get to configure the wireless card since the is no wireless button on the left pane

install the wireless package, as you were told above!

go to www.mikrotik.com -> download -> choose what device you have -> download ALL PACKAGES ZIP --> extract the wireless package --> upload with FTP --- > reboot

make sure that Winbox shows the same version number as the package that you are trying to install

please help me .
how do i ftp into an rb?

1. download an FTP program http://filezilla-project.org/
2. Connect to the IP address of your router (same as you use for Winbox).

are you sure you have enough TCP/IP experience to be running a router?

no please help

what port should i use?

How do i clean everything off this 133c rb and do a fresh loading?

you can use the reset jumper:
http://wiki.mikrotik.com/wiki/Password_reset

its still the same