Go to the Advanced panel, and select the Performance tab. Where it says
Preamble Type, select Long Preamble (the default is Short Preamble).
Without doing that, the DI-514 will not work with Airport.
Hope this saves someone some time.
Interesting. Regular Airport, not extreme. D-Link never got close to
figuring this out. Most of my time was spent on hold, then whenever a
tech would get on the line they'd put me on hold and the line would
disconnect. Very frustrating tech support.
> In article <cczona-A1F292....@netnews.attbi.com>,
> CC Zona <ccz...@nospam.invalid> wrote:
> > In article <BLOCKSPAMfishfry-46...@netnews.attbi.com>,
> > fishfry <BLOCKSPA...@your-mailbox.com> wrote:
> > > If anyone buys a D-Link DI-514 802.11b router ($49 at Amazon before a
> > > $20 rebate!) and intends to use it with an Airport card, here's a tip
> > > that will save you several frustrating hours on the phone with D-Link's
> > > highly unhelpful tech support. I actually found this solution by
> > > searching the Web while I was on hold.
> > >
> > > Go to the Advanced panel, and select the Performance tab. Where it says
> > > Preamble Type, select Long Preamble (the default is Short Preamble).
> > >
> > > Without doing that, the DI-514 will not work with Airport.
> > Odd. Mine is set to short preamble, and has been working fine for some
> > time. Did D-Link suggest any reason for it not working with yours?
> Interesting. Regular Airport, not extreme.
Me too. But it turns out I've got the DI-614+, not the 514. So maybe it's
normal for these two models to handle Airport differently.
> D-Link never got close to
> figuring this out. Most of my time was spent on hold, then whenever a
> tech would get on the line they'd put me on hold and the line would
> disconnect. Very frustrating tech support.
Yikes, that is bad news. Their inline help and online docs also were not
terribly helpful when I ran into problems.
Yep, no problem with a 614+ Amazon accidentally sent me vs. the 514 I
finally received today that required the Preamable to be "long". This
with an iBook g3/900 in OS 9.22, FWIW.
>On another subject, I have Cox cable modem and an AOL account. The AOL
>for OS X won't sign-on correctly using a BYOA (bring-your-own-access)
>over a cable modem connected to the WAN port of the DI-514. I have a
>wired D-Link DI-704 which works perfectly, so I changed the default IP
>addresses so that the two routers didn't share the same default, and
>disabled the DHCP server in the DI-514, and connected it LAN
>port-to-LAN port with the 704, and now I can sign-on to AOL for OS X
>also, both wirelessly and wired. Kris Tilford
I have DSL from BellSouth and AOL. I also have a D-Link DI-614+ (not a
514 like yours) and cannot connect to AOL for OS X through the AirPort
card in my iBook.
I had no problems connecting through OS 9. I also have no problem
connecting with AOL 5.0 when running Classic in OS X. But the OS
X-native client won't connect at home. If I take my iBook to work and
plug into the T1 network, it's no problem at all to connect.
If I follow what you did correctly... You have your cable modem
connected to your wired router, therefore allowing the wired router to
be your DHCP server. You then connected your wireless router to the
wired router as a LAN device, disabled the server in the wireless
router, and let the wired router assign it an IP address. Then you
were able to sign on to AOL under the OS X native client.
Is that the only solution to getting AOL for X to connect when using
an AirPort card and a third-party wireless router?
H.B. Elkins -- Beattyville, KY
"There's no doubt he's the best race driver in the world."
--Dale Jarrett, on the late Dale Earnhardt
Go Big Blue (Kentucky Wildcats)! Go #15 (Michael Waltrip, NAPA Chevy)!
To reply, just remove the restrictorplates...
So I write down "DI-514 and Toshiba Tablet" here as the key words and
hopefully it can help somebody elso who are trying to pull their hair
in front of the problem we had. This will also help those who tried
to help us but didn't succeed during the course, including the techs
within Toshiba who apparently did't know the solution and suggested us
to ship the unit back to the factory for diagnosis.