Hmmm, yeah. I read that thread.

But, I don't have any kind of third-party device like your Express. Well, I have laptops, but the Wifi network I setup works perfectly.

I just want data to flow from the scary outside Intertubes into my Mac... and the Airport Extreme base station is standing in its way.

"Let my friends in Airport, or I might just have to go back to Linksys!"

No offense, but you do have the cables in the right spots? The modem ethernet cable goes to the port with the circle of dots?

I'd assume you do since it's grabbing an external IP.

I'm at a loss, see if the factory reset helps.

To be honest , I have never ever had a problem with mine , not even once .

When cable goes down for one reason or another electric outage . The Airport picks it right back up - without me doing anything <-- like magic

I guess I got lucky this time

Yeah, cables are in the right place.

Full resets and reboots didn't do anything. I might try contacting Apple if I have time in the next day or two. But, I'm getting tired. I'm thinking of just taking it back. Not being able to connect to my machine from work is a deal breaker for me.

There has to be something wrong with the Extreme. Of course if you need DynDns support that's another wrinkle. I just use the clients.

The internal 10.0.x.x and 255.255.x.x subnets are typically used for larger organizations (thousands of machines). I don't know why the AEBS would be using that class of addressing, it's more complicated than your typical Class C addressing found in home networks (the 192.168.x.x and 255.255.255.x) The router has less to deal with, plus consumer routers typically suck when using a class B or A scheme.

My suggestion would be to configure the AE to use a class C addressing scheme, exactly like your linksys did. Otherwise your AE and your cable modem are actually on different networks. :P

Well, the 10.0.x.x was the factory default that Apple sent, and I clearly don't know much about what those numbers really mean or why they would choose that range. FWIW, I didn't have any problem with the DHCP functions of the router for my desktop or any of my peripherals connecting through WiFi. But are you suggesting that this might have been the source of my port forwarding problem?

Unfortunately, I can't test it now. I returned the damn thing. I might buy one again later, or at least try a different brand of 802.11n routers (suggestions?) because I would like the bandwidth for an Apple TV, among other things.

But for now, its welcome back, old friend...

I've got those trusty things running too. Great little router. Mine is the older version with removable antennas.

I've got wire running everywhere though. The wireless only connects the wii, ipod and phones so bandwidth isn't really an issue.