This is a forward from a customer: ---------------------------------------------------------------------- We are facing a crucial defect on joing ADS domains on private subnets. "private", in this case, means no DNS information. Many, many people here test the server in private subnets that have no DNS, and they have come across this defect. We reproduced the defect in mixed-mode ADS on a private subnet. The W2K ADS server was working fine, and we have a Linux router on the subnet (no connected to anything outside) that is also a DHCP server (NOT handing out any DNS server). On trying to join a ADS domain, we did a network trace, and it appears the correct information is not reaching the ADS server for some reason. Adding the server to /etc/hosts on the NAS system did not help. the client in these cases reports: "Unable to update server." ----------------------------------------------------------------------- I have the network trace available but it contains sensitive information to a customer so ask privately to get it.
If you are using multiple subnets, then you must either have DNS or WINS. It sounds like you have neither. Look at get_dc_name().
This is with a one subnet, not with multiple ones. I've sent a trace to you.
Customer identified a man-in-a-middle error: engineer mixed user names during join process resulting in unwanted behaviour. So it was configuration error. Change status to INVALID.
Verified with the customer. We might document a need to specify IP address in the case and not host name in smb.conf to get it working.
originally reported against 3.0.0beta3. CLeaning out non-production release versions.