forcing logon to particular DC

[imarine]

Hi,

I've just built a new DC andtransferred all the FSMO roles over to it from my existing DC. The existing server is still replicating and is still a DC, but without FSMO roles. It is also a GC server the same as the new server.
There are no event log errors and DHCP is running on the new server. Clients are using DNS on the new server as primary.

Every machine I login to and do a "echo %logonserver%" on is displaying that it is logging into the old DC. Is there a way of forcing clients to use the new server as well as a way of checking that they would should the old DC fail.

Thanks

 

[terrywilson]

Have you got sites defined under Sites and Services?

I would move your old server that you no longer want logons on to a seperate site that has no subnets assigned to it.

If that doesnt make sense I can give more directions.

 

[imarine]

Thanks for that. I plan on rebuilding this server soon, but dont want to dcpromo it just yet. I have since posting noticed that a few clients are using the new server for login, so I assume everything is fine.

 

[PScottC]

Domain Controllers will no allow logons until the SYSVOL has finished replication. You may have been trying too soon.

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers

 

[imarine]

The new DC has been up and running for about a week now, so the SYSVOL folder is replicated over.

 

[PScottC]

Cut the port speed of the NIC on the old DC to 10Mb/Half Duplex. I believe that Windows generates some preferences based on DC network bandwidth.



PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers