Print

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

[DCIFRTHS]

... I see there are a lot of you having problems with it - but you should acknowledge there are also a lot user without SecureSpot issues. ...

Why? It does nothing to solve the problems some people are having.

[sKullcrush]

thumbs up for a securespot-disabled firmware

[Halibut Point Memory]

Somebody told me that the original firmware came without this Secure Spot. Seems to me if it did once, it can again. What's the big problem with simply extracting it entirely? Seems to me this is really the only proper answer to this huge huge problem. I had thunderstorms that rebooted everything and once again I got hijacked to bsecure.com.

Is anyone at D-Link actually listening to us? It really isn't fair that I bought something with this many problems. I'm getting a real bad feeling about all this.

[mchulick]

D-Link take a look at all of the unsatisfied end users because some moron decided that everyone needed protection. Take a little time and offer a SS free firmware upgrade. You most likely already have it developed, just put it out there and then ask your customers how they feel. This Securespot problem is a cluster...

[nathandehmer]

Yes please get rid of the freaking Secure Spot P o S.  I hate having to come home from work and enable disable reset reboot to be able to access the freaking internet.  You are just luck that no one else has made a comparable router yet.  Because as soon as they do, all these buyers are going to see this and jump ship. 

[Sammydad1]

linksys has a new unit...  E3000 I think it is...  A/B/G/N both 2.4 and 5 GHz simultaneous...I think maybe only thing is no USB printer support and it has 4 gigabit LAN ports....  $149 on newegg

[roblarosa]

I've been using the DIR-655 for a few months now and just within the last few days this BS SecureSpot has been hijacking my router. I don't have it turned on within my router's settings and I canceled my SecureSpot account

Why is this issue not being addressed by DLink? The Dir-655 is my first experience with DLink and if this isn't resolved fast, it will be my last.

I knew I should have gone with a Linksys!

[Sammydad1]

Hi,

Don't just blast at DLink....  If you do some deeper probing, you will very likely find that all the consumer makers have had at times major issues with units here and there..... I personally went thru some heck a few years back with a netgear wgt-624 wireless router that had LOTS of folks up in arms....

The problem for these makers is whether or not it makes financial sense to try and uncover what are quirks to them, but are REAL issues for some folks.....but most others have no issues worth mentioning if any.  I have been fortunate enuff to fall into the latter category with my 655.

If you are saying there should be no NO ISSUES EVER with a router or its firmware, well then, I would like to agree with you 100%, but in real world, it probably isn't gonna ever be that way.

Blame DLink for selecting the Ubicom chipset that this router uses.  Ubicom sets the fee's for licensing which has kept the 655 out of the world of DD-WRT development from the reading I have done in the recent past.  If Ubicom would drop their fee schedule for this chipset, I bet the DD-WRT coders could have a working firmware in short order....but they don't want or need the hassles of fighting lawyers and such for infringment.....and I don't blame them.

[Halibut Point Memory]

What is the deal with this hijacking? It happened again this morning. This is really really becoming annoying. Mornings are not the time for things like this when I'm trying to get out the door.

I was trawling down the forum last night and found a thread about exactly this problem with a gazillion replies and it had been locked. The good news is that this isn't a "quirk" but a real issue obviously, and it seems like what kicked it off was the changeover to daylight savings/summer time. I know looking back, that's just about where my problems began. The bad news is that we haven't heard any news on a fix from the person who locked that topic.

I've got a bad feeling about this whole thing. I wonder if I can sell this brick to some poor unknowing sap? But then again, do I want that kind of bad karma?

So frustrating. Argggh!

[roblarosa]

Sammydad1 - I'd agree with most of what you say except in this case, this issue has been reported over a month ago and there is a sever lack of inaction on DLink's part to rectify the issue. Now, I'm no business major, but I would think that not fixing (ignoring)  a very public issue will cost them more in lost future business that it would to address the problem.

Their lack of customer support is appalling.

[Halibut Point Memory]

Oh my goodness! I trawled down further and found another locked topic about Secure Spot exposing credit card numbers! The moderator or whoever said it was locked because of "security reasons."

But that only piques my concern more. If it was closed for security reasons, what were they? Is this something to be concerned about? Talk about unnerving. No explanation. It's just left dangling out there.

Now I'm glad even more than ever that I never ever remotely considered Secure Spot.

All the more reason to eliminate this obviously faulty and now very scary "feature."

This just gets worse and worse. Sheesh.

[dirkpitt]

This thread is a re-post of another that I started back on March 30... http://forums.dlink.com/index.php?topic=12315.0

This just reinforces two things:  that many of us are feeling the same way with the problems that SecureSpot repeatedly is associated with, and that the mods here aren't paying much attention to the members or these threads.

I have personally had it with De-link and being ignored by the mods (never heard back from Lycan regarding packet capture), tech support (the bsecure servers have been reset and there is no more problem) and the unreliability of the basic firmware functionality on my DIR-655.

[dirkpitt]

If De-link's firmware has been built using any half decently formalized code development environment it should be possible to make a new build in a matter of minutes.

I assume that either it has not been built in that kind of environment (which would explain some of the undeniable faults in the code) or that they are much too busy programming for whatever bug-ridden router is to be their next cash cow.

Either way, De-link customers lose.

[G4IJL]

I do not have the option of "securespot" here in good old England. The router tells me it has the latest firmware. I am using - - Firmware Version : 1.21EU,  2008/11/03 , erm note the EU.

The firmware from the European web site of D-Link is DIR655A4_FW121EUb05 on my DIR-655 version  A3

I think I was offered the dubious delights of this securespot but declined that update some time ago and kept the EU version and its updates.

Take it from there. Don't blame me if you change the firmware and it screws up. I just stated what we have over this side of the planet.  

[scdl]

My personal experience - problems that seem related to firmware after the introduction of SecureSpot into 655.  I have opened a case number with tech support for my problem and I suggest that you all do so to, if you haven't done so by now.

I would also like to respond to an earlier comment about what seems like a defense of poor product support.  When a company sells a product, it warrants that it works. So, it does not matter the cost of the product or the cost of ongoing support (to the company) or whether the company thinks that a problem is just a quirk.  I don't know whether I will get better support from one of Dlink's competitors, but I am certainly a lot more likely to consider a competitor's product when what seems to be a relatively simple issue to fix is ignored.