HH5 port forwarding not working !!

I have recently moved to BT Infinity, all was good. Installed my Synology DS212 with its previous working configuration and it worked fine for several days (have all the logs)
The incoming backup started failing and upon investigation it appears that port 873 is no longer available. This has been established with ShieldsUP and canyouseeme.org
I have tested other ports shown as ok on the ShieldsUp report and they, such as port:6690 (Synology Cloud), work correctly when  entered into the hub via advanced settings.
There are no issues with Dynamic DNS. Each modification has been saved and to be sure I have rebooted the hub after each one.
Simply is this problem caused by:
The firmware update BT Home Hub 5 (Type A) | Software version 4.7.5.1.83.8.173.1.6 | Last updated 18/04/14
A change in BT's port blocking policy.
Accidental blocking of ports by BT.

An update
Have since been in contact with a BT support supervisor after much wrangling with the first line support. Finally after much re iteration of the status and tests I had repeatedly done and tested I was informed that it was an update error that may be fixed in the future. However I was told that by implementing my own router I would be able to access the ports needed. Having now purchased a Draytek 2860n and set it up on a different broadband connection with the same equipment and tested it I moved it onto my BT Infinity, changed the connection and gateway to match and, yes you are there before me, the ports are no longer available. Not only are BT either blocking or 'throttling' the service ports they are too ashamed or ignorant to come clean.

Similar Messages

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

  • 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

  • HH3 Type B port forwarding not working.

    Hi there.
    I have searched absolutely everywhere for a solution to my problem before posting here. Basically port forwarding isn't working at all on my HH3 Type B router.
    I've read all about the problems people have had with the Type A's but as far as I see nobody seems to have a problem with the Type B in regards to port forwarding or loopback.
    I've set up port fowarding on many different routers with many different ISP's so I don't think it's something I'm doing, or rather, not doing but you never know.
    These are the steps I take when setting up port forwarding:
    Firstly setting up my static IP (obviously only needed to be done once) which I've chosen one outside of the routers DHCP range as I've always done in the past. Then I open the router screen, go to Settings / Advanced Settings / Port Forwarding / Supported Applications and click "Add new game or application".
    I then enter a name, change "Copy existing game or application" to "No", and then change the "Protocol" to UDP or TCP as needed (also have tried using "Any" too with no luck). Next add a "Port Range" for example 12345 - 12345 then add "Translate To" 12345 - 12345 (port ranges obtained from portforward.com per application) then click "Add" and repeat for additional ports as needed.
    Once that is all done, click "Apply" then go to Port Forwarding / Configuration or go to Home Network, select the applicable device and choose the newly added application from the "Port Forwarding" drop down list (and choose applicable device if doing it from Port Forwarding / Configuration). Click "Add" once application is selected.
    Add additional applications where needed then finally click "Apply" to store the forwarded ports.
    Close router page and port forwarding should be fully setup and working.
    That's basically how I would do it anyway, but I also checked on portforward.com and it says pretty much the same and on these forums as well as a few other sites and I see nothing different but port forwarding still isn't working.
    In my router "Event Log" it does show "The Port Forwarding entry of [xxx.xxx.x.xx] has been added or modified.".
    My Firmware version is V100R001C01B036SP03_L_B. Last updated 19/05/13.
    I have no firewall on my pc and the one enabled on the router is set to default but have also tried disabling it. Have tried enabling DMZ as suggested in various places with no luck and have tried changing UPnP settings again with no luck.
    So if anybody has any suggestions I am all ears because this is bugging me so much as there are a few applications and games that require port forwarding and are pretty useless without it really.
    Thank you.

    If you follow the instructions on this page, it should work. Please see note about CG-NAT.
    Port forwarding problems
    There are some useful help pages here, for BT Broadband customers only, on my personal website.
    BT Broadband customers - help with broadband, WiFi, networking, e-mail and phones.

  • E4200 port forwarding not working (v1 1.0.05)

    Hi there.
    I'll try not to rant too much, but I've had nothing but problems with this 'supposed' high end router... and when I tried calling Cisco I got the old yee-ha to cough up $30 for tech support on a $200 router I got 10 months ago (/rant).
    Anyway, following several speed drop issues with my router, I factory reset about 5 times. I later read in the internetz that QoS on these routers was causing the speed to fall to half no matter what settings are used, so I disabled QoS. This time I seem to have steady speeds, but no port forwarding method I use works! Used to work fine, but now Single PF, PF Range or anything else I can think of fails miserably. Even DMZ can't seem to open ports...
    I am extremely disappointed in this router and please, don't advise me to factory reset: I've tried, it doesn't work and quite frankly I have way too many devices to painfully reconnect to not send me over the edge.
    Please, if anyone has any idea what's going on, your help is more than welcome.
    Thanks
    -ts

    technosinner wrote:
    My setup is pretty simple: a Docsys3 modem through my ISP, piped to my Cisco E4200, and a few computers and devices connected to that, all on the same level (no switch or hub).
    To my knowledge the modem doesn't filter or route anything, and I don't need to login or connect to my ISP - cable internet with direct filtering on the modem. I might have missed something but here is a question: if I open a port, will it show open even if there is no application to "receive" the connection? I'm asking because I'm starting to wonder if my server might be a bit fussy...?
    To protect your router against possible DNS Rebinding Attacks, certain actions will not work from behind a router.  Typically, doing this is for testing purposes. What you can do to test if a certain application (port forward) works remotely, is to do it from outside your network.
    To test this functionality, this must be done from the outside of the router (remote area).  This includes even if the “Filter anonymous Internet requests” is unchecked.
    check the site below for reference:
    http://blog.trendmicro.com/trendlabs-security-intelligence/protecting-your-router-against-possibl-dn...

  • Router Port Forwarding not working since Mavericks

    I have an iMac sat behind a BT Home Hub 3 (an ADSL router, if you're not aware), with several ports (POP3, SSH, HTTP, etc) from the outside world forwarded via the hub to my Mac. Since installing Mavericks (from Snow Leopard), NONE of these ports are now open.
    They're open on the Mac, and another machine on my home network can use them locally, but from outside the network, they're hidden. Shields Up shows them as Stealth.
    Things I've tried:
    Rebooting everything.
    Setting the Home Hub up again, forwarding all the ports again.
    Turning all the sharing off in Mavericks and then back on.
    Trying the same services on different ports.
    Trying different services.
    Turning off the Mac firewall.
    Turning off the router firewall.
    Trying the Mac on another IP address and reforwarding everything to the new one.
    Putting the Mac in the DMZ.
    I can forward ports to other devices on my network (e.g. my NAS) and they work fine, so port forwarding isn't completely broken on the router
    Here's the thing though...
    On a completely separate network, on a separate Mac (a 2012 MacBook Pro) that went from Mountain Lion to Mavericks, also behind a BT Home Hub 3, EXACTLY the same thing is happening. No ports can be forwarded to the MacBook Pro, but all the ports are open to the local network.
    Any ideas? I'm pretty sure this must be a bug in Mavericks as I can't see anything else it can be.

    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.

  • Port Forwarding not working correctly (BTHomeHub 2...

    I recently picked up the new Call of Duty: Black Ops 2 for my pc. Playing online mathes works fine, however trying to join with my friends and connect with them for co-op fails to work. My NAT setting in game was listed as strict and my friends (both on BT) had moderate so I assumed it had to do with that.
    After some research, I found out I had to forward ports to my PC which I've done but yet the game still refuses to connect. Sometimes I get lucky and, after forwarding the ports, I load up the game to be shown NAT: Open and I'm able to join my friends quickly, but after about one minute the game disconnects and my setting changes back to Strict.
    Now my problem is either one of two things:
    a) My ports are opening but are closing after a minute or two.
    b) Something is wrong with my router.
    It should also be noted that one of my friends actually had his NAT setting turn to Strict but he was easily able to forward his ports and get NAT open again. I copied exactly what he did and it didn't work. If it helps, I've also tried setting my computer up with a static IP and port forwarding to the exact IP address I set and not the device name, which still didn't work.
    Thank you for any and all help. I really hope I can get this sorted soon.

    Port forwarding is not likely to be the issue, there are many posts regarding NAT( Network Address Translation) issues, all over the Internet.
    Here are some examples from this forum.
    http://community.bt.com/t5/forums/searchpage/tab/message?filter=location&location=forum-board%3AOthe...
    If you look at my port forwarding help page, there is an address you can go to to see if a port is still open. Just choose any one of the port numbers associated with your game, and see if it still shows as open.
    There are some useful help pages here, for BT Broadband customers only, on my personal website.
    BT Broadband customers - help with broadband, WiFi, networking, e-mail and phones.

  • 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

  • RVS4000 Port Forwarding not working

    I am trying to forward ports through my RVS4000 however I have been unable to get it to work.
    I have enabled the firewall and set the ports mapping to the correct address and enabled them, however I can't reach any devices.
    All advice gratefully received :>)
    NM

    When troubleshooting Port forwarding on any device we use tools like Nmap on a outside machine looking in at your network, and http://www.canyouseeme.org/ to see if on the server or device you are using if the outside world can see the ports open. There is no known bug or issue with port forwarding on this device as long as you are on the latest firmware. If Nmap and canyouseeme is not showing the ports open you need to look at the internal workings of the network. I.E. does the same ports work on the inside of your network, second is what is between the RVS4000 and the Internet. Other routers or switches, Modem, and ISP. We have seen everyone of the previous devices block ports. When using Nmap or canyouseeme the ports should be open.
    Do you have a topology of your network and what ports you are trying to port forward?
    Cisco Small Business Support Center
    Randy Manthey
    CCNA, CCNA - Security

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

  • WRT54G Port forwarding not working

    Ok this is an odd problem. Ever since I got this router I have had issues with the port forwarding.
    I am forwarding 3389 TCP to 192.168.1.101 check box is enabled. The .101 address is given out by DHCP ( only set to give out 4 IPs). The forwarding did not work at all. I have configured dozens and doezens of routers with no issues except this one . It is Version 8. After a lot of reading on the net someone posted a similar issue where they could not forward ports to static IP addresses ONLY IP's given out in the DHCP range. Strange? yes you bet. So I decided to try it and sure enough I changed my 2 internal computer IP's to use DHCP and forwarded the ports to the IP of the computer I wanted ( 192.168.1.101) and it worked! How silly is that, it wouldn;t forward to static IP's. Well now the problem is back. Except this time if I forward to static IP's OR IP's given out in DHCP nothing works. As a test I moved the .101 computer into the DMZ and still nothing. This is beyond annoying. problem is this is sitting at a clients house in another city and I only have access to it via the web admin. I tried backing up the configuration and then restoring it. The restore worked but didn't fix my issue. I still can't get the forwarding to work. Resetting the defaults is not really an option cause I am not in the same city as the router.
    I have about 7 other SMC routers that have been working happily for 5 years straights. Why is this thing so mental? I did upgrade to the latest firmware before installing the router. Ayone have any suggestions as to why the forward doesn't work?.
    By the way I enabled the logs and watch them as I was trying to remote into the computer ( 3389) and sure enough it's hitting the router ok as it shows up in the logs. The web server is not working either, nothing is getting forwarded.
    No there are no firewalls at all installed on the computer I am trying forward to. Can anyone shed some light on this?

    Access router setup page ...uncheck block WAN request under security tab .... also check the updated firmware on the router ....

  • Port Forwarding not working (PLEASE HELP!)

    I have been trying to port forward a Minecraft server for fun, however the port will not open no matter how many times I try. Here's what I've been doing: Enter 192.168.1.1 in browser and log in. Once on the home screen -> advanced -> port forwarding rules -> add port -> tcp -> any source -> single destination: 25565 (default port for a Minecraft server) -> add port -> udp -> any source -> single destination: 25565 -> apply -> fire wall settings -> typical security -> port forwarding -> select my computer I am on -> select the port forward I had previously created -> add -> resolve now & apply. The status shows as active, but when I use a site like checkmyports.net, it states that the port is closed.Is anyone else having port forwarding issues? What's the problem? Did I miss something?   Thanks in advance.

    KevinC45 wrote:
    I have been trying to port forward a Minecraft server for fun, however the port will not open no matter how many times I try. Here's what I've been doing: Enter 192.168.1.1 in browser and log in. Once on the home screen -> advanced -> port forwarding rules -> add port -> tcp -> any source -> single destination: 25565 (default port for a Minecraft server) -> add port -> udp -> any source -> single destination: 25565 -> apply -> fire wall settings -> typical security -> port forwarding -> select my computer I am on -> select the port forward I had previously created -> add -> resolve now & apply. The status shows as active, but when I use a site like checkmyports.net, it states that the port is closed.Is anyone else having port forwarding issues? What's the problem? Did I miss something?   Thanks in advance.Do you have an application on the internal device that is listening on port 25565?  Port will only report as open if there is a listening appliaction on the port on the destination device. Try something simple that we know works e.g. remote desktop which uses port 3389Enable remote desktop on your computer - typically right mouse click my computer, select properties, select remote settings, select remote, select Allow connections any version.now logon to router select firewall settingsselect port forwardingspecify ip address of your machineselect Remote Desktop from services - will show tcp any -> 3389 udp any -> 3389select addselect apply Now try checkmyport.net and test port 3389If it doesn't show as open then it sounds like a firewall issue In either case you'll probably want to go back in and turn off remote desktop access unless you really want to access your machine from the outside. let us know the results. 

  • Port Forwarding not working properly.

    Router: WRT54G V.6
    Firmware: 1.00.9
    Basically, my port forwarding does not work. Using this link (https://www.grc.com/x/portprobe=55554), I can test a port to see if it's open or not.
    Whenever I open a port on the router, it displays the port as "CLOSED", while I am aiming for "OPEN". This is a new router, and this problem also was occuring on my old V.2 one. Strangly, when I first tried opening the ports, it worked fine. Next day, it appeared as close, and no other settings were changed.
    Any help out there? If any more information is needed, please tell me.

    Only if grc reports the port "STEALTH" you have no port forwarding. If it is "CLOSED" then the port on the computer you are forwarding to has the port closed. You must check the settings on the computer where you forward to to see whether the port is open or not. Simply setting up a port forwarding does not open a port. It simply forwards everything to the ip address configured in the port forwarding. Thus, if the port is closed there it is closed and not open.

  • Port Forwarding not working between Fios Router and Netgear R6200 AT ALL

    For the past two days I've been trying to forward port 80 and port 9000 from my Fios Router to my new NetGear R6200 Router and absolutely nothing is working. I need these ports open and forwarded as I need to forward them to my surveillance system from my R6200. The problem is that port forwarding is not working AT ALL. I've literally tried EVERYTHING. I turned my firewall off completely, enabled DMZ, changed my R6200 to a static IP, turned off uPnP on both sides, and reset my router to factory settings. I'm all out of patience and ideas. This is exactly why I went out and bought the R6200 in the first place, Verizon's Routers are atrocious.
    Hardware:
    First Router (Gateway): Verizon Fios Aciontec  MI424WR
    Second Router: NetGear R6200 Dual Band 802.11AC Router
    Surveillance System DVR: Zmodo H9114 DVR
    OS: Windows 8 Pro 64-Bit
    At this point I'm willing to try anything. Fios customer support knew absolutely nothing and wasted my time and if a tech is sent to my house I'm sure the same exact outcome will occur. I recall someone saying that cloning the MAC of a different REV. worked for them but I don't recall the details. Any help would be greatly appreciated.

    #1 As addressed in http://www.dslreports.com/faq/12506
    The DHCP Server in the secondary router should be off.
    #2 You only forward from the main router directly to the computer that you want to host on.
    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.

  • Port forwarding not working

    I've searched over this forum and several others and I've seen several questions like mine but still no definitive answers.
    I have a brand new Time Capsule (mid-2011) with Firmware 7.5.2 setup behind a cable modem. I have a static IP address assigned by my ISP and I have a Mac Mini Server edition recently upgraded to Lion Server hooked via ethernet to the Time Capsule. The TC is set up to DHCP reserve 10.0.1.2 using the Mini server's MAC address. I have been assured by the tech support people at GCI Cable (my ISP) that they do not block or restrict ports in any way. However, despite having all of the service ports set up to forward to the Mini server I can never access the server from outside (or inside) the network. I get the following results from a port scan:
    Port Scan has started…
    Port Scanning host: xxx.xxx.xxx.xxx
               Open TCP Port:           25                         smtp
               Open TCP Port:           110                        pop3
               Open TCP Port:           143                        imap
    Port Scan has completed…
    Apparently, some ports are working (mail) but all of the others fail to show up. I've tried deleting all of the forwards and entering them manually, turning them off-rebooting-on again, using the server tool in Lion to configure the proper ports but I've failed on all accounts. I had the same problem with Gen 2 Airport Extreme which I just replaced with the TC in hopes of solving the problem. Does anyone have any fixes to suggest? Am I missing something basic? Screen shots from the Airport Utility are attached below...
    Main Port Mapping Screen
    Web Service Setup
    Mail Service Setup
    iCal Service Setup

    Sorry, but I don't have a Windows computer handy at the moment so this will have to come by memory.
    Run the AirPort Utility.
    Select your TC, and then, select Manual Setup.
    Go to the Wireless tab.
    Change Router Mode to: Off (Bridge Mode)
    Click on Apply.
    Allow the base station to restart.
    Since you have done this before on another computer this should be familiar to you.

Maybe you are looking for