Macbook Wireless Authentication Problem

I am having a strange issue that I haven't seen much information in either the Leopard forum or the Snow Leopard forums. This issue started with the 10.5.8 upgrade. When I migrated to 10.5.8 the campus network wireless stopped working. The Campus Network runs on WPA Enterprise. I have no issues connecting to my WPA Personal network at home. Neither network broadcasts the SSID and both require authentication to access. The home network requires just a password to connect while the campus network requires both Username and Password authenticated via Active Directory. When connecting to the campus network opening the Network preferences pane shows Airport flashing Authenticating then Authenticated repeatedly. Eventually after 10-20 minutes of flashing the wireless will finally connect to the network. Console shows the following:
Sep 14 07:35:31 ***** eapolclient[324]: PEAP: successfully authenticated
Sep 14 07:35:32 ***** eapolclient[324]: eapmschapv2successrequest: successfully authenticated
Sep 14 07:35:32 ***** eapolclient[324]: PEAP: successfully authenticated
Sep 14 07:35:32 ***** eapolclient[324]: eapmschapv2successrequest: successfully authenticated
Sep 14 07:35:32 ***** eapolclient[324]: PEAP: successfully authenticated
Sep 14 07:35:33 ***** eapolclient[324]: eapmschapv2successrequest: successfully authenticated
Sep 14 07:35:33 ***** eapolclient[324]: PEAP: successfully authenticated
Sep 14 07:35:33 ***** eapolclient[324]: eapmschapv2successrequest: successfully authenticated
Sep 14 07:35:33 ***** eapolclient[324]: PEAP: successfully authenticated
Sep 14 07:35:33 ***** eapolclient[324]: eapmschapv2successrequest: successfully authenticated
Sep 14 07:35:33 ***** eapolclient[324]: PEAP: successfully authenticated
Sep 14 07:35:34 ***** eapolclient[324]: eapmschapv2successrequest: successfully authenticated
Sep 14 07:35:34 ***** eapolclient[324]: PEAP: successfully authenticated
Sep 14 07:35:34 ***** eapolclient[324]: eapmschapv2successrequest: successfully authenticated
Sep 14 07:35:34 ***** eapolclient[324]: PEAP: successfully authenticated
Sep 14 07:35:35 ***** eapolclient[324]: eapmschapv2successrequest: successfully authenticated
Sep 14 07:35:35 ***** eapolclient[324]: PEAP: successfully authenticated
Sep 14 07:35:36 ***** configd[15]: network configuration changed.
Following the instructions here:
http://www.viewfromthedock.com/2009/08/temp-fix-for-10-5-8-airport-bug/
Which has you replace the following 2 files fixes the issue:
AppleAirport.kext
IO80211Family.kext
Now that I have upgraded to Snow Leopard the problem is back again. This is a completely fresh loaded laptop. I erased and formatted the hard drive before installing Snow Leopard. I'm running an older Macbook that uses the Atheros card. A guy I work with has a slightly newer Macbook running a Broadcom card that doesn't have this issue.
I do have a log file I generated from this post:
http://discussions.apple.com/messageview.jspa?messageID=10123194
If that would be helpful in getting the problem resolved.
Thanks in advance.

Here:
Card Type: AirPort Extreme (0x14E4, 0x8D)
Firmware Version: Broadcom BCM43xx 1.0 (5.10.91.19)
Locale: ETSI
Country Code: TW
Supported PHY Modes: 802.11 a/b/g/n
Supported Channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140, 149, 153, 157, 161, 165
Country code may vary, according to base stations in the vicinity. When I'm at home in the UK, code is TW. At work in the UK, code is US. Verbose startup of the OS reveals variety long before authentication, so I guess that the country code sometimes reflects the characteristics of a nearest capable base station.
I have different issues in different environments. One of the issues is summarised at <http://discussions.apple.com/thread.jspa?messageID=10159356&#10159356> and in this area of Apple Discussions, I watch just a few other threads.

Similar Messages

HP Wireless Printing - problems with MAcbook Airport

