D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: Rodent on December 08, 2007, 03:05:56 AM
-
Hi,
I am running Windows XP Pro, DNS-323 Firmware is 1.03 both connected via a 1 GB switch.
Network Access Problem
After I restart my DNS-323 I loose Network Access to the device, I have three SHARES setup two require password access and one does not. After the restart when I click on the device via network places or the mapped drives I get ......
\\Dns323 is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have
access permissions.
The network path was not found.
or
An error occurred while reconnecting S: to \\Dns323\Storage
Microsoft Windows Network : The local device name is already in use.
This connection has not been restored.
The only way I can get access back is to go into the web configuration > click on Advanced > Network Access > edit one of the shares and apply, no changes need to be made. I than have Network access back.
uPnP keeps discovering problem
On my Windows XP computer I have turned on uPnP descovery so when I connect a device that is uPnP compliant it pops up in the system tray saying newly discovered device found, I have had a ADSL Router for years that was discoverd once and I have not seen it rediscovered since but the DNS-323 is being rediscoverd about every hour or two and it doesn't seem to matter if the uPnP AV Server is enabled or disabled.
This is not a big problem but it is annoying.
So if any one out there has any ideals I would love to hear them.
Thanks for reading
Rodney
-
Network Access Problem
I reckon we need to config the DNS-323 as a master domain of network. This way, we just authenticate in samba server when we click in protected folders, but i don't know how we will do it.
-
What I have found with uPnP keeps discovering problem is that under My Network Places when it discovers the device again I get two listings for the device for about 5 seconds, than one of the list items disappear leaving one item.
No sure if this helps anyone but it is getting really annoying.
-
Are you using the D-link Easy Search Utility software or Windows map utility to map your drives?
-
Are you using the D-link Easy Search Utility software or Windows map utility to map your drives?
I have tried both, after a restart the Easy Search Utility can see the DNS-323 and the shares the same as with Windows but when I click on Connect for a share that does not require a user name and password I am prompted for one so I would say it cannot access the shares. When I edit and apply one of the shares in the web interface the Easy Search Utility works fine.
Rodney
-
I had the same problem and think I resolved it by assigning a static internal IP (192.168.x.x) address to the DNS-323, instead of letting it renew from my DHCP (on the router) on a periodic basis.
-W
What I have found with uPnP keeps discovering problem is that under My Network Places when it discovers the device again I get two listings for the device for about 5 seconds, than one of the list items disappear leaving one item.
No sure if this helps anyone but it is getting really annoying.
-
Robert wrote:
I am running Windows XP Pro, DNS-323 Firmware is 1.03 both connected via a 1 GB switch.
Network Access Problem
After I restart my DNS-323 I loose Network Access to the device, I have three SHARES setup two require password access and one does not. After the restart when I click on the device via network places or the mapped drives I get ......
\\Dns323 is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have
access permissions.
The network path was not found.
or
An error occurred while reconnecting S: to \\Dns323\Storage
Microsoft Windows Network : The local device name is already in use.
This connection has not been restored.
The only way I can get access back is to go into the web configuration > click on Advanced > Network Access > edit one of the shares and apply, no changes need to be made. I than have Network access back.
Hi, I have exactly the same problems and have tried all solutions offered but nothings works - but strangely once in a blue moon it will work after a reboot - I have had the 323 since xmas and am so fed up with this problem I am about to throw it in the rubbish bin
Richard
-
Robert wrote:
I am running Windows XP Pro, DNS-323 Firmware is 1.03 both connected via a 1 GB switch.
Network Access Problem
After I restart my DNS-323 I loose Network Access to the device, I have three SHARES setup two require password access and one does not. After the restart when I click on the device via network places or the mapped drives I get ......
\\Dns323 is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have
access permissions.
The network path was not found.
or
An error occurred while reconnecting S: to \\Dns323\Storage
Microsoft Windows Network : The local device name is already in use.
This connection has not been restored.
The only way I can get access back is to go into the web configuration > click on Advanced > Network Access > edit one of the shares and apply, no changes need to be made. I than have Network access back.
Hi, I have exactly the same problems and have tried all solutions offered but nothings works - but strangely once in a blue moon it will work after a reboot - I have had the 323 since Xmas and am so fed up with this problem I am about to throw it in the rubbish bin
Richard
I know what you mean, I have had my 323 since Xmas also but I don't turn it off very often so its not suck a problem for me but when I do it is a pain in the ass.
I'm hanging out for firmware 1.04 and if this firmware does not fix the problem than I'm be looking for another solution.
Thanks for you input
Rodney
-
Thanks for that, this seems to have fixed the constant discovery of the device (something D-Link will have to look into?).
Rodney
I had the same problem and think I resolved it by assigning a static internal IP (192.168.x.x) address to the DNS-323, instead of letting it renew from my DHCP (on the router) on a periodic basis.
-W
-
I just have mine in the same workgroup as all my pc's and I named it DNS-323. I do not use any of the mapping software. I simply access it thru it's name (Enter in Explorer Address \\Dns-323). Why not just assign a static IP to it? I like statics for my printers and drive. Much easier when using FTP and you need a router to forward port 21 requests to the DNS-323. I set my router to assign DHCP's starting at 100 and up, printers at 90-99, DNS-323 at 192.168.XXX.21 (easy to remember port 21 and IP 21).
-
I would recommend assigning a static IP address to the DNS-323.
-
I have updated the firmware to v1.04 and am still having this same problem, after starting the DNS-323 I have to edit one of the network shares to what seem to me is enabling it. Can this not be done in the startup of the device?
I was hoping this problem would have been fixed with this firmware but it appears not, so when will the next firmware be released ???
Thanks
Rodney
Hi,
I am running Windows XP Pro, DNS-323 Firmware is 1.03 both connected via a 1 GB switch.
Network Access Problem
After I restart my DNS-323 I loose Network Access to the device, I have three SHARES setup two require password access and one does not. After the restart when I click on the device via network places or the mapped drives I get ......
\\Dns323 is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have
access permissions.
The network path was not found.
or
An error occurred while reconnecting S: to \\Dns323\Storage
Microsoft Windows Network : The local device name is already in use.
This connection has not been restored.
The only way I can get access back is to go into the web configuration > click on Advanced > Network Access > edit one of the shares and apply, no changes need to be made. I than have Network access back.
-
Hi, Rodent
I finally got this dam thing to show up after a reboot - I found that for some reason even when I set it to static and cloned the Mac address
it would not work - then I noticed the following -
IP Address: 192.168.0.xxx
Subnet Mask: 255.255.255.0
Gateway IP Address: 192.168.0.x
Mac Address: 00:1C:F0:0A:98:9B
DNS1: 220.101.191.xx
DNS2: 220.101.191.xx - these are the same as my wan DNS settings so when I changed them to the 192.168.0.xx range it all works fine even after a reboot it all shows up under my networks - so at last all is well - but how did my wan settings get there in the first place
Rich
-
I'll do some testing with DNS settings and get back.
;D Thanks for the info Rich...
Rodney
Hi, Rodent
I finally got this dam thing to show up after a reboot - I found that for some reason even when I set it to static and cloned the Mac address
it would not work - then I noticed the following -
IP Address: 192.168.0.xxx
Subnet Mask: 255.255.255.0
Gateway IP Address: 192.168.0.x
Mac Address: 00:1C:F0:0A:98:9B
DNS1: 220.101.191.xx
DNS2: 220.101.191.xx - these are the same as my wan DNS settings so when I changed them to the 192.168.0.xx range it all works fine even after a reboot it all shows up under my networks - so at last all is well - but how did my wan settings get there in the first place
Rich
-
My tests so far:
IP Address: 10.x.x.250
Subnet Mask: 255.255.255.0
Gateway IP Address: 10.x.x.254
DNS1: wan dns address 1
DNS2: wan dns address 2
If I setup the DNS-323 with my wan DNS IP Addresses the rebooting issue goes away but I have other network problem with DNS like web pages and even the DNS-323 web pages take ages to load and sometimes do not load.
IP Address: 10.x.x.250
Subnet Mask: 255.255.255.0
Gateway IP Address: 10.x.x.254
DNS1: 10.x.x.254
DNS2: 10.x.x.254
When setup with my gateway address web pages are fine but I have the rebooting of the DNS-323 problem again.
So I do not know what else to try ???
Thanks
Rodney
PS. I was going to upload a JPG diagram of my network but the attachment upload area is not writable so how does one add a picture to a post ???
-
imageshack.com (i think) you can post images there to share for everyone to see
-
In the thread 'right hard drive indicator is purple, do i worry?' aglio posted an image; how did he do it ???
imageshack.com (i think) you can post images there to share for everyone to see
-
aglio is hosting the image of a different server and his post contains a link to that server - you should be able to achieve the same thing with image shack
-
Rodent wrote
IP Address: 10.x.x.250
Subnet Mask: 255.255.255.0
Gateway IP Address: 10.x.x.254
DNS1: 10.x.x.254
DNS2: 10.x.x.254
When setup with my gateway address web pages are fine but I have the rebooting of the DNS-323 problem again.
Try changing your DNS1 & 2 to different settings as they appear to be the same as your Gateway Address eg;
DNS1: 10.x.x.256
DNS2: 10.x.x.257 or something similar
Rich
-
Rodent wrote
IP Address: 10.x.x.250
Subnet Mask: 255.255.255.0
Gateway IP Address: 10.x.x.254
DNS1: 10.x.x.254
DNS2: 10.x.x.254
When setup with my gateway address web pages are fine but I have the rebooting of the DNS-323 problem again.
Try changing your DNS1 & 2 to different settings as they appear to be the same as your Gateway Address eg;
DNS1: 10.x.x.256
DNS2: 10.x.x.257 or something similar
Rich
Out of curiosity - how did you arrive at 10.x.x.256 or 10.x.x.257 - are you sufficiently familiar with the network that you know the addresses of the DNS servers?
There is nothing wrong with the DNS settings being the same as the default gateway - in fact - it is very common with consumer routers to have the router act as a DNS forwarder, in which case the DNS server setting WILL be the same as the default gateway.
-
Correct, My router is the only address I can use beside the wan DNS addresses, I do not know why when I configure the DNS-323 with the wan DNS addresses I have so much trouble with network access to web pages, DNS-323 web pages etc.
Here is a picture of my network:
(http://rcsoftware.servehttp.com/downloads/HomeNetwork.jpg)
Out of curiosity - how did you arrive at 10.x.x.256 or 10.x.x.257 - are you sufficiently familiar with the network that you know the addresses of the DNS servers?
There is nothing wrong with the DNS settings being the same as the default gateway - in fact - it is very common with consumer routers to have the router act as a DNS forwarder, in which case the DNS server setting WILL be the same as the default gateway.
-
Fordem Wrote
Out of curiosity - how did you arrive at 10.x.x.256 or 10.x.x.257 - are you sufficiently familiar with the network that you know the addresses of the DNS servers?
There is nothing wrong with the DNS settings being the same as the default gateway - in fact - it is very common with consumer routers to have the router act as a DNS forwarder, in which case the DNS server setting WILL be the same as the default gateway.
I am NOT sufficently familiar with anything networking - but I have been having the same problem with my DNS 323 since xmas and since I (probably) stumbled accross a way to fix my problems, I thought I would share it with Rodent - Simple as that
This was my setup
IP Address: 192.168.0.xxx
Subnet Mask: 255.255.255.0
Gateway IP Address: 192.168.0.x
Mac Address: 00:1C:F0:0A:98:9B
DNS1: 220.101.191.xx
DNS2: 220.101.191.xx - these are the same as my wan DNS settings so when I changed them to the 192.168.0.xx range it all works fine even after a reboot it all shows up under my networks - so at last all is well
And when I changed DNS1 & 2 to the 192.168.0.xx range (where xx are say 30 & 31) it worked
Rich
-
Roli
The DNS settings on the DNS-323 are there so that the device can use DNS - domain name services - to locate any other device that is required, for example an ntp (network time protocol) server - if there is no DNS server at the ip address you specify, you might as well leave it blank.
Just in case you hadn't noticed - the details that you provide for your network don't match the scenario that Rodent listed - specifically your DNS settings point to a public DNS server, probably that of your ISP - whilst his point to his router - which as I have said already is perfectly normal
-
I have exactly the same problem as Rodent when restarting the DNS-323 and can only get network access to it by doing as Rodent suggested in his original post ("go into the web configuration > click on Advanced > Network Access > edit one of the shares and apply, no changes need to be made").
My router is the DIR-655 and the network settings of the DNS-323 are:
Static IP
IP Address: 192.168.0.199
Subnet Mask: 255.255.255.0
Gateway IP Address: 192.168.0.1
DNS1: 192.168.0.1
DNS2:
It isn't a huge problem for me now I know the fix as I don't turn the DNS-323 off often but there does appear to be a bug that needs fixing. My DNS-323 is on firmware 1.03 still.
-
Fordem,
IP Address: 192.168.0.160 = Router
Subnet Mask: 255.255.255.0
Gateway IP Address: 192.168.0.1 = Router
DNS1: 192.168.0.16 = Router
DNS2: 192.168.0.17 = Router
Just in case you hadn't noticed - the details that you provide for your network don't match the scenario that Rodent listed - specifically your DNS settings point to a public DNS server, probably that of your ISP - whilst his point to his router - which as I have said already is perfectly normal
Those above are the static settings that worked = Router
The 220.101.191.xx ones are my ISP ones and with them there it would not work on reboot - Thats why I changed them!!
Out of curiosity I dropped the DNS alltogether as you suggested done a reboot and it worked perfectly as you suggested.
The only other thing I changed the day I got it to work was to go to Device settings and put in a Workgroup name = workgroup the same as my computers.
To test this I went back and changed the Workgroup name to BLOGGS - rebooted and went into my network places - and the NAS did NOT show up at all - changed it back to WORKGROUP and it shows up under my network places.
The interesting thing was that when I put a shortcut to volume_1 on my desktop it did not matter what workgroup name I used, the shortcut still worked - but just did not show up under my network places if I did not use the workgroup name that matched my computers.
ps: I am not being argumentative about this I am just trying to understand what I done to get it working
Rich
-
Have the same problem. I have assigned static IP to DNS-323, this didn't resolve problem. After rebooting DNS I have to go to admin page and click 'apply' in the 'network access' page.
Is D-link going to fix this ?
And please remove 'UPnP AV SERVER' in the next firmware update - this likeness of DLNA is annoying.
-
This is an old post but since I started it I mite as well post my fix.
I have upgraded my firmware from 1.04 to 1.08 and this problem is now resolved.
R.
-
This is an old post but since I started it I mite as well post my fix.
I have upgraded my firmware from 1.04 to 1.08 and this problem is now resolved.
R.
I had your problem even with firmware 1.08. This fixed mine
http://forums.dlink.com/index.php?topic=13256.msg78153#msg78153
-
I had your problem even with firmware 1.08. This fixed mine
http://forums.dlink.com/index.php?topic=13256.msg78153#msg78153
Thanks, I've been following your post but your issue and mine are different, I have never had a problem seeing my DNS323 on my network and a small local home network should not need the use of hosts files, but if it helps you than thats fantastic.
I had this problem of not being able to access shares until I re-saved one share in the configuration with firmware 1.03 and 1.04 but since 1.08 the problem has gone away.
I just hope the problem does not come back with future firmwares...
R.