Port Mapping control page missing under firmware 7.3.2

The reference to "port mapping" on page 55 of the manual "Designing AirPort Networks Using AirPort Utility Mac OS X v10.5 + Windows" is now missing following upgrading my Time Capsule to firmware 7.3.2 - see:
http://manuals.info.apple.com/en/DesigningAirPort_Networks10.5-Windows.pdf
Could anyone out there shed some light on where this functionality has gone?
Further to this can anyone advise where I might access firmware v 7.3.1 so that I can regain this functionality?

This query can be disregarded.
It appears the v7.3.2 firmware upgrade reset the 'Connection Sharing' to 'Off (Bridge mode)'.

Similar Messages

Time Capsule port mapping is broken for L2TP Servers behind NAT config.

I'm hoping that someone here can refute the below bug assertion... am I missing something?
There is a bug with Apple’s Time Capsule/Airport Express Base Station (TC/AEBS) rendering L2TP servers on the LAN unusable:
When TC/AEBS is used as a router providing NAT services to the LAN, it will NOT under any circumstance provide port mapping services for 500/UDP, 1701/UDP, & 4500/UDP making L2TP VPN servers on the LAN side of TC/AEBS are unreachable from the WAN/Internet side.
*The conditions for my tests*:
3 different external networks used for all tests: MacBook Air at home on TWC network, the Air on AT&T mobile dongle, & CentOS server at ThePlanet.
MobileMe configuration was removed from both the TC/AEBS & Snow Leopard Server on the LAN.
I used port 501 for my control-test; spot checks of other ports worked as well, though they were all < 10000.
Simultaneous local and server monitoring of port traffic using
tcpdump -vvv -i en0 -s 0 -X port 500 or port 1701 or port 4500 or port 501
The TC/AEBS was configured to forward UDP ports 501, 500, 1701, & 4500 received from the WAN interface to the Snow Leopard Server on the LAN.
The port forwarding was accomplished both 1) manually via AirPort Utility, and 2) automatically via Snow Leopard Server’s Server Preferences utility. Each was tested separately.
*The tests*:
Netcat with the following commands, in turn, on the server:
nc -l -u 501
nc -l -u 500
nc -l -u 1700
nc -l -u 4500
which causes traffic to the udp port specified to be dumped to std out. Provides a confirmation of the tcpdump output.
On the various external networks, nc -u WAN-address-of-AEBS.example.com 501 to send UDP packets on port 501. The output of the nc -l 501 command and the server-run tcpdump confirmed that packets left the client and made it to the server as expected. Remember, 501 is the control-test.
For each test permutation on ports 500, 1700, & 4500, no packets made it to the server.
Based on some web research, I’m not the only one to have found trouble with this configuration, but I haven’t been able to find any conclusive tests.
I’ve filed a bug with Apple (#7720101) and encourage you to do the same.
Message was edited by: WebMarc

Confirmed here. This only seems to be a problem with Airport 7.5.x firmware though - I find the older TCs running 7.4.2 work as expected even with BTMM / MobileMe services active.
I'm so glad you posted this - I haven't found it mentioned anywhere else and was beginning to feel very alone with this problem. I also found that having two TC 7.5s in the mix - one at both ends - also results in no response to SSH or Remote Desktop ports.

Port Mapping Problem with AEX

I have a new Airport Extreme and a problem that did not exist with the Airport. I connect a Toshiba network camera to an Airport Express, set as a WDS remote, with the netcam connected to the wired ethernet port of the Express. I can see the netcam, which also functions as a web server, on the internal 10.x.x.x address, and have reserved a discrete 10.x.x.x address via the MAC/DHCP reservation function of the Extreme. Just like the older Airport which did this without a hiccup, I should be able to map a port (e.g. 1200) on the public IP to port 80 of the internal 10.x.x.x address, then access the netcam on the internal network from any browser (http://67.x.x.x:1200). My cable modem is just that: no router involved other than the Airport Extreme. I'm using the latest Extreme and Express firmware, and am either missing something with the new Leopard firewall, overlooking something else, or dealing with a product flaw. Any help is appreciated and Happy Holidays.

I have forwarded the port (have tried several different ports actually) in what I think it the correct way: using the Airport Utility, connected to the Airport Extreme, and, under advanced options, selected port mapping, entered the public TCP port of 1200, then the private 10.x.x.x IP address of the netcam (which I can access from the internal network with no problem), coupled with the private TCP port of 80. I then attempt to access the netcam from the Internet by entering http://my cable modem IP address:1200 (or another port to which I've attempted to map). This method worked for two years with the Airport, but, with the Extreme and Leopard (simultaneous transition), I'm stumped. After reading other about other port mapping problems, I reserved an IP address for the netcam based on its MAC with no positive results. I also set the firewall through the Security icon in System Preferences to allow all incoming connections. Thanks for taking the time to respond.

AEBS Gigabit 802.11n FW 7.2.1 - OS X 10.5.1 Port Mapping HELP!!!!

Hi
I have a AEBS with Gigabit Ethernet upgraded to Firmware 7.2.1. I am running OS X Leopard 10.5.1 and I am unable to successfully forward ports. Every time I query a port that I believe to have mapped successfully it appears closed using canyouseeme.org.
I have followed numerous instructions, but they all seem to be instructions for Tiger, I'm wondering if a setting has been missed. I have successfully assigned a static IP address to my machine but still the port appears to be closed. I do run the Leopard firewall using specific applications option (the third one), but I have also tried it with the firewall off and it still hasn't changed anything, the ports are always closed.
So now I'm pretty much stumped. Has any one actually managed to get a setup similar to mine working, with the ports being open? All advice appreciated.
Thanks
Message was edited by: dalyboy

Hello dalyboy. Welcome to the Apple Discussions!
Try the following to see if it will help ...
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 host device.
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 (what Apple calls Ethernet ID if you are using wired or AirPort ID if wireless) hardware address of the host computer>
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): <enter the appropriate UDP port values>
o Public TCP Port(s): <enter the appropriate TCP port values>
o Private IP Address: <enter the IP address of the host server>
o Private UDP Port(s): <enter the same as Public UDP Ports or your choice>
o Private TCP Port(s): <enter the same as Public TCP Ports or your choice>
o Click "Continue"
(ref: "Well Known" TCP and UDP ports used by Apple software products)

Airport Port Mapping problems...

I have an AIRPORT EXTREME firmware 7.6.1. I'm trying to get it to open port 443 in port mapping and it says it's open and when I port scan it's not. Am I missing something? Please see the enclosed image...

Hello ,
I have the same troubles got the latetest updates on AE en soft 6.0
i cant get my ports open !
it realy s...cks !!
i spend alreddy more dan 3 days to get it working , whit no results !!
i have 3 foscam Ip cams who doenst work anymore outside my LAN !
i tried to get it work whit 5.6 but than i got huge faillure on my AE drops out and need hard reset !
I hope ther are some techies from apple who can solve this troubles !
HELP HELP HELP HELP HELP
why do the change someting that works before fine !
before the updates everthing works fine
the big boss i passed away Rip
and the house is collapsing !

Where is my 'Port Mapping' tab

I'm trying to open a port on my computer and have followed the instructions I have found here and on the net. 'Go to airport utility/click manual setup/click Advanced/ choose 'Port Mapping'.
I have no 'Port Mapping' option under Advanced.. I have only 'Statistics', 'MobileMe' and 'IPv6'.
Can someone point out what I'm doing wrong? Thanks
Using Airpot Utility 5.4.2 and a TC firmware 7.4.2

Lars Hansen wrote:
I'm trying to open a port on my computer and have followed the instructions I have found here and on the net. 'Go to airport utility/click manual setup/click Advanced/ choose 'Port Mapping'.
I have no 'Port Mapping' option under Advanced.. I have only 'Statistics', 'MobileMe' and 'IPv6'.
Can someone point out what I'm doing wrong? Thanks
Using Airport Utility 5.4.2 and a TC firmware 7.4.2
In AirPort Utility in the "Internet" pane, do you see a button for "Configure Port Mappings..."?

EH&S: EA-PLm activation. EH&S missing under SAP menu

Hi all,
The EA-PLM extension (in a development environment)was activated (not by me) but EH&S folder is missing under logistics in the SAP menu.
I had also made this activation (by me) before in a sandbox environment and I was able to see EH&S in SAP menu without problem.
In Tcode SCPR20PR, I've checked EA-PLM-IMG, EA-PLM-MENU and EA-PLM-AKH and the logs show all green statuts.
So, do you have any idea to explain why I am not able to see EH&S in the SAP menu and to resolve this problem?
Thank's,
Best Regards,
Ludovic

Hello
it seems to be a problem which is well known in the EH&S world. I have done an inquiry and found these pages:
http://www.saptechies.com/faq-dangerous-goods-problems-after-ehs-upgrade/
which provides this usefuil help (hopefully; i did not control):
"If the EA-PLM switch is active, however the menu path is still not displayed, follow the instructions contained in Note 855959."
Furtheremore I found this link:
http://www.akiboks.com/text/93b25125-f5ab-48ef-a59a-76d4ccb9b841/1/pdf
Hope that this helps.
With best regards
C:B.

Port Mapping / port forwarding - help please...again...

Hi,
I am trying to use port forwarding/port mapping but after numerous failures to access my computer from an Internat connection, I am seeking advice or guidance.
I have a 2011 Apple Time Capsule, and under the Advanced tab on Airport utilities, Port mapping I have chosen +
it then comes up with a box in which I have entered the following:
Service - drop down menu (number of options...but have been advised on other threads to leave as is)
It then has 5 boxes:
Public UDP port(s) - 9080
Public TCP ports(s) - 9080
Private IP adress    - 10.0.1.x
Private UDP Port(s) - 9080
Private TCP Port(s)   -9080
note I have enabled NAT port mapping protocall. My ISP has advised that I cant use port 80 for some reason...but all others should be ok
note also the 10.0.1.x is a static address i have assigned to teh camera.
I have a dns provider, and when I use the URL on my LAN - I can access the camera....but as soon as I tryu to access via the WAN - it is unable to reach the server.
Other points - the TC is in normal mode (i.e. not Bridge)
Does anyone have any idea if I have set port mapping up correctly; any way i can test, any ideas how i can fix this??
I have tried this on a number of forums thus far - but no success to date.
Welcome all and any help!!!

LaPastenague wrote:
Have you reset the camera web page to use 9080?
i have checked again and in teh advances settings of my camera - it asks for HTTP port, HTTPS port, and for Nata Traversal it asks for an alternative HTTP port.   I have entered 9080 against all of these.
The TC is in normal mode ie as a router.. what modem do you have in front of it? Is it in bridge? Does the TC get the public IP or does the modem route the address as well? You will have no success via double NAT.
not sure what brand the modem is - but i can confirm it is set up as a modem only with both the router and wireless functions turned off.
The Modem is not in Bridge mode - neither is my ATC. The ATC gets the public IP address via the adsl modem. so double NAT should not be an issue
When you say you can access the camera using URL on lan, is that using the new port 9080? Please give explicitly what address you use.. (you can hide the full public address) and port.. and AFAIK this should NOT work as the TC would have to handle NAT Loopback which would amaze me if it does. According to all the info around the web the TC has no NAT Loopback and therefore should not be able to handle the address. I need to know therefore the exact address you use
this is actually using the url that my dns provider provides to me as i do not have a static ip address.   albeit this appears temperamental as to when it works sometimes from my LAN. after which it requests user name and password and I can then see the live stream.
one problem I have just noted is that when checking teh DNS setup - it still appears to default to port 80 which my isp has advised i can not use) so i am checking with teh dns provider how i change this.
The good news is port mapping must work on my ATC, as I have just set up my slingbox using their automatic port mapping assistant and it seemed to set up with no issues...i have also just confirmed that the stream can be viewed on the internet.