I've read through most of the problems related to printers on here and I think I have a unique one!!
I've just bought and installed a HP C8180 all-in-one printer. Installed as per instructions - on home network and across ethernet. I've reserved an IP address for it so its always in the same place. Works brilliantly (good printer!). However if I then disconnect ethernet and connect to my network via airport - it won't print! It will however, align, print test page (albeit slowly), clean cartridges etc - but no printing.
If I disconnect from Airport and reconnect to ethernet - no problems it prints fine. If I then connect via airport (keeping the ethernet connection at the top of the list) it works fine. If however airport is top of the list - it won't print.
Prints fine on USB too.
So I've deduced that for some reason its the Apple Macbook wireless that's causing the problem.
So does anyone have a solution - 'cause this is driving me nuts!
Thanks in advance.

I have a HP Photosmart 2710 All in One connected to a Aiport Express USB port, it works great, the WIFI in the printer doesn't work because it doesn't support WPA2 so I disabled it. The main router is quite a ways away but I still want to print to the printer wirelessly.
My suggestion:
1. Connect the printer via USB directly to macbook to load and test driver.
2. Use Airport Utility and configure Airport for printer, if it is already listed, remove and reinstall it.
3. On your Macbook it should change the driver from USB to the name of Airport, sometimes it helps to turn off the printer and turn it back on while connected to Airport.
Keep messing with it, it can be stubborn with Bonjour but it finally shows up. Make sure the Airport Utility can see the printer when connected to it.

MacBook Air wireless connection problem after sleep mode

Hello guys,
My MacBook Air have problems to connect back to my wireless after comming back from sleep mode. It needs few minutes until it finds again the network.
Does anyone have the same problem or better, a solution to this?

Hello there TheTomcat,
I would recommend the Solution section of our article Troubleshooting Wi-Fi issues in OS X Lion and Mac OS X v10.6 found here http://support.apple.com/kb/HT4628?viewlocale=en_US
Symptom: The network connection drops unexpectedly
Your Mac may not not stay connected to your Wi-Fi network reliably.
Your Mac may stop accessing the Internet during use.
Solution
Additional Information
If your symptom is not listed, or the above steps do not resolve the issue, you can search on the Apple Support site or contact AppleCare for further assistance.
All the very best,
Sterling

Macbook Pro Wireless Connection Problems

I bought my 13 inch macbook pro 1 week ago and I've had wireless connection problems from day 2 (I think after the updates).
Problems include:
- Safari cannot connect to the internet for 5~10 minutes after I turn it on, whether it be from sleep mode or completely off or restart (the fastest connection I got after turning it on was about 40 seconds)
- Loading takes ridiculously long and eventually Safari cannot find the server
- Airport signal (on the top right hand corner) is always full when it is not working
- Sometimes internet works but it is ridiculously slow
However, when the wireless connection stabilizes, Airport Signal is 2~3 bars full and internet works SOOO well and I love it so much when it does. But the problem is that it stabilizes like 30 minutes to never after I turn it on and it makes me so mad I want to explode this piece of crap in the microwave.
So I've called apple support, and they made me try four things:
1. Reset modem, router, and computer
2. Delete caches, reset Safari
3. Putting Airport first on the Service Order and resetting DHCP Lease
4. Connecting with Ethernet Cable then resetting the computer
None of these worked, and I'm suspecting that the cause of the problem is the hardware (not the aluminum body that's just bs) because my router and modem are working fine (my other samsung laptop is working perfectly). I don't think the problem lies in my network settings either because I did exactly what the Apple technicians told me to do. So after Appleguy made me try all 4 of those diagnostics, he told me to contact my router company NETGEAR because he thinks nothing is wrong with the mac hardware, so I did. The NETGEAR lady told me if one laptop is working and another isn't, there is nothing wrong with the router. So if nothing is wrong with my hardware, software, router, modem, ISP... Why do I have wireless issues????!?!?!?!?!?!?!?!?!?!
I'm going to return this <edited by host> or get another one with my warranty

Same thing here.
I've got a Macbook Pro 15" bought 6 weeks ago, airport express bought about a year ago. All updated with latest software/firmware, etc. Problems include:
-Sometimes when i pull down the network list, my network isn't even there, yet i'm still connected to it. My airport is appx 10 feet away in an open area.
-usually after opening safari or firefox for the first time upon sleep, restart, or just opening the program after i had quit it, it is miserably slow. it takes about 2 minutes for pages like msn.com to load. finally when they do, its faster than you can imagine. that lasts for about a minute. then its slow again.
-when logged into ichat and i send messages, i would sometimes get a "connection timeout" message. my buddy would end up getting the message about 5 minutes later.
My iphone and dell laptop work fine. i haven't tried running parallels, but if bootcamp works, so should prlls.
I've reset the modem about 20 times. i've reset the airport about 20 times. i even re-installed my OS on the mac and nothing has done it.
Weird thing is that i've had my mac for 6 weeks, and this problem surfaced only 3 days ago.
Clearly its not an issue of any of our ISP's. Due to the fact that this only started for me 3 dyas ago, i'm hopeful that its only a software problem and not something else. Hopefully apple will a) ADMIT THEY HAVE A PROBLEM HERE and b) FIX IT.

