Airport dropping connection

"Jolly Roger" <jollyroger DeleteThis @pobox.com> wrote in message
news:jollyroger-99C267.19110103082008@news.individual.net...
> In article <6fmus6Fcf9hsU1 DeleteThis @mid.individual.net>,
> "The Todal" <deadmailbox DeleteThis @beeb.net> wrote:
>
>> New MacBook, and the Airport claims to be connected to the wireless
>> network
>> but nothing actually connects to the internet - no web pages, no Software
>> Update. And the wireless network is fine because other computers are
>> having
>> no difficulty getting web pages.
>>
>> Is this a problem that others have had (maybe an incompatibility between
>> AirPort and the wireless signal emitted by the router?) or am I unique?
>>
>> Every so often I think I've solved it. I change the wireless channel on
>> the
>> router and things work fine until I restart the Mac. My latest attempt to
>> solve it was to repair the permissions on the Mac disk. The web pages are
>> now there, and everything is as fast and as reliable as I could possibly
>> wish... but for how long, I wonder.
>
> This sounds more like an authentication issue or something similar. For
> instance, if your router does MAC (Media Access Control) address
> filtering, and the MAC address of the computer from which you connect is
> not allowed, the computer will *appear* to be connected, but the router
> will not give it a valid IP address.
>
> WHen you experience this problem again, go into System Preferences >
> Network, and take a look at the IP address of the Airport interface. If
> the address is a self-assigned IP address, then the router is refusing
> to give you an IP address, and that's why you can't talk to the network.

I've disabled MAC filtering and have adjusted the TCP/IP settings so that it
gets its address from the router. Is there any way of adjusting the Airport
hardware settings (power output, roaming aggressiveness)?

In article <6fn4ciFcego7U1.DeleteThis@mid.individual.net>,
"The Todal" <deadmailbox.DeleteThis@beeb.net> wrote:

> "Jolly Roger" <jollyroger.DeleteThis@pobox.com> wrote in message
> news:jollyroger-99C267.19110103082008@news.individual.net...
> > In article <6fmus6Fcf9hsU1.DeleteThis@mid.individual.net>,
> > "The Todal" <deadmailbox.DeleteThis@beeb.net> wrote:
> >
> >> New MacBook, and the Airport claims to be connected to the wireless
> >> network
> >> but nothing actually connects to the internet - no web pages, no Software
> >> Update. And the wireless network is fine because other computers are
> >> having
> >> no difficulty getting web pages.
> >>
> >> Is this a problem that others have had (maybe an incompatibility between
> >> AirPort and the wireless signal emitted by the router?) or am I unique?
> >>
> >> Every so often I think I've solved it. I change the wireless channel on
> >> the
> >> router and things work fine until I restart the Mac. My latest attempt to
> >> solve it was to repair the permissions on the Mac disk. The web pages are
> >> now there, and everything is as fast and as reliable as I could possibly
> >> wish... but for how long, I wonder.
> >
> > This sounds more like an authentication issue or something similar. For
> > instance, if your router does MAC (Media Access Control) address
> > filtering, and the MAC address of the computer from which you connect is
> > not allowed, the computer will *appear* to be connected, but the router
> > will not give it a valid IP address.
> >
> > WHen you experience this problem again, go into System Preferences >
> > Network, and take a look at the IP address of the Airport interface. If
> > the address is a self-assigned IP address, then the router is refusing
> > to give you an IP address, and that's why you can't talk to the network.
>
> I've disabled MAC filtering and have adjusted the TCP/IP settings so that it
> gets its address from the router.

So that was the problem?

> Is there any way of adjusting the Airport
> hardware settings (power output, roaming aggressiveness)?

I haven't ever needed to, so I'm not sure. Maybe someone else can
answer this. I assume you've already searched Google for it?

--
Send responses to the relevant news group. E-mail sent to this address
may be devoured by my ravenous SPAM filter. Due to Google's refusal to
prevent spammers from posting messages, I often ignore posts from
Google. Use a real news client if you want me to see your posts.

JR

