WRV200 port mapping problems.

I did the port mapping to enable direct IP dialing from Linksys PAP2 VoIP adapter. It worked fine, untill I replaced the old router with a new WRV200.
The funny thing is the mapping works for some time, then it stops to work. To bring it back to work I have to restart the WRV200 router.
Everything worked fine with old Digitus DN-11005 router. I did not changed the settings in the PAP2 adapter. And, I used the same port mapping settings with WRV200 router. The PAP2 is set to DHCP and static IP is set through static DHCP client list in WRV200.
The only change from the old Digitus LAN settings is a different subnet IP. The old one was 192.168.123.0 the new one is 192.168.122.0
The direct IP dialing is done through WAN of the local Internet service provider. Both locations had the same Digitus router and PAP2 adapters installed with the same port mapping and PAP2 adapter settings. Now with one router changed to WRV200 the system does not work correctly. It looks like the port mapping in WRV200 stops working in about an hour after last usage of this feature.
Static CP Client Lis

I've been busy playing with the issue. Looks, like it is not the port mapping issue, after all.
The LAN is constructed from the WRV200 router and a Surecom EP-805SX 5 port switch connected to one of the router ports. The PAP2 adapter is connected through the switch.
When the PAP 2 appears to be locked it does not make outside calls, and it does not receive them. SIP registering does not work, as well. So, the communication with Internet does not work. In the same time, I can access the web config page of the PAP adapter. To bring everything back to normal I need to pull out and back in one of the WRV200 LAN port plugs. So, reseting of the whole router is not necesary, because disconnecting one of the LAN ports does the trick. What is bugging me is, it works with any of the 4 LAN ports. It does not have to be the LAN port the PAP2 is connected with.
I've noticed, also, a computer connected to the same switch the PAP is connected with has some problem to communicate with the DHCP server of the WRV200 router, from time to time.