Core 2 Duo Macbook wireless problem

hey everyone, i am new to this as i have had my macbook for 3 months and nothing has gone wrong until now. I have had problems with my macbook and my linksys wireless router. the other computers in my house are pcs and they work fine with the router. the minute i connect my macbook using airport, the network crashes or loses its signal strenght with all of the comps. does anyone know how to solve this problem or have there been any other situations like this. any help would be greatly appreciated.

Hi all & especially any Apple Support engineers who may be able to help with a fix on this!
I've just purchased my first mac (Dec 06), one of the new 2GHz Intel Core 2 Duo Macbooks, and I'm very very pleased with it, apart from this one thing...
I also have wireless access problems - I can't get the Macbook to AirPort connect to my BT-supplied 2-Wire 1800HG (Home Gateway) router, even after applying the recent 'AirPort Update 2006-002 13-Dec-06'. It seems to be a problem with just particular router families (may be wider than just 2-Wire products) as I could AirPort connect just fine to my parents wireless network while staying with them over Christmas. They use a UK phone company (BT) provided Voyager Wireless router, so a different brand, but with exactly the same wireless security as I do (128 bit WEP).
Before anyone asks, I know my router wireless setup works because other wireless products in my home (including an Apple Airport Express I use for iTunes streaming) work just fine! It seems to be a MacBook vs. 2-Wire thing!
The Macbook works fine when connected into one of the router Ethernet ports directly using a cable, but that's not exactly convenient for use in other rooms in the home!
So it looks like another revision of 'AirPort Update xxxx-xxx' is needed, this time with the necessary data for the 2-Wire router family (as must already exist in my 1.5 year old Airport Express!)
Please can you fix this for me Apple (and let me know when it's been done!)
Many thanks and Happy 2007!
Mark
Ipswich, UK
Macbook (Core 2 Duo) Mac OS X (10.4.8) 2-Wire 1800HG Wireless Router

I install windows 8 in my macbook pro, the problem is it cannot detect wifi connection and bluetooth

I install windows 8 in my macbook pro, the problem is it cannot detect wifi connection and bluetooth, because when i click the wireless in settings there are no choices... but when i use the mac os, everything is fine, the wifi, the bluetooth everything is functional, can you help me fix this problem? help will be much appreaciated.. thanks

How did you install Windows? Did you use Bootcamp Assistant or did you use a virtual machine like Parallels, Fusion, or VirtualBox.
If you used Bootcamp Assistant, did you download and install the Windows Support software (drivers) in accordance with the Bootcamp instructions?

Cisco ISE AD (Windows Server 2013) Authentication Problem

Background:
Deployed two Cisco ISE 1.1.3. ISE will be used to authenticate wireless users, admin access to WLC and switches. Backend database is Microsoft AD running on Windows Server 2012. Existing Cisco ACS 4.2 still running and authenticating users. There are two Cisco WLCs version 7.2.111.3.
Wireless users authenticates to AD through ACS 4.2 works. Admin access to WLC and switches to AD through ISE works. Wireless authentication using PEAP-MSCHAPv2 and admin access wtih PAP/ASCII.
Problem:
Wireless users cannot authenticate to AD through ISE. The below is the error message "11051 RADIUS packet contains invalid state attribute" & "24444 Active Directory operation has failed because of an unspecified error in the ISE".
Conducted a detailed test of AD from ISE. The test was successful and the output seems all right except for the below:
xxdc01.xx.com (10.21.3.1)
Pinged:0 Mins Ago
State:down
xxdc02.xx.com (10.21.3.2)
Pinged:0 Mins Ago
State:down
xxdc01.xx.com
Last Success:Thu Jan 1 10:00:00 1970
Last Failure:Mon Mar 11 11:18:04 2013
Successes:0
Failures:11006
xxdc02.xx.com
Last Success:Mon Mar 11 09:43:31 2013
Last Failure:Mon Mar 11 11:18:04 2013
Successes:25
Failures:11006
Domain Controller: xxdc02.xx.com:389
    Domain Controller Type: Unknown DC Functional Level: 5
    Domain Name:            xx.COM
    IsGlobalCatalogReady:   TRUE
    DomainFunctionality:           2 = (DS_BEHAVIOR_WIN2003)
    ForestFunctionality:           2 = (DS_BEHAVIOR_WIN2003)
Action Taken:
Log on to Cisco ISE and WLC using AD credentials. This rules out AD connection, clock and AAA shared secret as the problem.
2)     Tested wireless authentication using EAP-FAST but same problem occurs.
3)     Detailed error message shows the below. This rules out any authentication and authorization polices. Before even hitting the authentication policy, the AD lookup fails.
12304 Extracted EAP-Response containing PEAP challenge-response
11808 Extracted EAP-Response containing EAP-MSCHAP challenge-response for inner method and accepting EAP-MSCHAP as negotiated
Evaluating Identity Policy
15006 Matched Default Rule
15013 Selected Identity Store - AD1
24430 Authenticating user against Active Directory
24444 Active Directory operation has failed because of an unspecified error in the ISE
4)     Enabled AD debugging logging and had a look at the logging. Nothing significant and no clues to the problem.
5)     Tested wireless on different laptos and mobile phones with same error
6)     Delete and add again AAA Client/Devices on both Cisco ISE and WLC
7)     Restarted ISE services
8)     Rejoin domain on Cisco ISE
9)     Checked release notes of ISE 1.1.3 and WLC 7.2.111.3 for any open caveats. Nothing found related to this problem.
10)    There are two ISE and two WLC deployed. Tested different combination of ISE1 to WLC1, ISE1 to WLC2 etc. This rules out hardware issue of WLC.
Other possibilities/action:
1)     Test it out on a different WLC version. Will have to wait outage approval to upgrade WLC software.
2)     Incompatibility of Cisco ISE and AD running on Microsoft Windows Server 2012
Anyone out there experienced something similar of have any ideas on why this is happening?
Thanks.
Update:
1) Built another Cisco ISE 1.1.3 sever in another datacentre that uses the same domain but different domain controller. Thais domain controller is running Windows Server 2008. This works and authentication successful.
2) My colleague tested out in a lab environment of Cisco ISE 1.1.2 with Windows Server 2012. He got the same problem as described.
This leads me to think there is a compatibility issue of Cisco ISE with Windows Server 2012.

