Print

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

[muymal]

I can't FTP into my DNS323 from the internet.  Here's what I've done so far:

set up ftp server (advanced-ftp server)
fwd'd port 21 in router
put the dns323 in dmz

IE or FF, go to http://nn.n.n.nnn:21, I get "This address is restricted.  This address uses a network port which is normally used for purposes other than web browsing.  Firefox has cancelled the request for your protection."

Same address in FireFTP and I get "Unable to make a connection. Please try again.

Incidentally, I can access the DNS323 by going to nn.n.n.nnn and log in to change settings.  Just cant get to ftp.

Help.  TIA.

[fordem]

I can't FTP into my DNS323 from the internet.  Here's what I've done so far:

set up ftp server (advanced-ftp server)
fwd'd port 21 in router
put the dns323 in dmz

IE or FF, go to http://nn.n.n.nnn:21, I get "This address is restricted.  This address uses a network port which is normally used for purposes other than web browsing.  Firefox has cancelled the request for your protection."

Same address in FireFTP and I get "Unable to make a connection. Please try again.

Incidentally, I can access the DNS323 by going to nn.n.n.nnn and log in to change settings.  Just cant get to ftp.

Help.  TIA.

You're trying to connect to an ftp server using the http protocol - use ftp://nn.n.n.nnn

[muymal]

Sorry, forgot to mention that I have also tried "ftp://nn.n.n.nnn" in both IE and FF.  Should have worked in FireFTP anyway, correct?  Still stuck.

[fordem]

Well - I'm going to guess that the error messages you got on those attempts were not the same - so what were they?  You do realise that error messages have a way of pointing to the problem, if you know how to read them, don't you?

[Wiggs]

I can't FTP into my DNS323 from the internet.  Here's what I've done so far:

set up ftp server (advanced-ftp server)
fwd'd port 21 in router
put the dns323 in dmz

IE or FF, go to http://nn.n.n.nnn:21, I get "This address is restricted.  This address uses a network port which is normally used for purposes other than web browsing.  Firefox has cancelled the request for your protection."

Same address in FireFTP and I get "Unable to make a connection. Please try again.

Incidentally, I can access the DNS323 by going to nn.n.n.nnn and log in to change settings.  Just cant get to ftp.

Help.  TIA.

What IP Address are you trying to use?  To access the DNS from outside your network, you have to use the IP that is assigned to you by your ISP. 

Also, if you have forwarded port 21 in your router to the 'internal IP' of the NAS it does not need to be in the DMZ. 

Regards,


Wiggs

[muymal]

Well - I'm going to guess that the error messages you got on those attempts were not the same - so what were they?  You do realise that error messages have a way of pointing to the problem, if you know how to read them, don't you?

I posted an error message in my first posting.  But to be more clear, here is a summary:

In FireFox -
"ftp://nn.n.n.nnn" returns "Oops! Firefox could not connect to nn.n.n.nnn".  Same is true if I amend to "ftp://nn.n.n.nnn:21".
nn.n.n.nnn:21 returns "This address is restricted 
This address uses a network port which is normally used for purposes other than Web browsing. Firefox has canceled the request for your protection."
nn.n.n.nnn gets me to the login page of my NAS

In IE -
"ftp://nn.n.n.nnn" returns "Internet Explorer cannot display the webpage".  Same if I add ":21" at the end.
nn.n.n.nnn gets me to the set up login for the DNS323.


In FireFTP I get "Unable to make a connection. Please try again." when I enter any of the following:
ftp://nn.n.n.nnn
ftp://nn.n.n.nnn:21
nn.n.n.nnn:21

[D-Link Multimedia]

Did you make sure to "Start" the ftp server at the bottom of the FTP page? Also can you access it internally using the internal IP. Last question, are you attempting to connect BACK through your router into the NAS from the same internal network? Some routers don't support loop-back and you would need to test it from an actual remote location.

[muymal]

What IP Address are you trying to use?  To access the DNS from outside your network, you have to use the IP that is assigned to you by your ISP. 

Also, if you have forwarded port 21 in your router to the 'internal IP' of the NAS it does not need to be in the DMZ. 

Regards,


Wiggs

I am using the IP address of my router which I derived from 'whatismyipaddress.com'.  I also confirmed this in the router set up.

I put the NAS in the DMZ after I wasn't able to access it using only port 21 forwarding.  This has allowed me to at least access the set up page for the NAS.

[muymal]

Did you make sure to "Start" the ftp server at the bottom of the FTP page? Also can you access it internally using the internal IP. Last question, are you attempting to connect BACK through your router into the NAS from the same internal network? Some routers don't support loop-back and you would need to test it from an actual remote location.

