☰

Windows XP 域登录需要 40 - 60 分钟

tag-icon • tag-icon windows-xp roaming-profile windows login
Windows XP 域登录需要 40 - 60 分钟

Windows XP 客户端，已完全修补，带有 Symantec Endpoint Protection 11 客户端

Windows 2008 R2 域漫游配置文件文件夹重定向应用于文档、应用程序数据和桌面

我启用了 userenv 日志记录，并于昨晚 17:00 后登录。昨晚我离开时 17:45 用户 shell 尚未出现。今天早上我到达时，我检查了日志文件并发现了以下内容。

USERENV(3f8.e7c) 17:02:18:296 LogExtSessionStatus: Successfully logged Extension Session data
USERENV(654.a30) 17:04:09:468 ImpersonateUser: Failed to impersonate user with 5.
USERENV(654.a30) 17:04:09:468 GetUserNameAndDomain Failed to impersonate user
USERENV(654.a30) 17:04:09:468 GetUserDNSDomainName:  Domain name is NT Authority.  No DNS domain name available.
USERENV(c8c.cb8) 17:04:09:781 LibMain: Process Name:  C:\Program Files\Symantec\Symantec Endpoint Protection\SescLU.exe
USERENV(cd0.cd4) 17:04:10:781 LibMain: Process Name:  C:\PROGRA~1\Symantec\LIVEUP~1\LUCOMS~1.EXE
USERENV(d08.c84) 17:07:09:609 LibMain: Process Name:  C:\Program Files\Symantec\Symantec Endpoint Protection\SescLU.exe
USERENV(cbc.cc0) 17:07:10:625 LibMain: Process Name:  C:\Program Files\Symantec\LiveUpdate\luall.exe
USERENV(db0.db4) 17:07:10:781 LibMain: Process Name:  C:\PROGRA~1\Symantec\LIVEUP~1\LUCOMS~1.EXE
USERENV(e00.e0c) 17:07:11:062 LibMain: Process Name:  C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe
USERENV(e20.e34) 17:07:11:203 LibMain: Process Name:  C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe
USERENV(e40.e50) 17:07:11:406 LibMain: Process Name:  C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe
USERENV(efc.54c) 17:07:11:656 LibMain: Process Name:  C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe
USERENV(ccc.df0) 17:08:45:687 LibMain: Process Name:  C:\Program Files\Symantec\Symantec Endpoint Protection\SescLU.exe
USERENV(e24.e20) 17:08:45:937 LibMain: Process Name:  C:\Program Files\Symantec\LiveUpdate\luall.exe
USERENV(ff0.ff4) 17:08:46:078 LibMain: Process Name:  C:\PROGRA~1\Symantec\LIVEUP~1\LUCOMS~1.EXE
USERENV(32c.cd0) 17:08:46:265 LibMain: Process Name:  C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe
USERENV(cc4.3d4) 17:08:46:406 LibMain: Process Name:  C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe
USERENV(434.4d0) 17:08:46:593 LibMain: Process Name:  C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe
USERENV(f2c.ac) 17:08:46:828 LibMain: Process Name:  C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe
USERENV(d60.d7c) 17:09:40:265 LibMain: Process Name:  C:\Program Files\Symantec\Symantec Endpoint Protection\SescLU.exe
USERENV(d94.d98) 17:09:40:531 LibMain: Process Name:  C:\PROGRA~1\Symantec\LIVEUP~1\LUCOMS~1.EXE
USERENV(bc4.3c4) 17:10:52:765 LibMain: Process Name:  C:\Program Files\Symantec\Symantec Endpoint Protection\SescLU.exe
USERENV(37c.90c) 17:10:52:984 LibMain: Process Name:  C:\Program Files\Symantec\LiveUpdate\luall.exe
USERENV(580.540) 17:10:53:109 LibMain: Process Name:  C:\PROGRA~1\Symantec\LIVEUP~1\LUCOMS~1.EXE
USERENV(c18.c30) 17:10:53:312 LibMain: Process Name:  C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe
USERENV(c44.288) 17:10:53:468 LibMain: Process Name:  C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe
USERENV(a34.cf4) 17:10:53:656 LibMain: Process Name:  C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe
USERENV(d3c.d4c) 17:10:53:890 LibMain: Process Name:  C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe
USERENV(970.948) 17:15:09:468 LibMain: Process Name:  C:\Program Files\Symantec\Symantec Endpoint Protection\SescLU.exe
USERENV(150.9dc) 17:15:09:734 LibMain: Process Name:  C:\PROGRA~1\Symantec\LIVEUP~1\LUCOMS~1.EXE
USERENV(f90.cec) 17:20:38:718 LibMain: Process Name:  C:\Program Files\Symantec\Symantec Endpoint Protection\SescLU.exe
USERENV(d8c.d70) 17:20:38:984 LibMain: Process Name:  C:\PROGRA~1\Symantec\LIVEUP~1\LUCOMS~1.EXE
USERENV(9a0.fa0) 17:26:07:953 LibMain: Process Name:  C:\Program Files\Symantec\Symantec Endpoint Protection\SescLU.exe
USERENV(844.51c) 17:26:08:218 LibMain: Process Name:  C:\PROGRA~1\Symantec\LIVEUP~1\LUCOMS~1.EXE
USERENV(d00.9ac) 17:31:19:453 LibMain: Process Name:  C:\Program Files\Symantec\Symantec Endpoint Protection\SescLU.exe
USERENV(ad4.624) 17:31:19:718 LibMain: Process Name:  C:\PROGRA~1\Symantec\LIVEUP~1\LUCOMS~1.EXE
USERENV(654.694) 17:31:46:390 ImpersonateUser: Failed to impersonate user with 5.
USERENV(654.694) 17:31:46:390 GetUserNameAndDomain Failed to impersonate user
USERENV(654.694) 17:31:46:390 GetUserDNSDomainName:  Domain name is NT Authority.  No DNS domain name available.
USERENV(af8.610) 17:36:48:625 LibMain: Process Name:  C:\Program Files\Symantec\Symantec Endpoint Protection\SescLU.exe
USERENV(aa4.dfc) 17:36:48:906 LibMain: Process Name:  C:\PROGRA~1\Symantec\LIVEUP~1\LUCOMS~1.EXE
USERENV(2dc.5c8) 17:42:17:812 LibMain: Process Name:  C:\Program Files\Symantec\Symantec Endpoint Protection\SescLU.exe
USERENV(f70.8ac) 17:42:18:078 LibMain: Process Name:  C:\PROGRA~1\Symantec\LIVEUP~1\LUCOMS~1.EXE
USERENV(d50.c30) 17:47:47:062 LibMain: Process Name:  C:\Program Files\Symantec\Symantec Endpoint Protection\SescLU.exe
USERENV(c2c.c3c) 17:47:47:328 LibMain: Process Name:  C:\PROGRA~1\Symantec\LIVEUP~1\LUCOMS~1.EXE
USERENV(ef0.4cc) 17:53:16:234 LibMain: Process Name:  C:\Program Files\Symantec\Symantec Endpoint Protection\SescLU.exe
USERENV(cd4.c84) 17:53:16:500 LibMain: Process Name:  C:\PROGRA~1\Symantec\LIVEUP~1\LUCOMS~1.EXE
USERENV(828.8c4) 17:58:45:484 LibMain: Process Name:  C:\Program Files\Symantec\Symantec Endpoint Protection\SescLU.exe
USERENV(a24.b30) 17:58:45:750 LibMain: Process Name:  C:\PROGRA~1\Symantec\LIVEUP~1\LUCOMS~1.EXE

