I have an NT domain with PDC only. (it was a BDC once, but got promoted
to PDC, and former PDC got retired). Anyway, PDC is on NT4SP6a.
I've got clients on XP Pro machines, which take very long to log on.
Interesting thing though is that it's usualy only when the user logs in
for the first time this day on the particular workstation. If you log
out, and re-login, it's quite quick.
Tracing logins shows not much of usefull debug info.

[...]
SERENV(1d4.1d8) 14:35:14:515 ProcessBuild: Entering with build <2109>.
USERENV(1d4.1d8) 14:35:14:515 ProcessPrograms: Entering.
USERENV(1d4.1d8) 14:35:14:531 ProcessPrograms: Spawned
<C:\WINDOWS\system32\rundll32.exe
C:\WINDOWS\system32\shell32.dll,Control_RunDLL intl.cpl,,/u>. Waiting
for it to complete.
USERENV(3cc.3e8) 14:35:14:546 LibMain: Process Name:
C:\WINDOWS\system32\rundll32.exe
USERENV(1d4.1d8) 14:38:14:531 ProcessPrograms: Finished waiting for
<C:\WINDOWS\system32\rundll32.exe
C:\WINDOWS\system32\shell32.dll,Control_RunDLL intl.cpl,,/u>.
USERENV(1d4.1d8) 14:38:14:531 ProcessPrograms: Leaving.
USERENV(1d4.1d8) 14:38:14:531 ProcessBuild: Leaving successfully.
[...]
USERENV(1d4.1d8) 14:38:15:156 ProcessBuild: Entering with build <2196>.
USERENV(1d4.1d8) 14:38:15:156 ProcessPrograms: Entering.
USERENV(1d4.1d8) 14:38:15:171 ProcessPrograms: Spawned
<C:\WINDOWS\system32\rundll32.exe
C:\WINDOWS\system32\shell32.dll,Control_RunDLL input.dll,,/u>. Waiting
for it to complete.
USERENV(5ec.46c) 14:38:15:187 LibMain: Process Name:
C:\WINDOWS\system32\rundll32.exe
USERENV(1d4.1d8) 14:41:15:171 ProcessPrograms: Finished waiting for
<C:\WINDOWS\system32\rundll32.exe
+C:\WINDOWS\system32\shell32.dll,Control_RunDLL input.dll,,/u>.
USERENV(1d4.1d8) 14:41:15:171 ProcessPrograms: Leaving.
USERENV(1d4.1d8) 14:41:15:171 ProcessBuild: Leaving successfully.
USERENV(1d4.1d8) 14:41:15:171 ProcessBuild: Entering with build <2206>.
[...]

These are the places in which the log shows stops in login process.
(there were 2 or three more).
The whole process takes about 9-10 minutes.

Any ideas? I got completely stuck here.
--
/\-\/\-\/\-\/\-\/\-\/\-\/\ As a computer, I find your faith in techno-
\ Kruk@epsilon.eu.org / logy amusing.
/ http://epsilon.eu.org/ \
\/-/\/-/\/-/\/-/\/-/\/-/\/

This is a name resolution problem. Set up a WINS server and set it up so the
clients can use (via DHCP or whatever).

Ray

"Mariusz Kruk" <Mariusz.Kruk@epsilon.eu.org> wrote in message
news:slrnecbulr.t54.Mariusz.Kruk@epsilon.rdc.pl...
>I have an NT domain with PDC only. (it was a BDC once, but got promoted
> to PDC, and former PDC got retired). Anyway, PDC is on NT4SP6a.
> I've got clients on XP Pro machines, which take very long to log on.
> Interesting thing though is that it's usualy only when the user logs in
> for the first time this day on the particular workstation. If you log
> out, and re-login, it's quite quick.
> Tracing logins shows not much of usefull debug info.
>
> [...]
> SERENV(1d4.1d8) 14:35:14:515 ProcessBuild: Entering with build <2109>.
> USERENV(1d4.1d8) 14:35:14:515 ProcessPrograms: Entering.
> USERENV(1d4.1d8) 14:35:14:531 ProcessPrograms: Spawned
> <C:\WINDOWS\system32\rundll32.exe
> C:\WINDOWS\system32\shell32.dll,Control_RunDLL intl.cpl,,/u>. Waiting
> for it to complete.
> USERENV(3cc.3e8) 14:35:14:546 LibMain: Process Name:
> C:\WINDOWS\system32\rundll32.exe
> USERENV(1d4.1d8) 14:38:14:531 ProcessPrograms: Finished waiting for
> <C:\WINDOWS\system32\rundll32.exe
> C:\WINDOWS\system32\shell32.dll,Control_RunDLL intl.cpl,,/u>.
> USERENV(1d4.1d8) 14:38:14:531 ProcessPrograms: Leaving.
> USERENV(1d4.1d8) 14:38:14:531 ProcessBuild: Leaving successfully.
> [...]
> USERENV(1d4.1d8) 14:38:15:156 ProcessBuild: Entering with build <2196>.
> USERENV(1d4.1d8) 14:38:15:156 ProcessPrograms: Entering.
> USERENV(1d4.1d8) 14:38:15:171 ProcessPrograms: Spawned
> <C:\WINDOWS\system32\rundll32.exe
> C:\WINDOWS\system32\shell32.dll,Control_RunDLL input.dll,,/u>. Waiting
> for it to complete.
> USERENV(5ec.46c) 14:38:15:187 LibMain: Process Name:
> C:\WINDOWS\system32\rundll32.exe
> USERENV(1d4.1d8) 14:41:15:171 ProcessPrograms: Finished waiting for
> <C:\WINDOWS\system32\rundll32.exe
> +C:\WINDOWS\system32\shell32.dll,Control_RunDLL input.dll,,/u>.
> USERENV(1d4.1d8) 14:41:15:171 ProcessPrograms: Leaving.
> USERENV(1d4.1d8) 14:41:15:171 ProcessBuild: Leaving successfully.
> USERENV(1d4.1d8) 14:41:15:171 ProcessBuild: Entering with build <2206>.
> [...]
>
> These are the places in which the log shows stops in login process.
> (there were 2 or three more).
> The whole process takes about 9-10 minutes.
>
> Any ideas? I got completely stuck here.
> --
> /\-\/\-\/\-\/\-\/\-\/\-\/\ As a computer, I find your faith in techno-
> \ Kruk@epsilon.eu.org / logy amusing.
> / http://epsilon.eu.org/ \
> \/-/\/-/\/-/\/-/\/-/\/-/\/

epsilon$ while read LINE; do echo "\>$LINE"; done < Ray
>This is a name resolution problem. Set up a WINS server and set it up so the
>clients can use (via DHCP or whatever).

Nope. WINS server is up and running. Besides, if it was a name
resolution problem, it would happen every time.
I investigated it a little and it seems that it's somehow connected to
HKCU\Software\Microsoft\Windows NT\CurrentVerstion\Winlogon\Buildnumber
registry entry. When I log on to NT4 it's getting switched to something
low, then when I log back to XP, system tries to upgrade profile, and it
takes sooo long.

--
\.\.\.\.\.\.\.\.\.\.\.\.\.\ Rezygnuj±c z Assemblera -- tracisz na czyte-
..\.Kruk@epsilon.eu.org.\.\. lo¶ci i logiczo¶ci programu (Jacek Pop³aw-
\.http://epsilon.eu.org/\.\ ski)
..\.\.\.\.\.\.\.\.\.\.\.\.\.