search for: dc_msdcs

...p the names of the domain controllers to their IP addresses are missing or contain incorrect addresses. - Domain controllers registered in DNS are not connected to the network or are not running. --- Now, as far as I have gotten is, that the problem lies in (internal) DNS. If I query for _ldap.tcp.dc_msdcs.O.M.S I get the SRV record o.o.m.s instead of o.m.s $ host -t SRV _ldap._tcp.dc._msdcs.O.M.S _ldap._tcp.dc._msdcs.O.M.S has SRV record 0 100 389 o.o.m.s. Does anyone have any idea what is there for me to do, to get this working? I've searched the internet for solution and haven't found on...

...e the following Microsoft web site: http://go.microsoft.com/fwlink/?LinkId=5171 The specified domain either does not exist or could not be contacted. [ OK ] </snip> went to the link and followed instruction in how far possible with Samba and saw something about the _ldap._tcp.dc_msdcs record. added that (_tcp._ldap.dc._msdcs.ifs. SRV 0 0 0 .) to my config, but still no succes (thought that wouldn't do much anyway, since the link says it's only to reduce unneccessary traffic). Samba show's _only changes in nmbd-logfile_: <snip> [2003/08/25 14:30:00, 4...