"Jolly Roger" <jollyroger.RemoveThis@pobox.com> wrote in message
news:jollyroger-2E8A69.20472203082008@news.individual.net...
> In article <6fn4ciFcego7U1.RemoveThis@mid.individual.net>,
> "The Todal" <deadmailbox.RemoveThis@beeb.net> wrote:
>
>> "Jolly Roger" <jollyroger.RemoveThis@pobox.com> wrote in message
>> news:jollyroger-99C267.19110103082008@news.individual.net...
>> > In article <6fmus6Fcf9hsU1.RemoveThis@mid.individual.net>,
>> > "The Todal" <deadmailbox.RemoveThis@beeb.net> wrote:
>> >
>> >> New MacBook, and the Airport claims to be connected to the wireless
>> >> network
>> >> but nothing actually connects to the internet - no web pages, no
>> >> Software
>> >> Update. And the wireless network is fine because other computers are
>> >> having
>> >> no difficulty getting web pages.
>> >>
>> >> Is this a problem that others have had (maybe an incompatibility
>> >> between
>> >> AirPort and the wireless signal emitted by the router?) or am I
>> >> unique?
>> >>
>> >> Every so often I think I've solved it. I change the wireless channel
>> >> on
>> >> the
>> >> router and things work fine until I restart the Mac. My latest attempt
>> >> to
>> >> solve it was to repair the permissions on the Mac disk. The web pages
>> >> are
>> >> now there, and everything is as fast and as reliable as I could
>> >> possibly
>> >> wish... but for how long, I wonder.
>> >
>> > This sounds more like an authentication issue or something similar. For
>> > instance, if your router does MAC (Media Access Control) address
>> > filtering, and the MAC address of the computer from which you connect
>> > is
>> > not allowed, the computer will *appear* to be connected, but the router
>> > will not give it a valid IP address.
>> >
>> > WHen you experience this problem again, go into System Preferences >
>> > Network, and take a look at the IP address of the Airport interface. If
>> > the address is a self-assigned IP address, then the router is refusing
>> > to give you an IP address, and that's why you can't talk to the
>> > network.
>>
>> I've disabled MAC filtering and have adjusted the TCP/IP settings so that
>> it
>> gets its address from the router.
>
> So that was the problem?

No, it was something I did at the very outset.

The position remains that it seems to connect immediately to the wireless
network but no web pages come up and no mail can be retrieved, until five or
ten minutes later when it suddenly starts working properly. Changing the
channel of the router seems to speed things up, but that means using a
different machine to go into the settings and change the channel. Very odd.
I just wondered if others had experienced the same problem - google suggests
that there was a time when many people were complaining about their Macbook
"dropping" the connection which is a slightly different thing.

In article <6fo22oFc9g43U1.DeleteThis@mid.individual.net>,
"The Todal" <deadmailbox.DeleteThis@beeb.net> wrote:

> "Jolly Roger" <jollyroger.DeleteThis@pobox.com> wrote in message
> news:jollyroger-2E8A69.20472203082008@news.individual.net...
> > In article <6fn4ciFcego7U1.DeleteThis@mid.individual.net>,
> > "The Todal" <deadmailbox.DeleteThis@beeb.net> wrote:
> >
> >> "Jolly Roger" <jollyroger.DeleteThis@pobox.com> wrote in message
> >> news:jollyroger-99C267.19110103082008@news.individual.net...
> >> >
> >> > This sounds more like an authentication issue or something similar. For
> >> > instance, if your router does MAC (Media Access Control) address
> >> > filtering, and the MAC address of the computer from which you connect
> >> > is not allowed, the computer will *appear* to be connected, but the router
> >> > will not give it a valid IP address.
> >> >
> >> > WHen you experience this problem again, go into System Preferences >
> >> > Network, and take a look at the IP address of the Airport interface. If
> >> > the address is a self-assigned IP address, then the router is refusing
> >> > to give you an IP address, and that's why you can't talk to the
> >> > network.
> >>
> >> I've disabled MAC filtering and have adjusted the TCP/IP settings so that
> >> it gets its address from the router.
> >
> > So that was the problem?
>
> No, it was something I did at the very outset.

Why would you diable MAC filtering if you haven't determined it's the
problem?

Only now are we learning that you apparently had the MacBook configured
to use a manual IP address - is that correct? And now it sounds like
you've got it set to use DHCP - correct?

Is it getting a valid IP address, or a self-assigned IP address?

What sort of authentication is the Airport set to use?

Have you examined the Airport password(s) stored in your MacBook
keychain to ensure they are all correct?

Any details you can supply will help us help you. Without details about
your setup, helping you is kind of like playing a guessing game.

> The position remains that it seems to connect immediately to the wireless
> network but no web pages come up and no mail can be retrieved, until five or
> ten minutes later when it suddenly starts working properly.

