D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: raider4123 on February 17, 2009, 07:49:49 PM
-
After upgrading my firmware from 1.04 to 1.06, I have been unable to locate the nas on the network using the easy search utility. Does anyone have any idea why this may be happening?
-
What are the front panel LEDs doing? Are they on/off/flashing?
Was it configured for a static or dynamic ip address?
If dynamic, restart it and then go to the DHCP server and check to see what address it was given, and then put that in the browser.
-
The LEDs are on but not flashing. Before upgrading the fw, I configured it for static ip. The ip is still the same, as I can log into it from the web browser.
-
You don't need the Easy Search Utility to get the 323 working. Some people have reported the same issue, but if you have the manuals and have read them, you should be able to get everything up and working (and probably come out with a better understanding of the 323).
-
True, but I do need it to get the BitTorrent client installed right?
-
That seems odd that easysearch can't see it
Try another computer, maybe its a firewal
So the webbrowser can see it right so it is 100% connected to your network for sure
Easysearch has a refresh button which Im sure you used
Make sure firewall is off or try another computer and make sure its the latest easysearch program and latest driver 1.06
http://www.dlink.com/products/support.asp?pid=509
http://www.dlink.com/products/support.asp?pid=509 (http://www.dlink.com/products/support.asp?pid=509)
by default easysearch should work regardless of hookup
-
Hello all, I have the exact same problem. I have a Vista laptop and XP Desktop, I have disabled both the Windows firewall and ESET firewall. I have tried connecting both wirelessly and via Ethernet cable.
No matter what I try the ESU cannot locate the DNS-323. This being despite having a nailed up connection with it (ie I mapped the DNS within Windows Explorer and can access it on both machines wirelessly and wired).
I only want to add the BitTorrent client.
1. Does anyone know of an alternate method of loading the BT client onto DNS (beside using ESU)?
2. Does anyone have a suggestion for enabling my ESU to find the DNS on my setup?
PS have firmware V1.06 and ESU 4.4.0.0 (both machines are 32 bit, I have followed the instructions listed for Vista connectivity (secpol settings) nothing works - getting very frustrated)
Any suggestions greatly appreciated.
-
Further to my above post...
I have managed to get the dns-323 to show up (partially at least) through the ESU. This was by direct wired (ethernet) connection to my laptop. When the DNS shows in the ESU window and I click on it the options buttons on the right ('configuration', 'language') grey out and I cannot choose them. I have access to the 'bit torrent' button but once pressed, it pauses for a while. I am unable to access the hard drives or configuration menu while connected in this manner. When I reconnect with DNS connected through my router (netcomm nb9w) and try to select bit torrent, a dialogue box appears saying that client is not installed and it can be located on ESU.
One of the main reasons I purchased the DNS was for BitTorrent. The device works perfectly EXCEPT for the main reason I purchased it - BitTorrent. Any suggestions greatly appreciated.
-
Further to my above post...
I have managed to get the dns-323 to show up (partially at least) through the ESU. This was by direct wired (ethernet) connection to my laptop. When the DNS shows in the ESU window and I click on it the options buttons on the right ('configuration', 'language') grey out and I cannot choose them. I have access to the 'bit torrent' button but once pressed, it pauses for a while. I am unable to access the hard drives or configuration menu while connected in this manner. When I reconnect with DNS connected through my router (netcomm nb9w) and try to select bit torrent, a dialogue box appears saying that client is not installed and it can be located on ESU.
One of the main reasons I purchased the DNS was for BitTorrent. The device works perfectly EXCEPT for the main reason I purchased it - BitTorrent. Any suggestions greatly appreciated.
If you're going to use a direct connect configuration, you need to set static ip addresses.
-
Thanks fordem. It was remiss of me to say in my above two posts. I have tried both static and dynamic IP settings in both setups (ie wired/wireless) and on both PCs. Still no luck.
-
Thanks fordem. It was remiss of me to say in my above two posts. I have tried both static and dynamic IP settings in both setups (ie wired/wireless) and on both PCs. Still no luck.
Just checking - you say you tried both static and dynamic IP settings on both PCs, but you don't mention the DNS-323.
The scenario you mention - using a direct ethernet connection, and being able to see the DNS-323 in Easy Search but with the configuration buttons greyed out is caused by Easy Search being able to locate the unit through the use of ethernet or network hardware broadcasts, but being unable to communicate with it via tcp/ip - which will also cause you to be unable to access the hard drive or configuration web page.
What that says to me is that a physical network connection exists - that the ethernet broadcast can use to locate the DNS-323 - but that something is preventing tcp/ip communication from occurring, and, with a direct connection (ie, no DHCP server) the most common cause is a lack of appropriate ip addresses - either no address set or an address in a different subnet.
-
Hi,
Are yolu using the latest version of the easy share utility, i had to downlod this for it to see the DNS-323.
Steve
-
Thanks Steve and Fordem.
When I stated I had tried both static and dynamic IP on both PCs I actually meant I tried the DNS set to static IP and tried connecting wirelessly and then with ethernet to each PC. I also tried this with the dynamic setting.
Yes I am using the latest version (4.4.0.0) ESU.
I have just received an email from D-Link who suggest I try v4.2.0.0 so am off to give that a go.
Fordem, at the bottom of your last post you mention 'either no address set or an address in a different subnet'.
I have set the DNS IP using the web configuration (192.168.1.200) - I don't understand what I need to do with the subnet issue (or what to check). Any help appreciated.
Ta
-
Further to my above post:
1) I tried installing and running ESU 4.2.0.0 (earlier v suggested by D-Link) - no luck
2) I tried changing the subnet mask in the DNS from what it was defaulted at (255.255.255.0) and lost all contact (ie could not access via web interface) and had to reset device.
Any other thoughts or any known way of installing BT client without ESU? (I am asking D-Link same question but they haven't got back to me on that.
Ta
-
Fordem, at the bottom of your last post you mention 'either no address set or an address in a different subnet'.
I have set the DNS IP using the web configuration (192.168.1.200) - I don't understand what I need to do with the subnet issue (or what to check). Any help appreciated.
Ta
An ip address has two separate parts, a network portion & a host portion, and it is the subnet mask that determines where the one stops and the other starts. With a typical consumer network, the subnet mask will be 255.255.255.0 (and please don't change it unless you know why you're changing it) so that the ip address which will probably look like 192.168.x.y where x & y are numbers between 1~254 will split in to a network portion of 192.168.x and a host portion of y.
If you set static addresses on the DNS-323 and the PC and the network portion (the 192.168.x) do not match, then the devices will be on different "subnets" and will be unable to communicate with one another.
If you do not have a static address set on the DNS-323 it will default to 192.168.0.32 and you will need to set a static address in the 192.168.0.x network range to communicate with it - if you do not have a static address set on the PC, it will, in most cases, use a process known as APIPA to get a randomly selected address in the 169.254.x.y network range.
-
Thanks fordem
I am clearly a bit slow when it comes to the finer points of networking. What I think I take from your detiled reply is "don't change subnet if I don't know what I'm doing" (this clearly applies to me).
Is there anything I can check to make sure that PC and DNS (and router) are using the correct subnet?
With the DNS plugged into my router and my Vista laptop connected wirelessly (meaning I can access DNS drives through Windows explorer mapping and access configuration pages through the web (static ip 192.168.1.200) and firewalls turned off I would have thought that the ESU would be able to find the DNS??????
-
Two things ...
First - with a subnet mask of 255.255.255.0, if the first three sections (or octets) of the address - the 192.168.1 portion - are the same, then the devices will be on the same subnet.
Second - if you can access the drives and the config pages I would think that EasySearch should find the DNS-323 - it always has in my case - but if it doesn't for you, and Easy Search can see the unit when directly connected, which I think is what is happening, then lets' try to get BT installed that way.
Here's a step by step
1 - Start by setting the DNS-323 for DHCP - go in to the admin webpage, select Setup and then Lan and make sure the DNS-323 is configured as a DHCP client - if it's not, make a note of the settings before you change it, so that you can change them back after.
2 - Set the PC for a static address of 192.168.0.31, with a subnet mask of 255.255.255.0, the other stuff DNS servers and gateway can be left blank - again, make a note of any settings so you can change them back later.
3 - Connect the PC directly to the DNS-323 with an ethernet cable - and run the EasySearch - if it finds the DNS-323, try to install the client.
Finally - reconnect everything the way it was before and reset any addresses you may have changed.
Let me know how it goes
-
Thank you so much for your help Fordem, I now have BitTorrent on my DNS.
I still don't understand why ESU can't locate it through my modem/router but the goal has been achieved. Your efforts and tolerance of my ignorance with the finer detail of networking is GREATLY APPRECIATED. Thanks again - all good now. ;-D
-
You're welcome - and - like you, I don't understand why, EasySearch can't find the unit when your browser can.
My suspicion is it's firewall related, but, I believe you mentioned disabling the firewall - the thing is, I have come across at least one "internet security suite" (a combined anti-virus & firewall) that blocked telnet communication even though it was disabled, and I ended up having to uninstall it, I don't what you were using, and I don't know if it may be a similar issue.
-
I don't know if you've come up with an answer yet but I ran into the same problem. After a couple fun filled hours with 'customer support' >:( I figurd out the problem was wiith my vpn router. I swapped that out and the problem went away - put the router back and it re-appeared.
-
I don't know if you've come up with an answer yet but I ran into the same problem. After a couple fun filled hours with 'customer support' >:( I figurd out the problem was wiith my vpn router. I swapped that out and the problem went away - put the router back and it re-appeared.
Even with that "evidence" I wouldn't describe the router as the "problem" - there are too many variables that can change when the router is changed - I'll give you just one example.
The private network range used by the router is typically 192.168.0.x or 192.168.1.x (there may be others, these are the most common) and at some point the windows (or other software firewall) was configured to trust one of those two ranges. The router is then switched to one using the second range and most things - browsing email, etc. - work just fine, but certain types of local access do not. Switch the router back and the problem goes away.
The cause in this example is not the router, or the network address range, but the firewall configuration, changing the router makes the problem go away as will changing the network address range in the router's DHCP setup, but neither one of those is the problem.
-
I too have seen that alot as Fordem explained sometime it is just the anti-virus software not trusting certain IP address's or being picky about allowing new programs on the PC to access the network trying to protect it from viruses as that s what it is designed to do. This can take some knowledge of the software to properly configure it. Also having multiple anti-virus programs that are not designed to work together to protect your PC can cause major issues trying to access your network or install new programs. I would be willing to bet the issue you are seeing is due to the anti-virus software on the PC. I don't think I have every seen a case of this and had the customer tell me there is no anti-virus software on the PC.
-
I'm also cross posting this on the "cannot find harddriver, cant reset" thread (page 4 of DNS-323 thread):
Hardware version B1
Firmware version 1.03 (upgraded successfully to 1.06)
2 X 500G Maxtor drives.
After initial connection, I was able to get into the admin panel, and change the default
settings to what I wanted, activated the UPnP, IiTunes and FTP servers, setup network
access, connected via FTP etc. Everything was working fine. I was able to map
network drives, connect via FTP, login to Admin panel etc.
Then I did something very stupid ..... edited a saved config file with WORDPAD (don't ever
do this!), went into the Admin login panel, clicked on SYSTEM tab and told the DNS-323
to re-start with the modified config file, which it duly tried 2 do. I got the "wait re-booting"
page whilst the time counts down, and then it died.
I have tried everything to revive it, but no success. Here's what happens:
1. Power up DNS-323 and it starts, with power light flashing (like its supposed to).
2. After a few seconds, the drive lights turn solid blue.
3. The network light turns solid blue, but flashes once in a while.
4. The power light never stops flashing.
5. The DNS-323 does not connect to the DIR-655 router ........ so I cannot
see the DNS-323 with either a browser or the Easy Search Utility.
6. Pushing the keyhole re-set button to restore to factory settings does nothing, no matter
how long it is depressed.
7. The power button never stops flashing.
8. The only way to interrupt the DNS-323 is to pull the power cord.
So, bottom line is, I cannot access to any form of Admin function to reset the damn thing.
Is there any other way or method that one could use to "flash" an original factory default
operating system and configuration onto the DNS-323, so that I can have access to it ???
I have also tried a direct cable connection from my laptop to the DNS-323, but could not see
it. However, I might have done something wrong. With such a direct cable connection,
must a crossover cable be used ?? (I thought most RJ-45 ports on all devices are auto-detect
in today's world, so that any cable can be used). Also, how does one setup the IP configuration
on the laptop's NIC so that it can see the directly connected DNS-323 ???
This thing is brand new and I really want to get it working (I promise never to edit a config
file myself again!), and any help is appreciated ........... tried going thru D-Link's tech support
on the phone but that is a lost cause ..........
HELP !!
-
os2buddy - the easiest way out of that is going to be to RMA it.
Basically what is happening is the edited configuration file is preventing the web server from running.
-
I experienced this same problem exactly: the DNS 323 is on my network and working (I can map volumes, I can access the config pages) but it does not show up in Easy Search.
It appears to have something to do with the Ethernet port driver on my motherboard. Since I suspect it is a driver issue, it is relevant to note that I am still running Windows 2000.
Here is what I have observed:
1) Start ESU. DNS 323 doesn't appear.
2) Close ESU.
3) Open the properties page for the ethernet adapter. (In Win 2k: Control Panel -> Network Connections, then right-click the correct adapter icon and choose properties. Win XP is similar except that I believe the Control Panel item is called "Networking." You are on your own in Vista.)
4) Make some change in the properties and close the dialogue.... doesn't seem to matter what you change. For example, un-click the TCP/IP protocol component.
5) Again open the dialogue but now reverse the change you just made, then close the dialogue. (Note: most home and business networks require TCP/IP, so expect that your computer will not be connected to any network if you close the dialogue with that component un-selected.)
6) Now the DNS 323 shows up in ESU.
My theory is that by changing a property, you reset the driver for the Ethernet adapter. You have to do it twice, changing and setting and then reversing the change, because if you don't change anything when you close the properties dialogue, the driver will not be reset.
Further observation: after hibernate and restart the computer, DNS 323 is again missing from ESU. Follow steps 3-6 above and it's back.
YMMV but this has worked for me a couple of times now.