Tried miami-dx as well, wich results in the same problems.
...
Is there a chance this is caused by timing issues?
Doubtful, but always possible.
I'd wonder about some type of software conflict first.
As I understand it, MiamiDX is pretty different software-wise from EasyNet (which is AmiTCP v3 I think). So it's probably not the IP stack.
If possible, can you boot with no startup sequence and then do some testing?
(You might need to do some manual assigns before everything will work)
Also, do you have cardpatch and cardreset in your startup-sequence?
Not using a wireless card here (yet, I have one, but haven't hooked it up).
desiv