• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows 2K and Server 2003

Currently at my office we're running two different domains, one on WinNT and one on Server 2003. We're trying to get rid of the NT domain by migrating all the workstations to the 2003 server. I just tried migrating a workstation running Win2K. Switched the IP, subnet, gateway and DNS, and tried logging on to the 2003 domain. Got a message similar to "...unable to locate domain name <>...". I can ping the server, so I know they are talking. Is this a 2K/2003 thing, or is there something else I'm missing? Just prior to this, I migrated a machine running WinXPPro with no problems.
 
W2K should be just fine with a 2003-based server... at work we have XP and 2k machines, and they all run fine with our 2003-based domain. When it says unable to locate domain name, did you type in the name, and credentials with user@domain.org, or just user? You may want to try typing your credentials to join the computer to your domain like that (if you haven't already). It's solved my issues in the past.
 
Like nweaver says,,,did you remove the workstation from the old domain and add it to the new domain?
 
Yes, the workstation was moved from the old to new domain. We've migrated machines here before, but all were running WinXP Pro. This is the first workstation running W2K that we've tried migrating.
 
So it found the new domain fine, to add the computer to the domain, and the computer is showing up in AD U&C on the new domain, right? Do you have NetBIOS enabled? I know, NetBIOS is not SUPPOSED to be needed or even recommended on a Windows 2000 or later domain network, but for some reason, I've come across occasion where we get this same error and if I enable NetBIOS just to log in once, then I can disable it and the computer continues to work fine.
 
Back
Top