DSM-G600, DNS-3xx and NSA-220 Hack Forum

I have a similar setup to yours (WRT-54GS, 3 CPUs running XP, wired and wireless). The only problem I had out of the box was that the included Dlink search tool couldn't find the DNS-323. I tried it with both a wired connection and a wireless connection, but no luck. I finally scanned my network with the Angry IP scanner to find the IP address the DNS-323 was using, and simply connected to the http interface.

As far as the sequence of installing, You need to install your drives, format them, then upgrade the firmware to 1.03 or the 1.04 beta. I used ext2, as it is the default, but I haven't heard anything about problems using ext3.

Don't use the Beta firmware (1.04) unless you are playing around...it should only be used if you are interested in helping Dlink figure out the bugs in it.  You should stick w/1.03 (the most recent available formal release). 

The instructions that come w/the Dlink are all that you need...simply open the box and do what they say and you'll most likely be fine.

OK !!!   My unit arrived and I can say....after reading what I thought were some pretty 'worrysome' problems from people, I was able to install the unit and get it up and running on my network with the 'measure twice, cut once' rule of caution.  It was pretty easy and as stated above, follow the quickstart guide and all is well!
  After I connected the DNS-323 to the network, booted up my 'puter, and turned on the 323, my computer popped up a dialog which said "A new device is now avaliable on your network. For more information, click here".  I did not click here....I was afraid I might screw the install so I used the easy search util and found the 323 right away.  It did not ask me to log-in when I accessed the 323...it went right to the format screen and I was able to format in less than 15min with Ext2, RAID1 on 2 Seagate 500gig drives.   The name of the DNS-323 showed as dlink-EC23F3 which I thought was strange as all the examples I have seen showed "DNS-323" but I was able to change this after formating.  After formatting I was sent to the log-in screen and after logging in I updated the firmware to 1.03 with no problems.

  Thanks for the info from all!  It really is a cool unit!

  The next question I have is this....  After mapping the drive to my computer it is available....but the next day (if the computer(s) were turned off) I need to re-map to the XP's in the network.  Here is what I have done....  I set users and groups with only myself and my wife as a group with full access to 'volume_1' and my kids as a group with limited access to some folders on the drive.
  Will I always have to map the drive to access it?  Or is there a way to have it come up with the XP box when turned on?

  And I noticed that if I give "read/write" access to the volume (volume_1) and then 'read only'a ccess to a folder in the volume that the read only acces is ignored and read/write is used for that user/group.  I guess I need to learn about this!?

Thanks again,
Vman

Vmanjeff wrote:

The next question I have is this....  After mapping the drive to my computer it is available....but the next day (if the computer(s) were turned off) I need to re-map to the XP's in the network.  Here is what I have done....  I set users and groups with only myself and my wife as a group with full access to 'volume_1' and my kids as a group with limited access to some folders on the drive.
  Will I always have to map the drive to access it?  Or is there a way to have it come up with the XP box when turned on?

Vman

Did you tick "reconnect at log on" in the mapping section of windows explorer? or were you using easy search for the mapping? Try "My documents" -> "tools" -> "Map network drive" AND select - "reconnect at log on " FWIW.

Tack!  You are the Man!  And from Australia, no less!  My 19yr old son has wanted to go down under for several years now.  He has a three year plan to get there.....since Dad will not pay!

And DNS-323Talker, too!  Thanks for checkin' back with me!

  You know, I DL'ed all the 'stuff' from Dlink.com and did not think to actually READ it!  Thanks for the replys to both Q's.  I went back and read the pdf's and am OK now.  And you are right about all above.  The last time I did anything with this type of thing was networking my Amiga 4000T with WinXX back in the dark ages of 1996!
  I just set-up my 3 sons access to 'volume_1' with read only and then set up a folder 'Wildboys' for them to have full rights.  This way they will not mess-up our photo archive or iTunes (90 gig worth!).
  As far as mapping the drive...I do not have my 'puter password protected and the sign-in for the 323 I set up as a group with read/write access.  I did as you said and mapped the drive and in the 'map drive' dialog I clicked 'sign on with a different user name' and kept the checkbox checked for 'reconnect at log-on. But when I rebotted my puter it did not work.  I'll keep looking into this...maybe cause I do not have a login pw for the XP box?  Or that my 323 login is different??

  Now I need to get the FTP running so my family can access our foto archive.  Much better than writing lots of DVD's with pix on them.  Just let the family DL what they want.....I need to read the docs from my Linksys router so I can see how to set that up.  I set the 323 to a static IP and in the Linksys "applications and gaming section" (is this correct?) I set the static IP the start/end port #, TCP protocol...not really sure what the Application name should be, and enabled it....but I have no remore computer to test so I tried to use my laptop with SmartFTP Client but no go.  I'm not too sure how to type the address into SmartFTP.  The Dlink setup says to use the routers WAN address.  I'll keep plugging away at this too...!

