Assuming that your profile is not held upon the computer ...
I've one question ... Can you log into the system ?
If the answer is yes, then you have conducted the acid test & everything is working ... except the user's account is diabled.
I've occassionally seen this problem, where for some reason the system has not been able to log onto the domain.
The resolution that I use is ...
* Place the computer into a workgroup, and reboot
* you will then need to log into the system with
as the local administrator
* rename the computer, in accordance with your policy and reboot
* re-introduce the computer to the domain,
ensuring that you create the account upon the
domain .. ensuring that you have the correct
admin rights
* again reboot the computer
** Upto this point you will need to log into the
system as the local administrator
* once the system has booted correctly & you have
confirmed that you are connected to the network
reboot the system
* log in using your personal profile - this will
ensure that the system is connected to the
network
* reboot and ask the user to log in ...
If this fails take a look at the network adapter properties, and the bonding (right click network neighbourhood & select properties, ensuring that the network card is both enabled and the uppermost item on the list, (with the exception of remote services)
The most likely reason that the older profiles are working, is because of the information storage, (remembering the user's password ect - for local use).
Hopefully this will work for you
Arthur