The key to solving this is enabling Dlink to replicate the issues that are reported. Dlink has explained they cannot replicate the issues in the lab environment. So nobody seems to deny anything (I'm 100% sure Dlink staff have read each and every post), but if you want to solve it, you got to be able to diagnose in the lab to see what's going wrong. Only people reporting: 'it does not save x" or "it reboots" without the context of settings and configs is just not enough.
It's like asking a doctor to diagnose a disease when you only say to him "I don't feel well". But looking at the comments I've received this seems to be the genuine expectation of the local bunch here...
EDDIEZ.........I did not quote you! Who are you?
Since you have to respond EDDIEZ I understand what you said and it makes sense and I know I did not post a screen capture, config. settings. I would almost bet DLinks customer service is getting hammered and DLink knows somethings wrong.
All I was trying to do was bring up issues that people have and keep engaged in a way that could be productive.
As for your comment about the local bunch here can be done without....not helpful.
I bought my Dlink and yes my expections from DLink if they want my $$$ in the future is to fix the problems, in whatever means that works.
I updated to fw 1.31 because I was trying out VOIP and had issues of dropped calls or choppy audio. As I don't claim to know anything, it was learning curve to find a way for me to make it work.
I'll try the next few days if I have time to post my details with colors pictures and just maybe I can do a powerpoint walk through.