Previous 1 2 Next 24 Replies Latest reply: Jan 18, 2013 9:24 PM by JohnTh
bigjeffy Level 1 Level 1 (0 points)

I have two MacBook Pro Retinas in my business environment. I have both joined to the domain with network logon functionality enabled, however I cannot pass credentials to our wireless network prior to loggig into the machine. I cannot log into the machine because it is not connected, and therefore cannot validate my credentials for the first time in order to cache them locally.

 

I finally broke down and bought two tunderbolt to ethernet adapters so I could just plug into my wired network and deploy these machines. I am not connected, however the MacBook will not "connect" to the wired network until I've logged into the machine, so I am still faced with the same issue. How can I have the MacBook connected to the network so that I can use network auth credentials to log in?


MacBook Pro with Retina display, OS X Mountain Lion (10.8.2)
  • JohnTh Level 2 Level 2 (365 points)

    Are you saying that both your MBP's dont find the wireless network at all at work? Are you connected directly to the router at work wirelessly (before the problem)? Have you taken it elsewhere to see whether you have the same issues?

  • bigjeffy Level 1 Level 1 (0 points)

    It doesn't authenticate to the wireless until after the user has logged in, because our wireless network requires username and password authentication.

     

    At this point I am more concerned with why the wired adapter isn't connecting prior to login.

  • JohnTh Level 2 Level 2 (365 points)

    Lets take the 2 issues separately. When you click the WiFi icon on the top of the screen, what do you see? Do you see 'Looking for Networks ...'? Do you see your own network? Can you then join it if you select it? Lets keep the wired option for after we resolve the wireless option ...

  • bigjeffy Level 1 Level 1 (0 points)

    You cannot click on the wireless icon prior to logging into the machine. It is greyed out and has no function at the login screen. That is why we bought the wired adapters.

  • JohnTh Level 2 Level 2 (365 points)

    At this point its difficult to ascertain whether its the airpot on your MBP or your wireless setup at the office or the network login program. The fact that it doesnt connect even with a wire isnt any help either. Is this machine setup ONLY to be used at work? That is, can you take to a cafe to see if you get a wireless connection? Could you check with the person who set this up in the first place?

  • bigjeffy Level 1 Level 1 (0 points)

    It get's a connection fine once logged in, but you are missing the point of what I am saying. I need a persistant network connection prior to logging in. This is not supported in OSX using a wifi connection on a wpa2-enterprise peap network which requires authentication to join. OSX does have have a method for selecting your wireless network or passign auth credentials to join a network from the user login screen.

     

    If you want to treat them seperately, then can we just focus on why the ethernet lighting bolt adapter doesn't link up at the login screen?

  • JohnTh Level 2 Level 2 (365 points)

    Actually, I can't say a thing at this point because of the way your MBP is setup. And a login only when you have a persistent wireless connect is daft (my opinion only).

  • bigjeffy Level 1 Level 1 (0 points)

    A login only when you have a persistent connection is a limitation of overall design, windows and osx alike. How is a computer supposed to auth your credentials against an administration server if it cannot talk to the server that holds the usernames and passwords?

     

    Once I get it logged in the first time, it will cache the credentials, but how do I get it to auth that first time if it will not connect to the network to check the password?

  • bigjeffy Level 1 Level 1 (0 points)

    Here is my question that is independent of my configuration or network.

     

    Why does the thunderbolt ethernet adapter disconnect when there is no user logged in? This is not that case on other platforms and is counter intuitive to a wired network connection.

  • JohnTh Level 2 Level 2 (365 points)

    'A login only when you have a persistent connection is a limitation of overall design, windows and osx alike' ,,, Yes, that is accurate. You're presuming that after the first login, it will connect. Not so if the wireless networks drops. Most wireless issues on this Community is a testament to that. If you disconnect the wire, i.e. you basically dont have the Internet, you will be automatically logged out within a specific period of time because THATS how network security is built. At least, mostly. Hopefully, someone can guide you in this. But with the limited information available, there's no much that I can say. Your best bet is to fix this issue with the person who has setup your network.

  • bigjeffy Level 1 Level 1 (0 points)

    "You're presuming that after the first login, it will connect."

    I'm not presuming. If I use a local account instead of network credentials, then wifi does ask me for credentials and connects just fine. It holds its connection perfectly once a user is logged in.

     

    Same with the thunderbolt adapter. If I use a local account instead of network credentials, then the thunderbolt adapter pulls an ip and connects me to the network as soon as the user is logged in. Connection is maintained and there are no issues.

     

    I don't know what else to say to get you to stop talking/thinking about the wireless. My concern is why the wired connection has no link light until a user is logged in. This breaks network credential authentication and is not how MacBook's with built in ethernet ports behave.

     

    You have 100% of the information. Thunderbolt ethernet is not working until I log into the laptop. I am the person who set up the network, and there is nothing to restrict link functionality to wait for a user to login. The network doesn't even know if you're logged in or not, it only knows if something is plugged in or not.

     

    Wired connections work 100% fine on MacBook's with built in ethernet, but the same behavior is not happening on thunderbolt ethernet adapters.

  • JohnTh Level 2 Level 2 (365 points)

    You never did mention until now that you were the person who setup the network. Since that is the case, why not isolate what and where exactly is the problem? Is it the hardware? The software? Or the networking aspect? I'd suggest that you bring up your issue with some of the top participants in the MBP community.

  • GW77 Level 1 Level 1 (10 points)

    Well i think I have the same setup as BigJeffy and I setup a macbook air using 1. usb ethernet, 2. thunderbolt ethernet and 3. wifi to binded to AD for authentication.

     

    I have to use a local account to get the mac booted, then after it is booted I can logoff and THEN use any of the 3 methods listed above and authenticate to our AD domain, it even creates a mobile account. But then on next restart it wont show me the AD authenticated accounts. Only the local accounts. But again after I logon with the Local account and logoff then and only then the AD authenticated accounts show up to be used.

     

    So the similarity is how do we get the mac to reconize that there are available network resources such as usb eithernet or thunderbolt ethernet to use to authenticate.

     

    The sad thing is we may have to ban all non-ethernet built in macs if we can not get this to play well. We have imacs and mac-minis that authenticate just fine on boot up. Just the external ethernet systems have the issues.

  • JohnTh Level 2 Level 2 (365 points)

    My suggestion in case of a problem remains the same as in the post just above, 'Why not isolate what and where exactly is the problem? Is it the hardware? The software? Or the networking aspect?' After that if there is still an issue, then its best to provide a feedback to Apple either as a problem or as an enhancement. And of course the support community where they may be someone who could provide you with an answer that works.

     

    In BigJeffy's case, I suggested that he bring up his issue with some of the top contributors. But as you can see, he still hasnt done that (at least in the MBP community). If he has been successful and had said so here, you as well as others in the same predicament would have benefited from the knowledge shared. Which is the reason this community exists.

     

    My suggestion is for you to do what you think is the best for you given what you know. If that means 'banning' all external Ethernet systems, then so be it.

Previous 1 2 Next