Does anyone know if ISE 1.1.3 p1 supports AD DCs running 2012, if not which patch is required ot version?
Worryingly when ISE joins a 2012 DC it states it's connected successfully, and if another 2003 DC is available in that datacentre it will perform the auths against that DC whilst actually advertising (Connections in the GUI) that it's connected to the 2012 DC. We ended up mapping 8 PSN IP’s to another datacentre which has one Win2003 servers whilst the old 2003 DC is being promoted back, the 8 ISE servers started working, even though they still advertised they were connected to the 2012 DCs in the original datacentre - I performed a leave and join on one PSN and only then did it advertise that the node was connected to a DC in a different datacentre

Wireless authentication to a windows network

IF this is the wrong group please let me know and I will re-post...
I am trying to solve some problems authenticating to a windows network using a airport card....
I keep getting a non-trusted certificate message after/during the 802.x authentication box..We are not using certificates, at least that is what the admin tells me...so I have logged in as root, opened keychain and set the certifcates in question to trust always for all settings...I log out and then relogin as a normal network account and I still get the message which I can click continue and now I have access..
the other problem is that my home folder will not mount...I have to mount it manually through the finder..I am assuming this is because the airport network services are not running until I authenticate locally with a cached password....Is there a way to have the login window authenticate through airport so I can have my home directory mount automatically...
thanks for your help...

