D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: irongladiator on October 31, 2010, 03:58:02 PM
-
Hey Guys, I just got a DNS-323 with a Seagate Barracuda 500GB drive. Everything works great. But I'm a bit stumped on the whole FTP thing. I got it work internally, and it works great but where I'm confused is what to "Port forward". If I go (From Internet Explorer) to "ftp://My WAN IP", I can get to where you can enter a username and password, but once you enter it, it kinda hangs and then goes to a "Internet Explorer Cannot Display The Web Page" error. Whereas if I go to "ftp://DNS-323's LAN IP" I can get into it with no problem. I have Comcast for my ISP, are they blocking any ports, should I be enabling something? I'm new to all of this. Thanks in advance for any info guys!
-
Firstly, you'd be better off using a proper FTP client for Windows such as FileZilla. It's freeware and very popular and has many more options available to configure. In my experience it works better than standard Windows explorer.
Secondly, you will need to open the FTP port on your firewall (21 probably, but it depends what's in the DNS-323 settings under FTP) and have it point ("forward") to the internal LAN IP address of your NAS. If your NAS has a static IP address, this will help and is recommended anyway.
The idea is that when you request port 21 on your WAN address, your firewall/router will forward the request to your DNS-323.
You can check which ports are open on your WAN IP by using web services such as "Shields Up!".
If you don't always know what your WAN IP address is, look at a dynamic DNS service such as dyndns. This will allow you to register a host name like dns323.dyndns.org and have it automatically point to your WAN IP. This works by your router or the NAS telling the DDNS service what your current WAN IP address is.
-
Hey jamieburchell,
Thanks for the reply. I'll check out the "Shields Up!" Everything else you mentioned was already done. I'll repost if I have further questions.
**UPDATE**
It appears port 21 is opened up by my ISP.
So.....any other ideas?
-
Have you actually tried to connect outside of your network?
-
I'm a field technician for a telecom company. All of us techs have Internet in our vans. I'll check there, and report back. But to answer you question, no I have not tried outside of my network. I thought that in theory if you hit your own WAN IP it'd be just like if you were on the outside. Is that NOT the case? I'll report back in a few.
**UPDATE**
No-Go, from my work van. I can get to the point where it'll ask for my username and password. I enter them and the same thing happens I get to a page that says: "Internet Explorer Cannot Display The Web Page". Any other ideas?
-
Use FileZilla and try, not Windows Internet/explorer.
-
Did you notice that you can connect to the ftp server, in that it requests a username & password before it drops dead? ftp requires two connections - a control connection, which you are establishing, and a data connection, which is where you're getting stuck.
Internet Explorer defaults to passive ftp - for passive ftp to work you have to ...
1 - tell the DNS-323 to report the external ip address
2 - forward the range of "passive ports" you configured on the DNS-323 to the DNS-323.
You also need to be aware that the passive ftp functionality in the DNS-323 is broken, as it does NOT track changes to the external ip address, should that change.
Go to internet options, and deselect passive ftp and try again - I'll bet it works.
-
fordem,
Yeah it is the "Data" connection is where I'm getting stuck. I'll try an FTP client, but I would prefer to use Internet Explorer. This is what my settings are (I havent changed them at all):
(http://i583.photobucket.com/albums/ss280/2005_KJ_Owner/FTP.jpg)
-
If you really must use Windows explorer/IE - as fordem says, you can check/uncheck "Use Passive FTP" in the options menu.
Fordem is also suggesting that you'll need to open the ports on your firewall that are shown if you're using passive mode.
However, in both Windows and FileZilla I can access FTP in Active or Passive mode from outside of my network on my DNS-323 with just port 21 open on my firewall. I've also verified the ports that are open on my firewall.
-
If I may add to this discussion since I to am new to setting up an FTP. I have opened up the available ports in the router but am receiving this when I try to connect from another network using Filezilla as recommended.
Status: Connecting to xx.xxx.xxx.xx:21...
Status: Connection established, waiting for welcome message...
Response: HTTP/1.0 400 Bad Request
Error: Could not connect to server
I have verified that I can connect to other FTP's just not the DNS-323
-
Have you verified that you can FTP to the NAS from inside your network?
-
Yes we just verified that connection can be made from inside the network.
-
Does setting passive/active mode make any difference? Fordem suggests that using one over the other will help in certain circumstances. For me, I can use either with just port 21 open on my router/firewall.
Here's a handy tool that you can run from inside your network that will analyse your external IP and tell you which ports are open (to confirm).
https://www.grc.com/x/ne.dll?bh0bkyd2 (https://www.grc.com/x/ne.dll?bh0bkyd2)
It does sound like you are establishing an initial connection however.
-
Status: Connecting to xx.xxx.xxx.xx:21...
Status: Connection established, waiting for welcome message...
Response: HTTP/1.0 400 Bad Request
Error: Could not connect to server
Didn't you notice that you've got a http-response upon a ftp-request?
I bet you are not talking with your NAS from the outside but with your router. Are you absolutely sure that you have mapped outside tcp-port 21 to your NAS's private IP-address and tcp-port 21 in the NAT/PAT-rules of your router?
-
PteJack,
You might be better starting a new thread with your guide. Call it something like, A Guide to Setting up an FTP Server on your DNS-323 - then remove the posts from this thread. We've both hijacked someone elses thread :)
The moderators might even make it a sticky - but I've not seen them in a while.
Jamie
-
I just recently tried to set up my DNS-323 FTP server and have hit a brick wall. Here's what I've done so far..
- Assigned static internal IP to DNS-323
- Configured and started FTP service on DNS-323
- Successfully connected to FTP server internally over LAN
- Forwarded Port 21 in router configuration to DNS-323
- Set up DYNDNS.org account
Today I tried to connect to my FTP server at work and I could not connect.
Status: Resolving address of xxxxxxx.dyndns.org
Status: Connecting to xx.xxx.xx.xxx:21...
Error: Connection timed out
Error: Could not connect to server
If I'm understanding this error correctly this means that I can't even see my router? Is there a setting that its using to "hide" itself from the outside world? Or is the IP address for my DYNDNS account wrong already? I know that my external IP address can change occasionally, which is why I installed the updater tool, so this seems unlikely?
-
Good Idea Jamie, I'll do that and delete the posts in this thread.
Rayne, I've moved the thread to a new topic. Go there with your questions.
Pte Jack
-
I just recently tried to set up my DNS-323 FTP server and have hit a brick wall. Here's what I've done so far..
- Assigned static internal IP to DNS-323
- Configured and started FTP service on DNS-323
- Successfully connected to FTP server internally over LAN
- Forwarded Port 21 in router configuration to DNS-323
- Set up DYNDNS.org account
Today I tried to connect to my FTP server at work and I could not connect.
Status: Resolving address of xxxxxxx.dyndns.org
Status: Connecting to xx.xxx.xx.xxx:21...
Error: Connection timed out
Error: Could not connect to server
If I'm understanding this error correctly this means that I can't even see my router? Is there a setting that its using to "hide" itself from the outside world? Or is the IP address for my DYNDNS account wrong already? I know that my external IP address can change occasionally, which is why I installed the updater tool, so this seems unlikely?
The idea of dynamic DNS services is that your router or the 323 updates the record on your account with your external IP address. You need to make sure that's setup.
-
The idea of dynamic DNS services is that your router or the 323 updates the record on your account with your external IP address. You need to make sure that's setup.
dyndns had a utility that I installed that runs on my PC that does the same thing. Is this not the same as it running on the 323 or router?
-
I've never seen such a utility so I can't comment. The advantage of using it on your router is that it knows when to update the record. Also means you don't need a PC on. The NAS has the same facility too but I'd favour the router doing the job if possible.
I guess you need to determin if resolving to your IP is the issue.
-
I'm a DynDNS user myself, and in the past used a PC client to update my DNS record (if memory serves me right, it was called DeeEnEs) before I got a router.
When your IP changes, it may take some time before the client identifies that (minutes, probably, should be configurable) and updates your DynDNS account. When that happens I suggest you wait a bit (30mins, 1hr) and try again.
You can login to the DynDNS account to check when was it last updated.
Try FTP-ing from home using the sub-domain name you registered in DynDNS and see if that works.
-
dyndns had a utility that I installed that runs on my PC that does the same thing. Is this not the same as it running on the 323 or router?
True, most PC DNS Clients will grab the internal IP address from the computer and try to update the DNS Server with that IP rather than the External IP. This is why it is better to update from the Router if you can. If the PC DNS Client fails, you'll have to log into your DNS provider and update it manually.
PteJack
-
I have never seen a dynamic DNS client that would do that from any source, and I've used DynDNS and NO-IP for many years. I've used the PC clients as well as the NAS based clients, and they've always updated perfectly. The only time I tried to use a router based client, it was buggy and didn't renew the account at DynDNS properly, so I kept getting expiration messages.
I don't even know how this could happen, given the way the dynamic DNS clients function, so I'd suggest you look elsewhere for this issue.
-
I was stumped because I don't think it was the DDNS service that was the problem, because even if I tried to ping my router with the actual WAN IP address it wasn't finding it. The DDNS was actually resolving the address to the right IP address, and the PC client was actually updating the address correctly as well. After scratching my head last night for a few hours I think I decided to phone up my ISP and see why I couldn't ping my modem and they tell me that they are blocking certain ports. Such as port 21 & 80! So apparently they dont allow any of their clients to run personal FTP sites, web sites, etc. I was dumbfounded. Think I'll be looking for another ISP!
-
Or forwarding another port maybe?
PteJack
-
I cant ping my modem from outside my network. At all.
-
Your ISP may also be blocking icmp.
-
Usually, the failure to ping your router is the router blocking the pings. A plain modem won't respond to a ping, it doesn't have the capability.
-
Sorry, I have a Siemens Gigaset SE567 which is a DSL Ethernet modem/router.
-
Here's the manual for that router: http://downeydesign.com/eXtplorer/downloads/docs/SiemensGigaset-SE567-SE568.pdf (http://downeydesign.com/eXtplorer/downloads/docs/SiemensGigaset-SE567-SE568.pdf)
It should be in there... :)