• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Server 2003: Multiple domain controller question

TwiceOver

TwiceOver

Lifer
So I have set up Server 2003 on a machine here a while ago to play with and practice some things. Today I decided to set up another computer with 2003 so I can try out fault tolerance and some other things. My main goal is if one DC goes down, I'll still be able to log into the other one. As I understand, this is how it should work.

So After setting up the second DC I made sure replication was taking place, which it is. The sysvol folders are the same and all that seems good. However, when I take the first DC offline my other computers cannot sycronize with the second DC.

I have set up DNS on both DCs
Checked replication, seems to be working fine.

Any other help?
 
What do you mean, computers cannot synchronize with the second DC? Are the clients configured to use either DC as a DNS server?
 
When I take DC1 offline each computer gets the little icon in the task bar that says something like domain controller offline and when it comes back then I have to click that icon and syncronize all the offline content (Desktop, Application Settings, Documents).

All computers have DC1 as DNS Primary and DC2 as DNS Secondary.
 
That's offline files, usually used on laptops that aren't always connected to the LAN. Offline files is basically done on the client side...the server is just a normal file share, which are not synchronized between domain controllers (or any other type of server) by default.
 
Well it does this with all of the computers. Basically for every computer all that info is stored on the server and is replicated in the sysvol from DC1 over to DC2.

When DC1 is offline and I log on it doesn't connect me to DC2 nor run my scripts which are located in the sysvol on DC2. But when DC1 is connected and I log in everything works just as it should.
 
Well it does this with all of the computers. Basically for every computer all that info is stored on the server and is replicated in the sysvol from DC1 over to DC2.
Click to expand...

You can disable offline files. And it doesn't save that info in sysvol.

When DC1 is offline and I log on it doesn't connect me to DC2 nor run my scripts which are located in the sysvol on DC2
Click to expand...

Now that is a problem. When DC1 is off and you log into a client, run 'set log' from the command prompt..what does it say? Can you ping the FQDN from the client (ping domain.com)?
 
I am using offline files so that when i move from computer to computer everything stays the same, except start menu. That is working fine. I have the info stored in the sysvol for some unknown reason, I guess it just worked there to begin with.

I can ping both domain controllers using FQDN.

brb
 
Heh, Its like getting hit in the face with a sledge hammer. I realized my scripts won't work because they all refer to DC1 (Printing, Mapped Drives) Duh.

Still my offline files should be able to syncronize with DC2 if the sysvols are the same.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top