7264 Views 3 Replies Latest reply: Nov 17, 2007 11:31 PM by Tesserax
In you haven't already, check out this Port Forward reference: Port Forwarding for the Apple AirPort Extreme Base Station
As you have already noticed, these were instructions for the older 802.11g AirPort Extreme Base Station (AEBS).
Try these for the 802.11n version ...
AEBSn - Port Mapping Setup
To setup port mapping on an 802.11n AirPort Extreme Base Station (AEBSn), either connect to the AEBSn's wireless network or temporarily connect directly, using an Ethernet cable, to one of the LAN port of the AEBSn, and then use the AirPort Utility, in Manual Setup, to make these settings:
1. Reserve a DHCP-provided IP address for the Slingbox.
Internet > DHCP tab
o On the DHCP tab, click the "+" (Add) button to enter DHCP Reservations.
o Description: <enter the desired description of the host device>
o Reserve address by: MAC Address
o Click Continue.
o MAC Address: <enter the MAC hardware address of the Slingbox>
o IPv4 Address: <enter the desired IP address>
o Click Done.
2. Setup Port Mapping on the AEBSn.
Advanced > Port Mapping tab
o Click the "+" (Add) button
o Service: <choose the appropriate service from the Service pop-up menu>
o Public UDP Port(s): 5001
o Public TCP Port(s): 5001
o Private IP Address: <enter the IP address of the Slingbox>
o Private UDP Port(s): 5001
o Private TCP Port(s): 5001
o Click "Continue"
Tesserax, thank you for the detailed instructions. Unfortunately I have not been able to make it work still... What "Service" should I be selecting in the Port Mapping Tab? I have done everything else and still can not get it to work.
Also, I'm quite disappointed so far with the AEBS. It fails to list half the equipment logged on to it in the DHCP Clients table most of the time and it usually does not list anything under the ID tab, my prior router did. I have to guess what is what by MAC address... On top of that it NEVER lists the Slingbox (at least its MAC address is never on the list) even though it is obviously connected since it works flawlessly on the internal network.
Any other suggestions?