New
#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 :)