I view NAT rules in the firewall. As soon as I click on NAT winbox closes. Bug?
should i delete my mikrotik directory in %userprofile%\appdata\mikrotik (or whatever it is)?
I’ll try this and see if it fixes.
Hmm.. Have the same problem. Only happen when someone attack your mikrotik.
Try to take out the network cable in mikrotik and access it directly using a laptop with cross cable to the mikrotik.
… it is directly connected, and a crossover isn’t neccessary because the router has MDI-X capabilities …
I’m pretty sure deleting my temps will fix it, I just haven’t had a chance to do it. It’s highly unlikely it was “attacked”.
do it willbill, delete winbox temp files ti should fix your problem, as you wrote already
Didn’t help, downgrading to 2.9.39 worked tho! 
I think winbox for 3.0b5 is just buggy … i’ve had it instantly close in a few different spots, as well as show lists of choices in wrong places.
Sam
I’m having winbox problems with 3.0b7.
This is using the winbox that comes with 3.0b7 (had the same problem on older winboxes).
http://www.midcoast.com/~jp/winecap.txt
To get this, I logged into the 512, clicked on wireless, double clicked on wlan1, clicked scan button, clicked close button. close should have close out the scan window, not all of winbox.
The x in the corner of the scan window works fine. But then I x out of wireless interfaces, and winbox crashes.
I use wine version wine-20040813-7.2 which came with suse 9.2. I don’t have any problems with the normal 2.9 routeros series in winbox.
I am using latest wine-0.9.33, winbox runs fine, no issues.