D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: liammaps2010 on August 11, 2010, 01:59:04 PM
-
Every week or so, I am unable to access the web admin page of my NAS without power cycling the NAS.
WTF?????? Running 1.09.
-
I can only suggest removing any add-on applications and seeing if that changes the symptoms.
-
It's probably a DHCP issue. Maybe you already do this, but if you don't it's worth a try and can solve a lot of these types of problems. If your router supports it,. instead of having randomly assigned IPs for computers and peripherals on your network, reserve an IP for them. I started doing that when I got my dir-655 a coupe of years ago - it was the first router I had that could do it.
Another thing you could try is accessing with a different browser (as a temporary measure) and this will show if it is your computer rather than the router. Also, if you reboot the router and not the NAS and it fixes things you can be more sure it's a routing problem and not the NAS. Also, if you open a cmd window and type "ipconfig /flushdns" and try again and it works, that also points to it not being the NAS. All really just ways of narrowing down the problem.
My feeling is it is much more likely to be a routing issue than a bad NAS. Not sure if that helps but maybe a few ideas for you ;)
-
If it were a DHCP issue, he wouldn't have access to the NAS at all.
-
Sigh. Stop following me round threads for arguments. DHCP issue does not = DHCP failure. Changing IP addresses that get renegotiated (especially in windows machines) have a habit of going wrong. It is a common occurrence, especially, but not limited to, wireless adaptors - it was particularly common in some intel chipsets.
One cure is to move to set IPs.
Let the OP decide and stop following me around because you didn't like my advice on another thread - troll somewhere else pls.
-
troll somewhere else pls.
2255 gunrunnerjohn posts vs. 109 tentimes.
I think gunrunnerjohn has done his fair share of helping others, not exactly a fair comment is it?
I don't see how "If it were a DHCP issue, he wouldn't have access to the NAS at all" is trolling.
He's mearly pointing out that if the Windows machine was unable to resolve the name to or access the IP of the NAS, nothing would work - not just the web interface.
-
Sigh. Stop following me round threads for arguments. DHCP issue does not = DHCP failure. Changing IP addresses that get renegotiated (especially in windows machines) have a habit of going wrong. It is a common occurrence, especially, but not limited to, wireless adaptors - it was particularly common in some intel chipsets.
One cure is to move to set IPs.
Let the OP decide and stop following me around because you didn't like my advice on another thread - troll somewhere else pls.
I'm not following you around. You made a statement that doesn't make sense, and I called you on it. Sorry you find that offensive. ::) If he suddenly can't access the page, yet has access to the NAS, this is not a DHCP issue, I can't say it any plainer than that.
As far as your advice in my thread, you didn't have any useful advice, unless you kept it to yourself.
-
Quantity does not equal quality. Like I said, it could be a DHCP issue. By that I mean the reissue and reauthorization of IPs. It's a common problem. In the negotiation phase some clients get locked up. This doesn't just happen the first time the computer/device is turned on - it can happen on lease renew for example, or when, for some other reason the DHCP server re-issues (a small power failure too) That doesn't mean that every machine fails on the network or that the DHCP server has failed to issue the addresses correctly. It's usually a failure of the negotiation phase for lease of IP or issue of new IP. This can often result in a the DHCP server thinking it has given a successful address, the host showing as connected, yet connectivity lost. If you two don't understand that then I don't understand why you can argue about it. If the OP tries a few of my suggestions he *will* narrow the problem down somewhat.
If the poster wants any more help on that just pm me - I'm not reading this thread any further. Like I said Gunrunner - PLEASE stop following me round threads just to contradict me. It doesn't help anyone's experience of the forum.
-
Like I said Gunrunner - PLEASE stop following me round threads just to contradict me. It doesn't help anyone's experience of the forum.
Are you for real? Other than my own thread, which you were no help in anyway, this is the FIRST thread I've ever had any interaction with you in. Your ego must be very easily bruised if you're that upset about what has been said in one thread!
Suggestion: Don't take yourself so seriously.
-
What doesn't help user experience in a forum is having closed 1 on 1 discussions with one member who thinks he is right. A forum is a community for everyone to share ideas, help and to give suggestions - leveraging the experience and expertise of many people.
-
Every week or so, I am unable to access the web admin page of my NAS without power cycling the NAS.
WTF?????? Running 1.09.
Question: Is the unit completely dead, or do you still have access to the files?
I assumed since you didn't say it was dead that you still had file access. If that is indeed the case, one other thing you can try is to reset the unit to factory defaults and reconfigure manually, don't read in a saved configuration. That cures many ills with this box.
-
What doesn't help user experience in a forum is having closed 1 on 1 discussions with one member who thinks he is right. A forum is a community for everyone to share ideas, help and to give suggestions - leveraging the experience and expertise of many people.
Especially when, from all appearances, it's not that likely that he is in this instance. :)
-
I had the same issue where I could not log in to the admin page, it would cycle back to the login even though correct credentials were entered. Removing and replacing the BT client solved it for me. I now run the box for months at a time without restarting and I can access the admin options.
-
If your router supports it,. instead of having randomly assigned IPs for computers and peripherals on your network, reserve an IP for them.
Or just assign static IP addresses to your devices including the NAS.
-
It's probably a DHCP issue. Maybe you already do this, but if you don't it's worth a try and can solve a lot of these types of problems. If your router supports it,. instead of having randomly assigned IPs for computers and peripherals on your network, reserve an IP for them. I started doing that when I got my dir-655 a coupe of years ago - it was the first router I had that could do it.
Another thing you could try is accessing with a different browser (as a temporary measure) and this will show if it is your computer rather than the router. Also, if you reboot the router and not the NAS and it fixes things you can be more sure it's a routing problem and not the NAS. Also, if you open a cmd window and type "ipconfig /flushdns" and try again and it works, that also points to it not being the NAS. All really just ways of narrowing down the problem.
My feeling is it is much more likely to be a routing issue than a bad NAS. Not sure if that helps but maybe a few ideas for you ;)
Thanks for your ideas, but my NAS is on a fixed IP on my network.
-
Question: Is the unit completely dead, or do you still have access to the files?
I assumed since you didn't say it was dead that you still had file access. If that is indeed the case, one other thing you can try is to reset the unit to factory defaults and reconfigure manually, don't read in a saved configuration. That cures many ills with this box.
I have access to the NAS on my network and remotely. I just can't access the web login for admin of the NAS.
-
I had the same issue where I could not log in to the admin page, it would cycle back to the login even though correct credentials were entered. Removing and replacing the BT client solved it for me. I now run the box for months at a time without restarting and I can access the admin options.
I don't use BT.
-
Or just assign static IP addresses to your devices including the NAS.
I am on a static IP.
-
what do you get when you enter the IP address of the DNS-323 in your web browser ?
-
Did you try restoring to factory defaults and reconfiguring? How about removing any add-ons as a test? I'll bet one of those measures will restore normal operation, because there are tons of people running the plain DNS-323 with that firmware.
-
What happens if you ping it? If it pings ok then why not SSH to it and have a look about if you know some linux? Install funplug and get SSH setup then type 'top' once you are logged in as root - that will give a readout of what's running, cut and paste it here and I'll have a look.
For more info on that I have the links in my guide for installing 4k sector drives here: http://forums.dlink.com/index.php?topic=14484.0
Oh, and have you tried (when it fails) booting up a different browser and trying with that?
-
Did you try restoring to factory defaults and reconfiguring? How about removing any add-ons as a test? I'll bet one of those measures will restore normal operation, because there are tons of people running the plain DNS-323 with that firmware.
John, what are add-ons?
-
Add-ons are things like BitTorrent, NFS, SharePort, and no-ip.DDNS, Firefly, etc. They're applications you can install to expand the capability. If you haven't installed any of these, I'd try simply resetting to factory defaults and see if that resolves the issue.