Linksys App bug with port mapping

So I have the Linksys app installed on my Android phone. My router, WRT1900AC, is set up using port mapping. The port mapping is for an ssh app to control my 3 web servers. Each servers internal port is 22 and each servers external port is 20, 22, and 23 each one mapped to port 22. When signed in the the routher itself, not through the app, I can configuer these ports fine. However when I attempt to configuer these ports or the ip appress through the app, I get an error saying the port is in use. It seems the app is seeing the three servers using the same internal port and throwing an error.
Has anyone else experienced this?

I recommend you not use ports in the first 1000 unless they are for the standard server they are specified for. This is a good IT policy.
Example:
Port 22 External to internal IP Address of SSH server port
Port 21 External to internal IP Address of FTP server port
Instead use undefined ports in the higher end of the range.
Example:
Port 10001 External to internal IP Address of SSH server port
Port 10002 External to internal IP Address of SSH server port
The Linksys stock firmware will only do DNS proxing which isn't great for server networks.
For this application I recommend OpenWRT McWRT v1.0.5:
https://github.com/Chadster766/McWRT/releases
Install luci-ssl to enable SSL access and open router port 443 for standard secure remote access.
FYI:
Unless you have a USB to TTL cable for firmware recovery I recommend always flashing OpenWRT using the Linksys stock UI. This will put the Linksys stock firmware into the alternate boot image in case manual recovery is needed.
Do not delete the LAN, WAN and WAN6 interfaces. Pay attention to OpenWRT notices that say things are not reversible. OpenWRT can be unforgiving in those circumstances. If you have the $9.00 USB to TTL cable it won't matter because you can always load firmware through the boot loader.
OpenWRT McWRT has some issues:
https://github.com/Chadster766/McWRT/issues
Please remember to Kudo those that help you.
Linksys
Communities Technical Support

