port forwarding

[tragiccone56813]

I have built a NAS running as an FTP server ssh server and a couple other things. I had the server running just how I wanted it to for a while. We have Uverse and our modem/router  was not working so they replaced it with the model 5268ac. I have attempted port forwarding FTP ssh and a HTTP port. I also tried a port on my desktop to see if there was an internal firewall on the server. I have tested and all the ports are open but when i try to connect it responds with connection refused. I would very much so appreciate some help. 

[DrM]

does your router open the port on all machines or just a specific one? i know that my netgear requires that you set a static local ip first for a machine, then open the port on that specific ip

[thepriceyman]

11 hours ago, tragiccone56813 said:

I have built a NAS running as an FTP server ssh server and a couple other things. I had the server running just how I wanted it to for a while. We have Uverse and our modem/router  was not working so they replaced it with the model 5268ac. I have attempted port forwarding FTP ssh and a HTTP port. I also tried a port on my desktop to see if there was an internal firewall on the server. I have tested and all the ports are open but when i try to connect it responds with connection refused. I would very much so appreciate some help. 

FTP is an absoulute pain in the bum for port forwarding! There is two different types of FTP there is your bog standard port 21  / 20 (active) and then you have passive FTP which will use port 21 and then a RANDOM port on the server - it may be worth seeing if the router that you have has an inbuilt port forwrding section for commonly used ports and then using that rather than defining your own.

 

[tragiccone56813]

I have solved the topic after a night fooling with it but at the same time I don't know if it is truly a soloution. I need my router to loopback but I don't think this can be accomplished on my router

[benny_r_t_2]

Hi.  I know this is an old thread but it covers a problem ive been battling.  Port forwarding on the 5268ac gateway.

 

I just moved to Dallas Texas this week and signed up with at&t gigabit fiber.  They use the 5268ac gateway in all of their home installations.  I was having horrible time trying to diagnose and figure out why port forwarding (or what the 5268ac refers to as "pinholes") would only work if I'm outside my lan.  If i were inside the lan and reference my external wan ip (or dns url which directs to external ip) then the port forwarding did not work.  The ports are open though. In other words the 5268ac does not support NAT hairpin/loopback from inside lan.

 

Solution for me is to direct all inbound traffic through the 5268ac to the n66u via dmz+.  The n66u does support NAT loopback (it's also is far more intuitive to configure).   I kept dhcp server on both 5268ac and n66u.  All the reserved dhcp local ip assignments and port forwarding are being done on the n66u.

Locally i can refer to my wan url and depending which port i specify the n66u directs me to the correct internal ip and port.  Problem solved!

 

Locally I can also connect to either the n66u or the 5268ac via their respective wifi or connect to either via Ethernet and access devices/computers on either one.

 

This 5268ac not supporting NAT hairpin is a real booger and it really had me on a wild goose chase thinking i setup my servers wrong or somthing i had configured incorrectly.   I just always took NAT hairpin/loopback feature for granted and never knew a router could be be void of that feature.   Anyway, all is good now.

 

Thanks. 

 

I'm loving my 700+Mbps download and upload speeds now