Print

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

[moutonlong]

Having problems Using the Ftp feature on the dns 323. I've set it up and I have it working localy. As soon as I try to access it through the internet it doesn't work. I've had my service provider do the port fowarding for port 21 and forwarded from our wan ip to the ip address of the dns 323. I still cannot access it from the internet. Looking for assistance please.

[fordem]

What happens when you try to access remotely?  Is there an error message?  What ftp client are you using?

What do you mean you had your service provider do the port forwarding for port 21?  How are you connected to the internet?  In most cases the service provider is not responsible for customer premesis equipment and you have to configure forwarding for yourself.  Does the DNS-323 have a static or dynamic ip address, does it have a default gateway setting, is the port being forwarded to the correct ip address?

[moutonlong]

Remote access doesn't work. It times out and says it can't open. I'm using the DNS 323 ftp.
I had the provider open port 21 and they did the port forwarding from our WAN external IP to the IP address of the DNS 323. We have t-1 service. The IP's are Static. The provider installed the router and has control over it. And yes it is being forward to the correct IP address. Which is why it works just fine on site. I have a feeling it's a firewall issue with the router. That's the only thing I can think of. Checking into that now.

[fordem]

How do I put this over with out offending - going solely from your responses to my questions - I'd say you're more than a little off base.

I asked what ftp client are you using - your response appears to be "the DNS-323 ftp" - sorry - that is the ftp server, the client is the piece of software you're using to connect to the ftp server.  Try using Windows command line ftp client - go to a command prompt and type ftp - you will have to issue the required commands one by one, but you will be able to see exactly where the process fails.

Next - forwarding to the correct IP address - which is why it works just fine on site - forwarding is not used for local access, that is more likely to be why it works just fine.

It is possible that your problem is caused by a firewall issue with the router - however - if the provider has configured the router to forward the port, he/she should also have known that it would be necessary to configure the firewall to permit access - depending on the type of firewall/router in use, this may be a one step or a multi-step process.  With some firewall/routers, once the port is forwarded you're done, with others you must forward the port (in the router) and then allow the traffic (in the firewall).

Other (greater) probabilities are ....

- the client you are using is configured for passive ftp and not active ftp (which is what your DNS-323 & router appear to be configured for presently) - please see note below.

- the client you are using is configured for active ftp - BUT - the firewall at the client side does not automatically "fixup" the ftp protocol.

If you are using an ftp client that returns the error messages (the windows command line client does), we can pinpoint the location of your problem and then look for ways to fix it.

Note - the ftp server on the DNS-323 does not fully support passive ftp, it does work on a local network but it does not allow you to configure a number of parameters required for it to allow remote access using passive ftp - this will supposedly be fixed in the 1.08 firmware.

[moutonlong]

As you can tell I'm no computer genius. I'm trying to get this running while geting too much work done. Sorry if I was short. just trying to do too many things too fast.(Nature of the beast). I'll give all that a try as soon as I can free up time. And let you know how things go. Thanks for your help so far

[moutonlong]

Using FileZilla this is what I get when i try to connect.
Status:   Connection attempt failed with "ECONNREFUSED - Connection refused by server".
Error:   Could not connect to server

I'm still waiting to hear back from the company who installed and controls the router over here. I'm 69% sure the person i spoke with that did the port forwarding didn't know too much about what they were doing except pluging in the numbers I told them. When i asked about the firewall stuff they said they needed to talk to a tech person and would be geting back to me. Thats where I'm at.

[fordem]

I'm not familiar with filezilla but a quick google suggests that the connection refused message is likely to be firewall related.

If you like, PM me the public ip address and I'll give it a shot - I don't need a user name or password at this point - I should be able to connect to the server and at least get a login prompt if the port forwarding and firewall are correctly configured.

[ECF]

Using FileZilla this is what I get when i try to connect.
Status:   Connection attempt failed with "ECONNREFUSED - Connection refused by server".
Error:   Could not connect to server

I'm still waiting to hear back from the company who installed and controls the router over here. I'm 69% sure the person i spoke with that did the port forwarding didn't know too much about what they were doing except pluging in the numbers I told them. When i asked about the firewall stuff they said they needed to talk to a tech person and would be geting back to me. Thats where I'm at.

Have you tried putting the DNS-323 in the DMZ of the router. It looks like you are having a UPnP issue on the router opening the required ports or port forwarding issue with the router.

[moutonlong]

Just finished talking to the company that intalled the router. We were on the phone for a while trying dif. things. The ports are open and the port forwarding is going to the correct ip address. On my end I've got all the correct numbers inputed to the dns 323. For some reason it still won't connect.

[fordem]

Stop & restart the ftp server on the DNS-323 - see what effect that has - I've seen my DNS-323 return the exact same message I get when I try connecting to yours and that fixed it.

[moutonlong]

I've restarted the dns. I've stoped and restarted the ftp server on it also. It still doesn't work. Any more ideas?

so far I've made sure all the info of the ip has been inputed correctly for the ip settings
there port forwarding has been done to the correct ip
i've restarted everything.

[zeewee]

if you're behind a router, you have to forward your FTP port (21 by default) from your router to your DNS-323.

i have a linksys WRT54GS. On mine, I had to go to the "Applications and Games", then the "port forwarding tab" and I entered in

name: FTP
range start = 21
range end = 21
ip_address = enter in your local ip address of your DNS-323. I made mine static. (I gave it a fixed ip address)
check enable.

this allows port 21 to be forwarded from the router to the dns-323.

[ECF]

Make sure Filezilla is set to connect as Active FTP.

[ewanwhatarmy]

Other (greater) probabilities are ....

- the client you are using is configured for passive ftp and not active ftp (which is what your DNS-323 & router appear to be configured for presently) - please see note below.

- the client you are using is configured for active ftp - BUT - the firewall at the client side does not automatically "fixup" the ftp protocol.

I think this might be my problem.  I can connect using Filezilla and WinSCP but it times out when the client tries to retrieve the file directory.  However, when I connect using an online client such as net2ftp then it works.  I don't have access to the firewall at my work to check its configuration.  Is this my problem and is there a workaround?

[fordem]

Can you access from a hotspot or other location?  If not you can PM me the ip address or URL and other details and I'll take a look for you.

If it is your problem and you have no access to the firewall you can't fix it, and the work around is to use passive ftp, for which you will probably need to wait for the final 1.08 release.  Previous firmware versions had a broken passive ftp implementation, which is supposedly fixed in 1.08, I have not tested it, so I have no idea if the new implementation works properly