• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 263
  • Last Modified:

Windows 2008 DC issues when connecting to an old network.

Right..

I have a 2003 Windows server running as a DC with about 20 users on the domain. We bought a Win 2008 Standard Server and created a secondary DC which worked fine but when we tried to seize FSMO roles and make the 2008 Server the primary dc server. It failed.

After numerous research and search and trying all sorts from microsoft sites and EE, we decided to demote the server from the network to standalone, unplug the old server, give the new server its IP address and name and then promoted it to DC for the network.

Issues
1: The Server is working fine but when we try to view the other systems on the domain , it gives us an error message saying that the "workgroup" is not available for this user

2: ALL users that have been created on the new DC which mimic the accounts of the old system do not work on the client systems unless we detach the client system from the domain and then join the domain again.

3: Other systems on the network are not accessible from the network icon, but are accessible using the dos prompt and the backslash address of the system.

4: We can browse the network from client systems to client systems

Please can anyone advise on how to clear up this issues as time has expired and my boss is on my neck!!!

Thanks
0
souldj
Asked:
souldj
  • 3
  • 2
2 Solutions
 
woolnoirCommented:
Did all the FSMO roles transfer across before you switched the old server off ? can you verify (using the AD tools) which servers hold which roles ?

Did you migrate DNS and (optionally if you have it) WINS services across ?
0
 
souldjAuthor Commented:
They did not.

We did not migrate DNS across as we installed a fresh DNS. I believe we probably did not do the right things and thus had to create a standalone server and work from "scratch".

.....

0
 
woolnoirCommented:
then maybe bring the old server back online, that way the FSMO roles which are on the old box will (hopefully) work. Then add a DNS server to the new box and allow it to replicate. Then rather than siezing the roles, ask it to migrate them (using the AD tools).

When you mention above that you SEIZED the roles, what tool did you use, was it REALLY a sieze or was it a transfer (using AD gui tools).
0
Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

 
Darius GhassemCommented:
Run dcdiag post results
0
 
souldjAuthor Commented:
We had to basically rebuild the system as time was not on our side.

although your advice did point us in the right direction.

I will award you the points.
0
 
souldjAuthor Commented:
We had to basically rebuild the server from scratch.
0

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now