X3500 Port Forwarding Stops Randomly, must Reboot

Hi,
Hoping someone else has come across this and found a resolution...  I have a very new X3500 router setup within a small business.  I have approx 15 port forwarding rules configured - most of which are standard ones such as 80, 443, 25, etc.
For whatever reason, the router randomly (although now happening more frequently - every couple days) is dropping any port forwarding requests.  I can still login to the router's web interface, I still have internet access, etc., it's just incoming connections that seem to stop (I.e. Mail stops flowing and users cannot connect via RDP, etc.).
I can fix this immediately by rebooting the router, however obviously I shouldn't need to.
Linksys Support have advised me to untick 'Filter Anon Internet Requests' and to set the MTU to 1400.  Neither have made any difference.  I'm currently going around in circles with Live Chat again...
Any suggestions?
Thanks.

jononoy wrote:
Hi,
Hoping someone else has come across this and found a resolution...  I have a very new X3500 router setup within a small business.  I have approx 15 port forwarding rules configured - most of which are standard ones such as 80, 443, 25, etc.
For whatever reason, the router randomly (although now happening more frequently - every couple days) is dropping any port forwarding requests.  I can still login to the router's web interface, I still have internet access, etc., it's just incoming connections that seem to stop (I.e. Mail stops flowing and users cannot connect via RDP, etc.).
I can fix this immediately by rebooting the router, however obviously I shouldn't need to.
Linksys Support have advised me to untick 'Filter Anon Internet Requests' and to set the MTU to 1400.  Neither have made any difference.  I'm currently going around in circles with Live Chat again...
Any suggestions?
Thanks.
Yep, recently started having this issue too. Router has been in place for almost a yead and just in the last week its dropping the port forwarding and requires reboot to work.
I tried the same things as you.
Id like to follow this thread for a solution.
I have also just set up another site with the same router - Hope this doesnt happen to that one too.
Cheers

