Ticket Options

Question Details

TICKET ARCHIVE -> Airport And Broadband Problems

Jonl1 - Sep 15, 2005 - 7:36 pm

Hi - I have a powerbook 15inch G4, a bt broadband connection which i use a d-link dsl 300t ethernet modem to access. I also have an airport extreme which I am trying to set up to acces the internet wirelessly.

I've just moved internet provider from wanadoo (with the same equipment), where I had no problems. I have no problem if i simply connect the modem via my ethernet port, but as soon as I connect it to the airport extreme (and set that up from scratch), I get nothing. I have a strong signal from the airport, and the computer seems to be connecting wirelessly to it.

Help!

Thanks

skapp - Sep 15, 2005 - 11:04 pm

Let's start by checking the physical setup.

You should have the DSL modem's Ethernet port connected to the WAN port on the Airport Extreme Base Station. The AEBS should then be configured as a base station through the Airport Admin Utility. Configure its Network settings to Distribute IP Addresses and Share a Single IP Address Using DHCP and NAT. Check the Internet settings are Connect Using Ethernet and Configure is DHCP. Save those AEBS settings.

On your computer open the Network pref pane. Select Airport in the list and click on the Configure button. Click on the TCP/IP tab and set the Configure drop down menu to DHCP.

Now, turn everything off and wait at least one minute. In sequence first power up the DSL modem and wait until its status indicators show you are communicating with the ISP. Then power up the AEBS and wait until the status lights stop blinking or show it is communicating with the modem. Last, power up the computer.

If you open the Airport Admin Utility and open the AEBS configuration and check the Internet settings you should find a valid IP address and other connection information. This will show that you have a connection working between the AEBS and the DSL modem. You should then have a connection from your computer as well.

Jonl1 - Sep 16, 2005 - 11:05 am

Hi - thanks for replying.

I did everything you said - and yes there seems to be a connection between the DSL modem and the AEBS, but it's not registering on my powerbook - an error message comes up saying my computer is not connected to the internet.

skapp - Sep 16, 2005 - 11:24 am

On your Powerbook open Network preference pane. Select Airport from the list and click on the Configure button. In the Airport tab put a check by the Show Airport in the status bar. Click on Apply Now. You should see the Airport menubar item. Select it, then be sure Airport is turned on. Then click on the TCP/IP tab and in the dialog select DHCP in Configure drop down menu. Click on Apply Now button. See if you pull a valid IP address that should be in the 10.0.1.x range. If you see a 169... IP address, then there's a problem. Select Manually from the Configure drop down menu and click on Apply Now. Then re-select DHCP and click on Apply Now. See if that gets you a valid IP address.

It wouldn't hurt to connect an Ethernet cable from the LAN port on the AEBS to the Ethernet port on the computer and see if you can connect that way. At least that will indicate the AEBS, Modem, computer connection is good and the problem is just limited to your computer's Airport connection.

skapp - Sep 16, 2005 - 11:25 am

Oh, and BTW, what version of OS X are you using and what version of Airport software is installed? Also, have you installed the firmware update for the AEBS?

Jonl1 - Sep 16, 2005 - 12:38 pm

Thanks again- I've tried this and I have a valid IP address. I don't have a spare ethernet cable - but I'll get one and try this.

I'm using OS X 10.4.2 and I have the latest firmware update, and the most recent software, for the AEBS installed. Any more ideas?

skapp - Sep 16, 2005 - 1:02 pm

Bad Airport card in the computer? I'm stumped at this point. You're getting a valid IP address at the AEBS, a valid IP address from the AEBS to the computer, but no internet access.

I'd have to start back at square one. Remove the AEBS from the setup, connect the modem directly to the computer's Ethernet port and verify a connection to the internet. Then insert the AEBS but connect to the computer via Ethernet to verify that the AEBS is routing to the computer properly. Last, disconnect the Ethernet cable from the computer, turn on Airport card and see if you can establish an internet connection. At least this way you can systematically remove each item from the suspect list.

Jonl1 - Sep 16, 2005 - 1:58 pm

Thanks anyway - I'm fairly certain my powerbook's airport isn't the guilty party as this setup worked with my old ISP fine.

I guess I'm going to have to get apple's support team onto this!

Thanks again for your help

