D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: deca66 on December 11, 2010, 09:28:59 AM
-
Hi all,
I had only one disk on left drive and all worked fine. The NAS is access from Vista through static IP 192.168.0.99. I was accessing it from Vista with address \\192.168.0.99\Volume_1.
Today, I have inserted a second disk on the right drive (a Caviar Green - 2 TB WD20EARS). The admin interface has detected and has formatted it. But now, it goes wrong with this disk :-\
On Vista, I can only map drive "\\192.168.0.99\Volume_1", but not "\\192.168.0.99\Volume_2" (==> Windows cannot access to ...").
Easysearch can only see Volume_1
On the admin interface, tab advanced/network access, in "SMB list", I have now 2 drives whose path is "Volume_1" for one and "Volume_2" for the other, but share name is "Volume_1" for both.
With ftp, from /, I can see Volume_1 and Volume_2.
Any help ?
Thanks
-
It seems there is an inversion somewhere, as when I browse the DNS-323 using admin interface, Volume_1 data is actually under Volume_2 !!
Is the error coming from the fact that, when I had only one disk, I have put it on left drive ? If yes, how to come again to a normal situation without loosing my data ?
-
OK, I have fixed it by deleting SMB mapping and creating them again. All works fine now.
Sorry for disturbing you guys...
-
Hi again,
After the above problem, now, I cannot connect to the NAS using telnet under Vista "Command prompt" (launched being Windows admin). I get the error "impossible to open host connection". All other stuff work fine (web interface, Vista access to both drives, ping, ...)
Any ideas ?
-
A telnet service doesn't run on the NAS. For that, you need to look at third party software. Namely Fonz Funplug (FFP)
-
As already stated. Telnet does not run on the NAS in its original configuration. See (http://wiki.dns323.info/) for information on fonz funplug.
Regards,
Wiggs
-
Thanks for your reply. I do have ffp, but there was a problem following the install of the second disk. It works fine now. I apologize for my error again. Hope you'll not consider me too bad...