RV042 Port forwarding stops working when Firewall is enabled

Hey all,
I have a RV042 router on a single WAN and an internal LAN. I have configured port forwarding as follows:
HTTP[TCP/80~80]->10.0.0.6
HTTPS[TCP/443~443]->10.0.0.6
IMAP[TCP/143~143]->10.0.0.5
IMAP SSL[TCP/993~993]->10.0.0.5
SMTP SSL[TCP/587~587]->10.0.0.5
Everything works just fine when I have the firewall DISABLED. However, when I enable it the behaviour is erratic. 1 out of 10 attempts to connect to ANY port forwarded works. Almost all attempts time out.
Notice that this happens even if using only the default firewall rules (which should be bypassed by the port forwarding as I read in other posts).
My second try was to create firewall rules manually, overriding the default ones. I tried adding rules from source WAN1 (where my connection is) to ANY and to SINGLE IP's on every port. Nothing seems to work.
I don't know what I'm doing wrong, this is really bugging me. I had to turn the firewall off so we can access our servers from outside the office. This shouldn't have to be done.
Do you know anything I could try?
Best regards,
Theo
EDIT:
Just found out that my firewall is getting LOTS and LOTS of Blocked - SYN Flood entries. I think this is why we are having trouble with the firewall. Could this be the problem? I have no idea where all these SYN packets are coming from since they appear with spoofed IPs or come from different bots all over.

Hi Theo, if you want to over ride the default state table, you need to first make firewall rules to block all access then make your permission rules.
Such an example would be-
Action Deny
Service All
Source interface WAN
Source IP any
Destination IP any
Save
Action Permit
Service RDP
Source interface WAN
Source IP -xx.xx.xx.xx
Destination IP - xx.xx.xx.xx
Save
As for your concern about the syn flood, it can be a likely cause of your problems. Does the logging facility of the router give any indications?
-Tom
Please mark answered for helpful posts