skapp - Sep 16, 2005 - 4:02 pm

Well, apparently I haven't been much help, I'm afraid. I've found some other troubleshooting docs that may help, but you may have been down this road before.

http://www.macosxhints.com/article.p...5951&lsrc=osxh

http://docs.info.apple.com/article.html?artnum=107530

The following is an excerpt from a MacFixit.com report. Wednesday, August 10 2005 @ 01:31 AM PDT
Mac OS X 10.4.2 Special Report: AirPort connectivity issues

Solutions

Reverting to older AirPort kernel extenstions One potential workaround -- which has worked when this problem appeared with previous iterations of Mac OS X and various security updates -- involves reverting to older version of the AirPort kernel extensions.

This can be accomplished by first downloading the shareware utility Pacifist, then obtaining the AirPort 4.1 updater package.

Use Pacifist to open the AirPort 4.1 package, and extract the following files:

AppleAirPort.kext
AppleAirPort2.kext
AppleAirPort3.kext

Place these same files in the /System/Library/Extensions folder, replacing the old copies (you will be asked for your administrator password) and restart. You may need to repair permissions using Apple's Disk Utility (located in Applications/Utilities after restarting).

Crisp Hues is one MacFixIt reader who had success with this workaround:

"My original problem was AirPort causing my wireless network (Linksys WRT56G router and adapter) to stop working after 10.4.2 on my G5 dual 1.8 tower. The fix I've used is to downgrade to the AppleAirPort.kext and AppleAirPort2.kext files to the ones the ones that came with 10.4.1. and then repairing permissions. I got these files from the Apple Support Forums. Don't have the link anymore. It worked. Probably not a fantastic solution but seems good until Apple addresses this problem."

Delete then re-establish wireless network MacFixIt reader Arno reports that you may need to delete then re-establish any encrypted AirPort network configurations in order to take advantage of Mac OS X 10.4.2's enhanced automatic reconnection capabilities after sleep or restart.

Arno writes:

"I found out that is best to delete all preferred networks with encryption. And then add them again after manually connecting. Fastest way is temporarily turn on 'Automatically add new networks to preferred networks list' under 'Options' of the Airport network connection.

"After that, the problem with not reconnecting after sleep or startup was solved for me. Finally! It was most annoying with closed networks (hidden SSID)."

"Change Settings" on Base Station For some users, simply using the AirPort Setup Assistant (located in Applications/Utilities) to "Change Settings," then re-entering configuration information restores connectivity.

One reader writes:

"I had the same problem and fixed it fairly easily by running the Airport Setup Assistant and choosing 'Change settings on an existing Airport Base Station' and re-entering the previous (same) info as before."

Turn Base Station off, then on In some cases, turning an AirPort Base Station (or AirPort Express unit) off, then back on -- usually by unplugging then re-connecting to power -- re-establishes proper operation.

MacFixIt reader Scott Daniels writes:

"After installing the Mac OSX 10.4.2, I also got the error connecting to airport network message - from all three machines on the network. Fortunately, the solution was quite simple: I unplugged the two Airport Express base stations that comprise my wireless network (home), and plugged them back in again after a few seconds. Problem solved."

You may also want to try turning your internal AirPort card off then back on if you are having access issues. This can be accomplished through the AirPort menu item, or using Internet Connect (located in the Applications folder)

One reader writes:

"I have a 1Gz G4 Powerbook and following the update and restart, Airport stopped working so I turned off the Airport and turned it on again. I received a message which asked if I wished to update passwords in my keychain, when clicked 'OK' my Airport returned.. Hope this is useful."

"Keep Looking for recent networks" MacFixIt reader Jerry D reports that, in his case, selecting "Keep looking for recent networks" in the Network pane of System Preferences resolved his inability to connect to local networks.

Jerry writes:

I experienced a consistent problem in that every time I started up or restarted "I had to go into Airport Utility and run through set up each time. After fighting this for 2 or 3 weeks and futzing with settings over and over, I hit on a setting that cured this (maybe everybody already knows to check this setting, but I didn't) - In Network Preference, behind the Options Button - I had to select 'Keep looking for recent networks' under 'If no recent networks are found' - That fixed this issue."

Switching channels In some cases, switching channels on your (non-AirPort) WiFi base station can improve reception weakened by incremental updates.