Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[KevTech]

But as I remember well, the 1.2x firmware was even worse when i comes to router performance and Shareport performance.

Yes, it was a lot worse.

For me the 1.32 works like a charm (router & Shareport). So no need here to downgrade all the way back.

Works perfect for me as well.
I tend to feel some of these problems may be the way people are flashing (over wireless or maybe antivirus scanning while uploading file) or something in the way the router is configured.
Maybe uploading the old config from 1.11 after flashing. 

[LibertyMark]

I just can't get over EddieZ's arrogance.

He repeatedly talks down to, and minimizes, the reports of problems by other users.  He repeatedly states that "this doesn't apply to the whole population".  This is true, but it doesn't mean that there isn't a problem.  His posts are fanboy irrelevancies, but I guess that's what happens when you live on a router forum for years.

So, with no irony at all, he turns to his "this doesn't apply to everyone" shtick, and uses it himself with this comment:

"But as I remember well, the 1.2x firmware was even worse when i comes to router performance and Shareport performance."

So, there you go.  Since for him the above statement is true, then it must be true for everyone.  For me, the above statement is false.

So, I too want some kind of feedback from dlink.  I don't expect hard dates, but just the occasional check-in that says, "Yes, we're still working on it."

[EddieZ]

Just have a look back on the forum about the 1.2x firmware. You'll be surprised what comes up. Wheras I might be 'talking the issues down', there's tons of others that present the issues as being generic. While there's proof that it simply cannot be generic. I'm not denying someone can have issues and certainly not claiming the product is perfect.

Since there's others like me that don't have issue or only minor ones, I feel it is only fair to show that too. Also this keeps this forum from being nothing more than a stage for ranters and tech n00bs, taking into account this forum is not a direct communication channel with Dlink, but a users-help-users place.

When telling others that I have no issues and trying to let n00bs gain some more insight on how networking works and that it depends on more than a router alone is being qualified as 'arrogance' there's really something wrong with your attitude. If you're not happy and the router does not function, simply RMA it.

[EddieZ]

Yes, it was a lot worse.

Works perfect for me as well.
I tend to feel some of these problems may be the way people are flashing (over wireless or maybe antivirus scanning while uploading file) or something in the way the router is configured.
Maybe uploading the old config from 1.11 after flashing. 

There's tons of possibilities that can screw up a config or a network topology. But luckily it's all self proclaimed experts here that have perfect knowledge of Windows, hardware and networking 

And since I'm accused of being arrogant: Maybe it's just my degree of expertise that lets me have a perfectly working network. 

[LibertyMark]

Just using the word n00bs is enough to prove you are arrogant.

I can't RMA my router because it is around 2 years old.  It was working practically flawlessly until I flashed 1.32NA on it, and now shareport is unuseable.  The only problem I had with shareport on 1.21 was related to the shareport clients, not the router.  The clients sometimes wouldn't have a connection to the router after a computer awoke from sleep.  Stopping and re-starting the client software always fixed the problem.

Under 1.21, I went months between rebooting the router.  In fact, I never had to reboot it that I can remember.  It just always worked.  Now, under 1.32NA, I have to reboot every single time I want to print something.

When the exact same symptoms are described by multiple users in different environments, you know there is a problem.  All of this discussion about whether it is generic is beside the point.

[EddieZ]

Nope, that's no arrogance. That's reality. 

With 1.21 you're probably one of the lucky few that had no issues....Hey, that's the same situation as we have here with 1.3x, only it's the other way around!

But in case you missed it: I'm not denying that there are users with issues. I do challenge the fact it's qualified as a generic issue with the firmware, dismissing all other possibilites in configuration and topology. More or less the same claim you make about 1.2x.... 

[illusion121]

H/W A3 w. 1.32 NA.

No problems with 1.21 f/w. Huge problems w. 1.32NA. I am checking this site everyday now for a f/w upgrade. I ditto the comment about updates!

[KevTech]

H/W A3 w. 1.32 NA.

No problems with 1.21 f/w. Huge problems w. 1.32NA. I am checking this site everyday now for a f/w upgrade. I ditto the comment about updates!

Have you tried loading defaults then manually setting the network?

I had problems with the router when I loaded an old configuration after flashing the latest firmware but after a reset to default/manual entry of setting all is well.

[verizonfan]

"I just can't get over EddieZ's arrogance."


x2 on that one as well.  You need to learn to ignore comments from people like that when you participate on forums.  Eventually they move on when you don't respond to them and they find some other way to perpetuate their ego.

[kthaddock]

look at this post from Lycan from d-link !

http://forums.dlink.com/index.php?topic=7588.msg48512#msg48512


regards
kthaddock

[verizonfan]

"For those of you that continue to suffer with unusable routers do to firmware failure I suggest you contact technical support and request a replacement that has the previous firmware version. For now this is all we can do."


That's great in theory but does not go too smoothly in actuality.

[diske]

Not going as smoothly? Thats a good point. I mean, you call the phone# and you get someone that may or may not be involved with the forums here. They may just make you go through every single step. If Lycan (or another moderator) could outline a quicker process for RMA that would be great.

Why would I think thats appropriate? Well, the people on these forums are generally the ones that are spending their own personal time testing out other users's ideas to resolve their problems, helping beta test new firmwares, and no doubt saving time and money for dlink. These forums are basically how-to's for users, with most information submitted by users, no? What company isn't jumping on the Free Forum for Advise, for their customers... bandwagon lol?

Would be great if we could at least skip 1 hoop by calling and as soon as they say hello, we're just like "Yeah um, im from the forums and stuff? i've got 20posts regarding my model, spent about 15hours working on this, and still have a problem." and they go "Well dang, thanks for spending all that time yourself, talking to other people about our products and trying to figure it out..hows about a cup of hot chocolate? and another DIR-655 AX 1.X" lol ya knows?

[Xinot]

When there is so much so random problems and everybody is looking nothing but firmware, could it be something really weird like securespot settings etc (including trial time settings) BEFORE firmware upgrade? It is enabled by default after upgrade and are connecting to "somewhere" and talking about settings etc with "someone"... Maybe stupid idea but so are this issues too. 

[alphanumeric]

Works perfect for me as well.
I tend to feel some of these problems may be the way people are flashing (over wireless or maybe antivirus scanning while uploading file) or something in the way the router is configured.
Maybe uploading the old config from 1.11 after flashing. 

I re-flashed my DIR-655 to 1.32NA about a week ago. I downloaded a new flash file and Shareport utility just before doing the flash. I did it over a wired connection and reset my router to defaults before doing the flash. I set it all back up manually and installed Shareport. So far 7 plus days and Shareport is still working. I'd bet some of the problems are bad flashes. There are going to be some that do it over wireless without knowing they shouldn't. Maybe there should be some better more detailed instructions, a defined procedure for flashing the firmware. Granted not everybody is going to follow it but it may save some people from a bad flash. If my Shareport does keep working that would be what I think happened to me. I'm using all the same network settings I used before when Shareport didn't work. Just my 2 cents.

[LibertyMark]

That's good information, alphanumeric.  I plan on following the same procedure you did and try to do the whole thing over again.

When I moved from 1.21 to 1.32NA, I did it on a wired connection, but I used the saved config file from 1.21 to set it up again.  There seems to be some hint that maybe using the config file is not a good idea.  Maybe these problems are not related to the lower-level network processing of the router but simply a bad mapping of an older config file into the new firmware (which would still be a bug).  Just pure speculation.

Anyway, it may be a few days until I can re-do everything.  I am very interested in your continuing status.  If you can, keep us posted.  Thanks!