Rebuild DOMAIN as server failed - add existing m/c

  mitchamm 13:49 05 May 2005


Ok, server crashed (hardware fault).
Rebuilt domain under Windows 2003 Server.
1 - XP clients, when logging on, state they cannot find the domain.
2 - Machines can be seen thru Entire network, but when you try to attach either get 'currently on logon servers available' or 'you do not have access'.
Tests reveal that removing and re-adding to the domain from the clients seems to resolve the issue, however, when you do this, under XP, it creates a new profile under the 'Documents & settings' folder.
Any suggestions on resolving these issues without having to remove and re-add to the domain and mess up the profiles?

  Xzrox 01:18 12 May 2005

Ahhh the dreaded messing up of profiles that's encoded into the NT kernal of Windows 2000+.

By messing up are you saying the profile names are changing to 'DOMAIN.USERNAME'? If so, there is little you can do to stop this if you have already used the client under that username previously. This is because the NT core of 2000, XP and 2003 is rather specific when it comes to profiles and makes sure it does not generate problems for itself by trying to create profiles with exactly the same names as previously logged on users of (especially of seperate domains).

This is all on account of being able to enforce mandatory and roaming profiles, which means failsafe systems are in place to ensure original profiles aren't altered in any way.

This thread is now locked and can not be replied to.

Elsewhere on IDG sites

Honor 9 Lite review

How Social Media has Propelled Political Graphic Design and Art in the Last Decade

The best kids apps for iPhone & iPad 2018

HomePod d’Apple : date de sortie, prix et fiche technique