Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Another Joe]

I have a DNS-321 NAS connected to the DIR-825 Router. I'm having problems connecting to the FTP server from outside. I don't have problems connecting from inside the network so I think is something with the router. So far, these are my settings.

DNS-321
- FTP server using port 21
- DDNS enabled and connected to myhostname.dlinkddns.com

DIR-825 (REV B firmware 2.02)
- Virtual Server enabled pointing to my NAS IP address, TCP protocol and using port 21 in both public and private ports.
- DDNS enabled and connected to myhostname.dlinkddns.com
- Firewall settings: Enable SPI checked, TCP endpoint independent checked

My Dlinkddns.com account is active and running. The IP address in the ddns match my current external IP address in the router.

Any idea why I'm unable to connect to the FTP server from outside? Are there any incorrect settings in my set up?

Thanks,

[Another Joe]

This is what I'm getting from outside:

"ERROR
Proxy Error

--------------------------------------------------------------------------------

The proxy encountered an error.

Please try again later. "


I have reviewed my settings millions of times and I don't see anything wrong. What you guys think it could be?

[emanoyhl]

are you literally trying to access from outside your home, or are you testing on a computer within your own network?

if testing within your own network, try testing from outside your network - as usually you could have some kind of NAT redundancy error...

disable the ddns feature of the dns-321 and only use the ddns feature of your router... as the only point of having the ddns feature of the dns-321 is if it is directly connected to the internet, without a router...

also - ping your ip address - from a computer outside of your network (such as a friend's house or a cellphone using cellular network, not your home network) - if successful ping your port 21 you have setup

if you are getting proxy errors then make sure if you have a real proxy running, configure it properly, if you have no proxy remove it or use "auto" for proxy settings on your client (computer/browser, etc..)

please let us know your results! and good luck!

[JoeSchmuck]

Your problem has got to be in the DIR-825.  I have a pair of these and wish I didn't spend the money on them.  Try opening a DMZ for your DNS-321 IP address, see if you can access it then from outside.  I'm sure you will be able to.  The only difference between the DMZ and Virtual Server is, the Virtual server allows specified ports only, where DMZ allows all ports for the designated IP address.

-Joe (The other one)

 

[wayd]

try also forwarding port 20 as well... And using www.ftptest.net to test it really helps.

[gunrunnerjohn]

disable the ddns feature of the dns-321 and only use the ddns feature of your router... as the only point of having the ddns feature of the dns-321 is if it is directly connected to the internet, without a router...

As I've already mentioned, this is total nonsense, and totally wrong.  The DynDNS feature will work for any attached workstation or other device behind the router.  You should really learn how dynamic DNS works for DynDNS or NO-IP before you provide answers that are obviously wrong.

[JoeSchmuck]

As I've already mentioned, this is total nonsense, and totally wrong.  The DynDNS feature will work for any attached workstation or other device behind the router.  You should really learn how dynamic DNS works for DynDNS or NO-IP before you provide answers that are obviously wrong.

I agree, DynDNS will work fine.  I have DynDNS set up in both my main computer and my NAS, never had a problem.

You know, I really don't like it when inaccurate advice is given (emanoyhl).  I know I wing it all the time, but I don't think I've been caught in a lie yet    I do say key words like "I think" or "I suspect" when I don't know for sure and you will see those in many of my postings.  Thanksfully GRJ keeps me honest here.

I'm curious if Another Joe found his solution.

[Another Joe]

Yes, I think I found the problem. It was a combination of the router (my DIR-825 is dead after an unsuccessful firmware flashing) and my ISP blocking port 21 (Charter communications). I'm using an alternate port within the range of the NAS acceptable ports and the Cisco E2000 router. I can't tell much about the router performance since I bought it days ago. I couldn't afford the E3000 or the Netgear 3700. Any other router alternative to the DIR-825?

[gunrunnerjohn]

You can redirect ports using DynDNS or NO-IP so that standard FTP ports can be used externally and redirected to port 21 on your network by the dynamic DNS site.  In the router, you can then translate the port back to port 21 from the custom port so that local FTP access also works for port 21.

[JoeSchmuck]

Yes, I think I found the problem. It was a combination of the router (my DIR-825 is dead after an unsuccessful firmware flashing) and my ISP blocking port 21 (Charter communications). I'm using an alternate port within the range of the NAS acceptable ports and the Cisco E2000 router. I can't tell much about the router performance since I bought it days ago. I couldn't afford the E3000 or the Netgear 3700. Any other router alternative to the DIR-825?

My isp blocks port 80, go figure, so when I setup a website I needed to use a different port and used DynDNS exactly like GRJ mentioned.  I wouldn't be suprised if my port 21 was blocked also.  But if you found your own work around, thats great.

Are you using DDWRT for the DIR-825?  If so, the past few versions have not been kind to many folks.  I'm back to 14311 right now and since it does what I need, I can wait for a few people to say a newer version is working great before I tempt fate again.

You should PM me about using the DIR-825 or post a new thread for the DIR-825.  I don't frequent the forums too often but If I know there is something there, I'll look and do what I can to answer.  Other than weak wireless, it's actually a good product and should be able to handle all your routing needs.  If you're not using DDWRT, you might consider it.  I haven't used OpenWRT yet so I can't comment on it.

-Joe

[gunrunnerjohn]

I have DD-WRT on my TP-Link router, works pretty well here.

[JoeSchmuck]

I've been using DDWRT for many years and it's some great firmware.  It gives you comercial control over your consumer product. 

[gunrunnerjohn]

I just brought it up a month or so ago.  I bought the TP-Link just for using DD-WRT, it was a cheap 802.11n router with gigabit ports.

[Another Joe]

You can redirect ports using DynDNS or NO-IP so that standard FTP ports can be used externally and redirected to port 21 on your network by the dynamic DNS site.  In the router, you can then translate the port back to port 21 from the custom port so that local FTP access also works for port 21.

GRJ, I just implemented your suggestions about redirecting alternate ports to 21 and clients from outside my LAN can access the FTP without problems. Thanks!

[gunrunnerjohn]

Great, glad that worked out.