Re: Extremely slow logons
- From: "Karl Middleton" <nospam@xxxxxxxxxx>
- Date: Fri, 15 Jul 2005 16:47:55 +1000
James,
Is the troublesome workstation by any chance using a wireless LAN
connection?
I have seen this when wireless is used becaused XP starts up asynchronously
and uses cached credentials pending the network starting. The group policy
processing fails with the userenv message because the system has not
properly connected to the network.
Post back and advise how you are connected to the network.
Karl from Oz
"James Glenn" <msdn_newsgroups@xxxxxxxxxxxxxxxxx> wrote in message
news:ECA0B468-9562-4612-B7C0-94024096B0A4@xxxxxxxxxxxxxxxx
> Ooops I typed the wrong IP address for an A record in DNS....its fixed
> now.
> My client computer is getting the below error during group policy setting
> (which I assume is what is happening during the "Applying computer
> settings")
>
>
> Event Type: Error
> Event Source: Userenv
> Event Category: None
> Event ID: 1053
> Date: 7/12/2005
> Time: 10:38:52 PM
> User: NT AUTHORITY\SYSTEM
> Computer: TC6
> Description:
> Windows cannot determine the user or computer name. (The specified domain
> either does not exist or could not be contacted. ). Group Policy
> processing
> aborted.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> --
> James Glenn
>
>
> "James Glenn" wrote:
>
>> I did as you suggested and it did solve some other problems I was having.
>> However the problem still exists as described in the original post. I
>> suspect its the group policy application. There is a program (grpadm???
>> or
>> the like) -- is it having problem communicating the the SBS server or
>> locating it?
>>
>> I am getting the following errors in the client computer event log
>> --------------------
>> Event Type: Error
>> Event Source: Userenv
>> Event Category: None
>> Event ID: 1053
>> Date: 7/12/2005
>> Time: 12:36:34 PM
>> User: NT AUTHORITY\SYSTEM
>> Computer: TC6
>> Description:
>> Windows cannot determine the user or computer name. (The specified domain
>> either does not exist or could not be contacted. ). Group Policy
>> processing
>> aborted.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> ---------------------------------
>> Event Type: Error
>> Event Source: AutoEnrollment
>> Event Category: None
>> Event ID: 15
>> Date: 7/12/2005
>> Time: 4:44:57 PM
>> User: N/A
>> Computer: TC6
>> Description:
>> Automatic certificate enrollment for local system failed to contact the
>> active directory (0x8007054b). The specified domain either does not
>> exist or
>> could not be contacted.
>> Enrollment will not be performed.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>>
>> ---------------
>> --
>> James Glenn
>>
>>
>> "moismoje" wrote:
>>
>> > You can leave the Sonic wall as the DHCP server if you like. The key
>> > (see my
>> > detailed post latter in the thred) is to use the SBS server (domain
>> > controller) as the primary DNS server so that your workstation can
>> > properly
>> > resolve active directory and syncronize the domain and user sercurity
>> > policies.
>> >
>> > This will also solve the slowness of resolving the user/group list when
>> > changing security on the workstation level.
>> >
>> > "Nicolas Verhaeghe" wrote:
>> >
>> > > The firewall is the DHCP. It is a Sonicwall Pro 230.
>> > >
>> > > I use the ISP's DNS (Time Warner).
>> > >
>> > > It seems that the firewall DHCP sets all the machine to use the ISP's
>> > > DNS.
>> > >
>> > > You suggest me to set up DHCP on the SBS? How will my computers know
>> > > to use
>> > > it as DHCP and not the firewall, besides a manual setting of all the
>> > > machines?
>> > >
>> > >
>> > > "Karl Middleton" <nospam@xxxxxxxxxx> wrote in message
>> > > news:eRScjxyhFHA.576@xxxxxxxxxxxxxxxxxxxxxxx
>> > > > Nicolas,
>> > > >
>> > > > Your problem sounds like name resolution problems. Where do your
>> > > > client
>> > > > computers point for DNS? SBS is happiest when it is your DHCP
>> > > > server, DNS
>> > > > server, WINS server. I am betting you still have the client
>> > > > computers
>> > > > pointing at the old NT box.
>> > > >
>> > > > Change them over and see if that improves things. SBS has a nice
>> > > > Connect
>> > > > Computer wizard that will join the clients to the SBS domain
>> > > > instead of
>> > > > the NT domain.
>> > > >
>> > > > Regards
>> > > > Karl from Oz
>> > > >
>> > > >
>> > > > "Nicolas Verhaeghe" <nospam_nicver@xxxxxxxxxxxxxxxx> wrote in
>> > > > message
>> > > > news:42d438d2$0$32200$39cecf19@xxxxxxxxxxxxxxxxxxxxx
>> > > >>I migrated my users from an NT4 domain to a SBS 2003 domain and now
>> > > >>login
>> > > >>on is an excrutiatingly slow process.
>> > > >>
>> > > >> After entered the password, the message "Loading your personal
>> > > >> settings"
>> > > >> is quickly replaced by a "Applying your personal settings" message
>> > > >> which
>> > > >> stays on for 4 or 5 minutes before someone can use his computer.
>> > > >>
>> > > >> What is causing this problem?
>> > > >>
>> > > >> Another slowness is when I need to make a user local
>> > > >> administrator. I go
>> > > >> to the Users control panel, when I am asked to provide a name for
>> > > >> an
>> > > >> administrator. I choose to use a domain admnistrator account and
>> > > >> it takes
>> > > >> also 5 minutes as well before I have access.
>> > > >>
>> > > >> What is wrong here?
>> > > >>
>> > > >> Is it the fact that the NT4 domain is still up and running?
>> > > >>
>> > > >
>> > > >
>> > >
>> > >
>> > >
.
- References:
- Extremely slow logons
- From: Nicolas Verhaeghe
- Re: Extremely slow logons
- From: Karl Middleton
- Re: Extremely slow logons
- From: Nicolas Verhaeghe
- Re: Extremely slow logons
- From: moismoje
- Re: Extremely slow logons
- From: James Glenn
- Re: Extremely slow logons
- From: James Glenn
- Extremely slow logons
- Prev by Date: Driver VPCAppSv.sys has been blocked from loading.
- Next by Date: RE: Cannot get IMAP to work
- Previous by thread: Re: Extremely slow logons
- Next by thread: Intranet crashing
- Index(es):
Relevant Pages
|