macbookpro/aiport problems

G'day

Still using airport snow base station (the dual ethernet version),
connected via cable modem to Timewarner cable, connected via ethernet
and administered by an iMac running tiger 10.4.11. My Powerbook G4
(still using panther) connects to the internet via wifi through the
airport flawlessly. My macbook pro running tiger 10.4.11 does not.

The macbook pro sees my base station, and can connect to it - I get four
bars of signal and in the Internet Connect window the status is
"connected to the Shear Network". All well and good.

It self-assigns an IP address and is not connected to the internet (and
yes I've tried pressing the renew dhcp lease button). most of the time.
Sometimes (maybe every couple of hours) it will decide to connect (I
know because new messages have appeared in my mailbox), however the
connection is transient (sometimes it loses the connection while in the
middle of downloading a large mail attachment and is unable to finish
it).

I've tried rebooting the cable modem and the base station. Right now I'm
online by bypassing the base station and directly connecting to the
cable modem, so I know my computer can get on the internet via the cable
modem. Just not through the wireless network.

Is my best option to go buy an airport express or is there something I'm
not thinking of?

Thanks

DrRuth

In article <DrRuth-(E-Mail Removed)>,
Ruth Shear <(E-Mail Removed)> wrote:

> G'day
>
> Still using airport snow base station (the dual ethernet version),
> connected via cable modem to Timewarner cable, connected via ethernet
> and administered by an iMac running tiger 10.4.11. My Powerbook G4
> (still using panther) connects to the internet via wifi through the
> airport flawlessly. My macbook pro running tiger 10.4.11 does not.
>
> The macbook pro sees my base station, and can connect to it - I get four
> bars of signal and in the Internet Connect window the status is
> "connected to the Shear Network". All well and good.
>
> It self-assigns an IP address and is not connected to the internet (and
> yes I've tried pressing the renew dhcp lease button). most of the time.
> Sometimes (maybe every couple of hours) it will decide to connect (I
> know because new messages have appeared in my mailbox), however the
> connection is transient (sometimes it loses the connection while in the
> middle of downloading a large mail attachment and is unable to finish
> it).
>
> I've tried rebooting the cable modem and the base station. Right now I'm
> online by bypassing the base station and directly connecting to the
> cable modem, so I know my computer can get on the internet via the cable
> modem. Just not through the wireless network.
>
> Is my best option to go buy an airport express or is there something I'm
> not thinking of?
>
> Thanks
>
> DrRuth

Try specifying your own DNS servers. At least as an experiment,
try the OpenDNS.org DNS servers:

208.67.222.222
208.67.220.220

System Preferences -> Network -> TCP/IP

Bob Harris

"Ruth Shear" <(E-Mail Removed)> wrote in message
newsrRuth-(E-Mail Removed)...
> G'day
>
> Still using airport snow base station (the dual ethernet version),
> connected via cable modem to Timewarner cable, connected via ethernet
> and administered by an iMac running tiger 10.4.11. My Powerbook G4
> (still using panther) connects to the internet via wifi through the
> airport flawlessly. My macbook pro running tiger 10.4.11 does not.
>
> The macbook pro sees my base station, and can connect to it - I get four
> bars of signal and in the Internet Connect window the status is
> "connected to the Shear Network". All well and good.
>
> It self-assigns an IP address and is not connected to the internet (and
> yes I've tried pressing the renew dhcp lease button). most of the time.
> Sometimes (maybe every couple of hours) it will decide to connect (I
> know because new messages have appeared in my mailbox), however the
> connection is transient (sometimes it loses the connection while in the
> middle of downloading a large mail attachment and is unable to finish
> it).
>
> I've tried rebooting the cable modem and the base station. Right now I'm
> online by bypassing the base station and directly connecting to the
> cable modem, so I know my computer can get on the internet via the cable
> modem. Just not through the wireless network.
>
> Is my best option to go buy an airport express or is there something I'm
> not thinking of?

It sounds very like the problem I was having (see thread "Airport Dropping
Connection") with my new MacBook.

You are using an Airport snow base station. I don't know how old that
equipment might be. I have been using a Draytek Vigor modem and every
wireless computer in my house connects to it instantaneously except for the
MacBook (in fact, even changing the way the WEP key was entered, doesn't
seem to have been a long-term solution). Eventually I bought an Airport
Express, connected it with an ethernet cable to my Draytek DSL modem and
then established a connection between the MacBook and the Airport Express -
this seems to produce an instant-on wireless connection and is an acceptable
workaround for me.

I wonder if eventually Apple will issue a firmware or software upgrade for
the MacBook's Airport.

G'day

Jolly Roger <(E-Mail Removed)> wrote:

> 1. Is the Airport set to use WEP or WPA encryption?

WEP. WPA doesn't seem to be an option, probably because the base station
is too old.

> 2. If you are using WEP, are you specifying the WEP key on the MacBook
> Pro as a dollar sign prefixed hexadecimal string (something like
> $56f3e4dd924e6c29)?

So I'd seen you ask this in some other thread too, so I went out to try
and edumacate myself and read a bunch on the web and apple support. It
sounds like if you choose a 13 character plain text password, that stops
the hashing or whatever it's called, that sometimes results in problems.
I switched my base station to WEP 128 bit/ASCII and specified a 13
character ascii password. My powerbook G4 was able to connect no
problems. My macbook pro did connect to the wireless network as before
but is still unable to see the bigbad internet outside.

I did not try a hex string yet. I didn't see anything out there telling
me how to choose the hex password. Can you just pick any string (as long
as you limit yourself to A-F, and numbers and put an $ in the front)? I
will try that next. Thanks for your help.

Ruth

G'day

> > My macbook pro did connect to the wireless network as before
> > but is still unable to see the bigbad internet outside.
>
> Usually this is an indication that:
>
> The password was not supplied correctly when connecting.
>
> -OR-
>
> The router is configured to use MAC address filtering, and you have not
> added the MacBook Pro's MAC address to the router's MAC address filter
> table.

There is nothing specified in the Access control window, so I'm
presuming I'm not configured to use MAC address filtering.

So it really is the password - thanks for that clarity.

> If you set the Airport base station to use a WEP 128-bit hexadecimal
> key, you type in your password, and the Airport base station will
> generate a hexadecimal key.
>
> Then you prefix $ to that hexadecimal string when you connect to the
> router from your laptop(s).

When using either my macbook pro or my powerbook G4 to join a new
airport network, the password drop down menu gives me many options,
including WEP 128 bit hex (or ASCII which is what I'm currently using).
However, my airport base station admin utility only gives password
options of WEP 128 bit. It doesn't allow me to specify ASCII or HEX.
Does it automagically convert the ASCII to hex when I specify WEP 128
bit? And if so, how do I see the hexadecimal key that the base station
has generated based on the ASCII password I've specified?

Thanks for your help. I really appreciate it.

Ruth

Ruth Shear <(E-Mail Removed)> wrote:

> Jolly Roger <(E-Mail Removed)> wrote:
> > If you set the Airport base station to use a WEP 128-bit hexadecimal
> > key, you type in your password, and the Airport base station will
> > generate a hexadecimal key.
> >
> > Then you prefix $ to that hexadecimal string when you connect to the
> > router from your laptop(s).
>
> When using either my macbook pro or my powerbook G4 to join a new
> airport network, the password drop down menu gives me many options,
> including WEP 128 bit hex (or ASCII which is what I'm currently using).
> However, my airport base station admin utility only gives password
> options of WEP 128 bit. It doesn't allow me to specify ASCII or HEX.
> Does it automagically convert the ASCII to hex when I specify WEP 128
> bit?

For WEP there is always an underlying hex password, which is generated
from an ASCII password using a manufacturer-specific algorithm. (This is
why Apple base stations and computers can talk to each other using an
ASCII password, but you have to use hex passwords with third party base
stations.)

There is a possibility that Intel and PowerPC Macs use different WEP
ASCII/hex conversion algorithms, which might explain the problem you are
observing.

> And if so, how do I see the hexadecimal key that the base station
> has generated based on the ASCII password I've specified?

In both Airport Admin Utility and Airport Utility, there is an
"Equvalent Network Password" command in the Base Station menu which
displays the hex password.

--
David Empson
(E-Mail Removed)

"David Empson" <(E-Mail Removed)> wrote in message
news:1iltjn3.dt035z17r2ua9N%(E-Mail Removed). ..
> Ruth Shear <(E-Mail Removed)> wrote:
>
>> Jolly Roger <(E-Mail Removed)> wrote:
>> > If you set the Airport base station to use a WEP 128-bit hexadecimal
>> > key, you type in your password, and the Airport base station will
>> > generate a hexadecimal key.
>> >
>> > Then you prefix $ to that hexadecimal string when you connect to the
>> > router from your laptop(s).
>>
>> When using either my macbook pro or my powerbook G4 to join a new
>> airport network, the password drop down menu gives me many options,
>> including WEP 128 bit hex (or ASCII which is what I'm currently using).
>> However, my airport base station admin utility only gives password
>> options of WEP 128 bit. It doesn't allow me to specify ASCII or HEX.
>> Does it automagically convert the ASCII to hex when I specify WEP 128
>> bit?
>
> For WEP there is always an underlying hex password, which is generated
> from an ASCII password using a manufacturer-specific algorithm. (This is
> why Apple base stations and computers can talk to each other using an
> ASCII password, but you have to use hex passwords with third party base
> stations.)
>
> There is a possibility that Intel and PowerPC Macs use different WEP
> ASCII/hex conversion algorithms, which might explain the problem you are
> observing.
>
>> And if so, how do I see the hexadecimal key that the base station
>> has generated based on the ASCII password I've specified?
>
> In both Airport Admin Utility and Airport Utility, there is an
> "Equvalent Network Password" command in the Base Station menu which
> displays the hex password.
>

However, if the problem was related to the password, in theory the problem
should disappear if you remove wireless security from your configuration
and turn it into an open wireless network.

However the problem didn't disappear for me and nor (I would guess) will it
disappear for Ruth.

My hypothesis is that the problem is with the 802.11b, 802.11g and now the
draft "n" specification. I think the MacBook tries for some time to
negotiate a connection on the "n" specification and eventually drops down to
a "b" connection. How could that be proved, though?

"Jolly Roger" <(E-Mail Removed)> wrote in message
news:jollyroger-(E-Mail Removed)...
> In article <(E-Mail Removed)>,
> "The Todal" <(E-Mail Removed)> wrote:
>
>> However the problem didn't disappear for me and nor (I would guess) will
>> it
>> disappear for Ruth.
>
> Really? The last we heard, the problem had been fixed. You never
> followed up to that thread; so we have no details about how it
> reappeared.
>

You have all the details you need, matey.

Thanks for all your help, though. Absolutely invaluable. Now STFU before
you lead some other poor soul astray.

"Jolly Roger" <(E-Mail Removed)> wrote in message
news:jollyroger-(E-Mail Removed)...
> In article <jollyroger-(E-Mail Removed)>,
> Jolly Roger <(E-Mail Removed)> wrote:
>
>> In article <(E-Mail Removed)>,
>> "The Todal" <(E-Mail Removed)> wrote:
>>
>> > "Jolly Roger" <(E-Mail Removed)> wrote in message
>> > news:jollyroger-(E-Mail Removed)...
>> > > In article <(E-Mail Removed)>,
>> > > "The Todal" <(E-Mail Removed)> wrote:
>> > >
>> > >> However the problem didn't disappear for me and nor (I would guess)
>> > >> will
>> > >> it disappear for Ruth.
>> > >
>> > > Really? The last we heard, the problem had been fixed. You never
>> > > followed up to that thread; so we have no details about how it
>> > > reappeared.
>> >
>> > You have all the details you need, matey.
>> >
>> > Thanks for all your help, though. Absolutely invaluable. Now STFU
>> > before
>> > you lead some other poor soul astray.
>>
>> 1. I'm not your "matey", pal.
>> 2. How about you make me shut up, *****.
>> 3. I'm waiting.
>
> ...And just for everyone else's benefit, the last we heard from "The
> Todal" was this response to my suggestion that he use a dollar
> sign-prefixed hexadecimal equivalent WEP key generated by the Airport
> base station on his MacBook to solve his connection problem (which
> happens to be very similar in symptoms to Ruth's, BTW):
>
> In article <(E-Mail Removed)>,
> "The Todal" <(E-Mail Removed)> wrote:
>
>> Look, smartass....no, I withdraw that, because your implausible solution
>> to
>> my problem has actually worked and I can't understand why. For years I
>> prefixed the WEP key with 0x (I don't remember now where I got that
>> instruction from) but when I substitute the dollar sign, I get an instant
>> connection and I am now very satisfied. Let me know where I should mail
>> the
>> check...
>>
>> Thanks for taking the time to help and may you forever be jolly.
>
> Now, all of a sudden, ou of the blue, in another thread altogether, "The
> Todal" says it's not working anymore, while simultaneously refusing to
> give any further details.
>
> So just who is being unreasonable here? Reader beware. ; )

1. I'm afraid your solution actually worked for less than a day.
2. No, I don't know why. I really wish your solution had been better than
fool's gold, but fool's gold it certainly was.
3. It's not your fault. However, do try to employ logic when addressing a
technical problem. If the root cause was incorrect entering of a WEP key,
the problem should disappear if you remove all wireless security, shouldn't
it? Well, shouldn't it? Are you paying attention there? Knock, knock?
4. May you forever be jolly.

In article <(E-Mail Removed)>,
"The Todal" <(E-Mail Removed)> wrote:

> > Now, all of a sudden, ou of the blue, in another thread altogether, "The
> > Todal" says it's not working anymore, while simultaneously refusing to
> > give any further details.
> >
> > So just who is being unreasonable here? Reader beware. ; )
>
> 1. I'm afraid your solution actually worked for less than a day.
> 2. No, I don't know why. I really wish your solution had been better than
> fool's gold, but fool's gold it certainly was.

Except it's the right answer, as evidenced by the fact that it worked.
The fact that it stopped working is a new problem. Something changed or
(as a special case of "changed") was reset.

> 3. It's not your fault. However, do try to employ logic when addressing a
> technical problem. If the root cause was incorrect entering of a WEP key,
> the problem should disappear if you remove all wireless security, shouldn't
> it? Well, shouldn't it?

Of course it should. The most likely explanation is that you have not,
in fact, turned off security for the network you're trying to access.

--
"Harry?" Ron's voice was a mere whisper. "Do you smell something ... burning?"
- Harry Potter and the Odor of the Phoenix