Similar Messages

  • 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.

  • 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

  • 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 !

  • WRT54G - IP and Port mapping problems

    I'll set the scenario first so you can understand what i'm trying to do. I have a D-Link 524 configured trough PPoE to get access to internet. It has DHCP enabled (from 192.168.0.100 to .199). I had static ip configured in the D-Link router as 192.168.0.90 and some ports forwarded to my pc that's like 50 meters away from the router, in other office. The thing is, I added a WRT54G v6 router cause the wireless signal from the d-link didn't reach where I am, and some people needed to use it. So, I plugged my pc to the WRT54G, and the linksys to the D-Link. No, my problem is, I no longer have the static ip that the d-link assigned me (the linksys uses the 192.168.1.X range, and the d-link the 192.168.0.X range). Now, if I release my MAC address from the D-link and assing a static ip in the WRT54G, I could fordward the ports I had before in the d-link but in the linksys. The thing is, I can't find a way to assing a static ip in the linksys. And I tried to change the range of ip from the linksys to 192.168.0.X so I can still use the assigned address from the d-link but it didn't work, I couldn't access the linksys neither the d-link after changing the address, didn't get internet either, so i had to reset the linksys. After all of this... what the hell do I do Azureus can't connect, or any other P2P app for that matter (cause I had the ports forwarded in the other router, and I can't forward them in the linksys cause I get a dynamic local ip, if I forward them to, say 192.168.1.100 and some day I get assigned 192.168.1.101... well, I assume it won't work as expected)

    The WRT54G does not assign fixed IP addresses through DHCP. You have to set a static IP address on the computer itself instead of using DHCP.
    I would, however, recommend not to use the WRT as router but only as simple access point. Instructions are here. Set a LAN IP address like 192.168.0.2 on the WRT to keep it accessible inside your normal LAN. I think this setup will solve all your problems. You can still use the fixed IP address assignment from the DHCP server on the D-Link and you only have to configure a single port forwarding on the D-Link (instead of two which would be necessary if you connect the Linksys router through its internet port to the D-Link).
    With two access points you can create a roaming network by using the identical wireless settings on both routers (SSID, wireless security, wireless mode). Channels should be different and at least 5 apart. SSID broadcast should be enabled on both. Now most wireless clients are able to move between both access points without loosing the connection.
    Message Edited by gv on 06-01-2008 02:22 PM

  • Port Mapping Problem

    I'm using Filemaker Web Publishing and need to map port 591 to a local computer. I have a static IP address from my ISP but when I enter the info into Airport it doesn't seem to do anything. I've also tried, as a test, to set up personal web sharing and this does not work either. I was successful at setting this up with my old router so I know that this is possible.
    I've given my computer a static IP. I've also tried the having Airport reserve an IP address.
    Any thoughts?

    I'm using Filemaker Web Publishing and need to map port 591 to a local computer. I have a static IP address from my ISP but when I enter the info into Airport it doesn't seem to do anything. I've also tried, as a test, to set up personal web sharing and this does not work either. I was successful at setting this up with my old router so I know that this is possible.
    I've given my computer a static IP. I've also tried the having Airport reserve an IP address.
    Any thoughts?

  • Port Mapping is not working ?

    First of all, sorry for my bad english as it is not my primary language.
    So my problem is that I play Warcraft 3 and that I would like to host some games. To be able to host, I have to do port mapping for the ports : 6112-6119, which I did in the Airport Utility --> Advanced --> Port Mapping. I did it for every port 6112, 6113, etc. But the thing is that when I go on this website: http://www.whatsmyip.org/ports/games/ (Which is a website that tells me what ports are open on my computer), only port 6112 is open. Ports 6113-6119 are closed. Before my Airport Extreme, I had a Linksys and I had no problems with hosting and port mapping, which means it is not my ISP that is blocking the ports.
    Also this is the setup of my internet if it can help. I have an AirPort Extreme wich is connected to the modem in my basement (I did the port mapping on this one) . From this Airport Extreme, I have another Airport Extreme connected to it. I am connected to the second Airport Extreme in bridge mode with ethernet.
    I don't know if this was clear or not lol. Anyway I would appreciate any help. Thank You !

    This is just a guess, but if you still have that AirPort Extreme, you might plug it in long enough to have AirPort Utility do a File >Export Configuration File, then reconnect the Time Capsule and do a File > Import Configuration File.  Once that's done you may have to do a little adjustment to account for the disk drive.

  • Port Mapping is not working on Time Capsule

    I have replaced my Airport Extreme with a Time Capsule for back up purposes, but the Port Mapping functionality is not working as it did on the Airport Extreme.  I have my security camera DVR connected to the network and am using Dynamic DNS to resolve the WAN IP Address.  HAs anybody any experienced  this problem with Time Capsule?

    This is just a guess, but if you still have that AirPort Extreme, you might plug it in long enough to have AirPort Utility do a File >Export Configuration File, then reconnect the Time Capsule and do a File > Import Configuration File.  Once that's done you may have to do a little adjustment to account for the disk drive.

  • Port Mapping Not Working...at all!

    I've been tyring to get port mapping working correctly since I got the AEBS a few months ago. I've scoured all over these forums and the entire internet and found not a single suitable answer. I have my macbook pro setup up wirelessly all works fine except port mapping.
    My macbook is setup up manually with a static IP of 10.0.1.2 and lets say i want to map the port 41952. In the port mapping setup assistant on the base station I leave the service setting on "choose a service", public UDP 41952, public TCP 41952, IP address 10.0.1.2, private UDP and TCP 41952. Then I update and router resets... then I use the network utility to check the ports and they're not showing as open, I've used various internet websites as well and the port comes up closed. What on earth am I not doing? Someone please help! or let me know if you are having the problem as well.
    Thank you for ANY help.

    You are not performing a valid test.
    No, Cable modem plugged into WAN port, the computer i'm trying to open ports on is using a wifi connection with the aebs.
    You can not test the AEBS to see if the ports are open from the LAN side of the AEBS. You must be on the internet (WAN) side of the AEBS to test to see if the port is open on the AEBS.
    ...the computer i'm trying to open ports on is using a wifi connection with the aebs.
    You aren't opening ports on the computer, you are opening ports on the AEBS.

  • Port mapping stopped working using Mavericks

    Hi,
    on Snow Leopard, I had iVPN using port mapping up-and-running.
    Basically using this explanation (https://discussions.apple.com/docs/DOC-3415).
    On Mavericks it stopped working.
    I'm running AE 7.7.2, and Mavericks 10.9.1.
    Tools I tried are iVPN together with a DynDNS setup (also the Personal Website).
    I don't get non of these working anymore...
    Any ideas?
    Regards.

    OK solved, or at least the problem was not with the modem or router.
    Oddly, enough the app I was using to test the port forwarding did not recognize that the ports were open. Nor did the internet via canyouseeme.org. However, when I tried a previous version of the same app, it worked fine.
    I am still using 7.6.1, but I will upgrade the firmware and see if things are still ok.
    Sorry to clog up the boards with what turned out to be a non-issue. I'd erase this post if I knew how.

  • Port Mapping Question

    Well, I thought I had this all figured out...
    About a year ago I set up an older AirPort Extreme Base Station (Version 5.7) successfully to port to an iMac running OS X Tiger Server. As Leopard came out I decided that I wanted to do a little upgrading around the house and purchased the new AEBS along with a Mac Mini to run the new server software.
    I have no problems getting the AEBS set up, but the port mapping just doesn't seem to work correct.
    Right now I reverted back to the old system and seem to be serving just fine on the Mac Mini with OS X Leopard Server... But I'd really like to leverage the new AEBS.
    So, anyone out there can offer some advice on one of the settings I seem to be missing that seems to make this not work?
    Thanks

    It might also be a DCHS/NAT problem...
    Here's a post I added this morning...
    http://discussions.apple.com/thread.jspa?threadID=1320615&tstart=0

  • Is Time Capsule vulnarable with Upnp aka Port Mapping vulnerability?

    As you also might have already heard about this quite huge upnp vulnerablity, I tried and failed to find out if Time Capsule or other Apple's network products are using this bugged libupnp library or not.
    As a backup device it would be quite nasty if someone could hack in to the device and wipe all backups. US-CERT's list of manufacturers does not include Apple, so this is not helping much.
    http://www.kb.cert.org/vuls/byvendor?searchview&query=FIELD+reference=922681&sea rchorder=4
    So what to do, should we turn port mapping protocols off until Apple fixes this problem, or are we already safe with the Time Capsule's latest 7.6.1 version?

    Apple do not use upnp.. they use their own entirely different protocol.. NAT-PMP so whatever the upnp vulnerability is, I doubt apple has it.

  • 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...access home network remotely

    Hello,
    Has anyone successfully established port mapping through the AE (802.11n)?
    SSH access has worked for me but nothing else. Apple tech support was courteous but unable to solve problem.
    I'm trying to get port mapping (port forwarding on other routers) to work for AFP and FTP.
    Any help would be appreciated.
    Greg
    iMac, MacBook   Mac OS X (10.4.8)  

    Hi Greg,
    Thanks for your response. I will try it out.
    Yes, I did get her the new AE 802.11n.
    I am so impressed by it, I would go buy it for myself to add the print server capability, and dual band feature.
    To take advantage of N, I will either get a new Macbook Pro, or a new wireless card for my PB G4, preferrably the former.
    Cris
    Hi Cris,
    I have actually been successful now with AFP too.
    Does your sister have the new AE 802.11n? That's the
    one I have and here's what I did.
    1) Open AirPort Utility
    2) Select Airport Extreme
    3) Menu "Base Station", "Manual Setup"
    4) Select Advanced icon
    5) Select Port Mapping tab
    6) Click "+"
    7) Select a service "SSH" or "AFP" which ever you
    prefer.
    8) For ssh, private tcp port needs to be 22. Public
    IP address should be the IP address of your sisters
    imac on her local network. Private TCP port should be
    22.
    AFP is the same setup as ssh, except the Public tcp
    port should be any unused port number, for example
    5912. (You can get a list of used port numbers here:
    http://docs.info.apple.com/article.html?artnum=106439
    ) and the private tcp port needs to be 548.
    Helping your sister out will be much easier when OS
    10.5 becomes available later this spring and perhaps
    by the end of this month. Go to this link and click
    on the iChat icon. It will show you ichat's new
    capabilities. http://www.apple.com/macosx/leopard/
    Hope that helps,
    Greg
    iMac, MacBook   Mac OS
    X (10.4.8)  
    Powerbook G4 (17")   Mac OS X (10.4.9)  

  • Port mapping converting gui to cli

    Hi,
    I am having an issue with a new office LAN implementation and I was wondering if anyone can help.
    The current setup has a Linksys router and there are port mappings for the servers for a inside and outside port. This has been input via GUI. I am upgrading to a 3845 router and have converted the GUI input to Cisco CLI. This however does not work and the LAN does not behave as it did before.
    The Linksys GUI input is attached.

    Hi @samdilloway,
    A few questions for you:
    Did you check if those servers can go to the internet?
    Is the NAT functioning properly when they go outside?
    Here is a link of a page with the step-by-step process of the port mapping configuration. Make sure you're doing it exactly like that:
    http://kb.linksys.com/Linksys/ukp.aspx?pid=80&vw=1&articleid=21470
    Also, a link of a TSHOOT page for the same problem:
    http://kb.linksys.com/Linksys/ukp.aspx?pid=80&vw=1&articleid=22385
    To be sure, the problem that you have is that users from outside cannot access to the services your mapping, right?
    Let me know your answers.
    HTH.
    Don't forget to rate.
    Rgrds,
    Martin, IT Specialist

Maybe you are looking for