DLink DI-614+, WEP, and Portege 3505

I've had a Dlink router for a while and have used it without a problem
with WEP enabled and a Dlink wireless card on an old laptop.

I just bought a Toshiba Portege 3505. Unfortunately I can only access
the router with WEP disabled. With WEP enabled, I can't get an IP
address. I've tried fiddling with Open vs. Shared Authentication, 64
vs. 128-bit encryption, and I've turned off "4x" mode on the router.
No luck.

With Open Authentication enabled, the Portege says I'm connected with
a good signal, but I get no IP address; it's as if I've entered the
wrong encryption code. With Shared Authentication enabled, I can't
connect at all.

"Zack Gleit" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> I've had a Dlink router for a while and have used it without a problem
> with WEP enabled and a Dlink wireless card on an old laptop.
>
> I just bought a Toshiba Portege 3505. Unfortunately I can only access
> the router with WEP disabled. With WEP enabled, I can't get an IP
> address. I've tried fiddling with Open vs. Shared Authentication, 64
> vs. 128-bit encryption, and I've turned off "4x" mode on the router.
> No luck.
>
> With Open Authentication enabled, the Portege says I'm connected with
> a good signal, but I get no IP address; it's as if I've entered the
> wrong encryption code. With Shared Authentication enabled, I can't
> connect at all.

Set your 3505's LAN to the following settings:

IP=192.168.0.65
Subnet=255.255.255.0
Gateway=192.168.0.1 (assuming your router is set to default)

DNS=4.2.2.2
DNS=4.2.2.3

Reboot and you should be happy.

Rita

Rita A. Berkowitz <(E-Mail Removed)> writes:

> DNS=4.2.2.2
> DNS=4.2.2.3

You're mighty generous with someone else's name resolvers, eh?

> Reboot and you should be happy.

Yea but how do you think BBN/GTE/ETC will like it?

I'd post the correct ones (from www.help.rr.com) except I don't
feel like letting Time Warner write cookies on my machine.

Billy Y..

<(E-Mail Removed)> wrote in message news:bnefrk$980$(E-Mail Removed)...
> Rita A. Berkowitz <(E-Mail Removed)> writes:
>
> > DNS=4.2.2.2
> > DNS=4.2.2.3
>
> You're mighty generous with someone else's name resolvers, eh?
>

Talk to D-Link's support team about it, not me. These are the settings that
are recommended both over the phone and on their website.

Rita

Rita A. Berkowitz <(E-Mail Removed)> writes:

> > > DNS=4.2.2.2
> > > DNS=4.2.2.3

> Talk to D-Link's support team about it, not me. These are the settings that
> are recommended both over the phone and on their website.

Actually I'd rather talk with BBN about it - can you provide a URL
for this? I did look and I did see one screenshot with 4.2.2.2 as
the secondary resolver, but that's all I could find.

Billy Y..

It really sounds like the WEP key is wrong. Have you tried just re-entering
the key on both the router and the laptop? Also, be sure that both are set
to the same keylength - if the router is set for 128 and the laptop for 64,
it won't work. The only difference between Open and Shared Key
authentication is that you have to have WEP working correctly to complete
association with Shared Key. So your symptoms strongly suggest that WEP is
the problem. You are right to leave off 4x mode, since that's proprietary,
and even if a client card claims to support it there's no guarantee it's
implemented the same way.

As for the gateway setting mentioned elsewhere, My D-link router sets its
own IP address for gateway. I assume it just gets the ISP's gateway when it
connects on the WAN, and passes through DNS queries directed to its own
address. Or maybe it runs a local DNS server in caching mode, dunno. But you
shouldn't have to know about any servers outside your ISP's network.

"Zack Gleit" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> I've had a Dlink router for a while and have used it without a problem
> with WEP enabled and a Dlink wireless card on an old laptop.
>
> I just bought a Toshiba Portege 3505. Unfortunately I can only access
> the router with WEP disabled. With WEP enabled, I can't get an IP
> address. I've tried fiddling with Open vs. Shared Authentication, 64
> vs. 128-bit encryption, and I've turned off "4x" mode on the router.
> No luck.
>
> With Open Authentication enabled, the Portege says I'm connected with
> a good signal, but I get no IP address; it's as if I've entered the
> wrong encryption code. With Shared Authentication enabled, I can't
> connect at all.

Thanks for the input.

Oddly enough, I fixed the problem inadvertently by making sure that
the DI-614+ was set to use the first (of four) encryption keys and
that the client (Portege) was also set to use the first. I don't
understand why this made a difference: I always thought the four
choices were just for convenient switching of keys, and that as long
as the correct key (i.e., the correct password, not whether it was
first, second, third, or fourth) was active, everything would work.
I'm pretty sure I didn't make any other changes to explain my sudden
success.

In any event, everything still works even with 4x enabled and max
speed set to 22mbps on the router, even though Dlink says these
settings should be changed.

Very weird, I think. Thanks again for the help.

(Also, setting the LAN or DNS settings wasn't necessary: I couldn't
even actually connect to get an IP address, and everything now works
fine without changing these settings.)

