Print

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

[hmkabaker]

I sent the following info to tech support earlier today, before I found this forum.

Last week I downloaded and installed the firmware update 1.11.  The router was wired to a MacBook Intel Core Duo for the installation, with Airport turned off.

Our iBook duo could no longer connect to the network. All was well before the upgrade.

I find that the 802.11 b/g/n setting causes the router not to respond to b. The iBook cannot be upgraded to g or n.

If I set the router for b only, or b/g only, the iBook gets through just fine.

Other devices on the network, before and after, are the MacBook, two Dell laptops and HP wireless printer D7460. They continued to connect successfully.

Fiddling with DNS, DHCP or other settings won't solve this. Other iBook-DIR 655 owners also  are complaining about this problem on the Apple forum, including someone who just bought the router new.

If this is a known issue, what does dlink recommend? Will there be another firmware upgrade soon?

Thanks.

Harvey

P.S. Here's the iBook forum:
http://discussions.apple.com/forum.jspa?forumID=913

[aljimenez]

Not sure if a problem I encountered in my system is your problem. I replaced an old router with the 655. I have some new devices capable of high speed and wireless G along with some old ones that have wireless B which only can do WEP security. Initially I set my network with mix N, G, and B. But somewhere I read and found out that WEP is not compatible with a mix of N, G, and B. I had to set the wireless to G and B to get WEP to work...  Al

[hmkabaker]

Security mode is disabled. Wi-Fi Protected Setup is Enabled/Configured, FWIW.

[hmkabaker]

dlink tech support responded, saying this is a known issue. They are working on a solution. As of now, they have no solution.

When  running n/g/b, the router is swamped by n, so b cannot get through.

HK

[Lycan]

We are aware of this, it has to do with the way the 1.11 handles the signal after the firmware upgrade.
We are looking for a workaround.

[hmkabaker]

Hi,
Anything new on this issue?


Thanks.

Harvey