Without knowing whether or not you have a valid IP address during those
five to ten minutes, it's hard to proceed. I don't know how else to ask
this question. All you have to do is look and report the IP here.

It's also hard to help you without knowing how you have the MacBook
System Preferences > Network > Airport interface configured.

> Changing the
> channel of the router seems to speed things up, but that means using a
> different machine to go into the settings and change the channel. Very odd.

I doubt that has much to do with why you can't connect net resources
during the first five to ten minutes.

Does the signal strength reported on your MacBook indicate a weak signal
during the first five to ten minutes, or until you change the channel?

> I just wondered if others had experienced the same problem - google suggests
> that there was a time when many people were complaining about their Macbook
> "dropping" the connection which is a slightly different thing.

It's hard to know exactly what the problem you are experiencing is
without more details.

--
Send responses to the relevant news group rather than to me, as
E-mail sent to this address may be devoured by my very hungry SPAM
filter. Due to Google's refusal to prevent spammers from posting
messages through their servers, I often ignore posts from Google
Groups. Use a real news client if you want me to see your posts.

JR

"Jolly Roger" <jollyroger.DeleteThis@pobox.com> wrote in message
news:jollyroger-751867.08571704082008@news.individual.net...
> In article <6fo22oFc9g43U1.DeleteThis@mid.individual.net>,
> "The Todal" <deadmailbox.DeleteThis@beeb.net> wrote:
>
>> "Jolly Roger" <jollyroger.DeleteThis@pobox.com> wrote in message
>> news:jollyroger-2E8A69.20472203082008@news.individual.net...
>> > In article <6fn4ciFcego7U1.DeleteThis@mid.individual.net>,
>> > "The Todal" <deadmailbox.DeleteThis@beeb.net> wrote:
>> >
>> >> "Jolly Roger" <jollyroger.DeleteThis@pobox.com> wrote in message
>> >> news:jollyroger-99C267.19110103082008@news.individual.net...
>> >> >
>> >> > This sounds more like an authentication issue or something similar.
>> >> > For
>> >> > instance, if your router does MAC (Media Access Control) address
>> >> > filtering, and the MAC address of the computer from which you
>> >> > connect
>> >> > is not allowed, the computer will *appear* to be connected, but the
>> >> > router
>> >> > will not give it a valid IP address.
>> >> >
>> >> > WHen you experience this problem again, go into System Preferences >
>> >> > Network, and take a look at the IP address of the Airport interface.
>> >> > If
>> >> > the address is a self-assigned IP address, then the router is
>> >> > refusing
>> >> > to give you an IP address, and that's why you can't talk to the
>> >> > network.
>> >>
>> >> I've disabled MAC filtering and have adjusted the TCP/IP settings so
>> >> that
>> >> it gets its address from the router.
>> >
>> > So that was the problem?
>>
>> No, it was something I did at the very outset.
>
> Why would you diable MAC filtering if you haven't determined it's the
> problem?
>
> Only now are we learning that you apparently had the MacBook configured
> to use a manual IP address - is that correct?

I tried both ways to see if it made a difference.


And now it sounds like
> you've got it set to use DHCP - correct?

Yes, at the moment.

>
> Is it getting a valid IP address, or a self-assigned IP address?

Not sure if I understand that. It's getting an address assigned to it by the
router.

>
> What sort of authentication is the Airport set to use?

The MacBook's airport connects to a Draytek router using WEP authentication.
I tried switching off WEP leaving no security at all to see if that made a
difference and it didn't.

>
> Have you examined the Airport password(s) stored in your MacBook
> keychain to ensure they are all correct?

Yes.

>
> Any details you can supply will help us help you. Without details about
> your setup, helping you is kind of like playing a guessing game.

Understood.

>
>> The position remains that it seems to connect immediately to the wireless
>> network but no web pages come up and no mail can be retrieved, until five
>> or
>> ten minutes later when it suddenly starts working properly.
>
> Without knowing whether or not you have a valid IP address during those
> five to ten minutes, it's hard to proceed. I don't know how else to ask
> this question. All you have to do is look and report the IP here.

Yes, it has a valid IP address during those five to ten minutes.
>
> It's also hard to help you without knowing how you have the MacBook
> System Preferences > Network > Airport interface configured.

