Print

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

[jamieburchell]

My FTP was working fine for a year now and the stopped working.

I'm assuming your issue is a continuation of the thread (below) where you performed some sort of upgrade? I'm guessing with the limited details available that whatever "upgrade" you refer to broke something, if everything was working prior to that?

http://forums.dlink.com/index.php?topic=16351.msg93893#msg93893

I don't know why your router isn't allowing port 21 access. Clearly your NAS is if you can use FTP internally. A question for that forum.

If you choose to use the router's DDNS settings, disable it in your NAS.

[fordem]

Like Jamie says - use the router's DDNS setting, and disable it in the NAS.

User your browser and log into DynDNS - it should allow you to manually update the host record to point to the address you have logged in from - do that, and then go to a command prompt and issue the command - ping cj136.gotdns.com - and make sure it resolves to your routers public ip address (it doesn't matter if ping times out, what we want to see is what ip the URL resolves to).

When ping resolves correctly, then and only then can you hope to have anything else work.

[cjmedina]

Like Jamie says - use the router's DDNS setting, and disable it in the NAS.

User your browser and log into DynDNS - it should allow you to manually update the host record to point to the address you have logged in from - do that,

I'm not sure what you want me to do at dyndns.com

Here is some of the setting now:

http://home.comcast.net/~cjmedina/Capture7.JPG

http://home.comcast.net/~cjmedina/Capture8.JPG


 and then go to a command prompt and issue the command - ping cj136.gotdns.com - and make sure it resolves to your routers public ip address (it doesn't matter if ping times out, what we want to see is what ip the URL resolves to).

When ping resolves correctly, then and only then can you hope to have anything else work.

This is what it pings:

http://home.comcast.net/~cjmedina/Capture9.JPG

Pointing to wrong IP?

[TThibodeau]

You have the wrong address in your ping.

You are missing a dot
cj136.gotdns.com

If I ping the above address it resolves you local network address 192.168.0.105 not you isp provided address


Cheers
Thomas

[cjmedina]

Ok, It pinged to my DNS address 192.168.0.105


works fine locally but I can't open port 21

[fordem]

192.168.0.105 is your internal address - it's NOT going to work externally if it resolves to your internal address.

[cjmedina]

YES, I Know that but why can't i open port 21?

I,ve tried other ports such as 12345 with no luck. It won't open the ports!

I'm running Norton internet security and it knows and is set to share on 192.168.0.105 my NAS.

This is really pissing me off!

[Wiggs]

YES, I Know that but why can't i open port 21?

I,ve tried other ports such as 12345 with no luck. It won't open the ports!

I'm running Norton internet security and it knows and is set to share on 192.168.0.105 my NAS.

This is really pissing me off!

You should disable Norton while you are trying to access the NAS externally.  It adds an extra layer of frustration until you get it working.
 
Also, what do you mean when you say you "can't open port 21" (or other ports for that matter)?  I am confused.  This sounds like a firewall issue to me.  


Regards,


Wiggs

[fordem]

Pardon the pun - it's a DNS issue - Domain Naming System. - and until the host name resolves properly, there's no way to move forward.

[HSishi]

Your adress cj136.gotdns.com is *still* set on the INTERNAL IP of your DNS-323. As long as this adress is not updated to your EXTERNAL IP (which changes every dial-in of your router) you can't access your NAS from internet.

As already mentioned - turn off the DDNS feature of your NAS; it always updates with its INTERNAL IP because it can't detect the external one.

If your router doesn't support DDNS (check if the router has an advanced setup; mine has) you could use DynDNS' Update client.

Hope this helps.

//HSishi

[jamieburchell]

it always updates with its INTERNAL IP because it can't detect the external one.

This is simply not true, I've tested it. What would be the point of a DDNS system on the NAS if it can only report its internal IP?

The NAS's gateway needs to be set so it might have a chance of working out what its external address is.

[HSishi]

As cjmedina showed in his screenshot ( http://home.comcast.net/~cjmedina/Capture8.JPG ) the DDNS adress seems to be updated by the NAS and set to the INTERNAL IP. So the NAS knows how to connect to the internet.

Unfortunately, cjmedina didn't show us his / her LAN settings of the DNS-323 (yet) and, from the given screenshots, we can't see the firmware revision of the NAS.

cjmedina: If you have both (router and NAS) DDNS feature activated, disable the NAS's one and let just the router do the job.
If both are active, the router updates it to the new adress only after an internet re-connect, checks the update, and inform the LAN clients of the new external IP. Then the NAS updates again with the NAS' internal IP, which overwrites the router's update.

//HSishi

[cjmedina]

As cjmedina showed in his screenshot ( http://home.comcast.net/~cjmedina/Capture8.JPG ) the DDNS adress seems to be updated by the NAS and set to the INTERNAL IP. So the NAS knows how to connect to the internet.

Unfortunately, cjmedina didn't show us his / her LAN settings of the DNS-323 (yet) and, from the given screenshots, we can't see the firmware revision of the NAS.

http://home.comcast.net/~cjmedina/Static.JPG

http://home.comcast.net/~cjmedina/Firmware.JPG


cjmedina: If you have both (router and NAS) DDNS feature activated, disable the NAS's one and let just the router do the job.

http://home.comcast.net/~cjmedina/DDNS.JPG

http://home.comcast.net/~cjmedina/Router_DDNS.JPG

If both are active, the router updates it to the new adress only after an internet re-connect, checks the update, and inform the LAN clients of the new external IP. Then the NAS updates again with the NAS' internal IP, which overwrites the router's update.

http://home.comcast.net/~cjmedina/Status.JPG

http://home.comcast.net/~cjmedina/Router_Firmware.JPG

I see there is a quick ping test from the Router!

http://home.comcast.net/~cjmedina/FTP_Server.JPG

http://home.comcast.net/~cjmedina/Ping_Test.JPG

http://home.comcast.net/~cjmedina/Virtual_Server.JPG

http://home.comcast.net/~cjmedina/Port_Forwarding.JPG

http://home.comcast.net/~cjmedina/Router_DDNS.JPG

http://home.comcast.net/~cjmedina/Router_Firewall.JPG

http://home.comcast.net/~cjmedina/QOS_Engine.JPG

http://home.comcast.net/~cjmedina/NAS_Firmware.JPG


Let me know if you need anymore info to help me solve this problem?


Thanks,


Cliff


//HSishi

[HSishi]

Ok, the settings themself are looking fine. Your gotdns.com adress still routes on the internal IP so there's a problem with a lacking update.

You could try to force an update of the gotdns adress:
1. Disable the DynDNS feature from the router (with "Save settings") and wait a few seconds, then re-enable it (again with "Safe Settings").
2. Try to force a reconnect from the router.

Hope this helps.

//HSishi

[cjmedina]

OK I went in to the router DDNS settings and disabled it. Then saved, waited a few minutes and then re-enabled it and saved the setting.



Status: Connected
http://home.comcast.net/~cjmedina/ServerIP.JPG




Cliff