SADMS settings lost at reboot

Bug #665575 reported by Rémi BOULLE
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sadms (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: sadms

SADMS setting process is just fine. We can test AD authentication and it works.

After reboot, It doesn't work anymore. "No logon server". With a local account, on sadms window everything is green : domain and PAM but impossible to connect onto AD.

Tags: sadms

Related branches

Revision history for this message
Rémi BOULLE (rboulle) wrote :

It is on : Ubuntu 10.10

Revision history for this message
Rémi BOULLE (rboulle) wrote :

After a few more tests, it seems that avahi-daemon is a part of this issue... Thanks Bernard Bou for the hint.

A brutal : sudo apt-get remove avahi-daemon solved the problem.

Is avahi mandatory for Ubuntu to work properly ? Can we remove it while installing sadms ?
Thanks.

Revision history for this message
Rémi BOULLE (rboulle) wrote :

Read on avahi.org website :

====
If you come across a network where .local is a unicast DNS domain, please contact the local administrator and ask him to move his DNS zone to a different domain. If this is not possible, we recommend not to use Avahi in such a network at all.
====

Shall with exclude avahi when installing sadms ?

Revision history for this message
Bernard Bou (bbou) wrote :

This is due to Kerberos being very fussy with DNS. Name resolution of "local" domains is processed by avahi (see /etc/nsswitch.conf) and DNS is not even given a chance. And this is where we run into trouble.

A workaround is to remove avahi daemon altogether, as Rémi put it, which makes sense in an environment like AD, where naming is primarily handled by DNS.

Changed in sadms (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.