unfortunately there are severla problems with the solution and it really doesn't address the issue. I can't mount the volume on the dock as it won't mount, probably because it is the server itself that has been mounted, not the shared home folder. Also it might create a conflict by having an alias to the home folder that would conflict with the auto mounted home folder when I use the ethernet as a connection source. What I have is a multi-purpose machine.
1) I use a hardwired connect at my desk...
2) If I need to go somewhere that a port in the wall is not active, I can then use a wirless connection which allows me access to everything I need....
What I need to do is get this working so that the rest of the area can use it as well....
So the question still remains: Does the wireless authentication not mount the home directory because it is not tied into the login window. For example, in a hardwired case I login to the system and this authenticates me and mounts my home folder. When I unplug the ethernet cable and turn on ariport and log off I login to the login window but the 802.x box comes up and asks for my password....which then brings up a not trusted certificate. Which I have tried everyhting I know to make this accepted by the system, including logging as root and going into keychain and setting it to be trusted. This DOES not work. I still get the untrusted certifcate message and the home directory does not mount. So what I need is someone who is authenticating to a windows network using wireless. I have followed all the 802.x suggestions which include using only peap to authenticate through.
I hope someone can tell me how to stop the untrusted certificate error and how to mount the home directories. It would seem that there should be some type of setting to make airport startup prior to the login window or be hooked into the login window and pas that through to the wireless authentication. This is beyond my experience as you can see...
thanks

802.1x wireless authentication with certificates

Hi.
I have configured and working 802.1x authentication with certificates for Wired connections. with no problem.
when i try to authenticate the same machine with 802.1x and certificates , on Wirelss, the ACS rejects it with:
"12520 EAP-TLS failed SSL/TLS handshake because the client rejected the ACS local-certificate."
the ACS is the same, the certificate the same, and the root ca is the same.
what's hapenning????
Antero Vasconcelos

What supplicant are we using for wireless authentication? Do we have complete chain of certificates installed on the client machine? Can you check if we have root CA/intermediate correctly installed in client and ACS.
~BR
Jatin Katyal
**Do rate helpful posts**

Fix for Airport Wireless Connection Problem stating Self-Assigned IP and not wanting to connect in Lion OSX.

Fix for Airport Wireless Connection Problem stating Self-Assigned IP and not wanting to connect in Lion OSX.
Bought my girlfriend the newest Macbook Pro 13" and began experiencing problems with my wifi the moment we got home. Her Macbook would not connect to our home Wi-Fi while my old Macbook Late 2008 running Snow Leopard connected without a problem. Airport would say that it had a Self-Assigned IP address (168.x.x.x). Did not realize it was a Lion problem until after using her Macbook Pro and becoming jealous of the new OSX, I upgraded. Soon after I was unable to go online. Luckily I had my iPad 2 and I began to scoure the net for help. Ran into allot of suggestions but it was not until I tried the following all together was I able to share the good new, from my Macbook. Hope this works:
First go to Preferences > Network and click on the cog next to the + and - on the sidebar and click Set Service Order
     - Move Wi-Fi to the top and click ok.
     - Set location to Automatic
     - Click Apply
     - Click Advanced
     - Click the "-" on the selected Wi-Fi router you wish to connect to
     - Click Apply
     - Click Lock to Prevent Further Changes
Go to your Mac's harddrive, (Macintosh)
     - Go to Library > Preferences > SystemConfiguration >
     - Delete "com.apple.airport.preferences.plist" file
Turn off your computer
     - push and hold Option+Command+R+P
     - turn on computer
     - when the grey screen turns on you will hear the OS X "ON" sound (for lack of a proper term) and it will momentarily restart.
     - you will once again hear the "ON" sound, let go of all keys.
     - this resets your PRAM
Go to Preferences > Network > Advanced > + sign
     - click Choose a Network
     - Select your network and enter password
Viola!!! I tried this on my Macbook Late 2008 and my girlfriends new Macbook Pro 2010

     No you are clearly mistaken. The Self-Assigned IP address problem exists on many Macbook Pro models, including the current model, which I mentioned as being the original computer with the problem. While my 2008 Macbook is older it was working perfectly on Snow Leopard and didn't suffer issues until switching to Lion. So clearly the problem exists on the operating system and not so much the hardware.
     I called Apple Support and they had no fix for the problem and told me that this would hopefully be addressed in a subsequent update. It wasn't until I came accross the answer after trying many different methods that I got both of the Macbooks to connect to my router. Otherwise I wouldn't or could not have been surfing the internet for the last 4 months.
Cheers.

A Fix for Wireless Connection Problems

I’ve been struggling with connection problems for a week. Thankfully, I found a fix. Your mileage may vary, but this may be your answer:
Fix for Wireless Connection Problems on MacBook Pro

