Search results for query: *

OK. What if you unjoin these servers (if it's possible)? Could be that these are the problems with browser service. So you have neither error messages on your authenticating DCs nor on workstations? Can't suggest anything than trying to netdiag/dcdiag/addiag on the problematic workstations.

Also, have you tried running adprep /forestprep from the Windows Server 2003 R2 installation disc 2 to prepare the schema for the R2?

But the XP stations are looking to proper DC IPs? Right? Because it could be that these new boxes were given the IPs that previously were assigned to DC where you run your DNS service. I can't think of a problem with a slowdown on logon other than that your stations can't contact the DNS. What I...

Well, I don't know if you can do that with basic commands but you can do that using autoscript. Solution will [link http://jonaquino.blogspot.com/2006/07/find-window-command-line-version-of.html]look similar to this[/url] However you can set window title for the command window using the basic...

If neither of methods listed here help you, you can try this Offline NT Password & Registry Editor, Bootdisk / CD Read this information and FAQ describing how to use it.

Additionally, check this document with best practices to configure your DNS.

I still would double check that workstations do have access to that your new domain controller and that they are looking to the new server IP. Look at the System event log on these stations. Try running on your problem box. If neither helps try reinstalling the TCP/IP stack. There's also a...