What happens when you run this: nslookup -q=srv _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.democenter.berlin.pbgroup.lan
Fridtjof Busse wrote: > * Kyle Stemen <[EMAIL PROTECTED]>: > >> Could you try capturing the DNS packets from your other interface? >> > > lw-get-dc-name does not trigger any packets, even after restarting > netlogond. > But if I give the domain of the other AD server, it immediatly returns > the correct answer, so joining would most likely work. > Very weird. > > What turns up though is, when trying to get the information of the > other domain: > > 20081010165839:0xb7b6cba0:ERROR:[LWNetDnsQueryWithBuffer() > lwnet-dns.c:1155] DNS lookup for > '_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.democenter.berlin.pbgroup.lan > > Is there an DNS entry missing? > > >> Fridtjof Busse wrote: >> >>> * Yvo van Doorn <[EMAIL PROTECTED]>: >>> >>> >>>> Could you try running >>>> /opt/likewise/bin/lw-get-dc-name <your AD domain> >>>> >>>> >>> I think I got an idea what might be the problem: >>> The system has two interfaces, with an AD domain controller on each >>> of the connected networks (but the default nameserver hosts the >>> domain I'm trying to join). As soon as I run lw-get-dc-name with >>> the name of the other AD domain, it works. >>> So there's probably a lookup, but on the wrong interface (ethereal >>> only sniffs eth0). >>> How can I tell lw-get-dc-name to use a specified interface/network? >>> >>> >>> > > > _______________________________________________ Likewise-open-discuss mailing list Likewise-open-discuss@lists.likewisesoftware.com Found a bug? Please file a report: http://lobugs.likewisesoftware.com/
