Thanks Jerry -
I'll follow that other discussion. It looks like the solutions there are way
over my head at this point. I'll hold out for an easier bug fix. Thanks for
your work on this. I love the concept of Likewise and it could be a powerful
tool to bring Linux into my Windows-only school
Paul, the cache issue is LP BUG 572271
--
password caching no longer works
https://bugs.launchpad.net/bugs/509934
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubu
I am experiencing this same problem in 10.04. I made the mistake of
upgrading from 9.10 when I was still joined to the domain. I think this
messed a few things up. I then had to completely uninstall LWO from
synaptic. After reinstalling LWO 5.4 from synaptic and rejoining the
domain I can join
I installed Ubuntu 10.04 RTM on an Acer Aspire Revo 3610 over the
weekend for testing. Likewise installation and domain joining went
smoothly. However, subsequent reboots and authentication attempts often
result in failure. I searched and found that bug #509934 and #510683 are
very similar to what
likewise-open (5.4.0.42111-2) lucid; urgency=low
* LP BUG #509934, #510683 - Don't fail to load the lsassd
ad-provider when we fail to add a domain to the trust list
* LP BUG #543730 - Add likewise-open5-gui transition package
* Fix the likewise-open-gui Gnome Administration menu item
** Changed in: likewise-open
Importance: Undecided => High
** Changed in: likewise-open
Status: New => Fix Committed
** Changed in: likewise-open
Assignee: (unassigned) => Gerald Carter (coffeedude.jerry)
--
password caching no longer works
https://bugs.launchpad.net/bugs/509934
** Also affects: likewise-open
Importance: Undecided
Status: New
--
password caching no longer works
https://bugs.launchpad.net/bugs/509934
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
1.) with the new version 5.4.0.42111-2~ppa2~lucid uploaded to
https://launchpad.net/~likewise-open/+archive/likewise-open-ppa
i was able to unplug network cable, power on machine and log in
with a DOMAIN\first.last.
Thank you very much for fixing this (without reproducing it)
and making it availab
Those packages work for me.
--
password caching no longer works
https://bugs.launchpad.net/bugs/509934
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mai
I think that this is an issue with the lsassd active-directory-provider
failing to load due to trusted domain detection failures. Please test
the 5.4.0.42111-2~ppa1~lucid packages at https://launchpad.net
/~likewise-open/+archive/likewise-open-ppa
** Changed in: likewise-open (Ubuntu)
Statu
I am on 64-bit LucidLynx with all updates, and likewise-open 5.4.0.42111-1.
(Dell Optiplex 745 or Dell Latitude E6400)
--
password caching no longer works
https://bugs.launchpad.net/bugs/509934
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
I have the same problem.
machine connected to network.
boot.
log in as DOMAIN\first.last.
shut down computer.
unplug network cable.
boot.
log in as DOMAIN\first.last.
"authentication failure"
I can only log in with local Linux accounts at this point.
I believe if I then plug network cable in, an
running lsassd as root, while offline, with loglevel debug:
20100323183710:VERBOSE:0xb7839940:[lsassd_main() libmain.c:132] Logging started
20100323183710:INFO:0xb7839940:[LsaSrvVerifyNetLogonStatus() libmain.c:364]
LsaSrvVerifyNetLogonStatus call to LWNet API returned 0
20100323183710:INFO:0xb78
Initially, I have no network cable plugged in at all. AD logins don’t
work. I then log in as a local user, connect to a wireless network
which cannot access the DC. AD logins still don’t work. I then connect
to a VPN which can access the DC, and restart lsassd and netlogond. AD
logins begin wo
All of this works just fine for me. I'm just trying to figure out what
the differentiating factor is in your environment. So you have no
network cable plugged in at all right? Not just connected to a
different network which does not have connectivity back to your DC? You
said in comment #1
Note that I say "I should be able to" do this, because it works with the
upstream likewise-open packages.
--
password caching no longer works
https://bugs.launchpad.net/bugs/509934
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
That bug seems to describe problems with lsassd starting before
networking is up, but that once they've brought networking up everything
is fine. This suggests that they're talking about live logins, i.e. not
cached logins.
Am I reading that wrong?
When I refer to cached credentials here, I mean
Alex, would you look at Bug #510683 and see if anyof the network
discussion applies to your environment? Thanks.
--
password caching no longer works
https://bugs.launchpad.net/bugs/509934
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ok. tried against with a fresh Beta1 install this morning (after
install the likewise-open deb from main). Still unable to repro the
offline login failure. Is there anything unique about your setup?
** Changed in: likewise-open (Ubuntu)
Status: Confirmed => Incomplete
--
password cachi
I am running 5.4.0.42111-1 from main, yes.
Assuming you need only the CMD list from that ps output:
lwregd, dcerpcd, netlogond, eventlogd, lwiod, lsassd
I am trying to login with DOMAIN\user, because if I try to use either of
the other formats then the login: prompt is cleared when I type the @..
I need more information. Couple of questions:
* What likewise-open version are you running now? 5.4.0.42111-1 from
main?
* After the reboot, what is the output from " ps --ppid `pidof lwsmd` "?
* What is the format of the name you are using to login when offline?
e.g DOMAIN\user,u...@domain, u
This still isn’t working for me. I’ve purged and reinstalled the
package, and rejoined the domain. Online logins work, but after a
reboot they don’t work.
** Changed in: likewise-open (Ubuntu)
Status: Fix Committed => Confirmed
--
password caching no longer works
https://bugs.launchpad.
nvm..the delays were caused by {pam,nss}_ldap on my system. Offline logons
appears to be working
properly in the new packages.
--
password caching no longer works
https://bugs.launchpad.net/bugs/509934
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
I get some delays when logging in by offline logons are confirmed to work in
the 5.4.0.42111-1~ppa2~lucid packages I'll be submitting for the first Beta.
** Changed in: likewise-open (Ubuntu)
Status: New => In Progress
** Changed in: likewise-open (Ubuntu)
Status: In Progress => Fi
Can confirm. Caching does not work after a restart.
--
password caching no longer works
https://bugs.launchpad.net/bugs/509934
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
** Changed in: likewise-open (Ubuntu)
Assignee: (unassigned) => Gerald Carter (coffeedude.jerry)
--
password caching no longer works
https://bugs.launchpad.net/bugs/509934
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
If I then connect to a VPN which can reach the domain and restart lsassd
and netlogond, I can once again log in as myself. Caching does work as
long as lsassd continues running.
--
password caching no longer works
https://bugs.launchpad.net/bugs/509934
You received this bug notification because
27 matches
Mail list logo
