No Joy :-(
What worked yesterday, several times, today does NOT work! I used the Restore partition to repair disk permissions and then network accounts worked. It stayed working until a restart. Then network accounts were "not available". Doing the Permissions Reair from Restore brought the network back to working. This reapeated four or five times.
Today, I try the same thing and it does NOT work! INSERT VERY LOUD SCREAM OF ANGUISH HERE!!!!
I then tried doing a Onyx set of repair permissions, clean caches and so forth using a freshly downloaded copy of Onyx Lion. The first try after using Oynx allowed network accounts but it first showed the Red Dot (network accounts not availoable which changed to Yellow but still showing the "network accounts not available" message and then, after a few more seconds the dot vanished and my AD login worked just fine. Logged outr and logged back in and It worked three more times. Restart and back to the Red Dot. Neither Onyx or Restore partition repair permissions brought it back to even a Yellow on the next three tries.
INSERT EVEN LOUDER SCREAM OF ANGUISH HERE!!!!
This OS release should have been killed before it was ever released. Granted that AD is a Microsoft product and Apple doesn't like Microsoft a whole bunch but why Apple would let this Lion out of its cage before it was properly trained to work with AD is beyond comprehension!
I am wondering if there is any correlation to network infrastructure being used. I have a 100 M network I have to use and without students here now, if network timings and collisions or whatever are a problem, what can we expect when the network gets up to its normal load. If anyone has made AD work correctly, and REPEATEDLY, with Lion, what are you using for a network connection? When I ping the domain controller, the ping times I get range anywhere from .3 Ms to1.0 Ms. I am wondering if this variation in response time might have any correlation to why something will work one time but then not work again. If Apple has a response acknowledgement time that is to tight, could this be a problem area.
I do not work with the network hardware as such so my thoughts are purely speculative but I have noticed in recent months, when using ARD to access remote, on-campus, systems I have been getting a greater number of "communications failure" messages but when I try again, just a few seconds later, I can connect sucessfully. I am just beginning to wonder if, at least some of, the problem might not be centered in that area.