D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: netmation on January 17, 2009, 04:00:38 PM
-
Moving into a shared office space and before I get my IP address setup which I will assign to my router, I am curious as to which of these solutions will work. Assuming I want to put a device like a DNS-323 off of my DIR-655 router, accessible via FTP by public users. Any pro's and con's of these 3 setups.
1. Dynamic IP Address
2. Static IP Address from Internal Network 192.168.xxx.xxx
3. Static IP Address from Public Internet, and opening up ports
on the office Firewall.
-
1 - Dynamic address - it works BUT the address may change from time to time and drive mappings may fail as a result - when dealing with servers, a static ip is always advisable
2 - Static ip from the internal network - see answer above.
3 - Static ip from public internet - not possible, not if it's "behind" a NAT router.
You could have a static public ip and forward ports to the static private ip that you have the DNS-323 at, but then you have a slew of security issues to deal with.
-
Don't understand that it doesn't work behind a NAT router. Isn't the DIR-655 a NAT router, I can't plug it into that? Sorry my ignorance.
-
i use a Linksys Router with Tomato Firmware. I assign a fixed IP to the DNS-323 (Static IP), and of course, i name it.
So i can access the DNS using 2 different way : \\ipadressofthenas\Volume_1 (or 2)
or \\mynasname\Volume_1 (or 2)
Some router are not very good with DNS name, so access it using the Fixed IP you assign will work.
Other thing, if you are using access restriction on the DNS (username and Password). Try to use the same username and Passord in Windows, and on the NAS. Sometime, Windows made some weird response. Having the same username and password prevent these time of weird response.
use the naming convention 8.3 (8 char max... but don't use the .3 ..)
-
Don't understand that it doesn't work behind a NAT router. Isn't the DIR-655 a NAT router, I can't plug it into that? Sorry my ignorance.
Perhaps the second rule of ip addressing is that the address of a device must belong to the "subnet" it is connected to - if you have a device at 192.168.0.32 connected to a network that is 192.168.1.x - nothing on the network will be able to communicate with the device at 0.32 - from an addressing standpoint, they are not on the same network.
NAT routers, like the DIR-655, will always have a private network range on the internal interface - so if you connect a DNS-323 with a static public address to that network, you will not be able to communicate with it because of the different addressing.