>>If it is a name issue, how would I have >>been able to add it previously? Hmm.
Because Windows uses multiple name resolution methods. Without knowing the details of your environment, I can speculate that the domain controller may have at one time been handling the browser issues for your segment, but now some other machine is handling that role, and doesn't have all the info for the domain. ASB http://www.ultratech-llc.com/KB -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Adam Smith Sent: Thursday, December 05, 2002 12:16 AM To: NT 2000 Discussions Subject: RE: Adding Server to Domain > This seems like a name resolution issue. > > How is your DNS configured? Are you using WINS? Etc. I'm not completely familiar with the totality of ActiveDirectory yet, as I've mostly toyed with NT4 in the past. I have not configured WINS, and I'm not sure if it's running. DNS is running on FreeBSD. Our domain controller exists in the format of servername.sageautomation.com. According to your link, A correctly configured DNS infrastructure is essential to the proper operation of Active Directory. I may have to play around with DNS to further test this problem. I find it odd that I have been able to add this workstation to the Domain in the past, and it is also the only one I have tested so far. If it is a name issue, how would I have been able to add it previously? Hmm. Adam ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