There aren't many options, really, are there? Unless I'm missing something.
Airport is at the top of the list for connection options. Configure IPv4 is
set to "Using DHCP". It comes up with 192.168.1.24, subnet 255.255.255.0,
router 192.168.1.1. Under Configure IPv6 I've put "Off" because I am
assuming it doesn't do anything useful, but I tried the automatic setting as
well. DNS Servers shows the address of the router and nothing else. WINS
shows a NetBios name and nothing else. AppleTalk is off. I don't understand
the tab that says 802.1X - there is an entry "Login Window Profiles" with
Airport ticked.

>
>> Changing the
>> channel of the router seems to speed things up, but that means using a
>> different machine to go into the settings and change the channel. Very
>> odd.
>
> I doubt that has much to do with why you can't connect net resources
> during the first five to ten minutes.
>
> Does the signal strength reported on your MacBook indicate a weak signal
> during the first five to ten minutes, or until you change the channel?

No - and I've tried positioning the computer right next to the router to
rule out weak signal.

>
>> I just wondered if others had experienced the same problem - google
>> suggests
>> that there was a time when many people were complaining about their
>> Macbook
>> "dropping" the connection which is a slightly different thing.
>
> It's hard to know exactly what the problem you are experiencing is
> without more details

Okay.

This message is not archived

In article <6foickFchtkcU1.TakeThisOut@mid.individual.net>,
"The Todal" <deadmailbox.TakeThisOut@beeb.net> wrote:

> "Jolly Roger" <jollyroger.TakeThisOut@pobox.com> wrote in message
> news:jollyroger-751867.08571704082008@news.individual.net...
>
> > Is it getting a valid IP address, or a self-assigned IP address?
>
> Not sure if I understand that. It's getting an address assigned to it by the
> router.

What is the IP address?

> > What sort of authentication is the Airport set to use?
>
> The MacBook's airport connects to a Draytek router using WEP authentication.
> I tried switching off WEP leaving no security at all to see if that made a
> difference and it didn't.

If you're using WEP, chances are the password isn't being specified
correctly on the Mac side.

How did you specify the WEP password on the Mac, exactly? Did you just
type the pasword, or did you supply a hexadecimal representation of it?
Did you prepend the dollar sign ($) character in front of it, or not?

> > Have you examined the Airport password(s) stored in your MacBook
> > keychain to ensure they are all correct?
>
> Yes.

I'm betting not. I suggest you delete all keys for Airport passwords
from your keychain so the system will ask you for the password the next
time you connect. When it does ask, be sure to specify the hexadecimal
representation of the password prepended with a dollar sign character
($).

--
Send responses to the relevant news group rather than to me, as
E-mail sent to this address may be devoured by my very hungry SPAM
filter. Due to Google's refusal to prevent spammers from posting
messages through their servers, I often ignore posts from Google
Groups. Use a real news client if you want me to see your posts.

JR

"Jolly Roger" <jollyroger.TakeThisOut@pobox.com> wrote in message
news:jollyroger-300B73.20383805082008@news.individual.net...
> In article <6foickFchtkcU1.TakeThisOut@mid.individual.net>,
> "The Todal" <deadmailbox.TakeThisOut@beeb.net> wrote:
>
>> "Jolly Roger" <jollyroger.TakeThisOut@pobox.com> wrote in message
>> news:jollyroger-751867.08571704082008@news.individual.net...
>>
>> > Is it getting a valid IP address, or a self-assigned IP address?
>>
>> Not sure if I understand that. It's getting an address assigned to it by
>> the
>> router.
>
> What is the IP address?

I'm really not sure this is going to help you but here goes: 192.168.1.13

>
>> > What sort of authentication is the Airport set to use?
>>
>> The MacBook's airport connects to a Draytek router using WEP
>> authentication.
>> I tried switching off WEP leaving no security at all to see if that made
>> a
>> difference and it didn't.
>
> If you're using WEP, chances are the password isn't being specified
> correctly on the Mac side.

It is being specified correctly.

>
> How did you specify the WEP password on the Mac, exactly? Did you just
> type the pasword, or did you supply a hexadecimal representation of it?
> Did you prepend the dollar sign ($) character in front of it, or not?
>
>> > Have you examined the Airport password(s) stored in your MacBook
>> > keychain to ensure they are all correct?
>>
>> Yes.
>
> I'm betting not.

I deleted absolutely everything in the keychain.

> I suggest you delete all keys for Airport passwords
> from your keychain so the system will ask you for the password the next
> time you connect. When it does ask, be sure to specify the hexadecimal
> representation of the password prepended with a dollar sign character
> ($).

Interesting. I'm not sure I can do this: I use a string prefixed with 0x

