D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: blainem on February 26, 2008, 01:00:47 PM
-
When attempting to configure access controls from the advanced menu I enable the access control checkbox. I then follow the configuration wizard completing each step as directed by the wizard. When I complete the wizard and try to save the rule I get the following error message regardless of how I complete the wizard. "Name can not be empty string". Yes, cannot is misspelled in the message. I have tried every combination of choices in the wizard and many combinations of naming the rule to no avail. I contacted support and they offered an RMA but it’s probably out of warranty and I’m not convinced a new unit would fix the problem.
This did work properly on a previous firmware version, probably 1.04 or 1.05. I have not tried back loading to the previous versions to see where it did or did not work. I don’t know how well the router goes back and don’t really care to reload all the settings again by hand if the automatic recovery doesn’t work.
I want to use this feature to control what hours certain machines on the network have access to the internet.
Has anyone experienced this before, or have any advice?
Screen print attached.
Thanks,
Blaine
Dlink DIR-655
Hardware Version A1
Firmware 1.11
Connected:
2 Windows XP machines pro on custom hardware wired Ethernet
Denon receiver with media player wired Ethernet
Dell laptop via 802.11g
3MB Charter broadband
Ambit modem
-
It looks like I'm not alone in having this issue. This is my thread on another forum.
http://www.dslreports.com/forum/r20007323-Help-Me-DIR655-Access-Control-Err-Name-can-not-be-an-empty-s
Cheers
-
Hello,
I have recently upgraded my firmware from 1.03 to 1.11, and started receiving same problem.
I have posted on the other forum as well, but posting here as well, as this is the official one.
I have since tried rolling back to 1.03, and the problem goes away. Then I upgrade to, I think 1.04, or whatever the next one was. The problem didn't appear. Then I closed my browser and opened it again, and the problem was there.
Rolled back to 1.03, no problem, even when closing/reopening browser. Tried going to 1.11 directly from 1.03, and no problem. That is, until I closed the browser and opened the page again. The problem started appearing.
Can somebody from D-Link confirm this issue, and possibly point to a solution or when a fix will be released?
Thanks.
P.S. I've read somewhere else that the European version 1.11 does not have this problem, but upgrading to it would void the warranty. Just cant remember the link..
-
I have the same exact problem. (and it stayed even downgrading to 1.10) It’s taken a week and a half to move up the ladder to 3rd level support within Dlink, then on to the product team. 3rd level support supervisor and product manager were on the phone with me and say they do not have this issue. I have since sent them the two forum links. They advise me to reset the router even after a firmware upgrade (claiming that some info is still retained even after a firmware upgrade) I have yet to do this and get back to them with feedback. In the mean time I am sharing till I have a chance to kick my family off so I can test the recommendation.
They feel confident they can resolve. (BTW- I had to go thru 3 third level techs before I got one engaged enough to run over to the product design them right there and get a conference call going)
-
Thanks for posting the update. Please post the results of your tests here when you have time. I have tried the factory reset before and after firmware updates, but it has not resolved the issue for me, besides being extremely time consuming reseting all router settings manually each time.
-
The issue was determined to be isolated to that specific unit. After a replacement was approved the out going unit was tested for this functionality and passed with flying colors.
If you continue to have this issue please contact technical support and request to be forwarded to Level 3 support.
Once there, explain the issue and the agent will request remote management of your router.
If we confirm that the unit is indeed throwing that error, a replacement should be forthcoming.
-
Hi,
Did they say if this error is related to the other variations we have seen ??
Like not being able to create schedules and such
SD1
-
Having the same problem, I think I might have a workaround.
After reloading a working configuration, I make my changes and after that I, instead of doing more things before rebooting, I do reboot.
After reboot I can make other changes and I don´t get any error messges.
But starting from a working is however a must. :-[
-
Hi,
I just opened a new thread about FW updates and Browser "interference"... I am wondering if anybody with the error in this thread can verify their browser and post in the new thread....
Thanks...
Sammydad1
-
I'll look in to this and try to replicate in the lab.
-
The issue was determined to be isolated to that specific unit. After a replacement was approved the out going unit was tested for this functionality and passed with flying colors.
Yes, I'm the one who has the replacement on its way out to me to see if I can now use access controls. Tech support seems anxious to get my old one to test in their lab. They seems surprised that it did not work for them. (and it seems like that took a whole week of convincing)
So, I will post when I get , re set it up, and see if all is better.
-
Now I have the problem that I cannot even resore a configuration.
This is what i get: "Restore Failed
The device may be too busy to properly receive it right now. Please try the restore again. It is also possible that you are logged in as a 'user' instead of an 'admin' - only administrators can restore the configuration file. Please check the system log for any errors.
Please press the button below to continue configuring the router.
Has anyone had the same problem, and in that case, how did you fix it ?
??? ??? ???
-
Hi,
Yes..I had that problem...only "fix" as far as I could see, was not really a "fix" at all.... you have to press and hold the router reset button to put back to default settings.... then re-enter everything you need by hand...and it still may not work as expected.
I am using the Beta firmware now and after using the reset button, it finally let me fully re-enter my settings and then add new items to access controls and such.... The error seems to be all related to the v1.11 firmware not fully clearing the rom when you press the reset button..but I could be wrong.
There are enuff people now with this very same error to confirm it as an issue to me...at least.
SD1
-
That´s good to hear. Or not.
At least I´m not alone with this problem.
Hopefully we have someone from D-Link Support in here that can forward this issue to have something done about it. Hopefully also forwarded to EU-support for them to resolve.
Has anyone tried to downgrade fw to say 1.03 and tried to restore from there?
Obviously it has to do with 1.11 so I hope that something is done rapidly to get this problem resolved.
-
D-Link support has said they will RMA my DIR-655, but I'm still waiting to hear back from the RMA team if my router is still covered under warranty or not. Sent in proof of purchase via email yesterday. If not I guess I am out of options. I still have to believe this is a firmware issue though. I have an early version of the hardware (A1 with green LEDs.) What does everyone else have?
I have not gone back as far as 1.03, got tired of having to reconfigure everything each time. As far back as 1.05 I still had the same problem.
Cheers
-
I've previously downgraded to 1.03, and the problems disappeared. However, restoring settings saved from newer version does not work. But the problems we're having here do disappear.
This too makes me think that this is a firmware problem. Which brings me to another question, though I think I know the answer...
If there is nothing secret in the router firmware, maybe dlink could make it at list somewhat open source? I'm pretty sure this would allow for a lot more bug fixes and new features to be added. But I think I already know the answer to this...
-
Has anyone tried to downgrade fw to say 1.03 and tried to restore from there?
Obviously it has to do with 1.11 so I hope that something is done rapidly to get this problem resolved.
It is definitely _not_ limited to 1.11 !
When I upgraded to 1.05 (i think it was that) from 1.03 (which came with the router when I bought it), i didnt try to use many features. It wasnt until I upgraded to 1.11 when I tried using the "Access Control" settings. And it crapped all over itself. I downgraded to 1.03, and it was fine. 1.04 (or whichever one was after 1.03) already caused errors. And so did every next version up until and including 1.11. And so does 1.11EU, for that matter :(
Something makes me think that when the firmware gets updated, there's still old pieces of code in memory and get executed instead of new code. But thats just a thought, unconfirmed by anything at all. speculation.
-
Well apart from the Access control part the 1.11 works pretty good.
So as long as I don´t have to restore config I´m OK with this.
BUT!!!
In the the next fw-upgrade this MUST be resolved!
It´s to a bit to delicate not having the possibility to restore a config.
And manually typing it in again is for me not an option.
-
Well apart from the Access control part the 1.11 works pretty good.
So as long as I don´t have to restore config I´m OK with this.
BUT!!!
In the the next fw-upgrade this MUST be resolved!
It´s to a bit to delicate not having the possibility to restore a config.
And manually typing it in again is for me not an option.
yeah, dlink should definitely resolve this for the next upgrade.
For the manual retyping thing, what I did was just save ALL the config pages (just in your browser, chose to save the page). And after upgrade, I opened them one by one and copy pasted configs. Its tedious, but beats writing them every time by hand.
-
D-Link is sending me a new router via cross shipping from California to Michigan. It will be interesting to see if it behaves differently. I'll post the results.
-
Hi,
All I did was go to each page that I had made any customizations and print that page...then I had to manually re-enter each setting once I had gotten the 1.11 FW completely re-set to default.
It is as if you have to press the repeat the reset process 2 or 3 times to fully clear the ROM after the FW update. Maybe even a full power off is required in there too.....
I think I agree with others that it seems to be an issue where the ROM wipe-clear process is not completing 100%.....
SD1
-
Mine had the blue lights. But not sure of the replacement that UPS says should be on my doorstep when I get home. I hope its going to be trouble free now. I'll post and let you all know.
Hmmm, wonder what the 855 is like? Starting to get sour on the 655. It did a lot of resetting of itself over the last few days. I'll be glad to swap it out sooner than later
-
The replacement unit came today. It's the A2 hardware with blue lights. It was also preloaded with firmware 1.11.
I connected the router and set everything up starting with access controls rebooting at every prompt. So far everything seems to be working without the previous errors. I'll keep my fingers crossed and test it for a few days before sending the RMA unit back.
Thanks DLink. :)
Cheers
-
I had another rather interresting thing happening yesterday on the subject memory problems.
On my DHCP Reservation list appered the MAC adress on one of my laptops with one digit altered.
With the consequence that it didn´t get the "right" adress, but another DHCP-adress instead.
How is this possible, since I use the Network filter allowing specific MAC-adresses ?
What happends next?
I´m confused about all this and expect a solution soon.
>:(
-
I’ve had the replacement router for a couple of weeks now and everything seems to be working properly. I am running access controls with multiple schedules and a large set of blacklisted websites. I have yet to receive the old error message and have no other issues at this time. It appears that the issue was specific to my hardware.
I have not heard anything back from DLink on the unit that I returned.
Cheers
-
Our PM group is attempting to isolate and fix this issue.
-
Lycan, any word or update to this problem. I upgraded firmware and can not use the access control panel either. Using an older version of firmware doesn't help either. ???
-
Lycan, any news on this one? Thanks.
-
D-Link support has said they will RMA my DIR-655, but I'm still waiting to hear back from the RMA team if my router is still covered under warranty or not. Sent in proof of purchase via email yesterday. If not I guess I am out of options. I still have to believe this is a firmware issue though. I have an early version of the hardware (A1 with green LEDs.) What does everyone else have?
I have not gone back as far as 1.03, got tired of having to reconfigure everything each time. As far back as 1.05 I still had the same problem.
Cheers
Hi blainem,
Hardware Revision A3 has Bright Blue Lights in the front.
I wonder if D-link should not seperate the Hardware Revisions of the DIR-655 Routers, as they have done so with the DI-624 Routers and the Firmware Versions that run on each?
-
For what it's worth the firmware reports it as A2.
Cheers
-
Lycan, I have raised a Supportissue on this to my local support here in Sweden.
So far (14 days) I have not heard anything from them.
Very soon I will return my 655, and as I stated earlier, I´m very satisfied with it apart from this issue.
The local support is another problem.
Do you have any idea what´s happening ???
??? ??? ???
-
We are unable to pinpoint or even replicate this issue. I've RMA'd a unit that was suffering from this and couldn't get the unit to recreate the error.
We're workign on it and I'll bring it up again.
-
Lycan,
Anything we can do or provide to help replicate the error?
-
Just thought I'd chime in and report that I have the same problem. It's obvious that there is a problem with 1.11 but dlink can't figure this out?
-
This is a tricky one. We've tried to replicate the issue in house. I'd like to RMA someones unit that is having this problem. I might even be able to work out the shipping (maybe).
Any takers?
-
This is a tricky one. We've tried to replicate the issue in house. I'd like to RMA someones unit that is having this problem. I might even be able to work out the shipping (maybe).
Any takers?
I'd volunteer mine, but need to have access to the Internet on most of my PC, and don't have another router. Would it be possible to arrange the RMA in such a way that I get the new router from DLink first, and then send out mine for the developers to examine?
-
Just curious if they had any luck on the one I RMAed too.
-
I'd volunteer mine, but need to have access to the Internet on most of my PC, and don't have another router. Would it be possible to arrange the RMA in such a way that I get the new router from DLink first, and then send out mine for the developers to examine?
Yes. When you go to the RMA portal select Advance Replacement (or something along those lines), give a credit card number, agree to ship the broken one back. Then when you get the replacement return the broken ASAP (Credit card hold is charged at 30 days). Contact them by email or phone if it does not work that way.
-
I have the same problem for the last week, everything was working fine, I used firmware V1.20 for a long time without any problems and when I try to change a schedule in Access Control everything went down... I had to reprogram my router several times but same message keeps popping out... I'll need to start a "case" in the support area to get an RMA?
-
Lycan,
since I´ve raised a Support request on this to my swedish support and not heard from them for soon to be a month, maybe you can pull some strings. They can have mine to test on. If they even bother to reply to my request!
-
Just found this post, i have this error too. My box is unchanged, no updates have been done.
Product Page: DIR-655 Hardware Version: A1/A2 Firmware Version: 1.03
I have not updated my firmware since i see others also having problems with the 1.11 firmware.
Can anyone tell me if the latest DIR655A1_FW111EUb02.bin have this issue resolved?
Thanks.
-
Does anyone have this problem with a US DIR-655? I think two of the posters have mentioned they have EU versions.
-
@AWDL:
I bough mine in Canada, but I suppose its the same as the US version? It was having that problem both initially and with the EU version as well.
Also,..where is the RMA portal? A quick search didnt give me any links, so I figured I'd ask :)
-
Sendt a message to the local D-Link support yesterday with detailed problem descritpion; they told me to try a different name for the policy, thats it.
I have, as you others, tried various combinations with no luck.
-
@AWDL:
I bough mine in Canada, but I suppose its the same as the US version? It was having that problem both initially and with the EU version as well.
Also,..where is the RMA portal? A quick search didnt give me any links, so I figured I'd ask :)
Canada should have the a non-EU version, just like the US.
Canada doesn't have a portal. I was giving US answers. The US answer is rma.dlink.com
-
Does anyone have this problem with a US DIR-655? I think two of the posters have mentioned they have EU versions.
Hi AWDL,
DIR-655 A3 Firmware 1.11 USA Version here. If you click the Advanced Tab, click Access Control.
Access Control is not check. I checked Access Control. Click Add Policy.
This wizard will guide you through the following steps to add a new policy for Access Control.
I click Next.
Choose a unique name for your policy.
If I leave it blank, the error message is : The Policy Name cannot be blank.
When typing in a name no error appears.
Oh, by the way, I had receive the unit with Firmware Version 1.10 installed. I upgraded to Firmware 1.11.
-
I am having the same problem.
-
Choose a unique name for your policy.
If I leave it blank, the error message is : The Policy Name cannot be blank.
When typing in a name no error appears.
This seems quite logical though... ???
-
The update is this:
Since we can't replicate this error message even on RMA'd units for this problem. We have PM going through all the situations were they will throw the error message in question.
-
Well, having lately "upgraded" to the 1.20 firmware, the router is not stuck in an infinite reboot loop. Trying unplugging the power for a number of hours, didnt help. Ended up purchasing a new router (picked up a random one in the nearest computer shop, just needed something to ensure i have internet for the next little while).
I looked at the RMA website, and it says that I need a "case id". I take it I should call the dlink tech support, get case id, and then rma the unit? I bought it more than a year ago, so thats probably past the warranty period. What procedure should I follow in order to get a replacement router? I'm in Canada, by the way, if it matters.
Thanks.
-
The update is this:
Since we can't replicate this error message even on RMA'd units for this problem. We have PM going through all the situations were they will throw the error message in question.
My unit is having this exact same problem. I cannot add access control policies due to the message "Name can not be empty string." I have tried everything, even upgraded the firmware to version 1.31 (which I now regret because I understand that access control works in firmware version 1.03 and I can not downgrade).
I find it hard to believe that no one else is having this problem; either that or other users are using methods other than access control because they can not get it to work.
I would be willing to RMA my unit since it appears Dlink can not duplicate the error. I believe the error is hardware revision specific. I have hardware revision A2.
-
Try reflashing 1.31 and setting up manually from factory default (no restore of saved config). If the problem persists you can try to apply for an RMA (send the Dlink tech a PM)
-
Try reflashing 1.31 and setting up manually from factory default (no restore of saved config). If the problem persists you can try to apply for an RMA (send the Dlink tech a PM)
I have tried that as well and still get the error, even after a manual setup. As I said, I still thnk it's a hardwre version issue (I have hardware version A2).
I have sent a PM to Lycan inquiring about an RMA.
-
I have hardware version A2 too, but haven't seen the notice anywhere. So you can rule out the revision question.
-
What is the solution to this problem?
I have had my router for a while but I am trying to set up the access control today. "Current Firmware Version : 1.21;Current Firmware Date : 2008/10/09" The hardware is an A2. I have tried letters only, numbers only, combination of letters and numbers and have tried to leave it blank. I have also tried accessing the page both from Mac OS X 10.4 and Vista. All with the same result. When the router goes to save the page it returns an error "The name cannot be an empty string." and nothing is saved. I have not seen any other problems with it
-
I've never used Access Control so after reading your post I decided to try it. I have A3, 1.32Beta. I typed in "Control" for a name and everything worked. Of course, your mileage may vary.
-
Ok, it's September of 2009, and i have had this issue pretty much since I can remember. I am still having the issue. I cannot establish (create) Access Control Policy, cannot use the feature, which seems to be at the heart of the blocking, etc. on this router. Now I need this feature because my teenager is doing more on the computer. I have been through every firmware revision there is so far, and countless, painstaking manual reconfigurations of router settings, and the feature just DOES NOT WORK. What is the solution D-Link? What are we to do here? This is a real issue, and not at all a user-level mass blunder. The Access Control does not accept any policy name, not even the number 1 or the letter A, and somewhere the blocking and scheduling part of the firmware is completely broken. I have seen it posted in this thread that the problem cannot be reproduced? That has got to be an internal office disconnect between technical and forum somewhere. All one need do is go to the Access Control section of the router, enable it and then try to create a policy. That's it, you'll see the issue straight away, no extra questions, nothing funky; it simply does not work. Please let us know what you can do for us. Thanks.
-
DMB....
try using a different browser....I forget is that was mentioned earlier in that thread.... The bug it references shows up in several different ways besides the main one the thread was created about.... Such as in my case, trying to set a schedule's time, and being told that the time I set is in error or rather invalid.....sometimes a time like 01:30 AM will work....but 01:15 AM is invalid....
Go figger....
-
Thanks for responding...
Tried IE, Firefox; Same results. In Opera, there is a java issue that i don't see in the other browsers. the java (updated and running properly) scripts wont run correctly from the get go... I haven't gone to Safari. Tried it from Firefox in a Linux dist. also (Ubuntu).
I have noticed that "name can not be an empty string" happens when the Access Control check box is selected, and then you click on the save settings button, without even adding a policy, which of course makes sense, and seems like a legitimate error message. It's as if when one runs the add policy wizard, upon saving their policy at the wizard's end, it is coming back to the Access Control screen without being able to save the policy in the ROM / Flash storage on the router; and then to be added to a list of policies that I assume will form near the bottom of that A.C. screen at that point.
I really appreciate the input, any other thoughts?
-
Also, it seems that it may not matter, seeing some of the previous posts, but:
Firmware Version: 1.32NA
Hardware Version: A1/A2
Can I send mine back for testing? I thought i saw it mentioned that someone could be the guinea pig, although it seems like i am late getting here, and it's been over two years I believe...
Can I get a later Hardware Version, or simply get mine replaced for one that works?
-
Any further investigation or any discoveries?
-
This is absolutely ridiculous
-
ok, now i go to one of my client's DIR-655, who have A3, and messed around with their access control. They have firmware 1.20, so this is looking like a post v1.20 firmware issue everyday... The first annoyance i notice is the time cannot be night to morning, as in an "overnight" schedule, so i guess it always has to be daytime hours? that bites. I added policy and saved it, etc. and it worked. I would be willing to wager (a new router) that if the firmware is updated on theirs, access control will fail big and bad like every other one out there. ****, I mean, I can't even just do simple site blocking at this point. I love the amount of capability of this router, but this one is major... NO access control. come on I paid more than twice what I would have paid on a simple home router, including one of d-links... so now it's only worth half again as much as a cheapo. if there is a d-link god, please see this and do something about it...
I hope i don't need one of the features from any < 1.20 or any upcoming firmware updates for this small business client's router, because as it is now, those access controls, and the "rules" list are being used. I can hear someone saying this router isn't made for business, but then I say the price sure wasn't low if it is a toy router...
There are other issues (seemingly after firmware 1.3x), including the router not saving DNS Virtual Server entry at UDP port 53, if it is entered in the first slot of the Virtual Server list. no matter what i do it changes to a different port after the save/reboot. i just enter DNS on any other slot in the list and it saves port 53. Weird. Not to mention that restoring a configuration from a file is totally broken now, even with the same firmware used to backed up/create the file... but none of the issues i have had post 1.3x are as apparent as the issue in this thread, in my opinion.
-
dmb- if you want a schedule that is overnight, you have to break it up into two schedules. The 655 has an issue wrapping around midnight. The first schedule would end at midnight and the second would start at midnight.
-
I understand, thanks. Interesting that the router (1.32NA Firm) that has the empty string issue, allows time to bend around midnight, isn't it? :)
Note: The empty string issue, I am pretty sure, lies within the code that would be adding the "new policy" in the list at the bottom of the Access Control page.
on 1.32NA i can add schedules ok, simply cannot "save" new policies at the end of the "new policy wizard"
At the end of the wizard, the browser is redirected back to the Access Control page, and the checkbox for enabling access control disappears right before the error, and then reappears when the error box is cleared, showing access control is enabled, and obviously, there are no policies ever listed at the bottom of the page. Subsequent "save settings" attempts bring up this thread's title error at that point, which makes sense. I believe that the code is probably written that if a policy is created, or exists, then "policy wizard" should not launch, and additional buttons might appear there...
-
I was fine until I upgraded to 1.31. I was able to use the Access Control until 1.21 but god knows what the hell DLink did in 1.31 it screwed up everything. I don't think DLink cares its customers anymore because they made big bucks after the DIR-655 release. Until then they had 24/7 free tech support as I remember it.
I tried all the tricks to make it work like pressing the reset button and at the same time unpluging the power, using the factory restore from the app etc. but no luck. Always get the meaning less "Name can not be empty string".
What happening there is, their "Add Policy" wizard is failing to save the policy you're creating and hence when the call is made to the save function it raises that error. But, not sure what kind of stupid, useless programmers D-Link has. Fire them all and get the right people who does right work!
-
Anyone know if there is any new update on this issue. I really need the ability to do access control which was working until I upgraded. I'm gonna have to dump D-Link if I don't find resolution.
Btw, I called their tech-support & they were no help. The only solution offered to me was RMA which I don't qualify for since I've had the product for over 1 year.
I really hate it when companies don't regression test their software.
-
This is absolutely absurd. I am about to start a negative D-Link campaign if I cannot get through today as I am a managing editor of a couple of review sites for tech products. This issue has been present for 2 years and still no fix has been provided. Shame on you D-link. I am now having the issue trying to block some sites from my children and low and behold I get this error. This is after upgrading to 1.33 firmware. I have tried all of the tricks mentioned and still no success. When will D-Link listen to their customers. Will it take a negative campaign to make them change their ways. I will give them 1 week and then I'm going to let the dogs out. Please address this issue ASAP.
-
I just began having this error today. I was using the Access Control on a box that said hardware version A1 and Firmware 1.03. Suddenly when I was turning on Access Control (Enable Access Control) I got this error or at least a similar one, my error said "Rule name can not be empty string".
After trying everything I could think of, I upgraded my Firmware to 1.33NA. I now get the error message "Name can not be empty string". It is interesting that my hardware is now version A2!
I am sure I am not under any warranty as I have had my DIR-655 for several years, so it looks like there is no fix for this and I must purchase a new box as I have four children and I do need the Access Control features. Now do I go with a D-Link router which will save me some time as I am familiar with the product or do I get pissed off and purchase a different brand because this issue has not been resolved?
Since this issue has not been resolved is there any discount those of us who have the issue could get on a new box? I did get two good years out of my DIR-655 but I would expect a longer life than that.
-
Add me to the list. Upgraded my A1 tonight from firmware 1.21 to 1.33NA and now I am getting the same error with Access Control. I did not have this issue until I upgraded the firmware and I had been messing with access control a lot recently so I know the upgrade broke it. EXTREMELY frustrating. Aaaaaand of course I cannot downgrade the firmware. I have been a LONG time Dlink customer/supporter/seller so I know this probably will not be fixed anytime soon unfortunately. Heck, this firmware has been out for months already. Ill give it another couple weeks before I get a different router. Maye time to try something new anyhow.
-
MadMax....
If you dont have too many settings to lose, try using the hard reset button for like 20-30 secs....then do it again after the unit reboots....
It might allow for things now....
-
Hey Sammy. I tried that already with no luck. Did that work for you by chance? I am open to more suggestions if you have them. I do not mind losing settings over and over by trying things either if it gets my access control back in the end haha.
-
I had in the past a variation of the erro you are seeing in thet I couldn't modify any of my previously added access policy's....
I can do this now, but I am not sure what changed when I flashed the firmware that was not working previously.....
I know hen I went from 1.21 to 1.33 I had to do the Hard Reset dance to even get 1.33 to install.....
But afterwards, I could add and edit policies again....
I dont think it was a firmware bug as much as I think it was a quirk with the flashing process that affected that specific part of the firmware.....BUT that is only a hunch....
-
I have played with it for a couple of days with no luck. Hard reset, reflash, etc. Just thought I would update you. This is very disappointing.
-
10 seconds hard reset should be enough.
Firmware 1.34B03 is available to be used as a clean install.
http://forums.dlink.com/index.php?topic=12668.0 (http://forums.dlink.com/index.php?topic=12668.0)
Perform a hard reset after the update.
We have been unable to replicate this issue on version 1.34B03 and previous ones.
Recreate your config file, as it's possible that a corrupted file is being loaded.
Be sure to use IE browser that is up to date but not with third party security components that will limit processes in the Web GUI. Or instead use a different browser.
-
Still no luck almost 2 months later and new firmware. I feel like I have tried everything. Any other ideas?
-
HOLY ****! I finally got it working! Updated to the 1.34NA firmware and on the 3rd reset today I got it working. The only thing I did different the 3rd reset is that the FIRST thing I did right after the reset was set up the Access Control Rule before I set up my wireless network (SSID, key, etc.). Why setting up my wireless breaks Access Control I have no idea.
Carefully backing away from the router so as not to upset it...
And just to confirm.... after setting up my wireless I cannot add or change a Access Control policy but the ones I setup right after the reset still work.
-
Ok, dMb got it working. Not sure if I should be posting here giving the age of the thread, but other forums directed me here as the 'official' thread.
Same issue with a DIR-655, Firmware 1.34NA, Hardware A1/A2.
Done multiple hardware resets, reloaded factory config more times then I can count. Used three different browsers in 2 different OS's. Tried multiple variations in the name (with space(s), no space(s), all numeric, all text, alphanumeric.
Went to try the firmware that Bett0 told dMb to try, but
An Error Has Occurred!
The topic or board you are looking for appears to be either missing or off limits to you.
Admittedly I have not tried setting up access control before setting up wireless yet, but I don't see why I should wipe my router clean just to modify an access control schedule.
Guess its time to pull out my linksys router.
-
The firmware in Bett0's link was a beta firmware that is no longer available. Have you tried the 1.35NA firmware?