Port forwarding broke with 7.2.1 firmware
apple Verified ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I bought my AirPort Extreme with 802.11n (Fast Ethernet) when I was at MacWorld back in January and it's been great until I applied the 7.2.1 firmware update. Now it refuses to do any port mapping, no matter how much I reconfigure it. And I can't back to my mac working with it either. So frustrating.
Using default host or applying specific port maps no longer works. Restarting doesn't help either.
Anyone successfully downgraded the firmware or reapplied it? I am ready to toss it in the bin, and buy a cheaper $50 n router, since this Great White Disk no longer wishes to work properly. <sigh>
11 replies
Sign in or join Beachball Help to reply.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Downgrading the firmware was easy, it's in the Airport Utility menu.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hm. Did this really work for you? I still have the same problems, and they also started when I upgraded to 7.2.1. Tried downgrading but it didn't do anything (still no forwarding).
I had a few forwards before and I know it used to work. Now it just won't open any ports at all (not even ssh). Tried NAT Port mapping protocol and direct port forward from both 7.2.1 and 7.1.1.
Too bad because I wanted to try Back to my Mac. Without being able to get in, no way to try it out.
Not a problem with my level of sophistication either. I used to do remote desktop by doing SSH tunneling using the command-line without a problem before the 7.2.1 upgrade.
Please help if you can.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I am having issues with FTP port forwarding at the moment, the Airport Extreme doesn't seem to want to send out a directory list at all. This was never an issue with my old (and unreliable, kept dropping all connections) Netgear WNR854T, and infact I still have it and will use it together with the Airport Extreme until the nagging issues are sorted.
Other ports are fine, http (80) and my torrent port work well.
Is anyone else having this problem?
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
i just purchased a new AEBSn (gigabit) router and i'm not having any troubles using port forwarding.
i'm forwarding the following ports for my ps3:
5223/TCP
3478/UDP
3479/UDP
3658/UDPfor my mac
3389/TCP
21/TCP
2222/TCP
9090/TCPfor my lacie
8080/TCPi had a ***** of a time setting my new router up which is the main WDS router and connected 1 AEBSg and 1 AEBX for itunes streaming. i also have a vonage VOIP system, and the lacie is connected via the switch on a 10/100mbps link. what i found is that you can't have anything plugged into the router when configuring, and once it is configured and properly working with the mac your using to configure then you can plug stuff in. I'm also using DCHP reservations WPA2 and MAC filtering.
if you post your configuration, i'll be more then happy to assist in fixing these pesky issues, i know how you feel, as i was about to toss the new router through the window like a frisby...
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
No clients connected. That's the only thing I haven't tried yet. Unfortunately I write software for a living so I'm often forwarding ports and closing them back up as part of my regular day job. So disconnecting all clients just so I can add a new port forward is unrealistic.
Other than the need to port forward on the fly for my job, my configuration is pretty simple:
XBox (UPP 88, UDP 3074, TCP 3074)
Ssh with a custom high TCP portCustom TCP ports for work (8080, 8091, 3000 depending on what webapp stack I'm running)
For other stuff I usually just ssh forward.
I use MAC-based DHCP reservations for all the machines. There's usually about 7 or 8 clients (computers, printers, etc).
I ended up just getting a Belkin N MIMO at a black Friday sale. Doesn't do WDS (so I can't use the AEBSn to extend it) but at least it was cheap and it forwards just fine.
I'll wait until the new firmware and then maybe try again, just because it looks great on one's desk. But for now it's in my closet, as that can't be the only reason one buys hardware. Sigh.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
once my initial configuration was completed, i have successfully port forwarded to internal clients on the fly without any problems...
you might have a flaky unit???
i just forwarded additional ports for my VOIP lastnight without any problems...the only thing i don't like much is that the device seems to reboot everytime a new configuration is uploaded...this is a trememdous bummer...
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Downgrading didn't help. Nor has anything else. I am wondering why I replaced my $50 dlink router with this $200 shiny white Apple router which no longer works. **** techno **** ....
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I dream of the days of ssh tunneling... those days are gone my friend.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
have you tried returning your unit to the apple store, or bringing it in to see an apple genius?
i know this might be frustrating, but i just configured 4 of these unit for some friends at work without problems...
this is the only reason why i suggest that your unit might be a bust?!?! :0(
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Same problem here; FTP server behind Airport, worked great with my old crummy router, but the airport doesn't seem to support FTP (pasv) properly
So much for throwing $179 out of the window ...(not to mention the missing DynDNS option)
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Client firewall on workstation to blame. Reinstall of Mac OS X fixed the issue.