D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-321 => Topic started by: Highmaster2 on October 29, 2009, 08:21:16 PM
-
Just got this unit as a replacement from D-Link. Never got the 1st unit to show up either - tech support said return it. Opened the replacement, installed a Seagate Barracuda, plugged the ethernet cable into my DIR-655 and plugged up the power cable. Eventually, the power and left drive lights go steady and activity light flashes intermittently. Unit shows up in the DHCP list of my DIR-655 (1st unit never did) and has an IP assigned to it. Ran Easy Search from the CD, hit Refresh several times, unit would not show up. I d/l the latest version of Easy Search (4.8.0.0) from the WD site. DNS-321 still will not show up in Easy Search so I can configure it.
Any thoughts/solutions/ideas appreciated.
-
Highmaster2, as many on the forum have said before me, give up on the Easy Search and just use the mapping utility that came with most flavors of Windoze. It is an easier and faster way to get the drive mapped to your PC. I have yet to use Easy Search and I have the 321 mapped to all 4 of my PCs, running anything from XP to Win 7.
Or, if you know the IP of the 321, try logging into it directly from your browser and configure it that way, that always works for me too.
Hope that gives you some help.
Ryder
-
I agree, I can't see any reason for Easy Search, it's very easy to map drives with Windows, and that works every time.
-
Ryder & gunrunnerjohn,
I appreciate the suggestions, but the 321 does not show up when I try to use Vista's Map Network Drive function. Also, if I put the IP address into the address bar of IE, I get 25,000 search responses on that IP address. Let me give a little more detail on what I'm seeing: If I access the router using IE, I get the Status/Device Info page. Near the bottom is a list of LAN computers. When I power on the 321, the light for that connection lights up on the router and a few seconds later an entry shows up that is named dlink-0B433E and shows an IP of 192.168.0.197. (That is within the range of addresses I have the DHCP set for.) If I then go to Map Network Drive or click Network in the folders list of the Computer window, the DNS-321 is nowhere to be found. Also tried turning off DHCP to allow the 321 to provide it's own IP address. Still can't find anywhere the 321 shows up. Have also tried doing a reset on the 321. Still no change. Find it hard to believe that I've gotten 2 bad units in a row - feel like it must be something I'm missing. Would call D-Link tech support again, but I don't speak whatever language it is they're trying to communicate in.
Again, thanks in advance for any and all suggestions.
PS to D-Link... You should modify your spell check dictionary to include "D-Link"
-
In the address bar are you typing http://192.168.0.197?
-
Yes. Since I last updated the post, I have connected the 321 directly to my PC, restarted the PC and then reset (30 seconds) the 321. Still unable to see the 321 either through using the default IP, through the Network window or using Easy Search. Went back to connecting through the router (which I reset also). Turned router DHCP back on and assigned the 321 an IP of 192.168.0.32. Reset the 321 again. It shows up in the router's list (double checked the MAC address to be sure) but still can't see it using IP/Network/Easy Search.
-
I think you have firewall or NETBIOS issues. There is no reason that if the DNS-321 is connected and operating that you can't find it with Windows networking. I've used half a dozen of these at customer sites, and I've never had any problem running them with stock Windows networking and drive mapping capability.
Q1. Can you configure it using the web based capbility?
Q2. Have you configured the workgroup to be the same name as your computer?
Q3. Do you have NETBIOS over TCP-IP running?
Q4. Can you ping the DNS-321 by name?
Can you post this?
Hold the Windows key and press R, then type CMD to open a command prompt:
In the command prompt window that opens, type type the following commands one at a time, followed by the Enter key:
IPCONFIG /ALL
PING dlink-0B433E
Right click in the command window and choose Select All, then hit Enter to copy the contents to the clipboard.
Paste the results in a message here.
-
Q1. Can you configure it using the web based capbility? No
Q2. Have you configured the workgroup to be the same name as your computer? No
Q3. Do you have NETBIOS over TCP-IP running? Yes (according to ipconfig)
Q4. Can you ping the DNS-321 by name? No
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\johnny>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : QuadCore
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet
Physical Address. . . . . . . . . : 00-1F-C6-70-3F-E5
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::2ce0:a675:7633:be3e%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, October 30, 2009 13:16:42
Lease Expires . . . . . . . . . . : Monday, December 06, 2145 20:00:49
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Local Area Connection* 6:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{0F1CDD8F-3532-4612-AF12-5CDCF4CB7
0C6}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 7:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
C:\Users\johnny>ping dlink-0B433E
Ping request could not find host dlink-0B433E. Please check the name and try aga
in.
C:\Users\johnny>ping dns-321
Ping request could not find host dns-321. Please check the name and try again.
C:\Users\johnny>ping 192.168.0.32
Pinging 192.168.0.32 with 32 bytes of data:
Reply from 192.168.0.100: Destination host unreachable.
Reply from 192.168.0.100: Destination host unreachable.
Reply from 192.168.0.100: Destination host unreachable.
Reply from 192.168.0.100: Destination host unreachable.
Ping statistics for 192.168.0.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
C:\Users\johnny>
-
You didn't run the NBTSTAT -n command, that tells me the state of NETBIOS over TCP/IP. You also used the wrong name for your DNS-321 if what you posted previously was correct, it should be:
PING dlink-0B433E
Let's see those.
-
PING dlink-0B433E was included near the end of the previous post. I pinged both names because, when I turned DCHP back on, I reserved 192.168.0.32 for the 321 and called it DNS-321. Also pinged 192.168.0.32 wth no results. Didn't know anything about a NBTSTAT -n command, but here are the results:
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\johnny>nbtstat -n
Local Area Connection:
Node IpAddress: [192.168.0.100] Scope Id: []
NetBIOS Local Name Table
Name Type Status
---------------------------------------------
QUADCORE <00> UNIQUE Registered
ALABASTER <00> GROUP Registered
ALABASTER <1E> GROUP Registered
QUADCORE <20> UNIQUE Registered
C:\Users\johnny>
Please let me know if there's any additional info I can provide.
Thanks!
-
Can you ping the gateway 192.168.0.1?
-
I also would like to see if you can do the ping I listed:
PING dlink-0B433E
Next, if you have access to the D-Link WEB page, check and see what it lists as it's Gateway on the Setup/LAN screen.
Since I don't see this machine listed as a master browser, are there any other machines in this network? Can you post the NBTSTAT -n for those?
-
Can you ping the gateway 192.168.0.1? Yes
The plot thickens...
First, I (so I thought) took care of the master browser issue - added registry keys to this (Vista Business SP2) machine - isdomainmaster=true & maintainserverlist=yes. Also changed network type to private. Rebooted, ran NBTSTAT -n and it showed this machine as master browser. Still couldn't see the 321.
On a hunch, I went to the other PC on this network (XP), put the ip address shown in the router pages for the 321 into IE and Presto! I'm looking at the login page for the DNS-321. Went through the wizard, gave it a workgroup name of Alabaster and named the device DNS-321. Mapped the drive and the XP machine sees it/reads it/writes to it. BTW, the XP machine has the opposite registry keys - false and no.
I go to the Vista PC, reboot and run NBTSTAT - shows as Master Browser. I open Computer, click Map Network Drive and the DNS-321 shows up as an option. When I click on it, however, it tells me the network path cannot be found. I try using IE and going to the IP - nothing. Also, the Vista PC no longer shows master browser when I run NBTSTAT. So, the problem is obviously with this Vista PC, but I'm not sure what direction to go now.
Anymore thoughts welcomed...
-
The indications are that it's a firewall issue on the Vista box.
-
I normally run with the Windows firewall off, and the firewall in the f-secure security suite on. Wondering if it was a firewall issue, I disabled both before I made the other changes and only have on the firewall in the DIR-655...
-
Well, the firewall on the router has no effect on local networking, so that's not the issue.
How many computers in this network? Do all the others network properly?
-
Just a small thought, but I would seriously consider disabling ALL firewalls and going forward from there. I know the firewalls are not *supposed* to interfere with anything on the same internal workgroup, BUT, I have seen stranger things than that mess with your internal group.
Also, make sure that none of yer PCs have master browser turned on, except the one with the most recent O/S. An XP PC and a Vista PC, both with master browser enabled can play serious havoc with your internal network!
Try that and see where it takes you, then report back and I'm sure someone will have a good idea once that is done, if it doesn't cure yer problems.
Good luck dude, I hope that will have some measure of success for you!
Ryder
-
Disabled last firewall - other boxes have isdomainmaster set to no - plugged my son's Vista laptop into the network. It'll map the 321 even though the workgroup is different. Wife's XP box still sees the 321 just fine. Only box that won't see it is the one I need to see it the most (as usual).
-
One last question I can think of to ask you. Is there more than 1 PC on your network with DHCP turned on? And that includes the router, switch, 321 and any other gear that may have the ability to provide IPs. If so, turn all of them off except the PC that you use as the Master Browser, your Vista PC I believe? And post back to let this group know what happens then.
Your problem is unusual, as you well know. I'd really like to see this one get solved, I'm betting it's something very simple that all of us have overlooked!
Ryder
-
I have to believe this is some firewall component, nothing else makes much sense here.
-
I have to believe this is some firewall component, nothing else makes much sense here.
I tend to agree with you GRJ, it's possible that one firewall says it's disabled, but really isn't. Add to that the fact that Vista has always had networking issues on *some PCs* and the plot really thickens. My thoughts also wander to the fact that the 321 DID show up once on this PC, but the network path couldn't be found, and then that same PC is no longer BrowseMaster, even when it is forced to be by the addition of "isdomainmaster=true & maintainserverlist=yes". Did that setting change to "false" and "no" when you found that your PC was no longer the BrowseMaster?
Now, just maybe, it has something to do with something I saw but have no expertise in, in the ipconfig query, "Tunnel adapter Local Area Connection* 6 and *7". Would they have the ability to interfere with locating another device? Maybe someone with some knowledge about that could pipe in here and help this poor guy get his 321 working on his own PC.
I know it's not the 321, that's a given since the other PCs can see and map to it, it has to be the Vista PC (laptop?). But short of digging into the bowels of Vista Business, which no human should ever have to do, I'd say there is something seriously amiss with that PC. Especially since you can go in and configure the 321 with either of the other 2 PCs on that network. Either NetBIOS or one of the firewalls has gone A.W.O.L. and joined the dark side! Corrupt file, setting stuck in the registry, etc etc, but all too much to do through a forum.
My gut reaction is to say to reload the Vista PC from scratch and see if that clears up the problem? I know, easy to say, but probably impossible to do, as it is with 2 of my 4 PCs. I have 1 XP PC that got XP the day it was released, I have so much software on it that I'd never find all the discs again. But, it has also never given me a moment of grief, except when 1 of it's RAID 1 drives died. That PC was actually up and running for over 3 years without a reboot! HighMaster2, have I given you enough food for thought to consider dumping Vista and going "forward" to XP yet? ;D Just kidding of course, it's only my personal opinion that XP is probably the best O/S Bill G has ever put out, although 7 is showing some serious promise, even though it's built on the Vista codebase!
GRJ, Joe, D-Link, anyone care to comment on my shots in the dark? P.S. As a side note, I have been building custom PCs for people and fixing them, and networks, for over 20 years, and I've never come across something like this before. And it even moreso adds to my thoughts that Vista may replace Windows ME as Bill G's WORST IDEA EVER!!! ;) ;) ;D
Ryder
-
How about turning off IPv6, that will sometimes cause issues out of the blue in Vista.
Disable IPv6:
1. Hold the Windows key and type R, enter "ncpa.cpl" (without the quotes) and press Enter
2. Right click on each network connection and select "Properties"
3. Remove the checkmark from the box next to "Internet Protocol Version 6 (TCP/IPv6)
4. Click OK to exit the dialog
NOTE: You should do this for each network connection.
-
I'll try to reply in order...
Ryder: All boxes set to Obtain IP Address Automatically - they get IP (assigned) IP addresses from the DIR-655. At this time, ipconfig does not show master browser on this box, yet registry keys are still intact. I have no idea where the Tunnel Adapter info comes from. (I just love breaking new ground in the field of Vista research... and in response to your suggestion, I would rather have multiple root canals w/o painkillers than reload this box. However, that may be my only choice if I can't figure out something on this problem.
GRJ: I disabled the IP6 entries in both Vista boxes some time ago.
I looked at the Windows Features list to see if, like XP, there was an option to remove Networking so I could remove and re-install it. Don't see such an option. However, I did notice that IIS, Simple TCPIP Services and SMNP were all not checked/active. Would any of these make a difference?
-
HighMaster2: Breaking "new ground" is ok, but when the ground is already "broken", well....
But, I do have yet another possible thing to try for you. I don't know if Vista Business has this "feature", but my version does. So, when you go to the Control Panel, then to Network and Sharing Center, are all your "shares" turned on, except the Password Protected Sharing? That would be Network Discovery, File Sharing, Public Folder Sharing, Printer Sharing and Media Sharing? If not, turn them all on, even 1 by 1, until you possibly find the problem. And if they are already all on, well then I guess it's back to the think tank!
As far as your discoveries go, I can't speak to all of them. But since you can get on the internet, send email, surf, etc, I would suspect that none are affecting this 321 matter. Although I am wondering why Simple TCPIP Services is not enabled? But then again, your PC is set to be a MasterBrowser and it's not, so I'm really not sure what settings are working on your PC and which ones are just lying to you? ;) ;)
Ryder
-
The way to "remove" networking and reinstall it is to uninstall all the network hardware devices, than discovering them again after a reboot will rebuild networking.
Of course, for some of the network settings, you can also reset the stack and winsock.
TCP/IP stack repair options for use with Vista or Windows 7.
Start, All Programs\Accessories and right click on Command Prompt, select "Run as Administrator" to open a command prompt.
In the command prompt window that opens, type type the following commands, each followed by the Enter key:
Reset WINSOCK entries to installation defaults: netsh winsock reset catalog
Reset IPv4 TCP/IP stack to installation defaults. netsh int ipv4 reset reset.log
Reset IPv6 TCP/IP stack to installation defaults. netsh int ipv6 reset reset.log
Reboot the machine.
-
Ryder: Tried the settings in Network/Sharing - no change
GRJ: Did the stack repair commands you provided - no change.
Uninstalled the network adapter, rebooted - it installed a driver from 2007 (as opposed to the more recent I had been running) - everything works perfectly. Yep - I click on Network and everything in the house shows up, including the DNS-321. Mapped a drive to it and another dimension opened before my very eyes.
Why didn't you guys suggest that first??? (just kidding) I sincerely appreciate all your patience and assistance. Hopefully I can use your teachings to help someone else in the future.
Thanks!
-
Well, going to an old driver isn't normally my first move!
I will make a bet however. I'll bet if you reinstall the new drivers, the problem doesn't come back. ;)
-
Well, going to an old driver isn't normally my first move!
I will make a bet however. I'll bet if you reinstall the new drivers, the problem doesn't come back. ;)
But see, a fresh install would have put the old driver back and cured the problem, so technically I did suggest that! ROFL!!! Really though, glad ya got the problem solved, no matter how it happened. I'll remember to keep that "fix" in mind for the next time I run into something like this again, that's for sure! :D
And btw, don't take that bet, because I'm guessing GRJ could be about 99.999% right on that! ;) ;)
-
Agreed - a new install would probably have cured everything (except my disposition which had almost reached the point not of ROFL, but ROFS (screaming)). I also speculated that it was not the newer driver, just something that got corrupted. In fact, as soon as I get a chance I'll find the latest driver and see what happens.
-
Agreed - a new install would probably have cured everything (except my disposition which had almost reached the point not of ROFL, but ROFS (screaming)). I also speculated that it was not the newer driver, just something that got corrupted. In fact, as soon as I get a chance I'll find the latest driver and see what happens.
Awesome! And please update your post so we'll all get a chance to see what happens. :)
-
just in case another of the 16,850 or so old farts like me who have visited this forum over the years should stumble upon this thread and find no answers until they finally get to this one:
yes I tried all of the above. No I don't have an old driver -- my scenario: went to a new ISP and had to plug everything into a new modem/router. All the other peripherals worked fine -- (including the DiskStation NAS) but 2 days of headscratching could not get the D-Link DNS-321 to be recognized by Windows 7 or the Easy Search utility.
What finally did it: - I routed the NAS from the new wifi router to an equally old gigabit switch (D-Link DGS-1008G) causing the speed of the NAS to step down to 100 Mbps (instead of gigabit 1000 Mbps). I don't know why that worked - but it did - so there. YMMV. Cheers.
PS: once I could access the online configuration utility for the NAS, I noticed in the LAN settings that 1000 Mbps speed (as an option) was greyed out. So I'll keep using this thing for a while longer at a slower speed (just like me)
-
The switch being on the same network path, allows for better connections between wired devices. So if you connect the NAS and PC on the same switch, should see better connections between then. Curious that the speed dropped from 1000Mb to 100Mb on a Gb switch.
Be sure your using CAT6 LAN cables.
Set the connection speed of the LAN port on the DNS to 1000Mb instead of auto.
just in case another of the 16,850 or so old farts like me who have visited this forum over the years should stumble upon this thread and find no answers until they finally get to this one:
yes I tried all of the above. No I don't have an old driver -- my scenario: went to a new ISP and had to plug everything into a new modem/router. All the other peripherals worked fine -- (including the DiskStation NAS) but 2 days of headscratching could not get the D-Link DNS-321 to be recognized by Windows 7 or the Easy Search utility.
What finally did it: - I routed the NAS from the new wifi router to an equally old gigabit switch (D-Link DGS-1008G) causing the speed of the NAS to step down to 100 Mbps (instead of gigabit 1000 Mbps). I don't know why that worked - but it did - so there. YMMV. Cheers.
PS: once I could access the online configuration utility for the NAS, I noticed in the LAN settings that 1000 Mbps speed (as an option) was greyed out. So I'll keep using this thing for a while longer at a slower speed (just like me)