D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: littlecooldude on January 26, 2011, 07:56:51 AM
-
Hi Guys,
I've been searching for months to get this resloved. I've replaced the NAS, i've bought HDD's that are in the support list to be sure.
Still i get 1 of 3 errors. The Network drive is not found. or it says the network resource Actively refuses the connection, or You do not have permission to access this drive (or resource).
What I've done - I've tried the EasySearch Utility. I've tried to map it with Windows, using the NAS Name and the IP Address. Its set to static and i've also changed the IP Address. I've reformatted the drives serveral times, I've restored the default config, i've reflashed the unit. Sometimes it works, but then 2 mins later its not accessable. This happens on all 3 computers on my network, wired or wireless.
I can always access the DNS-323 GUI.
Any help would be greatly appreciated :)
-
Please provide some more information about your network setup. Do you have a router/switch? Is there DHCP? Are you using different subnets? Firewalls?
Regards,
Wiggs,
-
Standard Router, my PC is windows 7 Pro, The PC's are set to DHCP and the NAS has a static IP. I know enough to use the same subnet as the network or else it wont be accessable. Firewall and antivirus is disabled on my PC during testing to rule those out.
I can also Ping the NAS and access the GUI from Firefox at all times when I can't access the drive though windows. The DNS-323 also doesn't show up in as the network computers where my wifes laptop is visable.
This is the 2nd DNS323 that i have bought as Tech Support here told me my first one was defective and out of warranty.
-
I assume you are clicking on the Network tree when looking for the drive?
Also, if you have mapped the drive have you gone to the MANAGE drive in MYCOMPUTER to make sure the drive letter isnt being used somewhere else?
If easysearch is working try different drive letter?
-
I try a different drive letter everytime. You are correct, sometimes it shows in the network tree and sometimes its not. I get a network not available error when it is shown in the tree.
I can't map it through windows using the IP or the Device name and the Easysearch Utility.
-
I am not 100% sure, but it sounds like there might be a conflict somewhere on your network or router settings are off.
Try disconnecting all devices and put router beside the computer with the NAS attached?
-
Ok i'll try that, I really dont think its a network conflict. I've tried different IP address each time and I have a DNS Lease of 1 month on my router.
-
The router will have a range of IP address' it can use, i would double check that to make sure enought were available to assign to devices.
If that isnt working then there may be ports that need to be opened or other fine tune settings that I am not aware of how to do.
You model # of router should be posted to this thread
thanks
-
I'll post that tonight. Why would ports need to be forwarded for drive mapping? on a LAN? its not hitting any firewall at all. its an SMC Router provided by ISP.
-
Master browser issue? http://forums.dlink.com/index.php?topic=16493.msg94504#msg94504
Regards,
Wigggs
-
Thanks for the point in that direction, dont think its that since I can't map using the IP Address either.
Man this is annoying ???
-
Check your network settings on the NAS. The DNS-323 defaults to allowing ALL to the default directories it creates. If you added any users or groups or changed permissions on any of your newly created directories then you could run into problems like what you're experiencing.
I personally have also found that some add-ons (didn't bother narrowing it down...) may cause the NAS to disconnect from the network or slow network performance to unusable levels. So, to that end, I have removed all add-ons, reset to factory defaults and no issues since.
-
Can you explain new directories? All I did was create folders under the \Volume_1 - I didn't create any new users or usergroups. Should I?
Again anytime i try to map i just get Network name/resource/whatever cannot be found please check that you have the right blah blah blah. This happens when using IP address or the DNS-323 default Name with MAC Address.
-
If you cannot see the folder in the network drive then you wont be able to map the drives.
I had a problem on the weekend and was unable to map the drive but could see it. A reboot fixed that.
So if you cannot see the network directory then there must be more of a problem with the router handling the device properly and if you are 100% certain there are no IP conflicts there must be a router problem.
I think the IP conflict is the reason you cannot see it but you said thats not the case already.
I dont know enough about router settings to see how that might be blocking the device. Sorry
-
There is a chance that you haven't assigned a correct static IP to the nas. Some routers have their dhcp set up in such a way that only IPs within a range are acceptable for static usage. For example, my router works with IPs in the range 192.168.1.64 - 192.168.1.254. So, if I assign 192.168.1.12 to the nas then it is not going to work smoothly.
Besides that and in case the above is not your issue, I believe it is a windows 7 security problem and not a nas problem.
First of all, the EasySearch utility is not windows 7 compatible. Always run it with administrative rigths and in Windows XP compatibility mode (try it now).
Second, check if you have any weird jumbo frame settings in your ethernet card. This has caused me trouble before. If so, disable jumbo frames and test.
Third, check your windows 7 advanced network settings. Make sure network discovery is on etc.
Last but not least: I remember I had this situation once. As a solution I run a device-driver-like setup that is in the DNS-323 dvd. It installed something like a device driver... anyways, after that both the nas volumes were listed in my windows 7 and I could map them to drive letters again.
-
Windows Vista and Windows 7 want a special driver ("PnP-X support ..."). You can DL it either via
http://www.dlink.com/products/?pid=509 (http://www.dlink.com/products/?pid=509) -> Support ressources - Drivers or use the direct link to DLINK's FTP server:
ftp://ftp.dlink.com/Multimedia/dns323/Drivers/dns323_driver_PNPX_102.zip (ftp://ftp.dlink.com/Multimedia/dns323/Drivers/dns323_driver_PNPX_102.zip)
The package includes 32 and 64 bit drivers.
Hope it helps.
//HSishi
-
Windows Vista and Windows 7 want a special driver ("PnP-X support ..."). You can DL it either via
http://www.dlink.com/products/?pid=509 (http://www.dlink.com/products/?pid=509) -> Support ressources - Drivers or use the direct link to DLINK's FTP server:
ftp://ftp.dlink.com/Multimedia/dns323/Drivers/dns323_driver_PNPX_102.zip (ftp://ftp.dlink.com/Multimedia/dns323/Drivers/dns323_driver_PNPX_102.zip)
The package includes 32 and 64 bit drivers.
Hope it helps.
//HSishi
Sorry, but how I use this drivers in W7? ???
-
Sorry I haven't replied sooner, I just kind of gave up for a while, I'm going to try this driver out. Also I noticed that my wifes laptop is conflicting with my own, in event viewer i'm getting a bunch of MASTER BROWSER Conflicts with it. Could this be the reason for the DNS-323 not mapping?
Edit - I too need assistance, all I see is DLL and INF files, were in Device manager would I install this through the INF?
-
Do you actually need the driver? I have installed a DNS323 on two W7 machines so far without the drivers...
-
No - you don't need the drivers to access data from windows 7 - you do need them to stop Windows from telling you it's an unknown device (if you get that message, you may not)
-
I'm not getting any unknown device. This problem is just ridiculous.... I can ping the IP, when i do the cmd to see all the master browsers on the network, my PC is the only one, but the MAC Address of the DNS-323 shows all 00:00:00:00 etc.
However I was able to map the drive after i did a factory reset on the NAS. then again, I can't connect. When I try to connect via IP or DomainName it says its not available.
Wish I never bought this thing, DLink Tech Support seems to not know how to troubleshoot the issue, all I was told was to reset, and reseat drives.
Edit: I can FTP into the NAS just fine using the IP address....
-
Post the following information:
LAN IP address of the router eg: 192.168.1.1
DHCP range that is set in the router eg: 192.168.1.2 to 192.168.1.100
How many PC's on the network?
Under the LAN tab in the DNS-323 web interface:
What is the link speed set to, Auto, 100 or 1000?
Is the IP address set to static?
What is the IP address?
What is the subnet mask?
What is the gateway setting?
What are the DNS server settings?
Are jumbo frames enabled or disabled?
What firmware version are you using in the DNS-323?
What antivirus and firewall software is being used?
Let's say the IP address of the DNS-323 is 192.168.1.101. What happens if you click start, run, then in the run box type the following:
\\192.168.1.101
click ok.
or
\\192.168.1.101\
click ok.
If this works (which it should) then the DNS-323 can be mapped as a network drive using the IP address eg: \\192.168.1.101 or \\192.168.1.101\ or \\192.168.1.101\mydirectory or \\192.168.1.101\mydirectory\
I am on a Unix box so I can't try it, however, I think you get the idea. ;D
-
I'll do it again but I've already done everything you said.....
LAN IP address of the router eg: 192.168.0.1
DHCP: 192.168.0.12-192.168.0.100 (My ISP changed the DHCP Range so no conflictc)
PCs: 2
Devices: PS3,DNS-323
DNS-323:
IP 192.168.0.10
Subnet: 255.255.255.0
Gateway: 192.168.0.1
No DNS server settings
Jumbo Frames Disabled
FW: 1.09
AntiVirus: ESET NOD32 (I've Disabled this to see if I can Connect)
Already did the run before, its how i connect to the shares at work: Windows Cannot Access \\192.168.0.10 Check the spelling of the name. Otherwise there might be a problem with your netowrk. To try to indentify and resolve network problems, Click Diagnose. Diagnose says that the machine is refusing connection.
I've also tried to trouble shoot with ISP since they provided the router, their diagnostics on it say its fine (I really dont believe them though)
-
Try this
Reset the DNS-323 to factory default settings.
DNS-323:
Set IP to "Static IP"
IP: 192.168.0.200 (as long as 192.168.0.200 is not already used on the network)
Subnet: 255.255.255.0
Gateway: 192.168.0.1
DNS1: 198.153.192.1
DNS2: 198.153.194.1
Jumbo frames: disabled
Save all the settings. Try logging in using \\192.168.0.200
The DNS servers are from NortonDNS http://www.nortondns.com/ (http://www.nortondns.com/) don't worry they are ok to use.
-
No - you don't need the drivers to access data from windows 7 - you do need them to stop Windows from telling you it's an unknown device (if you get that message, you may not)
Correct.
-
Try this
Reset the DNS-323 to factory default settings.
DNS-323:
Set IP to "Static IP"
IP: 192.168.0.200 (as long as 192.168.0.200 is not already used on the network)
Subnet: 255.255.255.0
Gateway: 192.168.0.1
DNS1: 198.153.192.1
DNS2: 198.153.194.1
Jumbo frames: disabled
Save all the settings. Try logging in using \\192.168.0.200
The DNS servers are from NortonDNS http://www.nortondns.com/ (http://www.nortondns.com/) don't worry they are ok to use.
his dhcp server is in range 0.12 - 0.100 ... if he sets 0.200 it is not going to work.
--
set a correct static ip within the range and set the dns address to 192.168.0.1. try.
TBH, i am a bit confused about the actual problem... the ip is not working? the name is not working? the mapping is not working (sometimes or at all)?
-
so you get my confusion in this... if anything the IP address should work, and that totally messed up the tech from my ISP. The NAS lets me map with the D-Link Easy util. after say a fw upgrade/factory reset. But only for about 10 mins, then i get a cannot connect to share. by device name or IP Address. I can Ping, I can FTP into this. I cannot map the drive from any machine on my network.
-
littlecooldude,
Sounds like you've had a ton of fun with this.
Have you tried one of the following? This worked for me in my Windows 7 environment. Hope this helps!
Method 1
1. Start/run/regedit
2. Navigate to HKLM\SYSTEM\CurrentControlSet\Control\Lsa
3. Change the LmCompatibilityLevel to 1.
4. Exit regedit
5. Reboot
6. Attempt to map to the NAS using \\IPADDRESS\Volume_1 (or the share name you defined)
Method 2
1. Click Start, Run, then type "secpol.msc" (without the quotes). This will bring up the Security Policy system window.
2. Select Local Policies > Security Options.
3. On the right, scroll down and double-click "Network Security: LAN Manager Authentication Level"
4. Change the setting to "Send LM & NTLM -- Use NTLMv2 session security if negotiated"
5. Reboot
6. Attempt to map to the NAS using \\IPADDRESS\Volume_1 (or the share name you defined)
FYI...there have been numerous issues reported with mapping network resources in Windows 7. Here's just one thread:
http://social.technet.microsoft.com/Forums/en-US/w7it****etworking/thread/53ba4e62-1679-4f03-badf-006c9bfaf7a0
If the above doesn't help, some other things to try within security policy settings are:
1. Open Network security: Minimum session security for NTLM SSP based (including secure RPC) clients and uncheck the require 128 bit.
2. Open Network security: Minimum session security for NTLM SSP based (including secure RPC) servers and uncheck the require 128 bit.
Another good link:
http://www.spacefold.com/colin/blog/post/2010/06/12/Windows-7-cant-see-SMB-based-network-attached-storage-without-a-hack.aspx
Hope this helps!
-
so you get my confusion in this... if anything the IP address should work, and that totally messed up the tech from my ISP. The NAS lets me map with the D-Link Easy util. after say a fw upgrade/factory reset. But only for about 10 mins, then i get a cannot connect to share. by device name or IP Address. I can Ping, I can FTP into this. I cannot map the drive from any machine on my network.
Since starting from scratch all the time is no good and since ftp and ping works let us safely assume this is not a network problem, that is your nas device is successfully assigned to an ip address and is accessible throught the lan.
So, something is wrong with windows. Please, verify the following settings:
NAS -> Setup -> Device
Workgroup = THE SAME as the PC's workgroup
NAS -> Advanced -> Network Access
Type = SMB
SMB LIST
Share=Volume_1
Path=Volume_1
User/Group=ALL
Oplocks=No
Map archive=No
R/W=Yes
NAS -> Advanced -> DHCP Server
DHCP Server=Disable
NAS -> Advanced -> LLTD
LLTD=Disable
NAS -> Advanced -> Users/Groups
FWIW, add a user with the same name as the PC user account you log in with.
Windows 7
Computer -> (right click) -> Properties -> Computer workgroup -> Change settings
Make sure the computer and the NAS are in the same workgroup.
Windows 7 SAMBA Settings (BTW, what windows version are u running?)
Network and Sharing Center -> Advanced sharing settings
Current Profile=Home or Work
Network discovery=Turn on
File and printer sharing=Turn on
Public folder sharing=Turn off
Media streaming=off (turn it off even if you need it on, just to be sure about the set up. You can always activate it later).
File sharing connections=128bit
Password protected sharing=Turn on
HomeGroup connections=All Windows to manage homegroup connections (I assume you do not have a homegroup active. If you do please disable it for the time being).
Test #1.
Open Windows Explorer -> Network.
The NAS device must be listed there.
Test #2.
(Forget about the EasySearch tool.)
Open Windows Explorer -> Computer.
On the menu bar click -> Map network drive.
Try to map the Volume_1 to a drive letter.
If the above do not work then maybe the NAS device is defective.
-
his dhcp server is in range 0.12 - 0.100 ... if he sets 0.200 it is not going to work.
What you have written above is not correct as I was referring to assigning the static IP address using the DNS-323 GUI. Therefore, static IP addresses *must* be set outside the DHCP range to prevent the DHCP server assigning the same IP address to another device. This will create an IP conflict on the network.
If the static IP address is assigned using the GUI of the DNS-323 it must be outside the DHCP server range.
If the DHCP server is assigning the static IP address using the MAC address of the DNS-323, the static IP address must be within the DHCP server range.
-
The \Volume_1 as mentioned by others may help.
\\192.168.0.200\Volume_1
-
Well I didn't say thanks yet, so THANKS SO MUCH guys! i appreciate the help, now I have some things to try out that weren't offered before.
I'll try out what you say Hambone. I'm not ruling out a network issue as all PC's on the network experience the same issue.
My PC is Windows 7 Professional. Wifes laptop is Windows 7 Home.
My ISP changed the DNS-323 outside the DHCP range to avoid IP Conflicts.
@McPillager - I already confirmed everything you recomended - I thought it was a permission issue as well, that was only a temp fix as the issue came back.
I'll post back tonight see if anything works. I have a seperate wired router i'm going to connect to just the NAS and my PC and see if this resolves it if the below didn't work.
-
OK! bad news: Tried Hambones suggestions
Method 1: Didn't have that in the registry so I couldn't apply it, i'm reluctant to add it in manually as i'm not sure what it will do.
Method 2: I did try that and it didn't fix it :(
The other 2 options were already unchecked..... Next thing to do is remove the ISP router/Modem from the mix and see if that fixes it.
-
A wii question: is your ISP in remote control of your modem/router? Do you have administrator's access to it?
-
Good Question, yes they have remote control, I have a custadmin account... I dont think i even have access to port forwarding on it.
-
This (extraordinary) fact may as well be the source of all your problems my friend ;)
-
I thought so, I was able to map my drives while connected to a cross over cable. I'm going to pick up a wireless router and have my ISP set it up in Bridge mode.
Also I thought I had already removed funplug but I didn't and removed that as well. Has that ever been known to cause issues like this? I use it so that I can install and run twonky.
-
I had the same problem. I had setup my DNS-323 as a static address too. I upgraded my media server on the NAs and also did a windows update with a boat load of security fixes. Between these two, my drive was became invisible to Win7. I could ping it from a command prompt though and could see in Easy search - but could not Map the Drive in Windows 7 or via Easy Search.
I fixed it by going into the DNS-323 config console in 'Advanced' and enabled LLTD - Link Layer Topology Discovery. This allow my computer to see the drive - but I still could not connect.
Next I upgraded my firmware from 1.06 to 1.09 and whola I could see, map and access my files.
I did begin this process by resetting the drive (since I forgot the log on password) by pushing a paper clip in the reset button on the back. This might not be a bad idea to do first but may not be necessary. If you do, note that you do not have to reformat the drives - just click the 'Skip' button to bypass this.
-
Thought I'd give my two cents:
Just for the heck of it, reset all windows 7 services to default settings on your PC. I remember when I first upgraded to 7, I needed some additional services set to "automatic". The introduction of windows 7's homegroup changed some of the network-related services.
-
The Easysearch utility works fine with Windows 7 for me.
Anyway I'm pretty sure I can solve this for the OP, will write a quick guide. By Nod32 I'm going to presume you mean Eset Smart Security?
I'll provide notes and then if you need them screenshots, but see how it goes first.
1) Open Eset Smart security
2) Press F5 to open settings
3) Under the "Personal Firewall" on the left hand side select "Rules and Zones"
3) Click "Setup" under "Trusted Zones" which should be on the right hand side.
4) You should have a line or two of IPs, select the first and click next and change the option to "Allow Sharing" then click ok.
5) Repeat for each line listed.
6) Reboot PC.
That should sort it, it worked for me.
-
1)Access browser config
2)Tools, System, Defaults, click on "Restore to factory setting", then click on "Restart" above.
3)Go to your Easy search utility and "connect" the drives.