Problems After Joining New Domain

[elziko]

We recently installed a new domain server at our offices.

When I joined the domain a new user directory as created in "Documents and
Settings" called "user.domain" where my old folder was just "user". So I
copied over everything from "user" to "user.domain" (being careful not to
overwrite anything new that was created). I then deleted the "user" folder.

Since then when I reboot the computer the "Applying Computer Settings"
dialog appears for a very long time. Otherwise the whole computer seems to
work fine... no problems. All my programs (apart from one) have recreated
all their settings and stored them in the new "user.domain" folder.

I think these things may be related and windows seems to recreate my "user"
folder with a NTUSER.DAT file inside it.

Perhaps it wasn't a great idea but since I had a new folder in "Documents
and Settings" I thought I'd save some space by deleting the old one.

Any ideas on how I can sort this mess out?

TIA

 

[Malke]

We recently installed a new domain server at our offices.

When I joined the domain a new user directory as created in "Documents
and Settings" called "user.domain" where my old folder was just
"user". So I copied over everything from "user" to "user.domain"
(being careful not to overwrite anything new that was created). I then
deleted the "user" folder.

Since then when I reboot the computer the "Applying Computer Settings"
dialog appears for a very long time. Otherwise the whole computer
seems to work fine... no problems. All my programs (apart from one)
have recreated all their settings and stored them in the new
"user.domain" folder.

I think these things may be related and windows seems to recreate my
"user" folder with a NTUSER.DAT file inside it.

Perhaps it wasn't a great idea but since I had a new folder in
"Documents and Settings" I thought I'd save some space by deleting the
old one.

Very long login times are usually because of misconfigured DNS. Because
you copied over your old user account, perhaps you also copied over the
incorrect DNS. The server always looks to itself for DNS with forward
lookups set for Internet access. Workstations always look only to the
server for DNS.

How Domain Controllers Are Located in Windows XP -
http://support.microsoft.com/default.aspx?scid=kb;en-us;314861

DNS and AD FAQs - http://support.microsoft.com/?id=291382

Malke