Re: Clients (random ones) unable to login to domain, reboot, then can?

Thanks for the tip.

Basically, it seems the client, for some reason, cannot talk to the
domain controller .. this seems simple enough .. but i'm curious as to
why this happens, and how ..

If it was a network/ip/physical problem, why can i log in locally,
Remote Desktop to the server, no problems, log out, and yet STILL
cannot log in to the domain. And furthermore to that, why does a reboot
solve this problem?

Even more annoying is the fact this isnt limited to any specific
computers, could it possibly be the server? I'd have thought thered be
something popping up in the log,m like a rejected/failed
connection/login attempt .. but nothing ..

Anna Clark (remove this) wrote:
Hi vidguide:

Go to www.eventid.net and put in the event numbers. You will find lots of
information there to help you track this down.

Anna Clark

<vidguide@xxxxxxxxx> wrote in message
news:1161563984.644400.166120@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Ok, i've just taken over administration rolls at my new place of work,
and am learning the ropes on the setup here.

All pcs start up at 8am each morning, and lately, some are unable to
login. Its not always the same PCs (today it was mine!), and a PC that
did it yesterday, wont always do it today.

Windows boots up like normal, prompts for name, pass, domain. Put in
details, instant "wrong name/pass" message. Tried administrator,
instant fail. Log in locally, works, and I *can* remote desktop to the
server, etc .. so physical/IP networking is functional..

Eventlog on the server doesnt show ANYTHING unusual in any category ..
Local PC event log does, however, show this:
UserEnv: Event ID: 1053
Windows cannot determine the user or computer name. (Access is denied.
). Group Policy processing aborted.

And
AutoEnrollment: Event ID: 15
Automatic certificate enrollment for local system failed to contact the
active directory (0x8007052b). Unable to update the password. The
value provided as the current password is incorrect.
Enrollment will not be performed.


Oddly, if you reboot the client, it typically works as per normal then.
Once it required 2 reboots to get it to work, but typically it works.

Any ideas what could cause this?

Server is Windows 2003 SBS with Active Directory.

Thanks in advance!


.

Relevant Pages

  • RE: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: Printing from Win9x clients stops
    ... The printers with 9x drivers on the server appeared automatically in the ... > then right-click the name of the computer running Windows Small Business ... > From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • Re: after installing KB011829 OWA is not working anymore
    ... Based on my research, after you install hotfix KB911829, I suggest we ... Profile WMI Provider to each client computer that is running Windows Vista ... If you are running the Premium Edition of Windows Small Business Server ...
    (microsoft.public.exchange.connectivity)
  • Re: DHCP Issues. Very strange
    ... I understand the issue to be: some client computers ... can not obtain IP from SBS server. ... it is most possible a client side issue of Windows ... since you have join it to SBS domain and the Windows XP SP2 ...
    (microsoft.public.windows.server.sbs)
  • Site-tosite VPN Issue
    ... Windows Server 2003 domain controller ... Mixture of PCs running Windows 2000 Profressional with SP3 and Windows XP ... the VPN to the Windows Server 2003 domain controller. ... 12.7MB file from the server to the client PC. ...
    (microsoft.public.windows.server.networking)