Bug 7058 - first login fails when eth0 is managed by network-manager/wicd
Summary: first login fails when eth0 is managed by network-manager/wicd
Alias: None
Product: Samba 3.4
Classification: Unclassified
Component: Winbind (show other bugs)
Version: 3.4.3
Hardware: Other Linux
: P3 normal
Target Milestone: ---
Assignee: Michael Adam
QA Contact: Samba QA Contact
Depends on:
Reported: 2010-01-23 14:05 UTC by tatel (dead mail address)
Modified: 2020-12-29 14:00 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description tatel (dead mail address) 2010-01-23 14:05:21 UTC

Setting ubuntu karmic/debian squeeze clients to authenticate against a windows AD PDC server.

First login fails when eth0 is managed by either network-manager-wicd. winbind drops "Network is unreachable" on syslog and "Could not receive trustdoms" on log.winbindd. 

On Debian, with old-style init, setting eth0 on /etc/network/interfaces works nicely, I can log at first attempt either with network-manager and wicd.

On Ubuntu Karmic, with upstart, first attempt always fails

From syslog, it seems that, when eth0 is managed, winbind gets executed before is a proper connection up. A second login attemp works, however.
Comment 1 Kai Blin 2010-01-24 05:44:06 UTC
Seems to me like upstart fires up winbindd too early. Sounds to me like an Ubuntu Karmic issue, not like a Samba issue.
Comment 2 tatel (dead mail address) 2010-01-24 06:19:16 UTC
It was my first thought.

But I send it here because I get the same behaviour on Debian Squeeze, where there is old good system V init at work. 

Using network manager or wicd makes no difference, so, while I guess this is related to managing interfaces out of /etc/network/interfaces, I see that winbind is the only software involved in all cases. So sending here seemed the right thing.

Is this behaviour to be expected when interfaces are in "unmanaged" mode?
Comment 3 Björn Jacke 2020-12-29 14:00:51 UTC
if this isn't solved by now anyway, this is an integration problem of the distro, not a samba bug. Winbind is known to come up and work properly in a sane way.