very slow logon please help

[bill]

If anyone has any ideas on this please post. I am having
a problem with a windows xp pro computer that I have
joined to the domain. Just to clarify, I have many
windows 2000 pro machines that are set up the EXACT same
way other than when doing a ipconfig /all the 2000
machines say they are in broadcast and the XP machine
says it is in hybrid mode. None of them point to ISP DNS
or anything like that. The windows 2000 machines log on
fine but the XP machine sits at the logon screen for
about 5 minutes. After it comes to the desktop I check
the event log and see this error "No Domain Controller is
available for domain FRZN due to the following:
There are currently no logon servers available to service
the logon request. ." Now once it comes to the desktop,
I can view network resources just fine. I can also do a
net stop and net start of net logon with no errors or
problems. I have 1 2000 DC running DNS and AD, 1 other
2000 server running DHCP and DNS and an NT 4.0 backup
domain controller running nothing. I am running out of
things to look for to make this thing logon normally.
Thanks

[Nicholas]

Edit Group Policy to allow XP to wait for network initialization:

Navigate to Computer Configuration / Administrative Templates / System / =
Logon

Double-click "Always wait for the network at computer startup and logon" =
and enable this policy.

Ref: =
http://msdn.microsoft.com/library/default.asp?url=3D/library/en-us/policy=
/policy/logon_optimization.asp=20

To speed the startup and logon process, Windows XP Professional does not =
require that the network be fully initialized before a client computer =
can start up or before a user can log on. If a user has previously =
logged on to a particular client computer, he or she is subsequently =
logged on using credentials cached on that computer.=20
When a user switches from using a local profile to using a roaming =
profile, Windows XP Professional copies relevant portions of the user's =
registry from the server instead of from the local computer, to prevent =
an older local copy from overwriting the server copy. Thereafter, =
whenever the roaming user logs on, the computer always waits for the =
network, so the profile can be downloaded from the server.=20
When fast network logon is enabled (as it is by default in Windows XP =
Professional), if administrators remove the profile path from a user's =
object, it is recommended that they also either rename or delete the =
corresponding profile folder. If they do not, and an administrator later =
reenters the same path, the user will receive the older copy of the =
registry from the server.

Ref: http://www.microsoft.com/mspress/books/sampchap/5566e.asp


--=20
Nicholas

-------------------------------------------------------------------------=
---

"bill" > wrote in message: =20
...

| If anyone has any ideas on this please post. I am having=20
| a problem with a windows xp pro computer that I have=20
| joined to the domain. Just to clarify, I have many=20
| windows 2000 pro machines that are set up the EXACT same=20
| way other than when doing a ipconfig /all the 2000=20
| machines say they are in broadcast and the XP machine=20
| says it is in hybrid mode. None of them point to ISP DNS=20
| or anything like that. The windows 2000 machines log on=20
| fine but the XP machine sits at the logon screen for=20
| about 5 minutes. After it comes to the desktop I check=20
| the event log and see this error "No Domain Controller is=20
| available for domain FRZN due to the following:=20
| There are currently no logon servers available to service=20
| the logon request. ." Now once it comes to the desktop,=20
| I can view network resources just fine. I can also do a=20
| net stop and net start of net logon with no errors or=20
| problems. I have 1 2000 DC running DNS and AD, 1 other=20
| 2000 server running DHCP and DNS and an NT 4.0 backup=20
| domain controller running nothing. I am running out of=20
| things to look for to make this thing logon normally. =20
| Thanks
|