So the problem is simply this: it does connect to the wireless network and
then doesn't drop the connection - but whereas my iBook would connect within
seconds, I have to wait about 10 minutes before the MacBook successfully
connects. Could it perhaps have an ultramodern sophisticated Airport which
tries for the best possible protocol for the first few minutes before
settling for what it can get?

In article <6gbrlrFf23jjU1 RemoveThis @mid.individual.net>,
"The Todal" <deadmailbox RemoveThis @beeb.net> wrote:

> "Jolly Roger" <jollyroger RemoveThis @pobox.com> wrote in message
> news:jollyroger-300B73.20383805082008@news.individual.net...
> > In article <6foickFchtkcU1 RemoveThis @mid.individual.net>,
> > "The Todal" <deadmailbox RemoveThis @beeb.net> wrote:
> >
> >> "Jolly Roger" <jollyroger RemoveThis @pobox.com> wrote in message
> >> news:jollyroger-751867.08571704082008@news.individual.net...
> >>
> >> > Is it getting a valid IP address, or a self-assigned IP address?
> >>
> >> Not sure if I understand that. It's getting an address assigned to it by
> >> the
> >> router.
> >
> > What is the IP address?
>
> I'm really not sure this is going to help you but here goes: 192.168.1.13

It helps because it shows that the IP is a valid IP. There are certain
ranges of valid internal LAN IP addresses. If your IP were not in one of
those ranges, it is invalid. In this case, it's within a valid range
(192.168.1.*).

--
Send responses to the relevant news group rather than to me, as
E-mail sent to this address may be devoured by my very hungry SPAM
filter. Due to Google's refusal to prevent spammers from posting
messages through their servers, I often ignore posts from Google
Groups. Use a real news client if you want me to see your posts.

JR

In article <6gbrlrFf23jjU1.TakeThisOut@mid.individual.net>,
"The Todal" <deadmailbox.TakeThisOut@beeb.net> wrote:

> "Jolly Roger" <jollyroger.TakeThisOut@pobox.com> wrote in message
> news:jollyroger-300B73.20383805082008@news.individual.net...
> > In article <6foickFchtkcU1.TakeThisOut@mid.individual.net>,
> > "The Todal" <deadmailbox.TakeThisOut@beeb.net> wrote:
> >
> >> "Jolly Roger" <jollyroger.TakeThisOut@pobox.com> wrote in message
> >> news:jollyroger-751867.08571704082008@news.individual.net...
> >>
> >> > What sort of authentication is the Airport set to use?
> >>
> >> The MacBook's airport connects to a Draytek router using WEP
> >> authentication.
> >> I tried switching off WEP leaving no security at all to see if that made
> >> a
> >> difference and it didn't.
> >
> > If you're using WEP, chances are the password isn't being specified
> > correctly on the Mac side.
>
> It is being specified correctly.

No it's not. See below.

> > I suggest you delete all keys for Airport passwords
> > from your keychain so the system will ask you for the password the next
> > time you connect. When it does ask, be sure to specify the hexadecimal
> > representation of the password prepended with a dollar sign character
> > ($).
>
> Interesting. I'm not sure I can do this: I use a string prefixed with 0x

That's your problem. When you generate a WEP key, you get a hexadecimal
string that is the key. You need to prefix the hexadecimal string with $
for WEP in Mac OS X. So, for instance, if your password is:

ultr@s3cur3

The proper way to specify it in the Mac OS X dialog boxes is:

$756c747240733363757233

--
Send responses to the relevant news group rather than to me, as
E-mail sent to this address may be devoured by my very hungry SPAM
filter. Due to Google's refusal to prevent spammers from posting
messages through their servers, I often ignore posts from Google
Groups. Use a real news client if you want me to see your posts.

JR

"Jolly Roger" <jollyroger RemoveThis @pobox.com> wrote in message
news:jollyroger-4C8019.19073311082008@news.individual.net...
> In article <6gbrlrFf23jjU1 RemoveThis @mid.individual.net>,
> "The Todal" <deadmailbox RemoveThis @beeb.net> wrote:

>>
>> Interesting. I'm not sure I can do this: I use a string prefixed with 0x
>
> That's your problem. When you generate a WEP key, you get a hexadecimal
> string that is the key. You need to prefix the hexadecimal string with $
> for WEP in Mac OS X. So, for instance, if your password is:
>
> ultr@s3cur3
>
> The proper way to specify it in the Mac OS X dialog boxes is:
>
> $756c747240733363757233

