MDA III WiFi DHCP Problems

[Guest stug]

Hi all, I've got an MDA III, and I've been having trouble with WiFi.

Occasionally when I am at a hotspot (different kinds, T-Mobile, BT, Swisscom) when I turn on Wifi the MDA connects to the network, but doesn't assign an IP address (gives itself 169...). This isn't too bad as it only happens occasionally.

However on my home 3Com router, and my office Buffalo router, the MDA III refuses to acquire an IP address every time, despite my laptop connecting to both networks with no problems. I have checked the logs on my home router, and it seems to be offering the MDA an IP address, but getting no ackknowledgement. The MDA connects fine if I hard code IP address, subnet, gateway, and DNS server, but this is a bit of pain.

Has anyone else had any similar problems (and managed to resolve them 8) ?

Cheers,

Stuart

[Guest Wozbacca]

im having the same problem with my m2000

the m2000 gets a 169 address instead of getting one from the dhcp. on my mates belkin 54g it works fine, but on my 3com 54mbps it doesnt work. i've also found a few hotspots and its got a 169 from them too. it works fine with a static ip on my 3com wlan, but i dont konw the ip range of the hotspots to manually enter it in.

anyone have any ideas?

[Guest fraser]

You using wep? With wep enabled, a device with the wrong key can still assocate with the access point, but it can't communicate with anything. So you don't get an IP. All Microsoft OS's default to a random 169 address if they can't get one assigned; this means you can create ad-hoc networks if you want using wired ethernet. Not a very user-friendly failure mode!

[Guest beersoft]

I had the same problem with my m2000 and my linux firewall that was giving dhcp leases......it wasn't good as the m2k was killing the dhcp service on the server and then taking the server down :lol:

i resolved it by using the access point as dhcp server and swearing alot

the tcp stack on the angel sucks, and the wifi isn't much better

later

Owen

[Guest andyr27]

I fixed this my changing the subnet mask to 255.0.0.0 from the default draytek address of 255.255.255.0