Netgear Router Port Forwarding

[CranialBlaze]

We got a new Netgear N300 (DGN3500), upgraded from some 54mb thing, forgot its model number.

We have a file server sitting here that we just setup and with the old router the dyndns and port forwarding worked great, mostly cuz that router had very basic settings, simple enable all ports to 1 ip and done, all works.

Anyway, the port forwarding on this ones not working properly,I have set it up correctly as far as I can tell, went with the obvious of forwarding the specific ports needed, defining the same number in start and end, but now I have gone as far as 1 - 65534, in the hopes of simply opening it all up, which is not working. With the dyns address or the ip address I cannot access the server remotely.

I have done this twice before, works perfectly at home on my really ****ty belkin router. Done WoL packet test as its the only packets I know howto monitor and internally using either the loal or remote IP or dyndns address I can ping it cuz of the loop back support, but when I log into my server at home and try sending the packets from their nothing happens. Cant access the FTP or SSH which was working on the old router which we do not want to switch back to.

Anyone have any other test ideas to try and sort thisproblem out?

 

[Pada]

Are you testing it from a different Internet connection?
Because if you aren't... then it could be working, but the router may not have NAT loopback, preventing you from accessing the port forwarded service(s) on the router's public IP address.

 

[CranialBlaze]

Are you testing it from a different Internet connection?
Because if you aren't... then it could be working, but the router may not have NAT loopback, preventing you from accessing the port forwarded service(s) on the router's public IP address.

"but when I log into my server at home and try sending the packets from their nothing happens."

 

[Pada]

Sorry, I missed that part.

I suspect the SSH & FTP ports are redirected to the modem itself, because it probably has those services built in.

Have you tried port forwarding like <public ip>:1021 to <server's LAN ip>:21 , and then trying to access TCP port 1021 from your home?
If that works, then see if your modem is disabling SSH & FTP services on its WAN connection

 

[CranialBlaze]

Sorry, I missed that part.

I suspect the SSH & FTP ports are redirected to the modem itself, because it probably has those services built in.

Have you tried port forwarding like <public ip>:1021 to <server's LAN ip>:21 , and then trying to access TCP port 1021 from your home?
If that works, then see if your modem is disabling SSH & FTP services on its WAN connection

Nah bit of a paranoid, never use standard ports, ssh ports is 16912 (and use SFTP so same port). Took some really creative googling but seems the new firmware needs you to open the ports both in the port settings and firewall, the old router only had the firewall, also they don't call it the firewall they call it services and having nothing setup even with the option default on never is not enough,you need to define ports to specifically never block.

Smidge retarded, but all working now.

 

[Pada]

Ah OK. I'm glad you got it sorted out.

That firewall / port forwarding sounds similar to how you have to set it up on MikroTik routers when you're blocking incoming traffic by default, where you first have to allow incoming connections on the firewall and only then the port forwarding rules will work.

Using default ports for SSH/FTP is never a good idea. We had lots of hacking attempts on SSH for our servers when we used the default port. We then changed it slightly and then all of a sudden we didn't even have a single SSH hacking attempt!