Print

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

[deezomaxima]

I'm on the phone with them now to see what they are going to do about this router now that I've upgraded to a bad firmware without seeing the forums and the issues people were having with the newer firmwares. Rep is saying she hasn't heard anything which I don't believe but I'm going to be a nice guy until they sound like they don't want to help.

[FurryNutz]

Was there a reason you updated the FW? What was wrong with the router that caused you to update? If you used beta FW then you might need to understand that it's beta FW and not for release to the general public and those of us on here are willing testers for this Beta FW and thus since it's not released to general public that dlink CS does not support it until it goes final released to public when and if dlink decides to grace it. As for your router problems, why don't you give us some info on what ur problem is? What HW version and FW version is exactly loaded? What settings are you using. What issues are you seeing. Maybe we can help. I've posted some my settings on this forum for the 4500. Look and see if they might help you.

[deezomaxima]

I wasn't having issues with my router but totally went against my logic of "If it's not broken, don't fix it!" mentality. I saw there was added functionality with the Shareport Utility and decided to try it out so I upgraded to 1.21NA not even seeing all of the issues that people were having with it.

Shareport worked for about 2 weeks then stopped recognizing me USB HD. Tried to reflash but had no success. The I noticed that my Thinkpad T400 started to have connection issues and I thought it was due to a WLAN driver (which is a known to have issues disconnecting from wireless routers randomly). Then I noticed my Ipod Touch wasn't going to webpages then I knew my router was acting funny. I'd reboot and everything would be fine afterward.

I've been rebooting every 4 to 6 days to cure the lockup and even tried some of the things I've seen on the forum but it's still hanging.

My hardware is A1 and had the 1.02 FW on it when I purchased it. At this point, a tech is supposed to call me back but I felt that I should get in on what's going on here just in case the people here band together to get some kind of legal action going against Dlink. My router was rock solid until I upgraded to 1.21NA.

When I get some time, I will mess around with the setting you provided. I will not upgrade to any Beta because I want Dlink to be responsible for posting a FW that had problems. They can't fault people for trusting them so they need to make it right.

[TheAncientEvil]

Was there a reason you updated the FW? ...

Hey Furry, first, I understand there will allways be bugs, but I just want to point out that a specialized FW update that advertises fixes and new features should not be flawed to such a large degree.  I don't personally subscribe to the "if it aint broke don't fix it" line of thought when it comes to something that is part of network security or security patches etc.  Better to fix before someone breaks it for you.  The bottom line is, you shouldn't be afraid to apply an update that says it fixes things.  Of course you are on your own with anything listed as Beta or Alpha as you said.  That all being said.  Just my 2 cents.

[deezomaxima]

Thanks for the input guys. I just got a call from a network engineer with a very good proposal so I can't complain since the proposal is to do everything they can to make the issue better.

I will test the beta firmware tonight when I get home and watch it for a few days to see how the router reacts. I'm told by the engineer that people are giving good responses with the A1 hardware.

[FurryNutz]

Good to hear that there is resolution in site. I was only trying to provide some possibilities in the the CS service and engineering, sometimes both hands don't talk to each other. Thus sometimes you might have a CS person say that they may not know about the beta stuff and I presume that for the most part, they probably shy away from that unless there is a big problem.

Ya, not everyone needs to pay heed to the "if it works, don't fix it" I don't sometimes. However for general population and end user experiences, thats probably still a good rule. Let people like us go on the front lines and take the chances with new stuff. All is good.

[Puffnstuff]

It's also wise to check out a products forum prior to doing anything to it just so you can avoid your current situation.  My a1 was ruined by the 1.2x fw so after dlink sent me an a2 I've kept it at 1.16b3 which has its moments but overall works ok.

[deezomaxima]

Agreed. I've never had issues with any of my routers until now so you live and learn. I'll pay more attention next time but once I get my A2, I probably will never upgrade it past 1.15 anyway. I just need the router to be stable again in being my wife runs her business from our network and her blackberry. Our network is used heavily at times.

[Tyrone Biggums]

The official 1.20 and 1.21 Live FW is flawed. However dlink has fixed the issues with their beta releases.  I haven't tried the recent beta but the one before that I have not had any issues with i think it is Build 03? Let me check and I'll post again

[FurryNutz]

I agree, I should have paid more attention to the forums. Adding forums for all products that I use and have the option of upgrades. I was doing fine until 1.20 FW. Beta 03 and 08 seem great now. I hope the Wireless will become more stable. Seeing some random disconnects for some reason. Thanks for having forums and people like us here. Hehe.

[deezomaxima]

After a day of running 1.21NA Beta here's my stats:::

LAN Statistics

Sent :4
TX Packets Dropped :0
Collisions :0
Received :0
RX Packets Dropped :0
Errors :0


WAN Statistics

Sent :124
TX Packets Dropped :0
Collisions :0
Received :1065
RX Packets Dropped :0
Errors :0


Wireless Statistics

Sent :511
TX Packets Dropped :13
Received :392
RX Packets Dropped :9
Errors :4

I'm by no means a networking pro but what does this packet loss mean in terms of the beta FW?

[FurryNutz]

That they still need to work on the wireless section of the FW. I've been using B08 and it's not good. Keep getting disconnected alot and lots of packet droppings. However I'm using N Mode wireless. Not sure if G or mixed mode is doing the same, presume they probably do.

Wireless Statistics

Sent :473094

TX Packets Dropped :10235

   

Received :290377

RX Packets Dropped :202650

Errors :19508

[deezomaxima]

I'm using mixed b,g and n.