Wireless client "can't find DC" on startup: Event 1054

Discussion in 'Wireless Networking' started by Douglas Laudenschlager, Aug 28, 2004.

  1. Douglas Laudenschlager

    Douglas Laudenschlager Guest

    Problem: Wireless Windows XP sp2 client logs event 1054 from USERENV, "Can't
    find domain
    controller," every morning at startup, presumably due to a timing issue.
    Group policy refresh is aborted as a result.

    Configuration: Windows 2003 Std Server Active Directory domain with wired
    and wireless XP sp2 clients. Problem does not occur with wired clients.
    Gpupdate and similar tests work fine on the problem client after user login.

    Solutions attempted
    1) KB 304970: Use local policy on problem client to enable "Wait for
    network" at startup. Error still occurs.
    2) KB 298656: Specify IP of DNS server. Error still occurs.

    Other suggestions, please? Thanks!

    -Doug
     
    Douglas Laudenschlager, Aug 28, 2004
    #1

    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.
Similar Threads

  1. Looking for hotfix - 828940 Wireless Client Cannot Reconnect to a Wireless Access Point

  2. Wireless Loses Connection (Event ID 4201)

  3. PIX to VPN Client, cannot Access Client

  4. WinXP wireless zero config / wireless client flakiness - other options?

  5. Event ID: 4609 -> The COM+ Event System detected a bad return code during its internal processing.

  6. MGCP requested event vs. detect event

  7. Event ID 7026 error in event viewer

  8. Event Id 1014 DNS Client

Loading...