We have a problem with a handful of Windows NT4.0 Server and 1 Windows 2000 Prof client, we cannot logon to the Domain, the message we receive is "Domain Controller could not be contact". Can ping the servers\2000 machine OK, they can browse the network. These servers we're running fine, until one day, don't understand what could have triggered this.
We have created a new domain, with a new PDC and BDC and jioned the problem machines to this new domain, works fine, we have then trusted to two domains and we can logon to the original domain from the problem machines. Don't understand why it will logon to the original domain, when previously it couldn't contact the domain controller.
We have tried removing the computer accounts, updating service packs (service packs are the same across all servers), deleting network set-up, different NIC's but short of re-installing the server (which is not an option) we had no choice but to put these problem machines on another domain and trust the domains to get them working. One was an Exchange Server and the others were running Oracle and the Windows 2000 machine was running IIS. These are the only things different from any other NT Servers or Windows 2000 clients on our network.
Does anyone have any ideas on how I can get these machines back onto our original domain. If not we might have to move all the other machines to the new domain (or leave it as it is).
Any help much appreciated. My thoughts were that it has something to do with the compiter accounts in the domain, possibly licencing or the SAM database? We have not changed anything on this domain that coincides with this problem, but it did happen around the same time our company was flooded with Code Red I and II, but I don't think this could have caused the problem??
Jane
We have created a new domain, with a new PDC and BDC and jioned the problem machines to this new domain, works fine, we have then trusted to two domains and we can logon to the original domain from the problem machines. Don't understand why it will logon to the original domain, when previously it couldn't contact the domain controller.
We have tried removing the computer accounts, updating service packs (service packs are the same across all servers), deleting network set-up, different NIC's but short of re-installing the server (which is not an option) we had no choice but to put these problem machines on another domain and trust the domains to get them working. One was an Exchange Server and the others were running Oracle and the Windows 2000 machine was running IIS. These are the only things different from any other NT Servers or Windows 2000 clients on our network.
Does anyone have any ideas on how I can get these machines back onto our original domain. If not we might have to move all the other machines to the new domain (or leave it as it is).
Any help much appreciated. My thoughts were that it has something to do with the compiter accounts in the domain, possibly licencing or the SAM database? We have not changed anything on this domain that coincides with this problem, but it did happen around the same time our company was flooded with Code Red I and II, but I don't think this could have caused the problem??
Jane