Similar Messages

  • 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

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

  • Port forward stopped working after update

    i updated my software and the port forward stopped working and it will no longer allow access to my ip camera.

    Hey Cab,
    Yea, mine stopped working since the update to 10.8.2. It was working fine prior to the update cause I used it at work on a 50 inch Samsung. I undrstand that there was a driver update but I'm not sure why.

  • Ssh Port Forwarding Stopped Working

    I have used ssh port forwarding in the past, and it has come in handy.
    I have recently upgraded to Mavericks, but it does appear that my ssh port forwarding stopped some time before this. The last time I know it worked was 5/14/14, and feel it has worked more recently as well.
    Here's what I do, from my Mac I ssh to my work jump server (port 22, let's say its IP is 11.22.33.44), and my jump server has access to work PC (lets say IP of 10.1.2.3). My work PC has RDP running on it on the common port 3389. I have verified that I can set up a working RDP session at work from another box. Also, I know that my jump server can get to my PC at work as I can ping my work IP if I just ssh straight to my jump server. And I know that there is no firewall stopping me from the jump server as I can also open a telnet session to my work PC on port 3389, without errors.
    So, here's how I have done it in the past and it has worked, but now recently stopped working in Terminal app:
    ssh  -f  [email protected]  -L  3388:10.1.2.3:3389  -Nnv
    The verbose logging shows that it sets up connectivity. If I then look to see if my local port is listening I can type:
    netstat  -an  |  grep  127.0
    I will note that port 3387 is in fact LISTENing and waiting for connection
    I then start my RDP client app, and start a session to "localhost:3387" (I could also use "127.0.0.1:3387", and have, but it does not work either). My RDP client eventually times out. I have turned my firewall off and on, neither way works.
    Does anyone know why this may have stopped working?
    Your input is most appreciated.
    The verbose log shows the following is setup appropriately (with noted modifications to server names and actual IPs):
    debug1: Authentication succeeded (keyboard-interactive).
    Authenticated to somewhere.net ([11.22.33.44]:22).
    debug1: Local connections to localhost:3387 forwarded to remote address 10.1.2.3:3389
    debug1: Local forwarding listening on 127.0.0.1 port 3387.

    Unfortunately I don't have another device to test if RDP is working on my LAN, however, when I check out my network connections and this is what I see after setting up the ssh tunnel and prior to attempting the RDP connection (again names protected):
    my-rmbp:~ me2$ netstat -an | grep 127.0
    tcp4       0      0  127.0.0.1.3387         *.*                    LISTEN
    Then, as it is difficult to catch in the middle of TCP 3-way handshaking, here's what happens after an attempt with the RDP client while it sits and spins:
    my-rmbp:~ me2$ netstat -an | grep 127.0
    tcp4       0      0  127.0.0.1.3387         127.0.0.1.50323        FIN_WAIT_2
    tcp4       0      0  127.0.0.1.50323        127.0.0.1.3387         CLOSE_WAIT
    tcp4       0      0  127.0.0.1.3387         *.*                    LISTEN
    You can clearly see it's attempting to make a connection over the tunnel via my RDP client, but it's being shut down right away. I will obtain a WireShark packet capture and see exactly what's happening. Oh, and if I tried to RDP to a port other than the one I set up the port forwarding tunnel with, RDP would disconnect right away.
    What I'm most interested in is why, without any known changes, other than OS updates, did this work a few months ago, and now it does not?
    I have also tried other test ssh port forwarding, such as to www.apple.com forwarding 8080 on localhost to 80, and others, and none of those work either with web browsers, I assume this is something Apple has done to disable ssh port forwarding/tunneling. Perhaps someone else has bumped into this and found a fix? Please share!
    Also, I have heard that you have to be root in order to set up port forwarding, but clearly this is not accurate, as it worked before, and also as you can see above it worked without root. But I tried both ways, and sadly neither worked.
    Could it by my jump server? Possibly, but others at work do this and it works just fine for them from their Windoze PCs. So can't be that either.
    Perhaps my capture will tell me, I'll report back here with what I discover. Thanks in advance!

  • Port Forwarding Stops Working WRT400N

    Is anyone else having a problem with port forwarding on their WRT400N? I'm forwarding one service (https) and this stops working if it's not accessed after a 10 days or so. The only way to get it to work again is to reboot the router. I’m running the “latest" firmware, which is an oxymoron considering it's been over 12 MONTHS since Linksys updated the code... Which is appalling considering this appears to be their flagship wireless N router.

    I tried the hard reset and still the same problem, port forwarding stops after a period of time.   Sometimes 1 day, other times 10 days.  I have 2 servers on the local network, each running Remote Desktop on port 3389.  I have 2 ports forwarded to get to either server depending on the external port number.   E.g.:  The external port forward is {wan_ip_addr}:33389->{server 1}:3389 to get to server 1 and, {wan_ip_addr}:23389->{server 2}:3389 to get to server 2.  Works great when it works, but then, without error, just the port forwarding stops, and all other router functions seem to continue working.  Has anyone else come across this?  Any fixes?  Help!!!!
    Thanks in advance to any help!!

  • Dashboard stops working when parental controls enabled

    Don't say this is answered because the workaround suggested in another topic does not work. This needs to be fixed soon - very annoying. Here are the steps to reproduce.
    1. create 2 accounts.
    2. enable parental controls on one of them.
    3. set a time limit on the controlled account.
    4. login to the non-controlled account when the controlled account does not have access.
    5. access dashboard.
    6. note that it does not work (no widgets come up and you cannot add them back)
    If you try the workaround it is only temporary and you lose all your widgets the next time the controlled account is locked. I think there is more than one way to reproduce this but is the most common. Also, the workaround doesn't always work. I think this is a serious bug that fails the "it just works" test. This was my first OS X purchase and probably my last if these type of bugs continue to go unanswered.
    Model Name: Mac mini
    Model Identifier: Macmini2,1
    Processor Name: Intel Core 2 Duo
    Processor Speed: 2 GHz
    Number Of Processors: 1
    Total Number Of Cores: 2
    L2 Cache: 4 MB
    Memory: 1 GB
    2 admin accounts
    2 controlled accounts

    I had the same problem, Safari would not open at all in the accounts that had parent controls enabled. I resolved this by going into the admin account and making a copy of safari then pasting it into the library folders as well as the application folders. You can also paste a copy of safari into the other user accounts (desktop) from the admin account. Once that is done, open the parent controls  system  (check the applications to allow) Internet tab then check safari. Hope that works for you

  • 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

  • RV215W router port forwarding not working

    RV215W router port forwarding not working.
    Port forwarding works for a short period of time, then stops working.  Reboot router, works again for short period of time, then stops again.
    I have updated firmware to latest.  I had seen other similar bugs posted for 220 and I think 180, not sure if this router has similar bugs and waiting for fix release to firmware.
    I had recently purchased two, one deployed, will hold off on other now because of issues, and may have to move to different unit if a resolution not found this week.
    Dave Gritten
    IT Director
    Maritime Beauty
    3695 Barrington St
    Halifax NS  B3K 2Y3
    cell 902.223.9685
    phone 902.429.8510 ext231
    fax 902.422.7983
    [email protected]
    www.MaritimeBeauty.com

    It's not just single port forwarding that has bugs, the entire router has bugs and simply does not work as advertised. I have found the following bugs/aspects of this router that just does not work correctly: 1. If you have to open ports, and who doesn’t, this router will eventually stop accepting packets from WAN>LAN. You will still have Internet access but no open ports. A reboot will fix this problem. Oh, by the way, this router has no scheduled reboot option! <--That would be a workaround but a welcome one for this router. 2. Firewall Access rules do not work!! Yep, a Cisco router and basic functionality simply does not work. I called Cisco and even though the tech saw the router not working denied it was a bug! Said we have to do port mirroring, setup a workstation with WireShark and capture packets so we can debug the issues.  That would take several hours. I told him I would have appreciated if Cisco would have debugged the issues with their router BEFORE they shipped the units. Stay away from Cisco Small Business Routers. I wish I had. And if there are any Cisco die-hards out there willing to prove me wrong, just reply to this and please, prove me wrong that the RV series and specifically the RV215W is not JUNK.

  • USB Ports Randomly Stop Working

    I have an HP Pavilion dv6 Notebook with Windows 7. All of the ports, 2 2.0 and 2 3.0 ports, began to randomly stop working. My mouse light would still light up, but the mouse wouldn't work. If I rebooted the entire laptop, all of the ports would come back on for a short period of time before they randomly shut off again. They will also come back on for a short period of time if I close the lid for a few seconds and reopen it. However, lately, the 3.0 ports have stopped working entirely and the 2.0 ports stopping is becoming more frequent.
    The first time I noticed this was when I was testing a micro usb cable (it has stopped charging and I was testing whether it was the cable or the wall adapter). I plugged the cable into one of the 2.0 ports and it gave me a USB surge warning. Other than that, I haven't received any notices. The drivers are up to date. I have uninstalld the root hubs multiple times. I have tried all kinds of Power plans for the laptop. Nothing works. The USB ports still stop working, and it's becoming increasingly more frustrating.

    Hello Abby_Renee,
    With the USB 3.0 port not working, and your 2.0 port working intermittently, I would suggest the following document Troubleshooting USB Connections (Windows 7) for troubleshooting.
    In this document there is a specific option for USB 3.0 ports stop working, which would be the best steps to follow for your 3.0 ports. Now for the 2.0 ports, I would suggest USB device not detected by Windows (no device name in device manager), or the other option is USB devices are detected by Windows but are not working properly. The last two options are dependant on the specific errors you are experiencing.
    Please let me know the outcome of the troubleshooting steps.
    Good Luck!
    I worked on behalf of HP

  • How to know if port forwarding is working?

    i have 2 routers one netgear and the other linksys W4tg45 and i have port forwarding the same on both. now when i connect the netgear i am able to access the website from outside the LAN and when i connect the linksys it is not working anymore. is there a way to do diagnostics on the linksys to see that the port forwarding is working fine? charbel

    Try to update firmware on linksys router, that might make it work. You can download latest version from www.linksys.com/download

  • Why does AirPort Extreme stop working when I plug in a USB hard drive?

    Why does Airport Extreme stop working when I plug in a USB hard drive?  The USB drive has its own power supply.  I've tried isolating the hard drive from Airport using a powered USB hub to no avail.

    The USB port on the AirPort Extreme is borderline as far as its ability to supply adequate power to a hard drive. Another way of saying the same thing is that this is not a high power USB port, like you would find on a computer.
    Your 2TB drive likely requires a bit more current than the USB port on the AirPort Extreme can supply. It is also possible that the drive's firmware may not support a network USB connection....only a "local" connection to a computer. Check with Seagate support on that possibility.
    Try using a powered USB hub with the 2TB drive....and make sure that the drive is formatted correctly in Mac OS Extended (Journaled) or FAT32....which the AirPort Extreme USB port can accept.

  • My iPhone 5s sounds stop working.i did not do anything it just stop working when I tried to turn on my music player all the sounds is not working I already check the volume and it is not also muted :( what happened can anyone solve my prob

    Hello everyone my iPhone 5s sounds stop working.i did not do anything it just stop working when I tried to turn on my music player all the sounds is not working I already check the volume and it is not also muted :( what happened can anyone solve my problem please

    Hey Kirby17,
    Thanks for using Apple Support Communities.
    If you are not getting any sound from the speaker, follow this article.
    iPhone: No sound or distorted sound from speaker
    http://support.apple.com/kb/ts5180
    Ensure that there is nothing plugged in to the headset jack or the dock connector.
    If the iPhone is in a protective case, make sure that the speaker port isn't blocked by the case.
    Make sure that the speaker and dock port aren't clogged with debris. If necessary, clean it with a clean, small, dry, soft-bristled brush. Carefully and gently brush away any debris.
    If an audio issue occurs when using a specific application, try testing other applications to see if the issue persists.
    If the iPhone is paired with a Bluetooth headset or car kit:
    Try turning off Bluetooth.
    If you experience difficulties with the Bluetooth feature, follow these troubleshooting steps.
    Restart the iPhone.
    If restarting doesn't fix the issue, ensure that your iPhone is updated to the latest version of iOS.
    If the issue is not resolved, please contact Apple Support.
    Have a nice day,
    Mario

  • Why does my line-in audio port quit stop working while recording?

    My set-up is a bit confusing, so I'll try and be very specific.
    I record into Garageband via the following set-up:
    Microphone(s) run into TASCAM 4-track -> RCA-to-Stereo Cable runs out of TASCAM into MacBook Pro via the single audio port.
    This generally works fine for several hours, but the last 3 times I've had a recording session, the audio signal has dropped to virtually nil without any warning. At this point, even yelling into the microphone (with the TASCAM max-ing out) will only produce 1 volume bar in the "Line-In" system preference screen. At best, it sounds like a very quiet whisper.
    My microphone is working (works while recording to tape) as does my cable (RCA - to - Stereo) when used in other situations. Any ideas as to why this is happening? Am I tripping some sort of internal line-in volume...protector? (Is that even a thing?) Or do I need a new audio port?

    funny how to one seems to have an answer for this, I just posted my own issue, audio in line port just stopped working after update.

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

Maybe you are looking for