Print

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

[Toilet-Duck]

Is this with securespot on? If you disable the SPAM in the securespot services it fixes the wireless disconnects for me

[davevt31]

No, SecureSpot is off.  This has happened ever since we got the wii, not a big deal as I know what is causing it.  I would turn off the Standyby WiiConnect24 but the wife seems to like the weather and news channel on it.

[blaquesmith]

Dir-655 A4 Revision handles firmware (beta 1.22b05) fine. But Once I attempt to setup Ntp Server the router gets a bad case of reboot hiccups  and OpenDNS no longer states on their website the "You're using OpenDNS," banner when I visit their site. But that may just be their new site setup. And yes, I have set them as my DNS server on Internet Setup and DNS relay is checked  in Network setup. I use VLC to play media via SharePort no errors yet.  I haven't attempted a file transfer yet to check the speed

-blaquesmith

[KevTech]

I had it reserved also.  When WiConnect24 was on and in standby mode it would authenticate and de-authenticate every few minutes.  When standby mode was turned to just off it no longer would occur.

I don't use Wiiconnect24 as standby mode is not really standby since the processor and WiFi are still turned on.

When the Wii is fully turned on it uses about 17w and in standby (with Wiiconnect24 on) about 10w.
When WiiConnect24 is turned off the Wii only uses about 1w in standby.

[Tsumeone]

Dir-655 A4 Revision handles firmware (beta 1.22b05) fine. But Once I attempt to setup Ntp Server the router gets a bad case of reboot hiccups  and OpenDNS no longer states on their website the "You're using OpenDNS," banner when I visit their site. But that may just be their new site setup. And yes, I have set them as my DNS server on Internet Setup and DNS relay is checked  in Network setup. I use VLC to play media via SharePort no errors yet.  I haven't attempted a file transfer yet to check the speed

-blaquesmith

Same issue with the NTP on H/W A2, I think it's the firmware (I restored to factory defaults before I changed the NTP server and same thing- and FYI, I was trying to use pool.ntp.org as the server.)

First real bug I've seen so far in this new firmware, everything else (for me) seems to be working great.

[EddieZ]

If it is specific ntp servers that cause the issue: don't worry, every time server gives the same time, so you might as well use the standard Dlink ones. I honestly can not think of one reason the use another specific ntp server. Who would like to try? 

[KevTech]

I honestly can not think of one reason the use another specific ntp server. Who would like to try? 

Failure to sync the time is why I use a different NTP server (Microsoft).

[INFO] Tue Mar 03 19:57:02 2009 Time synchronization failed

[INFO] Tue Mar 03 19:56:59 2009 Requesting time from 207.232.83.70

[INFO] Tue Mar 03 19:56:59 2009 Time server ntp1.dlink.com is at IP address 207.232.83.70

[EddieZ]

The Windows timeserver is the one failing me. Dlink works fine. Perhaps a temporary situation, But the router keeps a good pace in its internal clock afaik.

[summerstormpictures]

If it is specific ntp servers that cause the issue: don't worry, every time server gives the same time, so you might as well use the standard Dlink ones. I honestly can not think of one reason the use another specific ntp server. Who would like to try? 

But if it worked before...why not now? Thank God this kind of change didn't affect the manual input on the dynamic DNS updating page where OpenDNS still isn't represented in the drop-down and the information must be input manually.

I'm getting the feeling that this ''tinkering'' toward a new release is simply not a priority. Things that worked are being broken while broken things are fixed. I know this is a beta but this whole process is beginning to seem fall under the ''half-arsed'' category.

With brand new devices from D-Link showing up on the market, it seems to me that's where the bulk of customer care and technical support is going to go now. So it looks like the wait just got longer for the loyal D-Link DIR-655 crowd.

This D-Link firmware update for the 655 seems to be the new MobileMe fiasco. The good news-bad news is that months (is that optimistic?) down the line when everything is finally working properly, many will have bailed for something reliable. You certainly won't get any new love from Mac users over the USB thing either.

I'm as of this post sending a note off to both Tekzilla and GeekBrief noting a general disappointment with their ''rave'' reviews of the DIR-655 as a great alternative to the overpriced Apple Airport line of networking products. I'm sure there is another non-Apple and non-D-Link device out there that one of them will find to rave about.