DPC3941t Gateway - Port Mapping

After swapping out my TC8305 gateway for the DPC3941t yesterday, I changed the local IP configuration from 10.0.0.1 to 192.168.1.1, as my home network is configured that way. My NAS and security cameras did not reconnect, and I did a hard reset on them and reinstalled with their setup files. After the first one was installed and working properly, and I was able to access it, I tried to access the gateway home page and it was blocked. I restarted it and was then able to log in. I installed the second camera and the same thing happened. The event log showed 88 entries of port mapping and port deletion. I was told by tech support last night to hard reset the gateway and start all over. I did the reset and am back at 10.0.0.1, with my NAS and cameras unreachable. The NAS and cameras worked fine on the TC8305, and the TC8305 worked fine until the last upgrade. They scheduled a technician to come back tomorrow but they don't do router configuration, only swap one out for another. Is there any fix for this other than my going out and buying a separate modem and router? Thank you for any enlightenment out there. Kat.

JayInAlg wrote:
My personal recomendation is to your your own high end router so you are in complete control of your network settings and port forwarding. If you don't have Comcast digital voice phone service, then you certainly can purchase your own modem also. If you do have CDV, then get the gateway place in bridge mode and connect your own router to LAN port 1. You will always be fighting this situation if you keep Comcast's gateway, which is deigned for basic internet funtions.I tried to work with the Comcast equipment due to my history of buying modems and routers that quit working shortly after their 1 year warranty expired. For the last 7 years, when a modem quit working, I called Comcast and they brought me a new one. I upgraded routers several times, never spending too much on one. I had the TC8305c gateway for the past 2 years and never had a problem with it until last month. However, now it is time to go back to the two box system. You are absolutely right. I bought an Arris/Motorola SB6183 modem and a Netgear WNDR4500 router yesterday. Due to Murphy's Law, I did the setup backwards. First, I put the gateway in bridge mode. Then set up the router. Then I disconnected the gateway and connected the modem to the coax, and ethernet to my computer. Did the activation through the browser, shut down the modem, connected the router and powered up both boxes. Everything is working fine. The NAS and the security cameras came back online without any reconfiguring. The guest network is on. Everyone is happy. Took less than an hour. Thank you for pointing this out to me. I hope the modem and router last longer than the 90 day warranty. I bought the protection plan, although they won't bring me a new one like Comcast did. Wish me luck. Kathy

