Stannerack
IS-IT--Management
I am having a real problem with our Win2k network. Let me fill you in with some history 1st.
We have 1 LAN with 3 Domains running over it. 2 of those domains are NT based, the other is Win2k AD. The Win2k server suffered a disk failure, and dispite running RAID5, managed to screw itself up. No probs, we had backups. I reloaded the server with Win2k, and run Directory Services restore mode, performed a restore and hey presto, a working server.
The odd thing was that under Network Connections, the LAN connection was showing as LAN Connection #2. odd. Also, DNS changed the way it working. I can't explain how though. It was originally configured to just run as a cache-only server for AD. Anyway, it sort of worked OK.
We now want to consolidate our 3 domains into 1, all running on Win2k AD.
Heres where my problem starts.......
I wanted to perform a clean install of Win2k server on one of our old PDC's rather than run an upgrade. I have lots of reasons for it. I backed up all user data to another server, promoted the BDC to a PDC so that we could later use the Active Directory Migration Tool to drag over the accounts. I then rebuilt the old PDC as a Win2k Server, installed all the drivers and SP2, SRP1, then tried to promote it to a DC within the existing Win2k AD domain we have.
It just would not see the domain controller on our win2k domain. After lots of research I figured out that I needed to create a reverse lookup zone on the AD controller with a pointer to itself.
The promotion then worked. After the promotion, the DNS server showed a stack load more settings. My problem now is that replication is not working. I also want to move all of the master roles from the old win2k server to the new one which has much bigger capacity. That won't work either. It says that the RPC server is unavailable, even though the service has started on both machines.
I disabled the DNS on the old Win2k server and created a new DNS server on the new win2k machine hoping that it would be like a clean DNS setup that I originally had when we 1st started using AD. No chance. It managed to keep all the settings and zones and pointers that the old disabled DNS had.
Help!
Is it likely that there is a dodgy setting in the DNS somewhere? I know nothing about DNS and don't really know what I am looking for.
I need to make the new Win2k Server the main server with all the roles transferred to it, because I also want to rebuild the oringinal AD server to accommodate a new stucture we want to implement.
Please could somebody tell me if I have gone the wrong way about this, or whether it is worth deleting all my DNS zones?
Thank you.....
We have 1 LAN with 3 Domains running over it. 2 of those domains are NT based, the other is Win2k AD. The Win2k server suffered a disk failure, and dispite running RAID5, managed to screw itself up. No probs, we had backups. I reloaded the server with Win2k, and run Directory Services restore mode, performed a restore and hey presto, a working server.
The odd thing was that under Network Connections, the LAN connection was showing as LAN Connection #2. odd. Also, DNS changed the way it working. I can't explain how though. It was originally configured to just run as a cache-only server for AD. Anyway, it sort of worked OK.
We now want to consolidate our 3 domains into 1, all running on Win2k AD.
Heres where my problem starts.......
I wanted to perform a clean install of Win2k server on one of our old PDC's rather than run an upgrade. I have lots of reasons for it. I backed up all user data to another server, promoted the BDC to a PDC so that we could later use the Active Directory Migration Tool to drag over the accounts. I then rebuilt the old PDC as a Win2k Server, installed all the drivers and SP2, SRP1, then tried to promote it to a DC within the existing Win2k AD domain we have.
It just would not see the domain controller on our win2k domain. After lots of research I figured out that I needed to create a reverse lookup zone on the AD controller with a pointer to itself.
The promotion then worked. After the promotion, the DNS server showed a stack load more settings. My problem now is that replication is not working. I also want to move all of the master roles from the old win2k server to the new one which has much bigger capacity. That won't work either. It says that the RPC server is unavailable, even though the service has started on both machines.
I disabled the DNS on the old Win2k server and created a new DNS server on the new win2k machine hoping that it would be like a clean DNS setup that I originally had when we 1st started using AD. No chance. It managed to keep all the settings and zones and pointers that the old disabled DNS had.
Help!
Is it likely that there is a dodgy setting in the DNS somewhere? I know nothing about DNS and don't really know what I am looking for.
I need to make the new Win2k Server the main server with all the roles transferred to it, because I also want to rebuild the oringinal AD server to accommodate a new stucture we want to implement.
Please could somebody tell me if I have gone the wrong way about this, or whether it is worth deleting all my DNS zones?
Thank you.....
