We have a test enviornment network which has an NT 4.0 domain controller. Nearly all the workstations in the test enviornment/domain are W2K Pro and XP Pro. All are joined to the NT 4.0 network with no apparent problems.
We have one W2K machine which was previously on our production enviornment network, but we tried to disjoin it from that domain and join it (for the first time) to a NT 4.0 test enviornment/domain called CSI.
The error I receive is that the domain CSI cannot be found. However the machine does get an IP address, and I can ping the PDC by netbios name AND IP address. Yet when trying to join the domain I get the error DOMAIN CSI CANNOT BE FOUND.
Anyone connecting a W2K or XP box to an NT 4.0 domain knows that this is a common Windows flake, and the work around is usually (in no particular order)...
Join machine to workgroup
Join machine to domain
Remove Computer account from PDC
Re-add computer account to PDC
Another suggestion was delete the COMPUTER account from the server manager on the PDC, then RE-ADD IT using a different name other than the original. On the client machine rename it to match the new name/account created on the PDC (so the SAM db would have a new SID for the client machine). To no avail also.
However even this isn't working. Right now I'm running a Windows Repair but I don't suspect that will resolve this issue.
Any ideas? I've also rebooted the PDC and Client machine several times and have been trying nearly all day. Could this be a WINS issue?