(E-Mail Removed) wrote in message news:<bnep6t$cfa$(E-Mail Removed)>...
> Rita A. Berkowitz <(E-Mail Removed)> writes:
>
> > > > DNS=4.2.2.2
> > > > DNS=4.2.2.3
>
> > Talk to D-Link's support team about it, not me. These are the settings that
> > are recommended both over the phone and on their website.
>
> Actually I'd rather talk with BBN about it - can you provide a URL
> for this? I did look and I did see one screenshot with 4.2.2.2 as
> the secondary resolver, but that's all I could find.
>
> Billy Y..

The keylists on router and client must not have been identical. For what
it's worth, I don't think D-link routers progress automatically through the
list. I think they transmit using the key marked default, and they decrypt
assuming the client is using some key from an identical list (key index is
transmitted in the clear in every packet). In any case, if both have
identical lists it doesn't matter if the keylist progresses or not, it
should work perfectly.

"Zack Gleit" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> Thanks for the input.
>
> Oddly enough, I fixed the problem inadvertently by making sure that
> the DI-614+ was set to use the first (of four) encryption keys and
> that the client (Portege) was also set to use the first. I don't
> understand why this made a difference: I always thought the four
> choices were just for convenient switching of keys, and that as long
> as the correct key (i.e., the correct password, not whether it was
> first, second, third, or fourth) was active, everything would work.
> I'm pretty sure I didn't make any other changes to explain my sudden
> success.
>
> In any event, everything still works even with 4x enabled and max
> speed set to 22mbps on the router, even though Dlink says these
> settings should be changed.
>
> Very weird, I think. Thanks again for the help.
>
> (Also, setting the LAN or DNS settings wasn't necessary: I couldn't
> even actually connect to get an IP address, and everything now works
> fine without changing these settings.)
>
> (E-Mail Removed) wrote in message news:<bnep6t$cfa$(E-Mail Removed)>...
> > Rita A. Berkowitz <(E-Mail Removed)> writes:
> >
> > > > > DNS=4.2.2.2
> > > > > DNS=4.2.2.3
> >
> > > Talk to D-Link's support team about it, not me. These are the
settings that
> > > are recommended both over the phone and on their website.
> >
> > Actually I'd rather talk with BBN about it - can you provide a URL
> > for this? I did look and I did see one screenshot with 4.2.2.2 as
> > the secondary resolver, but that's all I could find.
> >
> > Billy Y..

Thanks. My understanding was that only the key marked active was the
key used to encrypt/decrypt, and that the index was irrelevant (just
used to keep track of multiple keys one could easily switch between).
So, in my case, the "active" key on the router was the second one,
whereas I was using the first key on the client. (Of course, I had
the same keyword set on the second router key and the first client
key.)

Are you saying that all keys are used for encryption/decryption? I
know that can't be the case, since I still only have one key set on
the client, whereas two are set on the router. Alternatively, I guess
it must be the case that both keyword and key index must be the same
for WEP to work.

Gee, it seems like this aspect of WEP is not explained very well
anywhere, or perhaps I just missed it.

"gary" <(E-Mail Removed)> wrote in message news:<Pe1nb.561$(E-Mail Removed) >...
> The keylists on router and client must not have been identical. For what
> it's worth, I don't think D-link routers progress automatically through the
> list. I think they transmit using the key marked default, and they decrypt
> assuming the client is using some key from an identical list (key index is
> transmitted in the clear in every packet). In any case, if both have
> identical lists it doesn't matter if the keylist progresses or not, it
> should work perfectly.
>
> "Zack Gleit" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) om...
> > Thanks for the input.
> >
> > Oddly enough, I fixed the problem inadvertently by making sure that
> > the DI-614+ was set to use the first (of four) encryption keys and
> > that the client (Portege) was also set to use the first. I don't
> > understand why this made a difference: I always thought the four
> > choices were just for convenient switching of keys, and that as long
> > as the correct key (i.e., the correct password, not whether it was
> > first, second, third, or fourth) was active, everything would work.
> > I'm pretty sure I didn't make any other changes to explain my sudden
> > success.
> >
> > In any event, everything still works even with 4x enabled and max
> > speed set to 22mbps on the router, even though Dlink says these
> > settings should be changed.
> >
> > Very weird, I think. Thanks again for the help.
> >
> > (Also, setting the LAN or DNS settings wasn't necessary: I couldn't
> > even actually connect to get an IP address, and everything now works
> > fine without changing these settings.)
> >
> > (E-Mail Removed) wrote in message news:<bnep6t$cfa$(E-Mail Removed)>...
> > > Rita A. Berkowitz <(E-Mail Removed)> writes:
> > >
> > > > > > DNS=4.2.2.2
> > > > > > DNS=4.2.2.3
>
> > > > Talk to D-Link's support team about it, not me. These are the
> settings that
> > > > are recommended both over the phone and on their website.
> > >
> > > Actually I'd rather talk with BBN about it - can you provide a URL
> > > for this? I did look and I did see one screenshot with 4.2.2.2 as
> > > the secondary resolver, but that's all I could find.
> > >
> > > Billy Y..