The iTunes server works OK for my network.  I still do not see how I can (IF) I can set up a playlist for the 323 iTunes music...is THIS where I need to start learning fun_plug and firefly?  And, is anyone using one of Dlinks media servers?  I am mostly interested in playing iTunes playlists to our home stereo for those wild backyard parties we never throw.  The Dlink liturature seems to indicate I would have a nice display on a remote TV by the stereo.  And playing some mpeg files on the TV is a plus.

Tack....you worked hard on me and I am thankful for all....So if you pass this Q to another I don't mind at all !!!

Vman
Up-Over and on the other side (from down under)

Last edited by Vmanjeff (2007-07-15 04:32:06)

YOU are learning alot from me!!??  Looking at the other posts here I feel like a caveman asking a 2006 man how to make fire!  I am really at the beginning!!

  I looked up the WAN address of my router because the info blurb in the DNS set-up said "From the outside world, remember to access this FTP server by using the WAN address of your router"...and I tried this in Iexplorer and SmartFTP but this did not work....so taking a 'Q' from you I just tried my static IP and ...bam!...it is all there! 
  But how?  I mean, I have a static IP....what are the chances at least one other person in the world has the same IP!!??  How does my browser know to go to my DNS??   I am having my brother in another state check it out right now to see if he can log on.......

Vman
Virginia Beach, Va.

Hey Tack,

  My brother finally hooked up with me after paying attention to his woman (imagine... a woman comes between brothers!?)

  Anyway...on my local network the static IP works when entered into any browser/FTP program on the LAN.  But when my bro tried it did not work.  I needed to go into my Linksys set-up and find the IP assigned by my provider to my specific router (NOT the WAN address as shown in my routers routing table, this is what prompted my question at the beginning of the FTP thread since the DNS says to use the WAN address of the router)....then it worked!  He was able to browse all the folders I have given rights to.  I have to check out read permissions today.
  To explain, and make this a bit more confusing...Under advanced routing in my router setup is a button for 'routing table' and since the DNS instructions said to use the WAN address I just thought...well, use the WAN address (as put forth in the advanced routing table), which is different than the routers assigned IP.... clear??!!

  Reasoning it out I think this is what happens....someone correct me if I am wrong....My router is assigned an IP from my provider.  I set the routing/forwarding table in the router to 'point' assess requests to the DNS.  Using the DNS IP in my LAN goes to the right place but everyone else in the world needs to use my routers IP which then forwards the request to the DNS for access.  To confirm this I used my static Ip in my LAN and was able to FTP....then I tried my routers assigned IP in my browser and it worked too, so this tells me that the router was forwarding the request to the DNS...I think!?
I am concerned with my router setup though....since I have 'automatic configuration - DCHP' selected might the provider change the set IP for my unit?  Or is it hardwired to each router manufacturd...?  This would not make sence!!?  More research is needed...possibily on the link you provided....
  NOW my only concern is security!  Since to my understanding the log-in names and pw's are sent in the clear...

  Thanks for the link...Again, I have a wealth of info at my fingertips but do not think to use it!  Lazy, maybe? 

I am beginning to get curious about fun_plug 


Vman

Last edited by Vmanjeff (2007-07-16 16:04:29)

Vmann,

If you use DHCP and don't pay your provider to supply you with a static IP on your WAN address this could change anytime.

Regarding the WAN address. Have you had a look at the routing table now when you know the correct IP?
It really should be there as gateway address for the network on the WAN interface. However not for the network named 0.0.0.0.

frodo wrote:

Vmann,

If you use DHCP and don't pay your provider to supply you with a static IP on your WAN address this could change anytime.

Regarding the WAN address. Have you had a look at the routing table now when you know the correct IP?
It really should be there as gateway address for the network on the WAN interface. However not for the network named 0.0.0.0.

Hi Frodo

I checked with my provider and I would need a business account for a static IP so I will follow Tacks recommendation to use dynDNS.org I think.
And (again) regarding the WAN address, I looked at my routing table and it has 3 lines of entries.

DESTINATION LAN IP     SUBNET MASK     GATEWAY     INTERFACE
192.168.1.0                    255.255.255.0      0.0.0.0       Lan & Wireless
70.160.xxx.x                  255.255.255.0       0.0.0.0      WAN (internet)
0.0.0.0                           0.0.0.0                70.160.xxx.x  WAN (internet)

the 'x' are all numbers with one number different (the end number) between the two.  Reading what you said it seems that I should have the gateway IP (70.160.xxx.x) in the line above where it is.  Is this something I might have configured wrong?

Vman

Last edited by Vmanjeff (2007-07-17 09:31:44)

OK....rested...and I have let all the discussion sink in...!

Tack wrote:

Hi Vmann -
couple of things you are slightly confused about. Sorry I havn't been more clear.

I have d/l your router manual from the lynksys.com site http://www.linksys.com/servlet/Satellit … torWrapper  and will refer to it as I go


The WAN is your "wide area network" = the Internet (see page 40 of the manual to confirm this - ignore page 40 otherwise lol) - not the wireless local area network (WLAN- for example- note the 'L') so your WAN IP is the one your router is assigned by your ISP. (see status tab -> router -IP Address - Page 59 - NOT the local network tab...)

