Re: Slow XP logon times
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 3 Oct 2007 09:31:06 -0400
Aaron <Aaron@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
DCdiag and NetDiag all passed. Clients are pointing to the correct
DNS
Hi ....as mentioned, you have another thread going on in the other group
(server.general).
Abandon one thread - don't use both, or you're asking people to duplicate
others' work.
"Jorge Silva" wrote:
Hi
run dcdiag and nediag on the DCs, also make sure that the clients are
pointing to the correct DNS server and that you don't have
connectivity problems to the File servers that re hosting the
profiles.
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
"Aaron" <Aaron@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FC756018-A7BC-4B4B-9C86-5F7284C4C29B@xxxxxxxxxxxxxxxx
Had a Windows 2000 AD domain with 2000 pro clients using roaming
profiles. Insalled a few XP machines and they are taking up to four
minutes to logon to
the network using roaming profiles. Installed a new 2003R2 server
and moved
FSMO roles. Still kept the 2000 server as a domain controller with
the 2003
server. I can logon with no wait at all on the XP machines if not
logging in
as a roamin profile user. Only when logging in with credential of
roaming user does the XP logon times take so long. DNS is pointing
to the new server
first and the profiles are kept on the new servers. What could be
taking the
XP pcs so long to long in compared to the quick 2000 pro logons?
.
- References:
- Re: Slow XP logon times
- From: Jorge Silva
- Re: Slow XP logon times
- Prev by Date: Re: simple AD DNS question
- Next by Date: Re: Can I run gpedit.msc from server on remote computer.
- Previous by thread: Re: Slow XP logon times
- Next by thread: Re: How to disable screen savers on servers
- Index(es):
Relevant Pages
|