Resolution of a "domain" name at least in the shortened format you're discussing comes from Netbios. So where are the machines you're joining to the child domain getting their WINS info from, and does that location have the correct WINS information for your child domain? Another work around for this is ensuring that your client's are looking in the correct DNS suffix space, which can typically be assigned through DHCP. The "domain name" value, in DHCP can be used set's the default DNS suffix search zone for clients, which should also help new clients to see the domain name by the "netbios" name of the domain. HTH J -----Original Message----- From: windows2000-bounce@xxxxxxxxxxxxx [mailto:windows2000-bounce@xxxxxxxxxxxxx] On Behalf Of Matt Fowler Sent: Monday, July 12, 2004 10:09 AM To: windows2000@xxxxxxxxxxxxx Subject: [windows2000] adding workstation to child domain We have a 2003 Active Directory with an empty forest root and a child domain. When trying to add a workstation to the child domain, we have to input the entire domain path (child.parent.harpercollege.edu) instead of just the child domain name (child). Is this normal? I thought we'd be able to just add the machine to the domain name (child). Any thoughts? Matt Fowler LAN Specialist (847)925-6113 mfowler@xxxxxxxxxxxxxxx ******************************************************** This Weeks Sponsor StressedPuppy.com Games Feeling stressed out? Check out our games to relieve your stress. http://www.StressedPuppy.com ******************************************************** To Unsubscribe, set digest or vacation mode or view archives use the below link. http://thethin.net/win2000list.cfm ******************************************************** This Weeks Sponsor StressedPuppy.com Games Feeling stressed out? Check out our games to relieve your stress. http://www.StressedPuppy.com ******************************************************** To Unsubscribe, set digest or vacation mode or view archives use the below link. http://thethin.net/win2000list.cfm