D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: cjmedina on January 01, 2011, 12:58:30 PM
-
I'm having a problem with port 21 through my DIR-655 router.
My FTP was working fine for a year now and the stopped working.
I'm using the free DNS through dyndns.com
I have went thorough my configuration. It says the dns is connected to dyndns.com but when I check the ftp port 21 it is NOT open. It is being refused???
Right now I'm trying to figure out why the connection is refused.
Thanks,
CJ
-
Have you verified that ftp works locally? If not - start there - if you can't access the ftp server from the local LAN by it's ip address, then there is a problem with the server itself.
How are you "checking the ftp port 21"? If the ftp server is accessible from the local LAN and inaccessible from outside the LAN that would usually indicate a problem with the router and the port forwarding setup.
-
I can access locally with the local address.
I'm using this tool to check my ports http://www.dyndns.com/support/tools/openport.html and I have used others with the same result.
It's says the port is refused???
I have it set correctly for the dir-655 virtual forwarding
* Connection Open: The port is open and our tool is able to establish a connection. This indicates that your network is available on this port, and that a server application is listening on this port and accepting incoming connections.
* Connection Refused: The port is open, but no service is listening. This indicates that the port is available, but the computer or device is rejecting (refusing) the connection. This can occur if the service is not running, or if port forwarding is not correctly configured (see below).
* Connection Timed Out: The port is actively being blocked. The port can be blocked by a firewall, a router, or your ISP. This can also indicate the device is unavailable (e.g. turned off). Please see below for more information.
It was fine for a year
What the heck is the next check?
Could my ISP be blocking port 21 and if so how can I be sure it's the ISP?
Cliff
-
Are you sure than your dyndns address actually resolves to your external IP address?
You could also try using a different port number.
-
I ca get in by: ftp://xxxx:xxxxxxxxx@cj136.gotdns.com/
I just upgraded to Dynamic DNS Pro with dyndns.com
what is another port I can try to substitute port 21?
In the dir-555 router it says dynamic DNS: Status: Connected
And in the dns-323 the DDNS says: Status
Updated Successfully
Last Updated Time : Sun Jan 2 15:39:44 2011
Next Update Time : Wed Jan 26 15:39:44 2011
DIR-655
Virtual Server settings:
DSN-323_FTP public 21 TCP always
DNS-323 address private 21 6 allow all
With Open Port Check Tool I don't have port 21 open!
An attempted connection to 68.44.7.67:21 was refused. This typically indicates that there are no services available on that port, but that it is NOT being blocked by a firewall or your ISP.
Cliff
-
I had an interesting experience with my AVM 7390 router:
When I made a port forwarding rule "Allow port 21 on [NAS IP] to accept connections from web", I can't connect from web - I got timeouts.
But when I make a port forwarding rule "Allow FTP server on [NAS IP] to accept connections from web" it works.
Forwarding a port range 21-25 worked too.
So check your router if you can configure FTP server instead of a single port. If you can't, forward the port range 21-25 instead of 21 only.
//HSishi
-
I ca get in by: ftp://xxxx:xxxxxxxxx@cj136.gotdns.com/
Can or can't...?
When you ping your dyndns host name, does it resolve to your external IP address?
You can use any "spare" port number. You could for example forward port 12345 on your router to port 21 on your NAS.
-
YES
ftp://xxxx:xxxxxxxxx@cj136.gotdns.com/
from my local network
but if i do a port check it still says port 21 is refused????
If I enter my host name in the browser it goes to: Grandstream Device Configuration and asks for a password????
I can't change port 21 in the FTP server configuration in the DNS-323
so do I set a number in the router DIR-655 what number?
Thanks,
Cliff
my version is 1.09
-
You don't have to change the port number on the NAS. It can stay as port 21. I'm not familiar with your particular router, but I imagine you can "port forward" any external port number (12345 as I already suggested) to the internal IP address of your NAS- port 21.
Pasting "ftp://xxxx:xxxxxxxxx@cj136.gotdns.com/" doesn't really help me determine the issue.
What happens inside your network, doesn't necessarily reflect what happens outside of it.
If you try an alternative port number and your "tool" (try ShieldsUp website-it uses your external IP address to analyse your open ports) still says the port is closed, you have not configured your router/firewall correctly and your question might be better phrased in the router's forum.
You can also check with your ISP if they have blocked FTP.
-
If I enter my host name in the browser it goes to: Grandstream Device Configuration and asks for a password????
I'm guessing this is your router's web configuration page. Why? Because it's running on port 80 (web default) and you've put the host/IP address of it in your browser.
If that's not your router, then your dynamic host name isn't resolving to YOUR IP address afterall. Or, you've forwarded port 80 on your router/firewall to another device.
-
Shields up says only 2 ports are open 23 and 80
I have tried virtual server and port forwarding of 21 with no luck.
It used to work?????
-
When I attempt to ping cj136.gotdns.com, the URL resolves to an ip address of 192.168.0.105 and my ISP's gateway discards the ping request (as it should, because a 192.168.x.x address is considered unrouteable across the internet.)
This suggest a problem with how you have your dynamic DNS client configured, and also is a very good example of why you should not be attmpting to test remote access from within the same LAN.
-
This is what I have set in DNS-323:
http://home.comcast.net/~cjmedina/Capture.JPG
http://home.comcast.net/~cjmedina/Capture2.JPG
http://home.comcast.net/~cjmedina/Capture3.JPG
CJ
-
If fordem is correct, your DDNS host name is not resolving to your external IP address- which is problem number one (hence the persistant questioning).
Just out of curiosity, why did you enable DDNS on the NAS and not the router? If the router supports it, it would sure make life easier to use it.
Is the default gateway IP address of your NAS pointing to your router?
-
Here is what is set.
http://home.comcast.net/~cjmedina/Capture5.JPG (http://home.comcast.net/~cjmedina/Capture5.JPG)
http://home.comcast.net/~cjmedina/Capture6.JPG (http://home.comcast.net/~cjmedina/Capture6.JPG)
It was working and then stopped with the free DNS and I just upgraded to pro. Still don't work!
-
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 (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.
-
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.
-
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/Capture7.JPG)
http://home.comcast.net/~cjmedina/Capture8.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 (http://home.comcast.net/~cjmedina/Capture9.JPG)
Pointing to wrong IP?
-
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
-
Ok, It pinged to my DNS address 192.168.0.105
works fine locally but I can't open port 21 ???
-
192.168.0.105 is your internal address - it's NOT going to work externally if it resolves to your internal address.
-
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!
-
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
-
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.
-
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 (http://www.dyndns.com/support/clients/).
Hope this helps.
//HSishi
-
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.
-
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
-
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/Static.JPG)
http://home.comcast.net/~cjmedina/Firmware.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/DDNS.JPG)
http://home.comcast.net/~cjmedina/Router_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/Status.JPG)
http://home.comcast.net/~cjmedina/Router_Firmware.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/FTP_Server.JPG)
http://home.comcast.net/~cjmedina/Ping_Test.JPG (http://home.comcast.net/~cjmedina/Ping_Test.JPG)
http://home.comcast.net/~cjmedina/Virtual_Server.JPG (http://home.comcast.net/~cjmedina/Virtual_Server.JPG)
http://home.comcast.net/~cjmedina/Port_Forwarding.JPG (http://home.comcast.net/~cjmedina/Port_Forwarding.JPG)
http://home.comcast.net/~cjmedina/Router_DDNS.JPG (http://home.comcast.net/~cjmedina/Router_DDNS.JPG)
http://home.comcast.net/~cjmedina/Router_Firewall.JPG (http://home.comcast.net/~cjmedina/Router_Firewall.JPG)
http://home.comcast.net/~cjmedina/QOS_Engine.JPG (http://home.comcast.net/~cjmedina/QOS_Engine.JPG)
http://home.comcast.net/~cjmedina/NAS_Firmware.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
-
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
-
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 (http://home.comcast.net/~cjmedina/ServerIP.JPG)
Cliff
-
Mh, this is getting weird ... the adress cj136.gotdns.com is now resolved to 192.168.2.100 (still an internal IP).
Ok ... I assume your router's HW revision is NOT "DIR-655_REVB".
In this case, update your router's firmware (current FV revision is 1.35, you have 1.21) which fixes alot of bugs (including port forwarding and DDNS issues).
Start here to look for new firmware and maybe additional software: http://www.dlink.com/products/?pid=DIR-655&tab=3 (http://www.dlink.com/products/?pid=DIR-655&tab=3)
If upgrading the firmware does not help, we have to dig further.
In this case, please tell us more about your internet connection, esp. if your router is behind another router (means your network is a part of a company, college or university network).
If this is the case, neither your router nor your NAS may able to detect the correct "external" IP. And, to make it more worse, you won't be able to provide FTP services without approvement because the admin of your overall network structure has to grant you specific ports which have to be forwarded to *your* router and, from there, forwarded to your NAS.
DSL-over-satellite and (maybe) cable networks usually share *one* IP with multiple customers and the companies use NAT (via the MAC adresses of the access points given to their customers) which doesn't allow customer-sided servers.
But if your router connects directly into the internet, using PPPoE or any kind of DSL "Dial-in" you should be fine. Could you provide a screenshot of the status page? For security you can wipe the last two octets of your current IP but we have to see at least the first two parts of your IP to see if it's a special network or a provider's pool IP.
//HSishi
-
Ok this is strange.
I have been using the FTP function for about a year now. I thought my problem started after upgrading the NAS firmware. It had been recommended that I do a reset of the NAS, which I did, but with no luck.
I had both DDNS running on router and NAS and have disabled the NAS side.
It is strange that it now resolves to internal .100. I have a static connection to the NAS of.105
I may add that I have a VOIP connection that was behind the router until I had connection drop outs so it was recommended that it be before the router. I have not had phone connection problems since. My account is with Phonepower. It has been a good service for only $12 a month!
My esp is with Comcast.net in central New Jersey. And my Host DNS service was upgraded to pro in the hope of fixing the problem.
http://home.comcast.net/~cjmedina/Capture7.JPG (http://home.comcast.net/~cjmedina/Capture7.JPG)
http://home.comcast.net/~cjmedina/Stat.JPG (http://home.comcast.net/~cjmedina/Stat.JPG)
Here's my hardware version:
http://home.comcast.net/~cjmedina/HV.JPG (http://home.comcast.net/~cjmedina/HV.JPG)
I really don't want to upgrade the router firmware. It has been working before with this version I have and I just don't want to open another can of worms if you know what I'm saying?
When I did a check for firmware update it says I have the latest version!
If anything I would replace this router with a better one with less head aces.
Any recommendations for a good wireless router?
Cliff
-
I may add that I have a VOIP connection that was behind the router until I had connection drop outs so it was recommended that it be before the router.
I guess that solves that one then. Would that be the "Grandstream" device by any chance? It may have helped 2 pages ago to mention that network change ;)
-
So that may be the problem but how can I now get my FTP working again with the VOIP setup?
Cliff
-
Well - as the first step you're going to have to fix the name resolution - if you can't resolve the name you can't connect.
Try running a PC based dynDNS client and see what happens
-
Thanks you....
How do I fix the name resolution.
Can you recommend a client. I will also need to know how to set it up.
Cliff
-
http://www.dyndns.com (http://www.dyndns.com)
-
What do you mean by "name resolution"?
-
See if this works for you (http://lmgtfy.com/?q=name+resolution)
-
DynDNS has a windows-based update client which calls a script on their website ( http://checkip.dyndns.com/ (http://checkip.dyndns.com/) ) and get the IP which your provider assigned to you as response. --> http://www.dyndns.com/support/clients/ (http://www.dyndns.com/support/clients/)
Anyway, some things become clear now.
Your router does NOT have a direct internet connection, it gets his IP adress from the VoIP hardware device. So the best is to disable the router's DHCP and use the one of the VoIP hardware only.
Try the following:
1. Inform yourself if the router has a "hardwired" emergency IP adress and the settings you have to set your PC's LAN adapter to, in case the following steps do not work (some of routers have it in case DHCP doesn't work and the router's default IP was altered.)
2. Backup / export your router's settings (in case you have to hardware-reset it)
3. Disable the router's DHCP server.
4. Set all LAN clients to get their IP via DHCP.
This should force your clients to try to get IP adresses from the VoIP hardware.
If this does NOT work, you have to
- hardware-reset your router
- connect to your router via default or emergency IP adress
- re-import the previous exported settings so you have a working router again.
- Connect the WAN cable to the router.
I *still* recommend to update your router's firmware. "It worked for so long without problems" does NOT mean this will last forever - if this would be the case we wouldn't have this thread here ;) .
Maybe you can use your VoIP hardware *behind* the router as you did before. If your router builds up the internet connection your NAS won't have any trouble to update DynDNS anymore.
//HSishi
-
Thanks,
For all the help.
I will work on it in a few days and get back to you with the results.
I don't want to put the VOIP behind the router and have my phone service go out like it did every few weeks.
CJ
-
DynDNS has a windows-based update client which calls a script on their website ( http://checkip.dyndns.com/ (http://checkip.dyndns.com/) ) and get the IP which your provider assigned to you as response. --> http://www.dyndns.com/support/clients/ (http://www.dyndns.com/support/clients/)
Anyway, some things become clear now.
Your router does NOT have a direct internet connection, it gets his IP adress from the VoIP hardware device. So the best is to disable the router's DHCP and use the one of the VoIP hardware only.
Try the following:
1. Inform yourself if the router has a "hardwired" emergency IP adress and the settings you have to set your PC's LAN adapter to, in case the following steps do not work (some of routers have it in case DHCP doesn't work and the router's default IP was altered.)
2. Backup / export your router's settings (in case you have to hardware-reset it)
3. Disable the router's DHCP server.
4. Set all LAN clients to get their IP via DHCP.
This should force your clients to try to get IP adresses from the VoIP hardware.
If this does NOT work, you have to
- hardware-reset your router
- connect to your router via default or emergency IP adress
- re-import the previous exported settings so you have a working router again.
- Connect the WAN cable to the router.
I *still* recommend to update your router's firmware. "It worked for so long without problems" does NOT mean this will last forever - if this would be the case we wouldn't have this thread here ;) .
Maybe you can use your VoIP hardware *behind* the router as you did before. If your router builds up the internet connection your NAS won't have any trouble to update DynDNS anymore.
//HSishi
I'm going to take a bet that this fails miserably.
WHen you disable the router's DHCP functionality, it's not going to pass the DHCP requests through to the VOIP device on the other side - you'll simply end up with a bunch of PCs reporting limited connectivity.
-
DynDNS has a windows-based update client which calls a script on their website ( http://checkip.dyndns.com/ (http://checkip.dyndns.com/) ) and get the IP which your provider assigned to you as response.
Just so you know - all the script does is extract the source ip address from the incoming request and display it - now, if folks who wrote the update clients would do that, it would guarantee the correct ip address, but the dilemma now becomes knowing when it changes to prevent abuse lockouts.
At this point there is obviously a string of daisy chained routers - the VOIP device apparently acts as a router, and that is followed by another router which is the one we have been hearing about all along - even if you get the name resolution problem fixed, the daisy chained routers are going to cause you issues with port forwarding.
The solution is to get rid of one of the routers - since you want the VOIP - then find a VOIP box that can meet your routing needs, possibly adding a wireless access point.
-
Thanks Fordem,
Would this work?
http://www.dlink.com/products/?pid=446 (http://www.dlink.com/products/?pid=446)
CJ
-
First - that appears to be a discontinued product, and whilst I have nothing against discontinued products, and use them personally, especially when it means saving a dollar - I do so with the knowledge that I can resolve whatever issues may arise without having to contact support - you need to consider that aspect of it.
Second - you're asking if it will work - without providing any information as to what it is you're trying to achieve, and how you plan to get there - that router is one end of a connection, the other end connects to a telephone system somewhere - I have no idea of who your VOIP provider is, what equipment they use, nothing - your first step should be to ask them what works for them, if a particular product doesn't work or is not supported, then don't consider it.
-
cjmedina has chained routers (which were not chained in the previous "FTP worked" setup) and because of lacking a router with supports DHCP disabling, I can't check my suggestion by myself.
So I described what cjmedina has to do if the router does NOT pass the DHCP requests to the VoIP hardware.
But I get the imagination my suggestions are not welcome :-[ .
Bye.
//Hsishi
-
On my D-Link DIR-655 I have DHCP set and have selected that none of the IP's be reset.
If I remove the D-Link router from controlling/holding the IP's and trying to see if my VOIP device a Grandsteam VT502 provided to me by my Phonepower service will reassign all my IP's.
I need a work around...
???
-
cjmedina has chained routers (which were not chained in the previous "FTP worked" setup) and because of lacking a router with supports DHCP disabling, I can't check my suggestion by myself.[/quote[
I've worked with a lot, and I mean a lot, of routers - both consumer product and enterprise product and I have yet to see a router that does not allow it's DHCP server functionality - whether that functionality be the DHCP client on the WAN side, or the DHCP server on the LAN side - to be disabled. Consumer product comes with both enabled for ease of installation, enterprise product comes with them disabled - your consultant configures what's required.
So I described what cjmedina has to do if the router does NOT pass the DHCP requests to the VoIP hardware.
And I'm explaining why it won't work - the router is not going to pass the request through.
But I get the imagination my suggestions are not welcome :-[ .
Bye.
//Hsishi
I'm sure cjmedina welcomes your suggestions - I'm just pointing out WHY that particular suggestion WILL NOT work. Don't take my word for it - go right ahead and prove me wrong -
-
On my D-Link DIR-655 I have DHCP set and have selected that none of the IP's be reset.
If I remove the D-Link router from controlling/holding the IP's and trying to see if my VOIP device a Grandsteam VT502 provided to me by my Phonepower service will reassign all my IP's.
I need a work around...
???
I googled GrandStream VT502 and got two hits - one of which led me to a GrandStream HT502 (which I suspect is the same thing - with the VT version being supplied by a VOIP provider called ViaTalk.
Interestingly enough - it seems that ViaTalk's tech support would rather have you put their hardware infront of your router and leave you to figure out how to make your stuff work, that tell you how to get their hardware to work properly behind a router.
Anyway - it would appear that the HT502 acts as a basic router - you should be able to connect a network switch to the LAN port on the 502 and connect your PCs and have them access the internet, and, if you put your DNS-323 on that switch and configure the dyndns client on the DNS-323 to update dyndns, and setup port forwarding on the 502 - you might get the ftp server accessible from the internet.
The only thing you'd be lacking would be wireless access.