我看到一些帖子表明可能是 Windows 桌面搜索 3.01 导致了这个问题，所以我将其删除了。

我删除了“在启动或登录时始终等待网络”策略，认为这可能会有所帮助。

我没什么主意了。有人见过这个吗？

答案1

基础知识：

  • 计算机的网络是否配置为使用 Active Directory DNS 服务器（以及只有他们，没有外部的）？
  • 您能成功解析 DC 名称吗？
  • 您能成功 ping 通它们吗？
  • 您可以访问它们上的网络共享吗（fe SYSVOL）？

另外：如果您停止和/或卸载 Symantec Endpoint Protection，会发生什么情况？

答案2

我的第一个建议是禁用或删除一台客户端计算机上的所有赛门铁克组件，看看是否能解决问题。

答案3

看起来 Symantec Liveupdate 可能占用了资源？请尝试禁用该服务并重新启动。

答案4

当 UDP 端口 88 被阻止，或者客户端和 DC 之间的防火墙不允许大型/碎片化的 UDP 数据包时，我也看到了此错误（以及相关的缓慢登录）。解决方法（当时）是使用 KB244474 中的步骤（如何在 Windows 中强制 Kerberos 使用 TCP 而不是 UDP）强制 Kerberos 使用 TCP 而不是 UDP。

当我这样做时......一些标准的故障排除问题：

  1. 它是什么时候开始发生的？
  2. 有多少客户遇到过这种情况？
  3. 当它开始发生时，发生了什么变化？

相关内容