Similar Messages

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

  • 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

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

  • Linksys X3500 - Port Forwarding (limited)

    Hi everybody!
    We have purchased 3 pieces of Linksys X3500.
    One for us and a couple for an installer (our customer) who wants to make a wireless home network (for a couple of end users).
    I have to tell you that we are a distributor for security systems (Tvcc and so on) in our area (north of Milan) and we have a lot of NVR and DVR on our network we need to put on-line as demos.
    Today i start to configure the Modem/Router and i find no prob since i tried to add "some" port forwarding...
    We have about 60 single ports to configure and the page of device is limited to not more than 15 (customized) slots!!
    I was hoping the device was able to allow me to add more slots but it seams to be not possible!
    How can i do?
    (ps: i don't want to add an external firewall to do it!) 

    I wasn't talking about the algorithm of wireless but the one used for manage the priority of the traffic...(when devices are already connected)
    and if there's an external device (hardware) that can do a better job (like a "Lan Controller" but cheapest).

  • 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

  • Time Capsule 2 TB, stops port forwarding and cannot be accessed by AAU

    Hi
    I am having the above problem off and on since purchasing the TC. It is dialing in PPOE (fiber optic), connects fine to internet and feeds internet reliably by wireless and wired connections. It will however stop port forwarding and allowing access by Finder or Airport Util. simultaneously at what appears to be random intervals.
    I can unplug the electric and power back on and all is fixed for a week or so. This of course causes havoc with time machine, web server on the network, vpn service etc.
    I have all the updates on AAU osx and I believe everything possible.
    I have the TC, a mini running osx server 10.6.3, a macbook pro, macbook air (Leopard). All running 10.6.3 except the Air.
    I run time machine on all the computers but usually do it manually to avoid 2 machines accessing the Tc at the same time, though sometimes I forget to turn TM off and 2 comps. may be trying to access TC through Time Mach. simultaneously.
    I also have another wireless router getting the internet and making a wireless network in a separate building.
    I have read all the posts but do not see any clear solution or mention of the port forwarding stopping along with access.
    Any help appreciated. If it's defective my year will be coming up, so I want to figure this out now.

    Hi Bob,
    Yes I did a hard reset in order to set it up. I then used the Airport Utility to give it a Network name and base station name that was different from the Wireless AC one upstairs. I left everything else set to defaults and used 'Create a new wireless network'. Added some passwords and then let it boot itself. It all worked ok but as I mentioned I can then only access this downstairs network. The Wireless AC one then refuses to connect afterwards. The only way I can get the Wireless AC to work is to switch off the Wireless N one and then reboot the Wireless AC.
    Maybe I need to change the DHCP port ranges or something ? Is it correct to have x2 networks ?. I dont see any other option given wireless wont reach and I cant cable between the two to create a bridged network.

  • Remote TC access via port forwarding

    I have been trying to setup my network for remote TC access via port forwarding. Here's my setup:
    Verizon FiOS router (main router, dhcp & nat) -> connected to TC set in bridge mode with a static IP
    I can remotely access the TC using Back to my Mac with no problems, and of course locally on the home network via Wifi.
    Since the TC has to connect in bridge mode, port forwarding is done on the FiOS router.
    If I set a port forwarding rule in the FiOS router TCP,UDP (any) to port 548, it works. However I want to use a specific connection port
    so others can't connect unless they know the forwarded port. BTW, I have remote disk sharing set with Use Device Password.
    So here's what works:
    FiOS Router (TCP any -> 548, UDP any ->548)
    What doesn't work:
    FiOS router (TCP 8990 -> 548, UDP 8990 -> 548).
    Is there any additional setting required for specific port forwarding to work?

    You're my hero!
    I also have my TC in Bridge Mode to my Verizon FIOS Router.  I used to be able to access my TC remotely, but since I upgraded my router (MI424WR GigE), I had forgotten some port forwarding rules I must have established in my old router.  Once I re-created these two port forwarding rules (just like yours), I can remote access my TC (with TC password) again.
    In addition, I have a static host name aliased to my dynamic IP address through dyndns.org (I have the free version, which I don't think is available anymore, but there are other free providers out there) for easier remote access.
    Regarding, Secure Share Disks: with TC password vs a disk password. Is one more secure than the other?
    Thanks!

  • 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

  • IP changes on port forwarding

    I set up port forwarding, port 80 to 192.168.1.4
    Port forwarding works fine.
    After a day or so 192.168.1.4 changes to various IPs. such as
    8.15.17.117, and 63.251.179.13 both will be listed.
    Port forwarding stops working.
    I click <resolve now> and it changes back to 192.168.1.4
    and starts working again. But will change back after a day.
    How can I keep this from happening?

    #1 What is the exact brand and model of your router?
    #2 If you are not on FIOS, what is the brand and model of your modem?
    If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.

  • Teamspeak port forwarding

    I just had FIOS installed today and am in the process of setting everything back up. I have several ports forwarded on to allow for a Minecraft server for my son and a TeamSpeak server I manage. I have set up port forwarding on the Verizon MI424WR router and the Minecraft server is working just fine. However no matter what I do I can't get the Teamspeak ports open. Is there any reason Verizon would block port 9987 on their side or am I missing something here?

    Pookaluchia wrote:
    I just had FIOS installed today and am in the process of setting everything back up. I have several ports forwarded on to allow for a Minecraft server for my son and a TeamSpeak server I manage. I have set up port forwarding on the Verizon MI424WR router and the Minecraft server is working just fine. However no matter what I do I can't get the Teamspeak ports open. Is there any reason Verizon would block port 9987 on their side or am I missing something here?
    All ports are openable using port forwarding rules.  Must be something incorrect about your rule, possibly you said TCP not UDP for port 9987?
    should say
    UDP any -> 9987
    TCP any -> 30033
    TCP any-> 10011
    TCP any -> 41144
    all the other ports appear to be outbound and they should not be an issue
    https://support.teamspeakusa.com/index.php?/Knowledgebase/Article/View/44/0/which-ports-are-being-us...

  • Port forwarding on Sagem 2504 has stopped working

    I've had port forwarding configured and working on my Sagem 2504 router for months without issue.It suddenly seems to have stopped working.I have an unconfirmed suspicion this may be linked to the 3.18Skya4G firmware update - when was this update pushed out?I've tried deleting the rules and recreating them and also deleting/recreating the custom services and the rules. None of the above solves the problem.Someone else is reporting the exact same issue here. 

    Based on Borez' post I tried deleting everything and starting over. This *seems* to have fixed the problem. I believe the steps I followed were as follows:Delete all services and port forwarding rules.Reboot router.Recreate servicesRecreate rulesReboot routerSimilar to Borez the services/rules I recreated were identical to those which were there before - so no apparently good reason why this should have worked.

  • Port forwarding and LAN traffic suddenly stopped working

    My WRT54G was chugging along happily for many months, and suddenly all port forwarding and local LAN traffic stopped flowing. All PCs behind the router on the LAN side can get to all WAN sites just fine, but they cannot ping one another. All of them can ping the router (192.168.1.1) just fine.
    Any ideas?
    Thanks,
    Curtis

    I solved this.  Turned out to not be the router at all, but the accidental enablement of the "Stateful Firewall" within my Cisco VPN client.  Once this option is turned on, the machine gets isolated from the LAN, even when the VPN client isn't visibly running.

Maybe you are looking for