Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
I just installed a DNS-323 2 500gb drives, raid 1 with version 1.02 of firmware.
When i run the dlink easy serach software it finds the device
When i try to map the device it asks me for user name and password but then comes back with a message FAILED TO MAP DRIVE. I use the name and password of a user I defined when configuring the unit.
I am able to ping the drive from the dos prompt
Not sure what the problem is?
Any help greatly appreciated.
Thanks
Offline
Your firewall might be blocking it.
Offline
Had the same problem, downloaded mapping software version 3.0 from Dlink US site and it worked better.
Regards
Oscar
Offline
When I am trying to map the DNS-323 to Win XP as a drive I always get an error ´failure to map the drive´ with Easy Search utility and `with the explorer connect networkdrive.
I already switched off the firewall and conncted the PC and the DNS-323 directly via crossover.
The webinterface of the DNS-323 is working fine and Easy Search detected the drive and everything was fine until pressing the connect button.
The PC and the drive are in the same address-range(192.168.0.1 and 192.168.0.32).
Offline
I am having the same issue. I can see the device except I can not map any drives. I get the message "failed to map drive". I can invoke the NAS. I see it on the WebUI. I can pretty much do everything except map drives.
Called Dlink about 10 times and they couldnt provide and help.
Any help or tips will be much appreciated. I can provide any details if needed.
Thanks.
Offline
Most likely these problems is not related to DNS-323 at all. These are more likely your network/operation system/firewall problems.
In windows try to use:
net use * \\your-device-ip-not-name\HDD_a /user:admin
In linux try to use:
mount -t smbfs -o username=admin //your-device-ip-not-name/HDD_a
Offline
Tried every way there is out there, but it is impossible to mount in linux and get support for special characters (swedish characters for me). If I use smbclient it works perfectly. If I use Konqueror without mounting then I see the characters correctly (but you can't stream data). But when i use mount, smbmount smbmnt, mount with cifs and whatever settings in smb.conf or parameters to mount it just won't work. Even tried all fuse file systems without success (smbnetfs etc.).
Is this working for anyone?
/gotdiskey
Offline
I had the exact same problem - and found a solution..
Swedish bought DNS-323 (FW1.01) with one Samsung Spinpoint 500GB, connected to a Gigabit switch.
Connected the drive to the left slot first, formatted with EXT2, web interface runs fine - but cannot connect on neither the Mac Mini OSX 10.4.8 nor the XP SP2!
So.. did all kinds of fiddeling and ended up resetting the unit to factory defaults. Also read that in single drive config, it's best to have the drive in the right slot, so I changed that.
Reformatted, with EXT2 once again. Now only testing from the XP since that's the one I know best.
The drive answers to ping and I can web to the interface.
Still cannot connect, using the 3.4.0.0 version of easy search..
When I try to map in explorer using Start - Run on XP i get the message "the drive could not be mapped because no network was found"..
So.. after some googling I found that this error message was connected to having the Workstation service in Windows XP stopped.
I started the service (dunno why it was stopped) and it all worked!
To start the service: Click Start, right-clict MyComputer, choose Manage, choose Services, right-click Workstation and choose Start. Make sure it's set to automatic to keep starting when you boot.
I dunno what part of my troubleshooting that solved it but likely a combo of the above as it works on both the XP and the Mac now.
Hope it helped some at least!
Kind regards,
/Lycaon
Last edited by Lycaon (2007-02-15 22:49:46)
Offline
lost most control of my fingers so pleaqe bear with me, it hurts like hell 2 type.
checked mine it was already set. but i reset then set it again. still same problem..
did u set anything like logon as...
i see it has a setting allow service 2 interact with desktop. maybe i need 2 turn that on??
hope the next firmware update cleans a lot of this mess up. its lookin better...
Offline
No, the workstation service should be in standard mode, just make sure it's started.
Also, to troubleshoot further, make sure there are no firewalls in between the computer and the DNS-323 to eliminate one more possible source of problems.
Offline
sala wrote:
Most likely these problems is not related to DNS-323 at all. These are more likely your network/operation system/firewall problems.
In windows try to use: net use * \\your-device-ip-not-name\HDD_a /user:admin
Thanks a million Sala, you solved it perfectly for me (on windows), with only a little change : HDD_1 instead of HDD_a.
Which makes the correct code (replace the xx with the correct figures) :
net use * \\192.168.xx.xx\HDD_1 /user:admin
which can be entrered in a .bat file or manually whith : START / EXECUTE / CMD and then the code
Since you seems to know very much about it, would you mind explain us why the "net use * \\192.168.xx.xx\HDD_1 /user:admin" code works while the Dlink easysearch tool does not ?
Offline
Had the same problem.
Used another method. I will try to explain in english - hope you get the picture since my version of XP is Danish.
Open your explorer (not the Internetbrowser).
Use "Functions" and "connect to a network drive" (or similar).
Choose a drive letter
Enter the IP you have given the box and the volume name.
Example: \\192.168.1.50\Volume_1
Can not remember if I did this with or without the 2 backslashes in the beginning but if the example is wrong try removing them and it should work.
Check the box "connect on startup" or similar and it will connect every time you start your machine and the box is turned on.
Regards
Offline
I found a solution at least for my problem.
Owing to the common recommendation to de-activated all unused Services in the properties of the Lan-connection, I de-activated all but the TCP/IP. The client for Microsoft-Networks service is urgently needed for the network-drive.
Activating this service again solved my problem.
Regards
Last edited by broesel (2007-03-10 09:41:43)
Offline
My problem (which took me 2 hours to find out) was that I had disabled NetBIOS over TCP/IP in the "Advanced settings"->WINS in the TCP/IP proporties of the Local Area Connection Proporties.
I enabled it, and now it works!
Offline
linlars wrote:
My problem (which took me 2 hours to find out) was that I had disabled NetBIOS over TCP/IP in the "Advanced settings"->WINS in the TCP/IP proporties of the Local Area Connection Proporties.
I enabled it, and now it works!
Solved the MAP-DRIVE issue perfectly, thanks a million
Offline
I have had similar problems mapping to my 323 after I upgraded to Vista Ultimate.
After trying the suggestions in this forum and still having sporadic luck mapping a drive to my 323, I came across another forum that fixed my problem.
http://forums.microsoft.com/MSDN/ShowPo … p;SiteID=1
Apparently, Windows Vista (Which I have) uses a different kind of authentication type when connecting to Samba devices.
After changing the security policy as directed in the link above, I can connect to my 323 and can reconnect at logon with no problems.
I hope this helps.
Offline
I had a similar problem as 714TLMan. I'm running Vista Ultimate and DNS-323 with 1.03 firmware from dlink.se (i.e. an EU version of the firmware (?)) ftp://ftp.dlink.se/Products/dns-product … 3_1.03.ZIP
I had the problem that I could right-click on a share in Windows Explorer and select "Map Network Drive", "Connect using a different user name" and after multiple user/password prompts, the drive was mounted.
However, all attempts to do this from a script with "net use" failed.
After applying the change to the Vista NTLM authentication scheme as described in
http://crazytoon.com/2007/02/05/windows … -update-2/
it works perfectly to mount the shares from scripts.
net use w: \\my-dlink-323\work mypasswd /user:tommy
Offline
Props to 714TLMan -- that was my exact problem, and that link gave me the exact solution. No problems with Vista Ultimate connections now.
Offline
Hi!
Very nice thread. That MS link from 714TLMan really fixed my Vista machine regarding the connection to my DNS-323. I got an unknown password error when using net use etc.
But now, the strangest thing, my XP pro box cant connect to the DNS-323 anymore. Not IT gets error 86, wrong password/username.
I've cecked the NTLM thing, and it's ok, and I've checked the netBIOS settings and thats ok as well.
On small tip... if you're checking netbios, be sure to check it on the connection you are using to access the DNS-323. i.e. if you use WLAN, make sure you have netbios enabled there. I just checked my LAN connection first before I remembered I had WLAN enabled.
Well aneehoo... no luck with the XP box. Any advice?
Oh.. gots firmware 1.3, disabled firewall and defender on the XP box, no luck.
Can see the shares with a net view\\IPADRESS.
Offline
I just solved this problem by totally ignoring the EasyDrive software that came with the DNS323
Instead I formatted the drives using the DLINK interface and then set up a workgroup. My DNS323 had been connected to my wireless router, but I could not find it on the workgroup I had created. I tried everything I could think of but with no success. This is when I realised that this was the work of the devil, aka Norton.
As soon as I disabled Norton's Personal Firewall, and restarted the computer the DLINK appeared in my office workgroup.
I then used the map drive facility under My Computer-Tools to create the logical drives and map these to the 2 hard disks.
Hope this helps.
P.S this was on Windows XP.
Offline