Previous 1 3 4 5 6 7 Next 133 Replies Latest reply: Jan 8, 2015 6:41 AM by ktonini Go to original post Branched to a new discussion.
  • cosmo88 Level 1 (0 points)

    That seemed to shed a little bit of light on the subject.

     

    https://discussions.apple.com/thread/2433780?start=0&tstart=0

  • Grant Bennet-Alder Level 9 (56,466 points)

    So the take-away from that other discussion is that a single stream stays on one side, and does not benefit from having two links sitting there? Only a mix of multiple traffic streams can be balanced across the two bonded links. Is that right?

  • Eric Barger Level 1 (15 points)

    Is Link Aggregation working in Mtn. Lion for the Mac Pro or not at this point? I got screwed by that after the update and don't want to even try if it is still an issue.

     

    TIA!

  • mart30lon Level 1 (0 points)

    Still an issue... Never known Apple to be this slack before!!!

  • mart30lon Level 1 (0 points)

    We all need to file bug reports daily until they pull their fingers out!!!

  • slubig Level 1 (0 points)

    What's interesting is this:

     

    I have a new Mac Mini server with an aggregate link between the onboard ethernet and thunderbot gigE adapter. I have a NetGear 108Tv2 and am having zero issues with that connection, even through restarts.

     

    My late 2010 MacPro on the other hand is experiencing the same issues as above.

     

    Please fix this Apple!!!

  • calmasacow Level 1 (0 points)

    Someone please email Tim Cook a like to this thread!!!!

  • Rosko255 Level 1 (0 points)

    We just purchased seven new MacMini servers and are experiencing this issue. Just spent 2.5 hrs on the phone with Apple Enterprise support and Alliance support. They basically told us we need to consult the manufacturer of our NIC...

  • mart30lon Level 1 (0 points)

    See this is exactly my issue with Apple now. The enterprise team have just completely lied to you. Instead of just admitting the issue and promising it will be fixed, they choose to lie and point the finger somewhere else!!! It all worked fine in Lion and Snow Leopard... It's nothing to do with anybody but Apple. This kind of shoddy dismissive behaviour is not a great sign for anybody using Apple software in an enterprise capacity... You guys over there in America need to start taking some direct action. Return your equipment as faulty and if they won't let you... Sue them! Call the enterprise team back and call them out on it... They have just fobbed you off!

  • Eric Barger Level 1 (15 points)

    Did you not use Apple NIC equipment???

     

    If so, how could they say that?

  • mart30lon Level 1 (0 points)

    And why your at it ask them why they think its ok to only 2% tax on foreign profits whilst charging more than the US for all Apple products... Then offer this kind of substandard customer service and deceitful behaviour!

  • NiqueXyZ Level 1 (0 points)

    Does ayone notice that if you are using the server.app -- when you create a bond of any kind - it does *not* show up in the network section of the server app...at all.  It's like the server can't use it.  Anyone else experiencing this problem?

  • ICE Tech Level 1 (0 points)

    Yes that's exactly what I get. So on a Mac Pro I bond the 2 ethernets, I can browse the internet with Safari, both bonds working but they don't show up in server app. So if you try and set up any services on the server it says that you don't have a network connection and won't work.

     

    It's been like this since day 1 of Mountain Lion, a clean install with the latest version makes no difference. Lion was ok.

  • mart30lon Level 1 (0 points)

    Has anyone had any luck getting anything out of the Enterprise AppleCare team as yet?

  • Rosko255 Level 1 (0 points)

    So we spoke with an Engineer again today. They have acknowledged the issue (was informed the person I spoke with yesterday gave me the wrong info) and are working to resolve it. But they won't say when (in traditional apple fashion) it is going to be release. At least we know now that the engineers are aware of it and working on the issue. We can hope that when 10.8.3 comes around it will fix it...hopefully.

Previous 1 3 4 5 6 7 Next