[Fatman]

Now I know that I am going to regret this, but I am not personally aware of the MobileMe fiasco.  A search for MobileMe or "mobile me" turns up 3 posts where you call it a fiasco, but no meaningful information.

Looking at the posts it turns up I might add that it appears that you are specifically unhappy with your purchase (to the point of giving nearly identical rants with vague references in multiple threads) but keep working with it.  In fact you state that we have failed you for not being Apple enough, but have clearly stated the Apple solution is no better (or even worse).  I would go as far as to say that I am unclear on exactly what you issue is given what I have seen.

So care to let me in on this happening you are so upset about, especially the MobileMe fiasco?

P.S.  The "USB Thing" you reference isn't a Mac love or no Mac Love issue, it is a feature requested by many people.  One that I am going to start just referencing Lycan's and mine old posts explaining why it will never happen and we wish you would quit asking.  It has nothing to do with OS.

P.P.S.  Yes, I wrote this just to be the fourth post on a search for MobileMe

[summerstormpictures]

Now I know that I am going to regret this, but I am not personally aware of the MobileMe fiasco.  A search for MobileMe or "mobile me" turns up 3 posts where you call it a fiasco, but no meaningful information.

Looking at the posts it turns up I might add that it appears that you are specifically unhappy with your purchase (to the point of giving nearly identical rants with vague references in multiple threads) but keep working with it.  In fact you state that we have failed you for not being Apple enough, but have clearly stated the Apple solution is no better (or even worse).  I would go as far as to say that I am unclear on exactly what you issue is given what I have seen.

So care to let me in on this happening you are so upset about, especially the MobileMe fiasco?

P.S.  The "USB Thing" you reference isn't a Mac love or no Mac Love issue, it is a feature requested by many people.  One that I am going to start just referencing Lycan's and mine old posts explaining why it will never happen and we wish you would quit asking.  It has nothing to do with OS.

P.P.S.  Yes, I wrote this just to be the fourth post on a search for MobileMe

I don't doubt I'm occasionally repetitive. I'm sure it'll manifest itself even more in years to come. That unfortunate thing runs in my family.

As for my reference to the MobileMe "fiasco" -- it is the best way I could think to draw a comparison. I know it's a Mac thing and perhaps obscure here. I forgot my "audience." I won't refer to it anymore.

Basically, though, my post was a success in that it drew the attention of a tech--so I'm happy.

Now, surprise us with a new and definitive firmware we can load and forget that runs great--rather than releasing a bunch of betas--unless what you want--to hear back from us about problems.

[Fatman]

I don't doubt I'm occasionally repetitive. I'm sure it'll manifest itself even more in years to come. That unfortunate thing runs in my family.

As for my reference to the MobileMe "fiasco" -- it is the best way I could think to draw a comparison. I know it's a Mac thing and perhaps obscure here. I forgot my "audience." I won't refer to it anymore.

Basically, though, my post was a success in that it drew the attention of a tech--so I'm happy.

Now, surprise us with a new and definitive firmware we can load and forget that runs great--rather than releasing a bunch of betas--unless what you want--to hear back from us about problems.

I had someone here tell me it wasn't a D-Link thing and look it up for me.

Now for that sinking problem where you realize the person whose ear you have, isn't worried about this product and can't effect it in any way.  Best of luck.

[Lycan]

Beta firmware is released to attempt to allow the community access to code so we can effect changes to  the final release that the community requests.

The final release will come. be patient. it will be released when we're confident that it's successful.

People complain that the code we launch is buggy or has problems, so we spend more time testing it to make sure it runs, then people complain that it takes to long to produce. So the happy medium is releasing beta's that the community can use in the interim and provides us with useful feedback.

You are in no way obligated to use this beta, in fact if you're not comfortable with it, we HIGHLY suggest that you do not.

[mazman]

Has Wake on Lan been addressed in this beta?

[Fatman]

The WOL issue is not a bug, it is a proper security measure.  Forwarding unicast traffic to broadcast is bad juju, and there is no other way of ensuring the PC gets the magic packet without it being on and responding to ARP requests.