Userenv Event ID:1000

[Guest]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

On a demoted 2000 Server I am constantly receiving the following error:

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 3/5/2005
Time: 7:08:02 PM
User: NT AUTHORITY\SYSTEM
Computer: GFS
Description:
Windows cannot determine the user or computer name. Return value (1908).

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Any help will be appreciated.

 

[Guest]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

This is almost always a DNS error. Can you give us more info?

Make sure DNS is right and check it using nslookup to contact the domain by
name. If you can see the PDC emulator or GC you can get things like this.

--
Ryan Hanisco
MCSE, MCDBA
FlagShip Integration Services

"jstewart79" <jstewart79@discussions.microsoft.com> wrote in message
news:9709C4FD-C2B3-46F6-93D7-6EE339B8AB69@microsoft.com...
> On a demoted 2000 Server I am constantly receiving the following error:
>
> Event Type: Error
> Event Source: Userenv
> Event Category: None
> Event ID: 1000
> Date: 3/5/2005
> Time: 7:08:02 PM
> User: NT AUTHORITY\SYSTEM
> Computer: GFS
> Description:
> Windows cannot determine the user or computer name. Return value (1908).
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> Any help will be appreciated.
>

 

[Guest]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

In article <e7gt#GGJFHA.656@TK2MSFTNGP14.phx.gbl>,
rhanisco@flagshipis.com says...
> This is almost always a DNS error. Can you give us more info?
>
> Make sure DNS is right and check it using nslookup to contact the domain by
> name. If you can see the PDC emulator or GC you can get things like this.
>
>

I was getting this error - for us related to too many groups so AD
basically ran out of space and caused some authentication problems.

a regedit fixed this:-

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos
\Parameters]
"MaxTokenSize"=dword:00010000

basically increasing the maxtokensize from the default 12000 in sp4 to
whatever we needed