Airport Express G getting Port Forwarding to work from Airport Extreme N

I have an Airport Extreme N connected to a cable modem. I have an Airport Express G in another room, connected to a Local Ethernet Network. The AE G is setup as a WDS Remote to the AE N. Connectivity works and all is well.
What doesn't work is when I try to forward ports from the AE N to a device/system connected (via ethernet) to the AE G. The kicker is the port forwards work from "inside" the network. Outside they don't. I have been able to forward ports to anything connected to the N directly or wirelessly.
Any thoughts on what the proper configuration of the AE G or the AE N to get port forwarding to work from the AE N through to the clients of the AE G?
I have DHCP, and the clients of the AE G are getting IP addresses and working as they should.

I checked that. I can forward ports all day long to anything connected directly (or wirelessly) to the AE N. Anything connected to the AE G, ports won't forward. For some reason the AE G in bridge mode is not letting ports forward through.
Thanks for responding, though.

Similar Messages

  • Cannot get port forwarding to work on EA6500

    Hi,
    I have an EA6500 to replace the old WRT54G. I have an Apach server on my PC. On the WRT54G, I could easily set port forward to the server, it was working fine. But on the EA6500, I simply couldn't get it to work any more. What am I missing?
    TIA

    Thanks for the reply.
    As it turned out for some "security" reasons, EA6500 port forwarding only allows access from outside of the network, but not from netwrok behind the router.  So annoying, however I found this work around
    http://community.linksys.com/t5/Wireless-Routers/EA6500-NAT-Redirection-Bug/td-p/583820/highlight/fa...
    look for poster sflick1's solution, it really works. 

  • Cannot get port forwarding to work - what am I doing wrong?

    Hi All,
    I am sure I am doing something wrong, but can't see what.   All I need to be able to do is to port forward to one of my virtual machines web port on my file server.
    So, scenario is:
    Windows 2012 R2 Server.    IP address: 10.0.0.2      I have a VM running on there called spatial - it's IP address is 10.0.0.17
    Before moving to Windows 2012 R2 server and virtualization - I had multiple servers and to port forward, simply changed the listening port of IIS to another port from standard - say 81.  Then in my router, port forwarded web traffic to port 81 on that
    server - worked like a charm.
    Now however, when I have tried to do the same thing (10.0.0.17 web server listens on port 81) - the page times out.  If I leave it at port 80 - the server2012 IIS page answers.
    I guess I need to create some sort of gateway on the 2012 server to allow traffic to flow through to port 81 on the VM - but not sure how to?  Can anyone help?  Is there a simple walk through guide someone has written in order to achieve this -
    as I am sure is a very common request.  I have googled, but can't find exactly what I am looking for.
    thanks.

    Hi,
    The Hyper-V 2012r2 virtual switch have the extension security ability, please use the following PowerShell cmdlet to confirm your IIS vm virtual switch not enable the related
    security settings:
    Get-VMSwitchExtension -VMSwitchName "virtual switch name"
    =================================================
    For example:
    Get-VMSwitchExtension -VMSwitchName "External network MSFT"
    Id                 
    : EA24CD6C-D17A-4348-9190-09F0D5BE83DD
    Name               
    : Microsoft NDIS Capture
    Vendor             
    : Microsoft
    Version            
    : 6.3.9600.16384
    ExtensionType      
    : Monitoring
    ParentExtensionId  
    ParentExtensionName :
    SwitchId           
    : 0686a779-c79c-4fd0-9971-f9eb330ca089
    SwitchName         
    : External network MSFT
    Enabled            
    : False
    Running            
    : False
    ComputerName     
      : SERVERLAB-02
    Key                
    IsDeleted          
    : False
    Id                 
    : E7C3B2F0-F3C5-48DF-AF2B-10FED6D72E7A
    Name               
    : Microsoft Windows Filtering Platform
    Vendor             
    : Microsoft
    Version            
    : 6.3.9600.17042
    ExtensionType      
    : Filter
    ParentExtensionId  
    ParentExtensionName :
    SwitchId           
    : 0686a779-c79c-4fd0-9971-f9eb330ca089
    SwitchName         
    : External network MSFT
    Enabled            
    : True
    Running            
    : True
    ComputerName       
    : SERVERLAB-02
    Key                
    IsDeleted          
    : False
    ===================================================
    The related KB:
    Create Security Policies with Extended Port Access Control Lists for Windows Server 2012 R2
    http://technet.microsoft.com/en-us/library/dn375962.aspx
    Enabling Hyper-V Extensible Switch Extensions
    http://msdn.microsoft.com/en-us/library/windows/hardware/hh598144(v=vs.85).aspx
    Enumerating Hyper-V Extensible Switch Extensions
    http://msdn.microsoft.com/en-us/library/windows/hardware/hh598146(v=vs.85).aspx
    Hope this helps.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • SA 540 Can't get port forwarding to work.

    Now that the DMZ port doesn't seem to work, I have placed our Web and CRM server on a VLAN. I have created a firewall forwarding rule -> WAN to LAN HTTP allow always and pointed it to the internal IP address.
    When I type in our domain name in the browser I only get the Cisco remote management page, no forwarding to the web server.
    What am I doing wrong?
    I have tried to disable the remote management, but that still doesn't change anything. (btw, how do I change which port the RMON uses, it's grayed out in the setup page)
    SA 540 firmware 1.0.39

    No it does not work from outside my devise, I just get to the RMON page, no forwarding to my Web server at all. I've taken all FW rules away and just have the WAN to LAN allow HTTP "ip address of server" but still nothing.
    I got confirmation that the DMZ/Optional port does not work, I can't SSL from our Apple computers to our Network, and now it seems like we can't get our Web or e-mail servers working either if there is not port forwarding. On top of this, it now also seems like the SA 540 is blocking EDNS packets, slowing down our DNS server. Please tell me that there is something to be done, it can't be that Cisco have put a "Pro" devise out where only 9 out of 10 ports work and that you can not host Web, email or CRM servers because there is no port forwarding, not to mention it only supports IE browsers for SSL.
    I don't mean to sound cranky, but we have spend so much time trying to get this devise to work, please help. (I wish I could give you some logs, but logging doesn't seem to work either)

  • WRT110 - still can't get Port forwarding to work

    Here's the deal: Vista PC behind WRT110 in PPPOe mode which is behind a successfully bridged AT&T Westell modem/router (but it's not in DMZ mode). I've setup a static IP on my computer and enabled port forwarding to it in the router. Then I test port forwarding and still fail the test. On my Westell modem, it says I can share my (external) static IP with my router. Would that do anything helpful? Can you suggest anything else helpful? Thanks so much!!

    Mort wrote:
    You can use the Static IP under WRT110 .... using Internet Connection type ....
    If the port forwarding is not working then reset & reconfigure the router ...
    Thanks for your reply! If my modem is bridged, how do I know what my router's static IP address should be? Would it be the same as the modem?

  • Can't get port forwarding to work.

    I have the old white UFO airport extreme. v 5.7
    When I have port mapping to a particular LAN IP, let say 80 public and 80 private, and I setup that particular computer to use that LAN IP, that computer cannot connect to the internet. I have to use automatic DHCP, DHCP with manual address doesn't work. Any ideas?
    On the "Network" tab in the airport config, I tried both "Distribute IP addresses" checked and unchecked. Same thing, I cannot get it to connect if I manually assign the IP address of the computer I want it to port to (within the System Preferences -> Network - Built-In-Ethernet).
    I remember having less difficulty getting this done with a cheap netgear router and on windows NT with apache...

    When you manually assign the information to your computer you should use values similar to these:
    IP address: 10.0.1.201
    Subnet mask: 255.255.255.0
    DNS servers: 10.0.1.1
    Router/gateway: 10.0.1.1

  • Cant get port forwarding working, please help :(

    I bought an airport extreme yesterday, and since then ive been trying to get port forwarding to work. I've set it up before on other routers, and while its always been a hassle, this is the first time where I might just give up and take the router back. I've been searching the boards for solutions, and ive implemented several of them without success, and a call to apple's tech support got me nowhere. Im sure im just using the wrong number or setting somewhere, but I just cant seem to find it.
    One suggestion i read was to set up the routers connection to my modem manually, instead of through dhcp. When I switched from dhcp to manual, i noticed all the prior numbers except dns servers stayed entered, so i wrote down the ones from when it was set for dhcp and typed them in. My manual setup is:
    I.P.: 68.197.191.59
    subnet: 255.255.224.0
    router: 68.197.160.1
    dns: 167.206.245.68
    167.206.245.69
    every other setting i left on the default.
    the dhcp range is 10.0.1.2 - 200
    One entry recommended a static ip. I originally set one up with the dhcp reservation feature, but then another post said your ip should be outside the dhcp range. Not sure if either method is better, but ive set my system with the following static ip:
    i.p: 10.0.1.201
    subnet: 255.255.254.0 (i was unsure what to enter here, so i chose the same as the routers)
    gateway: 10.0.1.1
    in port forwarding i made an entry with 60000 for the 4 public/private tcp/udp and an ip of 10.0.1.201 (i have tried many other port numbers in the odd chance that the one i picked at random might have already been in use)
    I left every other setting on the defaults. The nat settings (a setting im not familier with) is current set for enabled with the default host box above it empty.
    I should mention, my pc is wired to the router. I am using utorrents port checking site, as well as canyouseeme.org. Neither can ever see my port, one simply says not open, the other says connection refused.
    I hope someone out there can help me with this, as the router is great with this one exception, and I'd rather not return it.

    For starters, it's probably not a bad idea to "factory reset" your device since it sounds like you've had a lot of people giving you different advice. This isn't to say that you've been given *bad advice* but, it may make things easier for a trouble-shooter if you start over from a "known" state.
    That said:
    You need to setup manual port mapping. The problem is, when somebody from the outside tries to access your computer, the Aiport (for lack of a better analogy) isn't expecting any visitors; so it turns them away. ---That matches what you are seeing from canyouseeme.org etc...
    Your error was when you "made an entry with 60000 for the 4 public/private tcp/udp and an ip of 10.0.1.201" Essentially all that will do is make a mapping for one port. Port "60,000" which to my knowledge, isn't used by anything.
    You have to tell the Airport specifically what "outside" ports (each and every one) that you want routed to what "inside" ip address.
    I use:
    Public TCP: 22,80,443,27900,13405
    Public UDP: 123,7777-7783, 13405,6881-6999
    Private IP Address: 10.0.1.201
    Private TCP: 22,80,443,27900,13405
    Private UDP: 123,7777-7783, 13405,6881-6999
    This enables: telnet, http, ssh, bittorrent and unreal tournament from the outside and routes ANY AND ALL TRAFFIC from those ports to my PC at 10.0.1.201 on the inside.
    If I ran AIM, or ICQ or one of those things, then you need to add the ports that that system uses to the list also.

  • How to get Port Forwarding to 8080 working on HH2

    Hi,
    How can I get port forwarding to 8080 working on my HomeHub2?
    I have a QNAP TS219P NAS connected via wired Ethernet to my HomeHub2.
    This has a Web Administration facility that should enable me to access & manage the NAS over the Internet.
    I have set the NAS to have a fixed IP address of 198.162.1.100 and enabled a dyndns account to point to my ISP WAN IP. I then used Application Sharing on the HH to forward all traffic to 8080 to the NAS device (called "Kermit" in my case).
    However, using http://mysite.dyndns.org:8080 simply brings up the admin page of the Home Hub.
    Despite the HH telling me the port is forwarded correctly, http://www.canyouseeme.org reports the port as - "Error: I could not see your service on nn.nn.nn.nn on port (8080) ...Reason: Connection refused"
    My HH firewall is set to "Default" (Allow all outgoing connections and block all incoming traffic. Games and application sharing is allowed.), but I have tried disabling it and this made no difference at all.
    I know that dyndns and port forwarding are working in other respects, since I also set the NAS up as a Web Server with a simple home page, and forwarded port 80 on the HH through to the NAS. Requests over the Internet for the http://mysite.dyndns.org:80 home page work fine...
    There's nothing in the HH Event log that I can make sense of and I'm going mad...
    Is anyone able to talk me through some good ideas of how to progress this?

    Another thing I thought of- did you setup the port forwarding to forward to your named IP address or to the hostname?
    I would recommend setting the port forwarding to your named IP address:
    http://192.168.1.254/app_config.lp?be=1&l2=0&l0=2&l1=4
    In this menu (Application Sharing -> Configuration, select "User Defined" in Device. A textfield entry box appears below device and hardcode 192.168.1.100 in there).
    Finally, any logs on the QNAP for your external connection attempts? - Could it be passing through the HomeHub and then get rejected by the QNAP?

  • Port Forwarding not working after 7.7.1 Firmware update

    I bought the new 6th generation Airport Extreme today, and after I set it up, everything worked great.  I have a VoIP phone that needs to have traffic on port 5060 forwarded to it, and that worked just fine as well. 
    However, I then updated to the 7.7.1 firmware, and the port forwarding stopped working.  I tried a hard reset of the Airport and re-entered all the settings, but it still didn't work.  I spent about 30 minutes on the phone with 2 Apple support people who tried hard, but couldn't help.  They also couldn't find a way to download the 7.7 firmware, so there was no way to downgrade.  They suggested I go back to the store and exchange it for another one, which I did, and now it all works again.
    Has anyone else had issues with port forwarding on 7.7.1?  I'm just wondering how I'll ever be able to update the firmware, since failure means having to get a new Airport.

    Huh,
    turns out the problem went away with another restart of the Mac Mini. I'm still uneasy about it though, as I do not understand how it went from working to not-working over night in the first place. But, at least for now, the problem seems gone.
    Thanks for commenting.
    Cheers
                Niels Olof

  • Port forwarding stops working several hours after reset

    I have a WRT350N (fw v. 1.03.2).  It's connected to an Alcatel ADSL modem (PPPoE configuration).  I've configured port forwarding to allow HTTP and SSH into a linux box on my home network (static IP).  I am able to get to the linux box from outside for the first few hours after I set up the configuration, but a few hours later I am no longer able to get to it from outside - port forwarding stops working though the settings remain as I'd left them.  Over the course of various attempts I've had the external connections just die (404 errors, host not found, etc) and sometimes the connection went to the router - getting the WRT350N login prompt (remote management is turned on, but on port 8080, not 80, so this was unexpected).
    The only way I've found to resolve this is to reset to factory defaults and reconfigure.  Then it works again for a few hours and shortly is again not forwarding.  I've tried other ports (VNC, RDC, telnet, SMTP) and the forwarding stops working on all ports at the same time.  My home machines are able to get out to the internet with no problems.
    I thought the router had a hardware flaw so i replaced it with an identical model yesterday, and sure enough, today I'm again stuck without external access to my home website.
    Any thoughts or suggestions would be welcome.
    Thanks,
    Nick

    I was able to trace the problem to torrent downloads.  It seems the router wasn't handling all the concurrent connections when handling torrents.  I haven't had problems since i stopped downloading torrent files.  I did add a static port mapping and configured utorrent to run on a single port on a machine with a static address but haven't had cause to download any torrent files since then, so i don't know if that will fix the problem.
    That being said, i've had no issues since i stopped the torrents.
    HTH
    Nick

  • Port Forwarding not working on new Home Hub 4

    Hi all,
    I'm trying to get port forwarding going on a new Home Hub 4, specifically so I can access my Netgear Stora through its web interface on my LAN.
    I've set the rules in port forwarding for the following ports:
    Port 80 is HTTP Server
    Port 443 is HTTPS Server
    Port 21 is FTP Server
    Port 22 is SSH Server
    All these are now open and connect to Stora, which has an address supplied by DHCP.
    However, when I check with various online port checkers, none of the ports are open and checking the trouble shooting logs of the BT Home Hub shows that the connection is being rejected. This is a sample of the message that is shown:
    IN: ACCEPT [57] Connection closed (Port Forwarding: TCP 192.168.1.69:22 <-->86.141.184.236:22 [184.72.89.72:42894] CLOSED/TIME_WAIT ppp1 NAPT)
    What can I do to make port forwarding work? I can't change the IP address of the Stora as I need to get into it via its web interface to do that.
    I can navigate directly through Explorer to the files on the Netgear Stora NAS but not through the web interface.
    Can anyone help?
    Thanks.

    i think by applying a static DNS i got it working, not 100% sure yet. edit: yep that worked, everyone can connect once again.
    Message Edited by briantoxicity on 01-01-2008 04:59 PM

  • E2000 Port Forwarding Stops Working

    I am using port forwarding for running a webserver. All is working fine. After a random number of hours or days, the port forwarding stops working. I can get in and look at the settings and they are correct. I can then change something on the port forwarding screen and resave it and it starts working again.  Do I have a bad unit ?

    Webserver might not be set to static IP. Try setting the webserver to static IP first, then make sure that static IP is enabled in the Port Forwarding screen of the router's web-based setup page. Also, protocol should be set to BOTH (TCP-UDP). You can also try having less firewall/AV restrictions on the web server (or none at all) and set MTU to 1400.

  • Airport Express 2nd WAN Port light always on, even when nothing is connected.

    My Airport Express 2nd WAN Port light always on, even when nothing is connected.
    Is this normal? The Airport utility also said that I didn't connect anything to the port - when there is a lan cable connected from the main Airport Extreme.
    The computer can connect to the WiFi from the Airport Express properly, but with blinking yellow and no internet connection, also it cannot obtain the ip address.
    After setting the Airport Express to the Bridge mode, the computer cannot access to the Airport Express anymore, with "Connection Time Out" error.
    The Airport Express was 3 days old, and was working properly until today. There is also one blackout today because of the storm.
    Had reset the Airport several times, didn't solve the problem.

    Hi again. That is a good idea. Check if router can grab an ip from your modem since wireless local connection through the router is working. If it can grab an ip and works fine on wireless, then you might have a problem with the ethernet ports. You might want to try assigning an ip address on the wired connection and see if ip of router is pingable. If really not working at all, possibility that router is not working properly anymore.

  • Has anyone ever plugged into the airport express to get online?

    Want to plug my xbox 360 into the airport express to get online so I don't have to move anything around.
    Right now my modem & router is in bedroom, & the airport express is in the living room (w/xbox and speakers) to extend wireless signal and throw music to speakers in living room.
    I can move it, just lazy and then won't be able to use speakers, and don't want to buy xbox wireless adapter.....
    It's already a bridge, it would make sense that I could plug in? maybe not ;}
    airport express/ aluminum powerbook g4   Mac OS X (10.4.8)  

    If you have the AirPort Express Base Station (AX) set up as a remote base station in a WDS configuration, then, yes, you can connect the Xbox 360 to the AX's Ethernet port for Internet connectivity. If it's setup as a wireless client, then no.

  • Port forwarding not working on WRT54G v5 Firmware Version: v1.02.2

    Hi
    Yesterday i updated firmware on my WRT54G v5 from v1.00.1 to v1.02.2 and now port forwarding does not work.
    I have 2 PCs connected to my router. Both PCs have static ip  (192.168.1.103 & 192.168.1.105). DHCP server in the router is ofcourse disabled.
    For some reason i can not get port forwarding it to work. The weird thing is that
    ALL requests are now forwarded to 105 regardless how i configure.
    * I have set up different port forwarding rules that points to my 103 PC.
    * I have put the 103 PC in DMZ.
    * I have disabled DMZ and removed all port forward rules.
    Still ALL requests are forwarded to 105??
    What i am doing wrong? Why does it default send everything to 105?
    Note that I had no problems with port forwarding before the upgrade.
    Everything was working fine.
    I upgraded because i wanted a fix for "DynDNS abusive updates".
    I have seearched the forum for tips and tried setting MTU size to 1396 and shutting down my entire network and then restart everything. Also tried to uncheck "Block Anonymous Internet Requests" but still same behaviour.
    I really need help!!
    Thanks
    D_M

    well it is weird...anyways try resetting the router back to factory default settings and reconfigure it...check whether it works for you or not.

Maybe you are looking for