We had an NT4 PDC and an NT4 BDC and a 2K application server in the domain. Everything was fine, until the PDC lost a drive. The BDC was promoted, the PDC repaired, and reinstalled to the network. The plan was to put the PDC and BDC back the way they were. But, the 2K member was no longer a member of the domain. I as fishing on the wrong side of the pond when I thought the problem was with the new promoted BDC now PDC. I took the old PDC that was repaired, found several problems (network card not installed and working properly, and same name as the the new PDC). I figured this was where the problems were, so I upgraded the machine to 2K server and took it off the LAN. I then used a new LAN with just this server, with AD installed, and a workstation. I successfully logged onto that server. When I introduced the old 2K application server, it could not find the domain. I got a 5719 event id error saying no NT or 2000 DC available for the domain. This is the same error I was getting on the original LAN with the NT4 PDC.
So the best I can figure, the 2K application server, that has to be part of the domain, had something changed when the original PDC went down. I had someone else do the original transition, because the failure occured when I was out of town for 1 week.
Currently I can:
1) Log on to the NT4 domain from any workstation, and then when the mapped drives look for the 2K application server, and can't find it on the domain, it finds that machine and forces a password request (we use the admin password for that server) to get connected.
***** OR *******
2) Log on to the 'test network' 2K AD domain from a workstation, then when I try to map a drive on the 2K application server, I tells me there are no logon servers available to process the request. So using this setup, the machine cannot be accessed, and 'forced' with a password.
After sleeping on this, I realize the problem must exist on the 2K application server. It is/was not set up with AD or DNS. It simply was a member of the NT4 domain, and used to work fine. What am I missing?
Thanks.
So the best I can figure, the 2K application server, that has to be part of the domain, had something changed when the original PDC went down. I had someone else do the original transition, because the failure occured when I was out of town for 1 week.
Currently I can:
1) Log on to the NT4 domain from any workstation, and then when the mapped drives look for the 2K application server, and can't find it on the domain, it finds that machine and forces a password request (we use the admin password for that server) to get connected.
***** OR *******
2) Log on to the 'test network' 2K AD domain from a workstation, then when I try to map a drive on the 2K application server, I tells me there are no logon servers available to process the request. So using this setup, the machine cannot be accessed, and 'forced' with a password.
After sleeping on this, I realize the problem must exist on the 2K application server. It is/was not set up with AD or DNS. It simply was a member of the NT4 domain, and used to work fine. What am I missing?
Thanks.