Yeah BR, please tell me what your cure is. I have the same setup as you, Vista with the same wireless card you have. Cannot stay connected to the internet. Have spent hours on the phone with tech support and they can't fix it. I hate this f....ing computer, will never buy another one. Please let me know what you did. Once I get it running right I'm selling it and will buy a cheap Dell, never have any problems with them. I have keyboard problems, capital letter problems, connection problems, and download can take 1 to 2 days. Pure BS!!!!!!!!!!!!!!!!!

Secure wireless authentication

I have just been reading all the posts about secure wireless access and I am
not happy with the direction Novell has chosen to take.
I have been extremely pleased with Netware, GroupWise & ZenWorks but Novell
is starting to loose it's appeal.
Let me summarize what I have learned and see if I have made any mistakes
with my understanding.
1. Novell has stopped development on their Radius server and have no plans
to resume development.
2. Novell contributed code to the open source FreeRadius project.
http://www.novell.com/news/press/arc...2/pr05008.html
3. There isn't any Radius server with 802.1x authentication that runs on
Netware (Netware kernel).
a. Novell's Radius server (BMAS or the newer NMAS server) doesn't do
802.1x authentication.
b. I have contacted Funk and this is their reply. Steel-Belted Radius
Server will run on Windows and Solaris (Linux is coming).
http://www.funk.com/News&Events/sbr_linux_pn.asp
c. MTG House hasn't gotten back to me about a solution for Netware. (I
am doubtful, I didn't find anything on their website.)
4. You need to run a Radius server that does 802.1x authentication and will
work/integrate with eDir.
a. FreeRadius (Linux) will integrate with Edir.
http://www.novell.com/documentation/...ius/index.html
http://www.novell.com/coolsolutions/feature/15383.html
b. Funk's Steel-Belted Radius server (Windows, Solaris & Linux is in
beta).
http://www.funk.com/radius/default.asp
c. Aegis Server
http://www.mtghouse.com/products/aeg...er/index.shtml
5. You need a 802.1x Client to authenticate to a Radius server for wireless
authentication.
a. Microsoft has 802.1x support in their client. (read this from other
posts in this forum)
b. Novell isn't planning on putting 802.1x support in the NW Client.
(read this from other posts in this forum)
c. There are 2 Radius clients that integrate with the NW Client for
Radius Edir authentication.
1. Funk's Odyssey Client ($45 - $50 per workstation depending on
quantity) + added annual maintenance costs.
$2281.25 for 50 Client licenses & annual maintenance.
http://www.funk.com/radius/wlan/wlan_c_radius.asp
2. Aegis' Client ($32 - $39.99 per workstation depending on
quantity) + added annual maintenance costs.
$2240.00 for 50 Client licenses & annual maintenance.
http://www.mtghouse.com/products/aeg...nt/index.shtml
http://www.mtghouse.com/novell_app_note_122204.pdf
3. When FreeRadius is integrated with Edir is this separate client
still needed?
I didn't see anything about a separate client being needed while
reading the Integrating FreeRadius with Edir documentation.
6. FreeRadius support is going to be built-in to the next version of Edir.
http://www.novell.com/news/press/arc...2/pr05008.html
Why didn't Novell contribute code to port FreeRadius to Netware?
At this point in time they are still giving us a choice between the Netware
kernel and the Linux kernel. To me that says they are willing to make
things work with both systems until they drop support for the Netware
kernel. Ok, so give me support for 802.1x authentication in the Netware
kernel. I don't have stray single purpose servers floating around my
network and I don't want to have to begin that practice just to get Radius
802.1x authentication working.
I also won't put my district at a disadvantage by upgrading to the Linux
kernel until I know Linux well enough to administer it properly. I am the
IT department at this district so I don't have a great deal of extra time to
run about learning the new things I would LOVE to learn. I'm sure I'm not
the only person in this situation so Novell should take these things into
concideration before they just drop support for a product they say they are
still supporting. Obviously all of the real support is going toward the
Linux side at Novell.
Daniel Blake
Milford Central School

