Port forwarding not working between Router & seperate Modem


  1. Posts : 95
    Windows 7 Ultimate x64
       #1

    Port forwarding not working between Router & seperate Modem


    On Thursday (technically it's Friday now in the UK) I was setting up a Synology DS414 for my Church. No problems setting it up, works fine for both PC & Mac over local LAN, however it has a method of setting up Port Forwarding via UPNP or manually via a small and select list of routers. This is where I get problems, if I go to configure a router then it will recognise the Router & although it takes a while (probably at least 5 minutes if not longer), it adds its own Port forwarding to the router but it will fail the test for three of the ports (21, 80, 5000).

    My Church has a frustratingly complex setup, they had a Belkin N+ ADSL Modem Router, changed ISP & had problems with web pages which turned out to be something to do with the DNS servers, changed those to Google and OpenDNS & it worked fine, anyway they decided to change hardware to future proof the system (as it were) didn't carry over the DNS changes that I told them about & had the same web page problems again. However instead of going down the simple route and getting a Router with integrated modem they decided to get two seperate pieces of hardware, the reason being that they wanted the Netgear Nighthawk (R7000) because it had faster WiFi Speeds than its ADSL Counterpart (not that this now matters as the two people that wanted the fast speeds can't get them because the 5GHz network doesn't play nice with concrete walls).

    So using the Nighthawk then required an ADSL Modem so they bought the TP-Link 8817 ADSL2+ Modem with USB & Ethernet. This in turn caused more problems because both had the same default gateway & the person who set it up changed the Nighthawk's gateway to 10.xxx.xxx.xxx because it told him to (it looks sloppy & is harder to remember for non techie people IMO). I set it up properly, Modem was 192.168.0.1 and the Nighthawk 192.168.1.1 with a fixed IP address between the Modem & the Nighthawk, that was set up in the Nighthawk rather than the in the modem.

    Now on my home setup (Virgin Media Superhub 2 set to Modem Mode with a Linksys EA6700), I just set up a port forward in the router and I can generally see it as "Open" from an external port checker app on my phone. This does not seem to be the case on my Church's System. There are NO settings for port forwarding in the ADSL Modem, there is a Firewall and SPI, which are both disabled (the latter being automatically disabled & the former being automatically ENABLED), but this has made no difference whatsoever. Internet seems to work just fine otherwise, but no ports can be accessed externally.

    I have a suspicion that the Modem isn't properly set up as I have noticed its settings seem to indicate that it is in Bridged mode when I thought it should be in PPPoA, the latter requires a Username and Password which I had written down from when I put in one of my old ADSL Modem Routers before they got their new hardware.

    Unfortunately I'm due to go on holiday today for two weeks but it's bugging me why it isn't working as it should. A Modem with a Firewall Disabled should just pass everything straight through to whatever is connected on its Ethernet port, should it not? If so why does it have a way itself to be configured via UPNP? Is this perhaps where the problem lies? Is the ADSL Modem designed to be directly connected to a PC & not to a router? Or should the Modem be set up as PPPoA & the Nighthawk set up as PPPoE with the same ISP credentials for each one?

    Any help would be much appreciated :)
      My Computer


  2. 2xg
    Posts : 2,377
    Win7 & Win8 64bit
       #2

    Hi Steve,

    I don't know if I might have overlooked it in your post regarding your Church's ISP. Are you with Virgin Media same as in your residence?
      My Computer


  3. Posts : 95
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Unfortunately not, I've forgotten who they are with but according to a quick whois search of the domain on the username, it is Broadband Only Limited. But they are effectively Hotchilli Internet since they registered the domain name adslonly.co.uk and Speedtest.net says that's who the ISP is. There are no settings in the Modem for port forwarding, I did disable the Firewall that blocked DoS etc but that made no difference to the port forwarding unfortunately. Like I say I have the username and password so I could pop in at some point during the week & hope that nobody is using the internet when I want to chance things :P.
      My Computer


  4. 2xg
    Posts : 2,377
    Win7 & Win8 64bit
       #4

    Let me do some reading about Hotchilli Communications.

    Also, I'll have to see what type of setup requires for these 2 devices. What's the model of this Netgear Nighthawk.
    So using the Nighthawk then required an ADSL Modem so they bought the TP-Link 8817 ADSL2+ Modem with USB & Ethernet.
    If I were to set this up, typically it should have been on the same subnet - i.e. 192.168.0.1 and 192.168.0.2 (exclude these 2 fixed IPs when configuring DHCP - 192.168.0.3 to 192.168.0.100). Configure DHCP only in one device, disable the DHCP on the other one. This is probably why port forwarding is not working, having 2 different subnets setup in one network.
    I set it up properly, Modem was 192.168.0.1 and the Nighthawk 192.168.1.1 with a fixed IP address between the Modem & the Nighthawk, that was set up in the Nighthawk rather than the in the modem.
    Again... let me get back with you. It might take a little while for me to reply back.
      My Computer


  5. Posts : 95
    Windows 7 Ultimate x64
    Thread Starter
       #5

    Here is the Netgear Nighthawk and here is the TP-Link Modem.

    I never really thought about them both being in the same subnet, I didn't think it really mattered since the Modem ought to just pass everything onto the Router and the router's firewall should be the main firewall through with port forwarding is done.
      My Computer


  6. 2xg
    Posts : 2,377
    Win7 & Win8 64bit
       #6

    My apology for the tardiness, I have been pre-occupied....

    Does this apply for the TP-Link modem? fyi... this is not a recommended setting as it is not safe at all.
    There are NO settings for port forwarding in the ADSL Modem, there is a Firewall and SPI, which are both disabled
    How is DHCP or Auto IP being distributed - from the TP-Link Modem which 192.168.0.X or the Netgear Nighthawk with 192.168.1.X subnet?

    Since you can't do port-forwarding from the Modem, you'll have to do it from the Netgear, therefore you have to have the same subnet. See if this Tutorial that I wrote helps your Church's network setup.
      My Computer


  7. Posts : 95
    Windows 7 Ultimate x64
    Thread Starter
       #7

    No problem. I've been preoccupied as well. I took some screenshots on Sunday of the setup of the modem as follows.

    The TP-Link Modem is connected to the WAN port of the Nighthawk, every device is connected to the Nighthawk which gives out the IP's, the firewall is only disabled on the modem and is enabled on the nighthawk. I believe I may have found the "answer" reading other forums: the modem is set to bridge mode which seems to be correct, but at present the Nighthawk has a static IP to the Modem rather than being set to PPPoE & inputting the ISP username and password.

    Hopefully the screenshots provided will help you understand what is going on and how things are set up :)
    Attached Thumbnails Attached Thumbnails Port forwarding not working between Router & seperate Modem-screen-shot-2014-09-21-13.59.01.png   Port forwarding not working between Router & seperate Modem-screen-shot-2014-09-21-13.59.15.png   Port forwarding not working between Router & seperate Modem-screen-shot-2014-09-21-14.00.09.png   Port forwarding not working between Router & seperate Modem-screen-shot-2014-09-21-14.00.46.png   Port forwarding not working between Router & seperate Modem-screen-shot-2014-09-21-14.01.35.png  

    Port forwarding not working between Router & seperate Modem-screen-shot-2014-09-21-14.02.58.png   Port forwarding not working between Router & seperate Modem-screen-shot-2014-09-21-14.04.16.png  
      My Computer


  8. 2xg
    Posts : 2,377
    Win7 & Win8 64bit
       #8

    Sorry, can’t find any helpful setup guide from Hotchilli Communications website or searching the web, but I did check other Providers setup in UK which gave me some ideas.

    Setup your ADSL Modem and Router by following this guide. I would stick with my previous post by assigning the same subnet - for your Modem (192.168.0.1) and your Router (192.168.0.2). Try the Bridge Mode first then assign Static IP to the Router, if Bridge mode didn’t help, try the PPPoE.

    Hopefully others will have valuable insights. :)
    Last edited by 2xg; 24 Sep 2014 at 18:51.
      My Computer


  9. Posts : 93
    Win7 Starter
       #9

    I have almost the same setup as your Church. I like the separate modem so I can turn off Internet access without disrupting the router network normal handling of files and access between linked PCs.

    You need to reset both modem and router back to factory. Turn each on, leave them to complete their boot then wait maybe another minute. Time it!! Now, hold down the reset button for at least 30-seconds, then release. Time it!!

    If you just hold down the reset for a short time it will simply reboot the current setup.

    Hook the modem ONLY to the PC, access setup, set the IP address as 192.168.0.99 (or anything but 1)
    Set the Modem in Bridge Mode.
    You do NOT need to setup a PPPoe account in the Modem, the router will take care of that later.
    Turn it off for fifteen seconds and turn it on.
    Use a browser to check that 192.168.0.99 (or whatever) allows access to the Modem.

    Hook the router ONLY to the PC, access setup and set the base IP to 192.168.0.1
    Set the Range to 192.168.0.2 to 192.168.0.120 (or whatever)
    Make sure the DHCP is enabled.
    Set the Mode to PPPoe
    Full in the ADSL user name and password.
    Turn it off for fifteen seconds and turn it on.
    Use a browser to check that 192.168.0.1 allows access to the Router.

    Plug a cable between the modem and the blue-WAN port on the router.
    Plug in the ADSL line to the modem.
    Plug a cable between the PC and the yellow-LAN port on the router.
    Wait!!
    Watch the lights on the modem and the router. You should see them settle in about two minutes or so.
    Use a Browser to check for Internet access.

    You will no longer be able to access the modem with the IP 192.168.0.99 (or wahtever) while it is connected via the WAN port, but should see the router and then all devices connected beyond.

    Use an Android phone with Wifi Analyzer and use the Tools, LAN Neighbors to see what's around you with wifi waiting to connect.

    Then, you can begin to do the Port Forwarding.
      My Computer


  10. Posts : 95
    Windows 7 Ultimate x64
    Thread Starter
       #10

    CarvedDuck, that's what I ended up doing except I kept the different subnets. I accidentally tapped "DELETE" in the modem's WAN setup page which reset the settings then had a fight to get it to accept the VPI/VCI settings. There were multiplay PVC circuits in the modem which you could select from, PVC6 was 0/38, after that I had to enable the virtual circuit and set it to 0/38, without setting it up that way it wouldn't accept it if you used a different PVC Circuit and still input 0/38, it would fail due to there being a duplicate circuit with those settings.

    Either way I set it up as PVC6 0/38 in 1493 Bridged Mode then set the router up as PPPoE with the ADSL credentials, saved and the router rebooted and the port forwarding worked.

    Like you said the Modem then can't be accessed but considering I'm the best IT support they have that's not much of a problem.

    Thanks everyone for your help :)
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 06:10.
Find Us