Port Mapping Filezilla FTP Server

I just got a new AirPort Extreme Base Station (802.11n). I must say, I'm pleased for the most part. I'm having an issue with remotely connecting to my FTP server inside the network though.
Setup:
The whole this is connected as follows:
Cable Modem - AEBS - Wired Windows PC
On this windows PC I run an FTP & HTTP server. Both are functioning properly as they always have, both on the localhost and within the network.
The HTTP protocol is working fine. I have port 80 mapped to my PC's static IP of 10.0.1.100. I can browse my hosted site from a remote PC no problem.
Yet, from a remote PC I am unable to fully establish FTP communication. I have port 21 mapped to my PC's static IP as well. Communication seems to be happening; the remote PC gets prompted for their username and password. Shortly after (within a timeout time), the FTP server replies that it cannout open the data channel.
Data:
Here is the Remote PC's log of the FTP session:
Status: Connecting to $server.com ...
Status: Connected with $server.com. Waiting for welcome message...
Response: 220 $greeting
Command: USER $username
Response: 331 Password required for dave
Command: PASS $pass**
Response: 230 Logged on
Command: SYST
Response: 215 UNIX emulated by FileZilla
Command: FEAT
Response: 211-Features:
Response: MDTM
Response: REST STREAM
Response: SIZE
Response: MLST type;size*;modify;
Response: MLSD
Response: UTF8
Response: CLNT
Response: 211 End
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is current directory.
Command: TYPE A
Response: 200 Type set to A
Command: PASV
Response: 227 Entering Passive Mode (10,0,1,100,16,141)
Command: LIST
Response: 425 Can't open data connection.
Error: Could not retrieve directory listing
Solutions Attempts:
I have tried mapping the FTP data port (20) to the server's static IP to no avail. I even went as far as setting the server as the default host (DMZ); this didn't work either.
Am I looking at a fresh firmware bug here or am I missing anything? Thanks for your help.
P.S. No changes have been made on the server and every other no name router I've used has successfully port mapped the server; it's definitely the new hardware.
Windows PC Windows XP Pro
Windows PC Windows XP Pro

