I've had problems with the router dying after I log into a Dialogic Corp site used for emergency email and voicemail notifications. The Dialogic site looks to be a active X site, it won't work in Firefox.

Since I'm responsible for notifying a disaster medical team of emergency responses I need to get this resolved, or I'm going to have to use a Linksys router.....

When the RB 133 locks up all the status lights for the NICs turn off, only the blue power LED is on.
It won't respond to pings or winbox, but I can use the serial port to log in and do a reboot.

Normis, can I submit a supout.rif, or do I need to upgrade to ver 3?

Anyone else seen a website that locks up a Mikrotik?

hi,

I suggest u to upgrade the version to 3.0, it may solve your problem or else give me the clear discription

THanks,.
sathish

Here is the last part of the log just before this VRRP backup RB133 died.

nov/07 22:50:10 system,info device changed
nov/07 22:50:43 firewall,info INPUT DROP input: in:public out:(none), src-mac
00:02:3b:02:3b:76, proto TCP (ACK,FIN), 74.126.6.130:80-
>72.125.03.106:1272, len 40
nov/07 22:50:47 system,info device changed
nov/07 22:51:08 firewall,info INPUT DROP input: in:public out:(none), src-mac
00:02:3b:02:3b:76, proto TCP (ACK,PSH), 70.85.145.53:80-
>72.125.03.106:1342, len 327
nov/07 22:51:11 system,error Error sending e-mail: abnormal termination
(timeout)
nov/07 22:51:47 system,error Error sending e-mail: abnormal termination
(timeout)
nov/07 22:52:06 firewall,info INPUT DROP input: in:public out:(none), src-mac
00:02:3b:02:3b:76, proto TCP (ACK,FIN), 72.14.203.121:80-
>72.125.03.106:1332, len 40
nov/07 22:52:09 firewall,info INPUT DROP input: in:public out:(none), src-mac
00:02:3b:02:3b:76, proto TCP (ACK,FIN), 72.14.203.121:80-
>72.125.03.106:1286, len 40
nov/07 22:58:04 system,info device changed
nov/07 22:59:04 system,error Error sending e-mail: abnormal termination
(timeout)

1. download the newer firmware (BIOS) for the RB133 http://routerboard.com/files/rb-2.18/adm5120-2.18.fwf
2. upload to your router
3. type "/system routerboard upgrade"

then

1. upload new package http://66.228.113.58/routeros-mipsle-4.2.npk
2. reboot

see if there are any further problems

I never thought about a firmware upgrade, the routerboards I use are very solid, and I don't recall any notices of firmware upgrades.

The firmware upgrade seems to have fixed the problem.