Link to home
Start Free TrialLog in
Avatar of PCgod2004
PCgod2004

asked on

Apple Macbook Wireless gets put on Exclusions List when trying to connect to Cisco Access Point

I work in a College IT department for a University. I'm working between a student of ours and our Network Operations Center (NOC). The student has a brand new Apple Macbook running Leopard 10.5.1. When trying to connect to our University's Wireless Network he receives a Connection timeout error almost instantly. Our wireless network consists of Cisco Access Points. MAC Addresses are required to be registered before a connection can be made, plus the laptop must be set for Open Network and have a WEP key.

My contact at NOC tells me something on the laptop is remembering an invalid ip address or assigning itself an invalid ip address before it receives its DHCP address. Each time it changes its address it causes a re-authentication. After 5 failed authentications it is placed in exclusion for 60 seconds.

The only way for the laptop to connect to the wireless network is for NOC to disable the security policy for this "5 failed authentications". Once that policy is turned off, the laptop connects instantly. NOC is only willing to disable this policy for testing only, so it must remain on the rest of the time.

Attached is the log from the Cisco Access Point and Macbook System Log.
Cisco Access Point Log:
 
Tue Nov 27 15:20:56 2007: 00:1d:4f:fa:bf:50 Invalid MSCB state: ipAddr=10.241.3.202, regType=2, Dhcp required!
Tue Nov 27 15:20:56 2007: 00:1d:4f:fa:bf:50 Orphan Packet from 172.30.39.218 on mobile 00:1d:4f:fa:bf:50
Tue Nov 27 15:20:56 2007: 00:1d:4f:fa:bf:50 Invalid MSCB state: ipAddr=172.30.39.218, regType=2, Dhcp required!
Tue Nov 27 15:20:57 2007: 00:1d:4f:fa:bf:50 Orphan Packet from 192.168.1.107 on mobile 00:1d:4f:fa:bf:50
Tue Nov 27 15:20:57 2007: 00:1d:4f:fa:bf:50 Invalid MSCB state: ipAddr=192.168.1.107, regType=2, Dhcp required!
Tue Nov 27 15:20:57 2007: 00:1d:4f:fa:bf:50 Orphan Packet from 192.168.1.101 on mobile 00:1d:4f:fa:bf:50
Tue Nov 27 15:20:57 2007: 00:1d:4f:fa:bf:50 Invalid MSCB state: ipAddr=192.168.1.101, regType=2, Dhcp required!
 
Macbook System Log:
 
Nov 27 15:18:23 macbook airportd[6539]: Error: Apple80211Associate() failed -6
Nov 27 15:18:23 macbook SystemUIServer[1571]: Error: airportd MIG failed = -6 ((null))  (port = 51347) 
Nov 27 15:18:23 macbook SystemUIServer[1571]: Error joining NoWireUC: Connection timeout (-6 timeout connecting)
Nov 27 15:18:42 macbook TextMate[1778]: Error checking for new version: no Internet connection
Nov 27 15:18:42 macbook TextMate[1778]: Will try again in one hour 
Nov 27 15:19:01 macbook ntpd[24]: sendto(17.254.0.28) (fd=23): No route to host
Nov 27 15:19:11 macbook airportd[6548]: Error: Apple80211Associate() failed -6
Nov 27 15:19:11 macbook SystemUIServer[1571]: Error: airportd MIG failed = -6 ((null))  (port = 51347) 
Nov 27 15:19:11 macbook SystemUIServer[1571]: Error joining NoWireUC: Connection timeout (-6 timeout connecting)
Nov 27 15:20:05 macbook ntpd[24]: sendto(17.254.0.28) (fd=23): No route to host 
Nov 27 15:20:52 macbook mDNSResponder[15]: getifaddrs ifa_netmask for vmnet8(7) Flags 8863 Family  2 172.16.6.1 has different family: 0
Nov 27 15:20:52 macbook mDNSResponder[15]: getifaddrs ifa_netmask for vmnet1(8) Flags 8863 Family  2 172.16.112.1 has different family: 0
Nov 27 15:20:52 macbook mDNSResponder[15]: SetupAddr invalid sa_family 0
Nov 27 15:20:53: --- last message repeated 1 time ---
Nov 27 15:20:53 macbook airportd[6549]: Error: Apple80211Associate() failed -6 
Nov 27 15:20:53 macbook airportd[6549]: Error: Apple80211Scan() error 16
Nov 27 15:20:53 macbook airportd[6549]: Error: __performScan() failed, entering fail-save workaround..
Nov 27 15:20:56 macbook mDNSResponder[15]: getifaddrs ifa_netmask for vmnet8(7) Flags 8863 Family  2 172.16.6.1 has different family: 0
Nov 27 15:20:56 macbook mDNSResponder[15]: getifaddrs ifa_netmask for vmnet1(8) Flags 8863 Family  2 172.16.112.1 has different family: 0 
Nov 27 15:20:56 macbook mDNSResponder[15]: SetupAddr invalid sa_family 0
Nov 27 15:20:57 macbook mDNSResponder[15]: getifaddrs ifa_netmask for vmnet8(7) Flags 8863 Family  2 172.16.6.1 has different family: 0
Nov 27 15:20:57 macbook mDNSResponder[15]: getifaddrs ifa_netmask for vmnet1(8) Flags 8863 Family  2 172.16.112.1 has different family: 0
Nov 27 15:20:57 macbook mDNSResponder[15]: SetupAddr invalid sa_family 0 
Nov 27 15:20:58: --- last message repeated 1 time ---
Nov 27 15:20:58 macbook airportd[6549]: Could not find any preferred networks; trying broadcast requests..

Open in new window

Avatar of pheidius
pheidius

if they are right about it self assigning  tehn might be worth it to go into terminal and do a release/renew. I think it is sudo ipconfig set en0 BOOTP  or you could try sudo ifconfig eno down ; sudo ifconfig esudo ipconfig en0 BOOTP n1 up
"The ipconfig set en BOOTP causes OS X to release the address; then ipconfig set en DHCP causes OS X to attempt to get a new address. On some networks, the behavior will basically be the same, but depending on the topology and what\'s going on, you could get very different results doing a RELEASE/NEW LEASE versus a true RENEW.

On the GUI version, OS X has a bug in its behavior where its RENEW is actually a REBIND. Again, this is probably going to get you the same results on many networks, but it\'s not a real RENEW. The difference between a RENEW and a REBIND is that a RENEW is a directed unicast to the original server that gave you the address asking for an extension on the list; a REBIND is a broadcast that you do after you don\'t get an answer on your RENEW (T1 has expired, and T2 has expired). " 

I  any case I think it could not hurt to do a complete release below the gui level and then reset its new adress

o, by the way looking again at your post, it might be en1 instead of en0  asen0 would be your ethernet port while en1 would likely be your wireless port .perhaps before you reboot the modem you could run  ipconfig getifaddr en0 0r en1 as the case may be and see if it is selfassigning  a nonworking ip
Avatar of PCgod2004

ASKER

Didn't seem to make a difference.
We believe it may be a hardware issue.
Booting laptop from another system over firewire yields the same results.
Booting the system over firewire on another laptop allows access to the network.
Problem stays with the hardware.

Checked all system updates, changed MTU, and reset the PRAM multiple times. Still no luck.
ASKER CERTIFIED SOLUTION
Avatar of pheidius
pheidius

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial