MacBook Pro will not connect to Cisco Wireless Network

I have just bought a brand new MacBook Pro, running Leopard (OSX 10.5.1) and I just cannot get it to connect to the Wireless Network at my workplace.

The MBP connects to wireless network and authenticates just fine, but will not obtain an IP address from the DHCP server.

The wireless network consists of 16 Cisco Aironet 1200 Access Points controlled by a Cisco Wireless Network Controller. It does not broadcast its SSID and is WEP 128-bit hex protected.

Changing the network from WEP to WPA is out of the question for me as this is under the control of my customers IT Department and they do not have any problems with their PCs connecting to the network. It appears to be an Apple issue.

For reference, my old Vaio PC, my Nokia N95 and my iPod Touch ALL connect to the same wireless network without any problems whatsoever, first time, every time!

If I boot into Windows XP from my Boot Camp partition, XP can connect wirelessly to the network without any problems, so it is not MacBook hardware related...

It has to be a bug in Mac OSX... doesn't it?!?

Things I have already tried (following suggestions on many forums):
* Switching Airport off/on
* Deleting various network-related Plist files and rebooting
* Manually assigning an IP Address (not really permitted but doesn't work anyway!)
* Disabling all network adaptors except Airport

AP Grapher shows that the MBP is connected to the wireless network, at good strength, and packets are being sent and received, but Internet Access is not possible as no IP Address has been assigned. Instead, my MBP shows a 169.* IP Address (self-assigned). It should be a 10.1.255.* address.

Can anybody please help? Thank you.

MacBook Pro 17" Intel 2.4GHz 4GB RAM, Mac OS X (10.5.1)

Posted on Dec 10, 2007 8:24 AM

Reply
56 replies

Apr 8, 2008 8:32 AM in response to SJRNET

Hi

Im having the same issue with connecting my wireless network
i will turn my Macbook on and it will just work and connect with out a problem but when i pack for my college day il close the lid to sleep the macbook and once im at college il open the mac up let it set self up and it will ask me to connect to the wifi network so il type in the security code given to me and it will timeout but when it does connect, it will assign it self a self-assigned ip address which is very stressful and i wont be able to connect and then once i get home the same thing happens but will never connect untill i change the router security code via a windows pc?

so i took to the apple store and to my suprise it 100% worked infront of the genious so he told me theres nothing wrong with it but he did tell me to a hard ware check via DVD-Boot, no problems

so please i will appreciate any help from anyone!!

Tris

Apr 11, 2008 1:40 PM in response to egalsim

I have a 15" Macbook Pro with the built in Airport NIC (Like all of them). I can connect to my home AP (Netgear) with no problem at all, using either WEP or WPA (Configured both ways to test). I can connect to every public access point that I've tried.
When I try to connect to my work Access Point that is configured with 128bit WEP Key, I get connected to the access point, but never get a DHCP address. It's a basic WEP key setup, with no LEAP, or any other authentication.
I can connect with a XP laptop with no issues (our entire organization uses XP, and nobody has an issue).
I have dual booted (BootCamp) my Macbook into XP, and I can connect and get a DHCP address.
This leads me to believe it's a driver issue on the Mac.
I have tried multiple AP's on our network, all with the same results.
I have verified that my built in firewalls are completely open, and have double checked by running the "ipfw flush" command, and then "ipfw list" shows "allow from any to any".
I went out and purchased a 3rd party USB Wifi card, and it connects with no issues, but I don't want to carry that around.
I completely rebuilt my 10.5.2 leopard from scratch, to make sure it wasn't anything left over from the 10.4 with the same results.
I've made sure that the keychain entry is set so any application can access it.
I have tried to manually enter the IP address, again, same results.
I have installed the above mentioned update, and was looking forward to coming into work today to try it out. Same results 😟

May 19, 2008 3:52 PM in response to cadair

I am an IT consultant, working at an Oil giant here in the UK (green sign, lots of buy outs recently...I am sure you can guess who!) I was offered a T60 company Lenovo (still look like they were designed in 1992!), but no I said, I want to use my brand new Macbook Pro 17".
I brought it in today, my shiny new dream machine, and sat down at a hotdesk with many envious eyes looking over my shoulder, and then? I could not connect my £1800 laptop to the internet. How basic a fault is that Apple?
I work within deskptop services, they were looking at Apple as a serious contender for their laptop fleet. HAH! not anymore, I sat with a group IT director trying to show him a keynote presentation that was on my home iMac which I could not get at because my laptop would not connect to the internet.
He laughed his head off and asked me why Apple machines were so expensive...I was embarassed professionally for buying a piece of technology that does not work and for Apple for losing (talking literally here) business with a major player. Why would you pay over the odds for a computer that cannot perform basic tasks?
Apple will never be recognized in the business world until they remove idiotic problems like this, or at least recognize them.
~Okay rant over 😉
I cannot connect (as I am sure you have gathered) to my work network. It's a WEP protocol and everyone else can. I could even connect with my Macbook (2.16 mhz bought July 2007). But not with my new 10.5.2 machine. I get the connection timeout whenever I try to connect, although it did connect once, it never did again.
I am angry and frustrated that this problem exists and that is has not even been acknowledged.

I can even think of a reply to Apple's advertising for Bill Gates - a Mac and a PC side by side, the trendy guy unable to connect to the net while the fat PC guy reads his emails and then starts playing Second Life ⚠

Boy am I p **d.

Jun 2, 2008 8:16 PM in response to Pomme1976

I love it.... You and I work for the same company on different sides of the Pond.
I'm in the Houston headquarters, and have the exact same problem as you do in the UK.
I updated to 10.5.3 with the hope that the issue is fixed, and of course, it's not.
Obviously we are using identical Access Points.
Please let me know if you've ever got a resolution.
Look me up in the GAL
C.Adair (I'm the only one with that first initial in the GAL)

Aug 11, 2008 2:48 PM in response to cadair

Not sure if you all still have this issue or not but I have a Cisco 1200 series AP at home with the 1st Generation Mac Book Pro and my wireless works like a champ using WPA-2 TKIP encryption. you DO HAVE to broadcast the SSID in order for it to work but the weird thing is I can get some of the new macbook pro's at my office to work with the same config. Not sure what chanhged in OS version for the mac but... All of my Thinkpad T60's work just fine but the new mac's I have my SSID broadcasting but no go. The Cisco 1240AG have the latest IOS installed as well.

Oct 13, 2008 8:18 AM in response to SJRNET

I just wanted to follow up on this - this problem is still alive and well. There is some fundamental problem with Macs and Cisco wireless networks. Where I work, we have a Cisco wireless network (1200s I believe) with WPA enabled and Mac users are having no end of trouble.

Some of us can't get connected at all - the authentication dialog just keeps popping up over and over or it accepts your login, but you never get an IP address.

Of course, the building is full of PCs of various brands that all work fine.

It's pretty incredible this problem has still not been solved.

Apple, if you want Macs to be adopted in the workplace, they HAVE TO WORK FLAWLESSLY WITH CISCO NETWORKS! This is a no-brainer.

Oct 16, 2008 5:42 AM in response to aleister2008

We're having the same problem in our office. Specifically with the Cisco Aironet 1200 also. We have three identical MacBookPro machines all getting the same problem. Older macbooks work fine just a problem with new MBs and MBPs.

Have logged the issue with apple and provided extensive information about the issue including logs and firmware etc.

I suspect it's an issue with the firmware/driver of the wireless card in the newer machines.

This is an incredibly frustrating and embarrassing situation for apple advocates in the corporate workplace and needs some proper attention. Cisco is the standard for major corporation and Apple need to procure some of these boxes and get on with some proper testing!

Oct 16, 2008 11:37 PM in response to SJRNET

I'm having the same problem with OS 10.5.5 and all the previous Leopards.
I tried running Parallels with XP and Firefox and got online.
In fact I'm posting this from XP Firefox and I even have Explorer online.

I don't know why I can't get online with OS X & Safari. There was some reference to DNS problems in another forum, but that's over my head to troubleshoot.

Hope this may help to find a solution!

Oct 23, 2008 7:33 AM in response to SJRNET

We have over 200 MAC book’s connecting too 2 different Cisco wireless networks at two different locations. This combination of product has caused our organization excruciating pain supporting our customer base. Our PC’s connect flawlessly, but the MAC books we have had trouble with release 10.5.2; 10.5.3. We installed 10.5.4., and the connections finally started to work correctly, getting associated then receiving a DHCP IP address. We took the leap to 10.5.5, and our originals problems have reappeared, same problems as many of you discussed in this forum. Clients associated but many do not receive DHCP IP addresses. Have any one else experience similar results with 10.5.4 and 10.5.5? Thanx ..

Nov 25, 2008 11:59 AM in response to aleister2008

Is there any updated information on this topic? It's VERY frustrating.

My school uses Cisco Clean Access to authenticate computers to their network. Every single Windows PC connects perfectly but 70% of Mac users (OS X 10.4 and 10.5) cannot connect to the school's Cisco wireless network, mine included. However, when I use a USB wireless adapter in my MacBook I'm able to connect to the same Cisco network flawlessly. Is this a problem with the Atheros wireless card in my MacBook and the crappy driver that Apple develops for it or something else?

Again, this is very frustrating and resulting in many Mac users to turn away and resort back to PCs. I figure Apple should take serious notice of increased loss of market share in the corporate and educational world...

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

MacBook Pro will not connect to Cisco Wireless Network

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.