Hopefully someone will have an idea here. Have a new RB333 running 3.01rc13 with a public ether1 and a private (192.168.7.1/24) wlan1 using an Atheros AR5413 card.

I have configured a dhcp server on wlan1:
name="dhcp1" interface=wlan1 lease-time=3d address-pool=dhcp_pool1
bootp-support=static authoritative=yes always-broadcast=yes

Pool:
name="dhcp_pool1" ranges=192.168.7.2-192.168.7.254

Here is the problem... my Palm TX connects perfectly and is assigned an ip from the dhcp server. My wifes Acer laptop connects perfectly also. But my laptop, using a trendnet cardbus tew-421 card connects, associates, but never can talk to the MT dhcp server. It eventually times out saying no dhcp server could be contacted.

Note that this same card connects to a D-Link wireless router and gets assigned an ip via the d-link dhcp server just fine..

I swapped out the trendnet card for a d-link dwl-650+ cardbus adapter on my laptop, and it connects to the MT, associates, and gets an ip from the MT dhcp server just fine.

So, it is only the trendnet adapter that can not find and communicate with the MT dhcp server.

Any suggestions? Thanks!

Buy a different adapter.

Oh, that's helpful. So every client using my hotspot who happens to own this card, and can use it on non-MT hotspots, will be very happy when I tell them to go buy a new adapter if they want to use my, or any other, MT hotspot.

I would like to find out why the trendnet adapter works with non-MT dhcp servers, and fix the problem.

But hey, thanks for the reply...

The problem is obviously with the Trendnet adapter and not Mikrotik. Contact them for a solution. The probably need to update a driver.

I don't see how it is obvious that the problem is with trendnet and not with MT.

Trendnet could just as easily, and correctly, say that their card works with every AP except MT, so it is obviously a problem with MT.

Be fair... we know there is an interoperability problem, but at this point we don't know who's fault it is.

Sure.