Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
I've struggled for over an hour to get this thing to work and pretty unhappy so far. The documentation is rubbish for a low level computer user. Can someone please help me out? I have disabled firewall, defender, virus, adware, spyware, and all other background programs I can think of. The "easy search utility" will still not map the drive to the computer. What do I do to get this thing on my list ofm drives in "My Computer"? [windows xp sp2]. Thanks.
Offline
I got mine to work in no time after plugging it in... didn't have to disable any anything. Anyways, log into your router and find out the IP address of your DNS-323 box. If you can't find it, this means the DNS-323 doesn't exist on the network. If it's there, suggest you type in the MAC address and give it a static IP address ... usually people do this static IP if it's a server. After that, open internet explorer and type in the IP address... for example "http://192.168.0.200" (whatever yours is set at). Type in the admin (username) and password (none). Then run the setup wizard and go from there. Eventually it'll reformat the drives. Good idea to download/install the newest ver. 1.02b firmware before loading any files on this NAS drive. Later after the setup (including setting up users/accounts), the D-Link easy search utility will be more useful. (Download the newest utility from their website too.) Good luck.
Offline
Thanks so far Phil. A major boost to morale. Logged into the router and found the DNS-323. How do you tell if the IP address is static or ... whatever the alternative is. How do I make it static? Where do I type in the MAC address?
I opened IE and typed in the IP address I copied down, using the "http://" prefix, but got a message saying the address couldn't be found.
What's the next step? Thanks again for your help.
Offline
Hi,
This sounds very odd and network related. Can you ping the DNS? From the router, get the IP and open cmd.exe. Issue command "ping 192.168.XXX.XXX".
If you can ping the device properly, try to mount it. In the explorer, type: \\192.168.XXX.XXX\HDD_1 or \\192.168.XXX.XXX\Volume_1 depending on firmware.
If you cannot ping the device, then you have some kind of network issue.
Step 1 - Check your cables, broken cables are a pain in the .... and unfortunately quite common.
Step 2 - Check you IP's, network masks and gateway address. Typically 192.168.0.xxx, 255.255.255.0 and 192.168.0.1 in home environment.
Step 3 - Use a free IP adress and set it to the DNS from the Easy Search Utility. It is using multi-cast and if your cables are ok you should be able to set it even if there are IP address colissions on your net.
Step 4 - Twisted cable and static IP both on PC and NAS
Step 5 - Replace the unit. Put it in the micro, full effect, 30 seconds and then send it to D-Link. No traces....
HTH/Apan
Offline
OK, progress report. I have managed to set the IP address to static via the easy search utility, download and install the firmware update (BTW, the file pre-install was labelled 1.02b but the status page in the utitlity shows firmware version of 1.02 ... is this common?), formatted to RAID1, ext2.
The problem now is that the unit doesn't show up on the list of drives, and I get an error message of "Failed to map drive".
How do I get the unit to show up (without coaxing it along by showing it the micro) ?
B
Offline
Bish wrote:
OK, progress report. I have managed to set the IP address to static via the easy search utility, download and install the firmware update (BTW, the file pre-install was labelled 1.02b but the status page in the utitlity shows firmware version of 1.02 ... is this common?), formatted to RAID1, ext2.
The problem now is that the unit doesn't show up on the list of drives, and I get an error message of "Failed to map drive".
How do I get the unit to show up (without coaxing it along by showing it the micro) ?
B
Try to map it using IP, in explorer type \\192.168.0.XXX\Volume_1 and you should see the disc. From time to time, in XP , I have problems accessing the unit using it's 'name'. However, IP always work. I never have this problem with W2K and I'm thinking that the problem might be related to the negitionation part where XP will take over the "server role" and W2K will not.
And, if you put it in the micro, remember to have fun and keep in mind that this might brick your unit
Offline
Thanks everyone, it's up and running now, and visible on the network. Cheers.
Offline