Ok, I'll give them the benefit of the doubt and say fine the Netware kernel
might as well be considered dead. So they are giving me support via
FreeRadius if I just migrate to OES (Linux). Ok, I might/can live with that
as a Novell decision.
But that still doesn't explain why they don't give us some client to log in
via 802.1x. Giving us the server but not the client is like giving us a
locked door without a key. That's just plain stupid. I would rather stay a
Netware - OES shop, but if Novell can't think something this simple through
then I'm a little nervous about staying with them. What could they think up
next?
I guess Novell has decided to port all it's software to Windows cause it
sucks so bad at business decisions. GroupWise & ZenWorks run completely on
Windows now, so why do I need OES at all? Except for complexity &
integration issues of course. I mean why would I need to purchase Edir for
Windows if I didn't stay with OES? Or Nsure Identity Manager for that
matter. So if we start looking deeper into this we see Marketing all over
this thing. Novell Marketing has always done such a good job for Novell.
Novell has given me a real choice that will work though. If I migrate
completely to a Windows network it just works without any added costs. Heck
it even makes my installs easier without having to install the NW Client on
every new workstation. I can still run ZenWorks & GroupWise too.
Now, how is Novell Marketing going to screw up and make me hate GroupWise &
Zenworks so I migrate completely away from Novell products? Way to go
Novell!
Daniel Blake
Milford Central School
"Jim Michael" <[email protected]> wrote in message
news:[email protected]...
> mcsdtech wrote:
>
>> 1. Novell has stopped development on their Radius server and have no
>> plans to resume development.
>
> Correct, so far as we know.
>
>> 2. Novell contributed code to the open source FreeRadius project.
>> http://www.novell.com/news/press/arc...2/pr05008.html
>
> Yes. Code to allow easier integration with eDirectory.
>
>> 3. There isn't any Radius server with 802.1x authentication that runs on
>> Netware (Netware kernel).
>
> Correct.
>
>> a. Novell's Radius server (BMAS or the newer NMAS server) doesn't do
>> 802.1x authentication.
>
> Correct. It was developed quite a while before 802.1x even existed.
>
>> b. I have contacted Funk and this is their reply. Steel-Belted
>> Radius Server will run on Windows and Solaris (Linux is coming).
>> http://www.funk.com/News&Events/sbr_linux_pn.asp
>
> Correct, but Stell-Belted Radius is probably the last solution I would
> look at. Radiator is a commercial product that runs on Linux or Windows
> (it is Perl-based) and you will get far better support from them on
> eDirectory issues and general Radius problems. freeRADIUS is what I would
> run on Linux if you don't want to spend a dime on the software.
>
>> c. MTG House hasn't gotten back to me about a solution for Netware.
>> (I am doubtful, I didn't find anything on their website.)
>
> Not familiar with them.
>
>> 4. You need to run a Radius server that does 802.1x authentication and
>> will work/integrate with eDir.
>> a. FreeRadius (Linux) will integrate with Edir.
>> b. Funk's Steel-Belted Radius server (Windows, Solaris & Linux is
>> in beta).
>
>> c. Aegis Server
>
> And Radiator (what I run) http://www.open.com.au This is the solution we
> run.
>
>> 5. You need a 802.1x Client to authenticate to a Radius server for
>> wireless authentication.
>
> Correct.
>
>> a. Microsoft has 802.1x support in their client. (read this from
>> other posts in this forum)
>
> Correct. Technically, the "support" is in Windows, not the MS client.
>
>> b. Novell isn't planning on putting 802.1x support in the NW Client.
>> (read this from other posts in this forum)
>
> Correct.
>
>> c. There are 2 Radius clients that integrate with the NW Client for
>> Radius Edir authentication.
>> 1. Funk's Odyssey Client 2. Aegis' Client ($32 - $39.99 per
>> workstation depending on
>
> Correct.
>
>> 3. When FreeRadius is integrated with Edir is this separate
>> client still needed?
>
> Yes. You ALWAYS need a 802.1x supplicant (client) on the workstation.
> Windows has one built-in, which works FINE against eDirectory. HOWEVER,
> because of the way it works you must log into eDirectory *after* fully
> logging into windows. That is unacceptable to most organizations (you
> would have to manually log in and map drives to NW, etc). This is why
> there are third-party clients that integrate specifically with the NetWare
> client.. they allow the 802.1x authentication to "insert" itself
> in -between the Windows and eDirectory login, thus preserving all of the
> normal features like dynamic local user, zen policies, etc.
>
>> I didn't see anything about a separate client being needed
>> while reading the Integrating FreeRadius with Edir documentation.
>
> A client is always assumed.
>
>> Why didn't Novell contribute code to port FreeRadius to Netware?
>
> Because Novell's future direction is Linux, and there isn't much demand
> for a NetWare Radius server.
>
>> At this point in time they are still giving us a choice between the
>> Netware kernel and the Linux kernel. To me that says they are willing to
>> make things work with both systems until they drop support for the
>> Netware kernel. Ok, so give me support for 802.1x authentication in the
>> Netware kernel. I don't have stray single purpose servers floating
>> around my network and I don't want to have to begin that practice just to
>> get Radius 802.1x authentication working.
>
> You can always make your wishes known at
> http://support.novell.com/enhancement
>
>> I also won't put my district at a disadvantage by upgrading to the Linux
>> kernel until I know Linux well enough to administer it properly. I am
>> the IT department at this district so I don't have a great deal of extra
>> time to run about learning the new things I would LOVE to learn. I'm
>> sure I'm not the only person in this situation so Novell should take
>> these things into concideration before they just drop support for a
>> product they say they are still supporting. Obviously all of the real
>> support is going toward the Linux side at Novell.
>
> I understand the frustration, but I doubt things will change. There is a
> big difference between "supporting" existing products and adding major
> enhancements to products to support new standards. I just don't think
> Novell believes it is worth dedicating development resources to enhancing
> Radius on NetWare, for those few that can't/won't run a Linux or Windows
> box where the software already exists.
>
>
> --
> Jim
> NSC SYsop

My MacBook Air has problems connecting to a saved network when I first open it.

My MacBook Air has problems connecting to a saved network when I first open it. When it idles, the connection gets lost and even clicking on the network won't connect it. Then I have to turn off wireless and turn it back on for it to connect. My boyfriend's MacBook Pro does not have this same problem and this problem started maybe 2 months ago and nothing about our internet or router has changed, and its only my computer having the problem. Its a 2013 MacBook Air and my softward is: OS X 10.9.1 (13B42). Please help!

Hello, nheredia05.
Thank you for visiting Apple Support Communities.
There are a couple steps that I could recommend trying. Power cycle the router and test to see if the behavior persists. Next, try an remove this prefered network from your list and then add it back again. Make sure all firmware updates have been processed on the router side and the settings have been optimized for performance. If the issue still persists try the steps in the second article.
iOS and OS X: Recommended settings for Wi-Fi routers and access points
http://support.apple.com/kb/ht4199
About Wireless Diagnostics
http://support.apple.com/kb/HT5606
Cheers,
Jason H.

We have dsl and apple extreme router, 2 iphones, 2 ipads a pc and a macbook. wireless speeds are terrible until the macbook is disconnected, then speeds are normal. ideas?

we have dsl and airport extreme router, 2 iphones, 2 ipads, a pc and a macbook. wireless speeds are terrible until the macbook is disconnected, then speeds are normal. ideas?

generalgeorge wrote:
This is a new issue on an old setup. The mac was recently upgraded to maverick. thanks
Say no more.. upgrading to Mavericks.. any upgrade install is prone to issues.. the Mavericks one is the worst of any recent upgrades.
Lets just try and isolate the problem.
In the setup of the AE, give different names to the two wireless bands.. so go into the airport utility.. click the AE, Click edit.. click the wireless tab.. and now type in a new name.
Try AE24ghz
Then click the wireless options and change the name for the 5ghz..
Make it AE5ghz
Then update the AE.
In the computer.. select either band.. and see if your other clients are affected if they use the band that the Mac is not using.
Alternatively turn off wireless in the macbook and use ethernet.. oh please please have a Mac with an ethernet port.. otherwise buy a Thunderbolt to Ethernet adapter.. it is well worth having. wireless is never to be trusted.

Tablet will not connect to router it is saying authentication problem

Tablets saying authentication problem after password is put in,and i dissconected my phone now that wont connect

Hi whittydaz,
Thanks for posting onto the Forum,
It's not good to see that you are having trouble connecting to the Sky Router with your wireless devices. Can you please tell me if you are able to connect to a device wired at all? What lights are appearing on your Sky router at the moment?
Have you reset your Sky Router by pressing and holding the button on the back of the router for longer than 30 seconds?
Please let me know the answer to these questions and hopefully we can get to the bottom of this
Cheers,

Macbook Wireless Authentication Problem

Similar Messages

Maybe you are looking for