G
Guest
Heres my setup.
We have a Win2K server in our production network - no problem there.
For disaster recovery, I have had ISDN lines installed which we would use
with a win2k server as backup should our main site burn down or be destroyed.
The backup server is identical to our production server, same ip, same
domain name.
Today I took a machine (win2k pro) off our production network and plugged it
into the backup network. The active directory was copied from the production
server to the backup server, and the win2k pro machine had been on he
production network for 3 years so its name showed up in the backup active
directory.
When I logged onto the win2k pro, I received the message: "The system cannot
log you on to this domain because the systems computer account in its primary
domain is missing of the password account is incorrect." Password and user id
were correct, and that user (me) had been on the productin network for 3
years.
I logged on to the win2k pro locally, and in frustration just joined the
domain (which was already joined) without disjoining, workgroup, rejoining
etc. I rebooted and that solved my problem. HOwever, this backup server and
ISDN lines will be used in case of a disaster and I don't see how I can talk
200 users through logging on localling joining the domain etc.
I called a tech place and they said that the win2k's may be looking for the
mac address of the production server. I don't know if thats true or not, but
does anyone have an idea on how I could setup the backup server to recognize
the workstations as soon as the user logs on?
Also, after I had joined the domain to the backup server, tested programs
etc, I had no problems when I removed that Win2k pro machine from the backup
network and put it back on the production network - it came right up.
Thanks for any help you can provide.
We have a Win2K server in our production network - no problem there.
For disaster recovery, I have had ISDN lines installed which we would use
with a win2k server as backup should our main site burn down or be destroyed.
The backup server is identical to our production server, same ip, same
domain name.
Today I took a machine (win2k pro) off our production network and plugged it
into the backup network. The active directory was copied from the production
server to the backup server, and the win2k pro machine had been on he
production network for 3 years so its name showed up in the backup active
directory.
When I logged onto the win2k pro, I received the message: "The system cannot
log you on to this domain because the systems computer account in its primary
domain is missing of the password account is incorrect." Password and user id
were correct, and that user (me) had been on the productin network for 3
years.
I logged on to the win2k pro locally, and in frustration just joined the
domain (which was already joined) without disjoining, workgroup, rejoining
etc. I rebooted and that solved my problem. HOwever, this backup server and
ISDN lines will be used in case of a disaster and I don't see how I can talk
200 users through logging on localling joining the domain etc.
I called a tech place and they said that the win2k's may be looking for the
mac address of the production server. I don't know if thats true or not, but
does anyone have an idea on how I could setup the backup server to recognize
the workstations as soon as the user logs on?
Also, after I had joined the domain to the backup server, tested programs
etc, I had no problems when I removed that Win2k pro machine from the backup
network and put it back on the production network - it came right up.
Thanks for any help you can provide.