1. Try to connect to your FTP-Server in AKTIVE-Mode,
it's a setting in your FTP-Client
Most all FTP clients are defaulted to passive mode, and I want to connect without asking all users to change their settings.
Previous routers did not require anything like this, why would this new base station obfuscate the setup?
2. Don't use the same AirportXtrem internet
connection (for testing your FTP-Service) where is
your FTP-Server behind. I don't know why, when I try
to establish a connection I could not go out and come
back through my AXtrem on the same way.
Try it with a Modem, UMTS or with another internet
connection.
I don't know exactly what you're talking about. Please explain better or with more details.
Windows PC Windows XP Pro

How do I use Port Mapping?

b How do I use Port Mapping?
(This document will assume that you are using and ABS/AEBS/AX as an internet router and have DHCP & NAT turned on.)
Sometime you may want to offer access to a computer on your AirPort network to users on the internet, whether it be a web site, or for file sharing, or just remote access for yourself when traveling. If any of these sound like something you want to do, then you need to understand how Port Mapping works.
b AirPort as Firewall
Most of the time your AirPort base station will not let any traffic into your network which did not originate from your network. It will let everything out and replies to your traffic back in, but it will not let sessions initiated on the internet side of the base station in to your network. This is what is referred to as the "NAT firewall" capability of the base station and it provides effective protection for your network from the internet. What Port Mapping does is poke a hole in this wall to allow certain type(s) of traffic into the network and direct this traffic to a specific computer on the network. In the firewall world this is commonly referred to as an "inbound proxy" or "inbound translation" rule or "PAT" (Port Address Translation) in the router world.
b The Need for Manual Addressing
Since a Port Mapping entry in the base station configuration requires an inside private IP address to be specified, the computer to which to mapping entry applies should always have the IP address specified in the mapping entry. Thus, DHCP should not be used for a computer offering services on the internet as the Port Mapping entry will no longer work if the target computer's IP address changes. In general, an Apple base station's DHCP server will try to assign IP addresses in the 10.0.1.2 to 10.0.1.200 range. IP addresses above 10.0.1.200 can be Manually assigned to computers and other devices on the network up to 10.0.1.254. 10.0.1.255 is reserved (it is the broadcast address for the 10.0.1 subnet). To Manually set up the TCP/IP information for a Macintosh running Mac OS X, go to System Preferences -> Network and "Show" the appropriate interface (Ethernet or AirPort) and click on the TCP/IP tab. Select "Configure Manually" and enter the following information:
IP address : 10.0.1.201 (or whatever address you decide to use)
Subnet mask : 255.255.255.0
Router IP : 10.0.1.1 (the AirPort base station LAN IP)
DNS server : 10.0.1.1, or whatever DNS server IP your ISP uses
After making these changes verify that your computer can still access the internet and local resources on the LAN before continuing.
b Port Mapping a service
In our example we will be hosting a web site on a computer which we have given an IP address of 10.0.1.201. Basic web sites are accessed using the HyperText Transport Protocol (HTTP) and this protocol typically uses port 80 to communicate. In order for others to see the web site, we must configure a Port Mapping entry in the base station configuration to not only allow the web browsers in, but to tell the base station what IP address the web server is using. The Port Mapping entry has three parts: Public Port, Private IP, and Private Port. In this case you would use the following values:
Public Port : 80
Private IP : 10.0.1.201 (this is the computer hosting the web site)
Private Port : 80
In order to access the web site from the internet, users must reference the base station's WAN port public IP (determined by looking at the base station configuration summary page in the AirPort Admin Utility). Since this address may change over time, you might want to use a Dynamic DNS service to simplify connecting for your users.
Sometimes the port you wish to use may be blocked by the ISP. In this case, use a different non-standard Public Port number for the service, but keep the Private Port standard. In the above example, if the ISP was blocking port 80, you could potentially use 8080 instead, so:
Public Port :