So it is a miracle that it connects at all? If you're right, it shouldn't
connect after ten minutes or ten hours.

In article <6gdeo4FfahskU1 DeleteThis @mid.individual.net>,
"The Todal" <deadmailbox DeleteThis @beeb.net> wrote:

> "Jolly Roger" <jollyroger DeleteThis @pobox.com> wrote in message
> news:jollyroger-4C8019.19073311082008@news.individual.net...
> > In article <6gbrlrFf23jjU1 DeleteThis @mid.individual.net>,
> > "The Todal" <deadmailbox DeleteThis @beeb.net> wrote:
>
> >>
> >> Interesting. I'm not sure I can do this: I use a string prefixed with 0x
> >
> > That's your problem. When you generate a WEP key, you get a hexadecimal
> > string that is the key. You need to prefix the hexadecimal string with $
> > for WEP in Mac OS X. So, for instance, if your password is:
> >
> > ultr@s3cur3
> >
> > The proper way to specify it in the Mac OS X dialog boxes is:
> >
> > $756c747240733363757233
>
> So it is a miracle that it connects at all? If you're right, it shouldn't
> connect after ten minutes or ten hours.

Perhaps it's connecting to some other base station unbeknownst to you.
Or, perhaps something else is going on.

--
Send responses to the relevant news group rather than to me, as
E-mail sent to this address may be devoured by my very hungry SPAM
filter. Due to Google's refusal to prevent spammers from posting
messages through their servers, I often ignore posts from Google
Groups. Use a real news client if you want me to see your posts.

JR

"Shawn Hirn" <srhi.DeleteThis@comcast.net> wrote in message
news:srhi-466DEE.05503205082008@newsgroups.comcast.net...
> In article <6fn4ciFcego7U1.DeleteThis@mid.individual.net>,
> "The Todal" <deadmailbox.DeleteThis@beeb.net> wrote:
>
>> "Jolly Roger" <jollyroger.DeleteThis@pobox.com> wrote in message
>> news:jollyroger-99C267.19110103082008@news.individual.net...
>> > In article <6fmus6Fcf9hsU1.DeleteThis@mid.individual.net>,
>> > "The Todal" <deadmailbox.DeleteThis@beeb.net> wrote:
>> >
>> >> New MacBook, and the Airport claims to be connected to the wireless
>> >> network
>> >> but nothing actually connects to the internet - no web pages, no
>> >> Software
>> >> Update. And the wireless network is fine because other computers are
>> >> having
>> >> no difficulty getting web pages.
>> >>
>> >> Is this a problem that others have had (maybe an incompatibility
>> >> between
>> >> AirPort and the wireless signal emitted by the router?) or am I
>> >> unique?
>> >>
>> >> Every so often I think I've solved it. I change the wireless channel
>> >> on
>> >> the
>> >> router and things work fine until I restart the Mac. My latest attempt
>> >> to
>> >> solve it was to repair the permissions on the Mac disk. The web pages
>> >> are
>> >> now there, and everything is as fast and as reliable as I could
>> >> possibly
>> >> wish... but for how long, I wonder.
>> >
>> > This sounds more like an authentication issue or something similar. For
>> > instance, if your router does MAC (Media Access Control) address
>> > filtering, and the MAC address of the computer from which you connect
>> > is
>> > not allowed, the computer will *appear* to be connected, but the router
>> > will not give it a valid IP address.
>> >
>> > WHen you experience this problem again, go into System Preferences >
>> > Network, and take a look at the IP address of the Airport interface. If
>> > the address is a self-assigned IP address, then the router is refusing
>> > to give you an IP address, and that's why you can't talk to the
>> > network.
>>
>> I've disabled MAC filtering and have adjusted the TCP/IP settings so that
>> it
>> gets its address from the router. Is there any way of adjusting the
>> Airport
>> hardware settings (power output, roaming aggressiveness)?
>
> Does your MacBook Pro have an IP address when it tries to connect
> wirelessly? I saw the same thing happen on a friend's PowerBook. It
> wasn't getting an IP address so it was defaulting to the AirPort's
> address. We solved the problem by clearing out all the preferences in
> the home and system libraries and rebooting.
>
> If that doesn't help, call Apple. Since your MacBook is new, why not use
> the warranty that comes with it?

It may be working normally for all I know - I don't want to have to hand it
in and wait for several weeks and then be told no fault has been found.