Yes.  Currently the button at the bottom of the page says "Stop FTP server"

Actually, I have not yet tried to access the FTP server from the LAN.  Will try when I go home.

No, I am trying to access the NAS from my work computer.

[OlegMZ]

Yes.  Currently the button at the bottom of the page says "Stop FTP server"

Actually, I have not yet tried to access the FTP server from the LAN.  Will try when I go home.

No, I am trying to access the NAS from my work computer.

The easiest way to check if TCP port is opened is to go to command prompt and issue following command:

telnet X.X.X.X  YY

Where X.X.X.X is the IP addess of destination and YY is the port number (21 in your case)
If the port is really opened you will see at least black screen (in general case) or some text reply in case of HTTP, SSH, FTP, SMTP and many other protocols. If port is closed you may either get error saying that port is closed, connection is reset or just timeout error if there is no device at this address or firewall/device just silently dropped your packet without sending notification back (i.e. ICMP port unreachable).

BTW Are you sure that port 21 is not blocked from inside your network at work or by local firewall on your work PC?
It is always a good idea to test connectivity to NAS locally (from the same network where NAS is installed). IF it works, but access from the internet fails, check your router config and log messages once again.
Can your provider block FTP traffic?

[muymal]

The easiest way to check if TCP port is opened is to go to command prompt and issue following command:

telnet X.X.X.X  YY

Where X.X.X.X is the IP addess of destination and YY is the port number (21 in your case)
If the port is really opened you will see at least black screen (in general case) or some text reply in case of HTTP, SSH, FTP, SMTP and many other protocols. If port is closed you may either get error saying that port is closed, connection is reset or just timeout error if there is no device at this address or firewall/device just silently dropped your packet without sending notification back (i.e. ICMP port unreachable).

BTW Are you sure that port 21 is not blocked from inside your network at work or by local firewall on your work PC?
It is always a good idea to test connectivity to NAS locally (from the same network where NAS is installed). IF it works, but access from the internet fails, check your router config and log messages once again.
Can your provider block FTP traffic?

When I telnet into the NAS I get "Could not open connection to the host, on port 21: Connect failed"

Ok, I will check access from within the LAN. 

ISP is Comcast.  Not sure if they block FTP.

[irotjaf]

It is crucial to test if ftp locally works.

In my case ftp also didn't work from my same computer. I tried it from another computer to find it was working. Maybe you should do the same (ask a friend).

Second, if you have a DSL modem apart, you should set up port forwarding also there. The forward should go to the router, not to DNS itself (this is my setup and is working).

[OlegMZ]

Second, if you have a DSL modem apart, you should set up port forwarding also there. The forward should go to the router, not to DNS itself (this is my setup and is working).

Port forwarding should be configured on (every) device which performs NAT/PAT. If, for example, DSL modem acts a a router and performs NAT, it should have port forwarding configured also. But is is better to configure PPPoE on the router itself and use DSL as a modem only. 2 NAT one after one makes no sense.
Check WAN IP of your router (from config page). If it is public (not from 10.x.x.x, 172.16.x.x - 172.31.x.x or 192.168.x.x range), it should be fine.

For telnet do not forget to specify port (21) after IP address. By default it will go to TCP/23.

[muymal]

It is crucial to test if ftp locally works.

In my case ftp also didn't work from my same computer. I tried it from another computer to find it was working. Maybe you should do the same (ask a friend).

Second, if you have a DSL modem apart, you should set up port forwarding also there. The forward should go to the router, not to DNS itself (this is my setup and is working).

I'm using a Linksys cable modem (on Comcast).  No settings available.

IP address on LAN for DNS323 is the standard 192.168.1.102.  From within the LAN i tried FTP://192.168.1.102:21.  FireFox returns:  Failed to Connect  Firefox can't establish a connection the the server at .....

[irotjaf]

I'm using a Linksys cable modem (on Comcast).  No settings available.

IP address on LAN for DNS323 is the standard 192.168.1.102.  From within the LAN i tried FTP://192.168.1.102:21.  FireFox returns:  Failed to Connect  Firefox can't establish a connection the the server at .....

Do you have a modem or do you have a router?

It makes me think you have a router after the modem. In that case disable all firewalls and put the NAS in DMZ. Only after you make ftp work in a local network you can go ahead to try and make it public.

P.s. If your comcast modem doesn't have any setting, it probably means it will forward all packets to whatever *only* device is connected to it (computer, router, ...). I would advise to take a look how other people having your modem could put a ftp/http server online.