You are funny ;-)  Yes, this did get me, but not in the way you think!  The DNS-323 set-up FTP screen said to use your routers WAN. I found the routing table in the post above in my router and there is an entry for WAN.  This WAN did not work (the 70.160.xxx.x IP)....but it is the WAN IP of the router, I thought???  Confusion..  Adding to the confusion was the fact I had never port forwarded anything in my life so I was not sure if I had set this correctly in my router.

The initial  IP your brother entered seems to have been the DNS323's  static IP INTERNAL to your network, not the WAN IP. Internal IP's on your network will be 192.168.1.3 (for example). the "192.168..... type are "reserved ' for internal network use - not Internet use - a simplification admittedly)

Yea....we tried this initially because my mind could not resolve the conflict between my ID and my ego so when the super ego finally took over I collasped in a sweaty lump and just had a cigarette.....  Wait, I got sidetracked... I had an idea of what was really happednig but it reached a mind roadblock so I did not really get it until I read you post..several times!
  I did what another of your posts suggested and used the IP of MY intranet and was able to use the DNS-323 static IP to log-on intranet and the routers dynamic IP assigned by my provider to log-on also.
  Using the WAN IP I found in the table did not work from anywhere and as a lark I told my brother to enter the dynamic IP of the router and he got on...but I did not understand how and why, again, until reading your latest post!  I now seem to remember going through this when I set-up the Amiga to WINxx network back when.  It seems I used Samba on the Amiga and a program called Tropic on the PC to serve the Amiga...and the 192.168 reservation for home use, etc....etc...

The confusion is the term STATIC IP

There are two sorts relevant to this discussion - your router MAY have a static ip and your DNS323 may have a (different) static IP - you were confusing the two. I NOW know your router has a DYNAMIC ip and your DND323 a static ip - read below

Automatic configuration DHCP - This means your ISP will assign the WAN IP to your router upon booting and at other specific times as required - i.e. you have a DYNAMIC WAN  IP to the outside world   eg 203.123.456.321 (it is theoretically possible you have a WAN static ip and are simply getting the same IP assigned every time anyway - only your ISP can tell you for sure - usually you pay extra for this lol)

I checked with my provider and they release all IP's every 24 hours and then renew them.  I was hoping to avoid other complications....but... I finally took your advice and signed up with www.DynDNS.org .  The free service I signed up for seems to work seamlessly and fast!

More on Static IP's
SOME ISP's assign your connection (your router in this case) a STATIC unchanging/unique ip on the internet - some a DYNAMIC ip that will change from time to time - without you knowing - hence the need to use something like www.DynDNS.org (see my prior post). This site can be updated with your new IP as required . Routers are able to tell the site when the ISP's IP they have been assigned changes - You can configure this in YOUR router ....Page 36 of the manual - tab DDNS. Register (= free) with dyndns.org first.

After reading this again...since my router has this in its setup (and I enabled it) does this mean I do not need the utility to update my IP running in the background on my 'puter?  And that the router, when my provider...Sorry, I will just RTFM !!!!!  Lazy again.... ;-)

You also have an "internal" static IP assigned to your DNS323 you say at http://dns323.kood.org/forum/p4849-2007 … html#p4849 - this could also be static or dynamic but you have chosen static (good!). You seem to have sorted that out. This internal IP is NOT unique - just unique within your network BEHIND your router.... read up on networks and sub nets :-) This IP is used by millions <?> of different users, but is only accessible through the "front door" of your router. Your router "knows" where to send incoming requests - like FTP - from the port forwarding  table (application and gaming  Page 51 manual - linksys talk ) you have set up ( Send all port 21 to the DNS323's LAN IP). 
   
You router will in its turn - act as a local DHCP server WITHIN you network ( automatically assign a "within-network" <internal> IP to each connected device) unless you give the devices a STATIC internal ip....(whew still with me?)  Either way - assign your DND323 a static IP in your network (LAN IP)  so you can easily access it from out side....otherwise you risk the assigned LAN IP of the DNS323 changing next time you reboot the DNS323 as it MAY be dynamically assigned another IP by your router- ( for example - currently DNS323  may be 192.168.1.99  ..... next boot it MAY be 192.168.1.35..... if the router is sending FTP to 192.168.1.99 still - you will be outa luck...) The corollary is also that your ROUTER may be assigned a different WAN ip by the ISP when the router reboots - so you brother may NOT get you at 203.123.456.321   (for example)

Still with you and ...done!  I think alot of the confusion, besides you being from another country where good english is not the norm , is in the translation and specific jargon associated with "computers" as opposed to something like my job or average everyday life.  I do not know the jargon well enough and sometimes put my own twist on things.

I now suggest we set you up with  DynDNS.org ( or similar) so your cousin/brother/bank manager can ALWAYS and easily FTP into your DNS323

My bank has their hand in my pocket already...I think I will keep the DNS-323 a secret


Vman