My home networking policy already includes giving static IP addresses to any permanently connected network device, namely because DHCP service implementation too often reveals flaky on all routers I tried from different vendors (LinkSys, D-Link & Netgear devices) sometimes giving out the same address to different clients, sometimes denying service altogether!) I got the same problem with AE, firmware v6.3, set in client mode to a D-Link DI-624 router (latter does not support WDS, hence AE in client mode), WPA2 security, except it does persist with static IP address set up on the AE If it fails to do so, it will still display a green light. It looks like it does indeed disconnect from the network and then tries to reconnect. May 22 11:28:10 Severity: 5ĝisconnected from network. May 22 11:07:20 Severity: 5Ĝlock synchronized to network time server (adjusted +1116752819 seconds) Jan 01 01:00:11 Severity: 3 No address for NTP server. This is the log file, shortly after the AAX has been running for 30 minutes. This is the setup: AAX, Firmware 6.1.1, operating in client mode in a WEP-encrypted network, network configuration by DCHP, AirTunes enabled. Rinse, repeat every dozen of hours or so. My AAX drops off the network while still displaying a green LED that says: 'I am fine.' However, it isn't. It desperately needs a better way to communicate its current state. What's the deal? I think that the Apple Airport Express (AAX) is broken by design. It now has happened a number of times, so I am posting my issues now here at vowe's magic flying circus to give Google an opportunity to catch it. What do you think Apple does with error reports in their forum? Admit that they have a problem? Forget it. Apple Airport Express dropping off the network by Volker Weber

Airport disk archive