Public Port : 8080
Private IP : 10.0.1.201
Private Port : 80
Your users would then have to enter "http://<publicIP>:8080/" (where <publicIP> is the public IP address of the AirPort base station) to access the web site.
b Internal Access
It should be noted that when accessing these services from within the network you cannot reference the Public IP/Public Port, but rather you must use the Private IP/Private Port. Thus, "http://10.0.1.201:80/" in the above example.
b Limits and Options
There is a maximum of 20 Port Mapping entries that can be made in an Apple base station configuration. If you use an AirPort Extreme or AirPort Express base station there is an option which can be helpful in the case where you need many ports opened to a single computer. This is the "Default Host" option. When using this it is not necessary to use Port Mapping at all as all ports will be opened to the specified "Default Host". This is found in "Base Station Options". The default IP address for the "Default Host" is 10.0.1.253. You may change this IP address. The target computer must be Manually configured as specified above with the same IP address. Since all ports are now open to this computer, you should enable and configure the Mac OS X firewall on the default host computer to protect it from intruders.
b Useful Related Links
<a href="http://docs.info.apple.com/article.html?artnum=52002>"Designing AirPort Extreme Networks: Manuals</a>
"Well Known" TCP and UDP Ports Used By Apple Software Products
IANA Port Number Assignments

Photoshop submenu is missing under tools menu in bridge

I Have downloaded the new Photoshop CC 2014 and updated Bridge. Trying to send some pictures from Bridge to photoshop as layers is not possible because the photoshop submenu is not available under tools.
Checking Bridge preferences > start up, does not show Photoshop.
Checking Library> Adobe > BridgeCC > start up, does not have Photoshop in it.
Can somebody help me restore the Photoshop submenu.
Thanks
Rene.

Today when I start Bridge it had a message asking if I want to install a "Photoshop extension”.
So my problem is solved.
Thanks.
René Born 
[email protected]
El 22-06-2014, a las 14:58, DavyAllan <[email protected]> escribió:
Photoshop submenu is missing under tools menu in bridge
created by DavyAllan in Adobe Creative Cloud - View the full discussion
I have the same problem when trying to do a photomerge.
Work around by opening files than doing 'add open files'
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at https://forums.adobe.com/message/6484656#6484656
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page:
To unsubscribe from this thread, please visit the message page at . In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Adobe Creative Cloud by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

Need help with port mapping on Airport Utility 6.1

Ive been trying to port map on my TC with Airport Utility 6.1 and failing miserably. Port still closed. Can anyone advise where Im going wrong? Am trying to set up my home camera to be viewed outside.
I managed to key in the ports etc under Network and Port Settings. But nothing works. I'm tearing my hair out.
Any suggestions to try would be helpful.
Thanks

Use the 5.6 utility.. it is much easier and I think works better.. although you cannot load 5.6 directly into 10.8 the version for Lion actually works fine.
Download 5.6.
http://support.apple.com/kb/DL1482
Download unpkg
http://www.macupdate.com/app/mac/16357/unpkg
Open the AU 5.6 dmg and drag the pkg over the open unpkg.. it will create the directory on the desktop. You can either run it from there or drag the utility to your utilties directory.
Take screen shots of each step. Post them here.
That way we can tell you where it has gone wrong.
What port exactly does the camera need open?
How are you connecting remotely?
ie do you have a fixed public IP?? If not how are you getting IP?
Is the TC the only router in the network.. it is irrelevant unless the TC is the one and only router.

Port Mapping problem with a Snow Base Station

I wish to enable port mapping with my Airport Snow Base Station. (SBS) I am using an Earthlink Efficient Stream 5667 DSL modem to my SBS. I am running firmware version 4.0.9 and connecting with 10.4.3.
So -- enabling port mapping requires that the IP address on my 10.4.3 computer doesn't change, and that I then map the ports. However, I can not manually assign an IP (say 10.0.1.201) as my 10.4.3 can not connect using either "DHCP with manual address" or "manually" (where the router and subnet mask match the DHCP assignment)
What should I do?

Do not use the "DHCP with manual IP address" - that is a mode not supported by most networking devices on the market.
What you should do: on your Mac, open System Preferences->Network->Show Airport->TCP/IP tab. Select to "configure manually". Then enter the following parameters:
- IP address: 10.0.1.201
- subnet mask: 255.255.255.0
- router/gateway IP: 10.0.1.1
- DNS IP: use either 10.0.1.1, or enter the actual IP address(es) of your ISP's domain name servers

Port Mapping control page missing under firmware 7.3.2

Similar Messages

Maybe you are looking for