This is strange and feels like a Win Server 03 issue underlying but I'm not sure.
I am unable to add a new workstation to the domain. I guess this is the first client I am adding after swing migrating the others over from SBS2000/WS2000 to the 2003 version. In my SBS 2000 domain this seemed pretty straightforward and even if things got 'out of whack' I never had to bring the client setup diskette into the process. If I simply went to the client and removed it from the domain, setting it back to a workgroup, then rejoined the domain everything was happy (as long as I made sure to use the full domain name, not the NETBIOS name). After my swing migration this solution even corrected one existing system that couldn't log on to the domain.
- At the workstation, when attempting to join the domain the process eventually times out with an error indicating "...domain does not exist or could not be contacted."
- At the SBS 03 server I receive the error message, "You must be a member of the SBS Admin or Power Users group to create computer accounts." Ultimately the computer is added to the list, but no AD parameters are identified (OS, service pack, etc.). The dialog prompting to run 'connectcomputer' from IE on the client appears, but this process fails as well at the workstation.
- SBS Server is 2003 (R1)
- Workstation is running Win2K Pro SP4
- Although I intend to set up a reservation in DHCP for this workstation, for now I've set a static unused address in the scope and pointed DNS to the SBS system.
- I can successfully ping the SBS server with either the server IP or the domain name.
- The SBS server can ping the new workstation
- I am using User CALs
- DNS is running and there are no conflicting or any, for that matter, host or pointer records using the workstation's IP
- The administrator account on the SBS server has Power User, Admin, Domain Admin and Enterprise Admin privileges
- All of my computers exist in the Computers OU under the My Business OU (which I renamed)
- At one time I did have a computer (different hardware/install) in the AD with the same name, although as long as it's deleted I understood there should be no conflict as it would have a different SID anyway, right?
Ideas? Is the culprit DNS? AD? Thought I at least had this part of the process down then this happened. This is actually the system that was running SBS 2000 which I'm repurposing as a tech machine.
For the heck of it I tried a different computer name that I had never used before and reviewed Windows components installed. Anyway, now I'm getting a "specified network name no longer available" error.
Thanks to any and all takers.