Here we need PortFast enabled otherwise, I believe the machine does not come up with an IP address,then we have to manually, `sudo dhclient` to fix that problem. (that was true with HardyHeron)
Putting that aside, I have noticed that logging in with an active directory account after a reboot, does not always work. "authentication failure" So I put this in the /etc/rc.local as a work around: sleep 15 /etc/init.d/lsassd restart So worse case, a user has to wait 15 seconds prior to the initial failed log in. Without this delay and restart, I would have to log in to the machine, with a local account, and manually restart lsassd. I figured the problem was that everything starts up so fast on Linux, that the likewise stuff just doesn't help itself out, by trying to restart on its own. -- 'lsassd' has to be restarted in order to login https://bugs.launchpad.net/bugs/510683 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
