event id 1000 return value 1722

[jasonb]

i am hoping to find somebody in this forum that may know
the answer:

on a client machine, this is the error that i have in my
event viewer over and
over and over:

Event ID: 1000
Event Source: Userenv
Description:
Windows cannot determine the user or computer name. Return
value (1722).

at first you see the error and you think ahhh this is easy
and it sounds easy if you read the article 261007 (on the
microsoft knowledge base) it says the behavior
can occur if the address for the configured preferred DNS
server on the client is invalid or unreachable.

too bad everything is set correctly here

i am unable to find anything else to help me with this. i
have tried removing it from the domain and placing it
back. i have tried removing it from the domain and
deleting the computer account, then placing it back in the
domain......... nothing is getting this error to go away.

any ideas anyone?

i have done all the obvious things and it will not go
away..... everything is functioning fine but obviously
there is a setting somewhere that is making it write to
the event viewer.

please somebody help

thanks

 

[Buz [MSFT]]

Here are some not as common causes of this error and things to look at:

1. - The problem could happen if the server is trying to apply policies and
profiles
across the Cross-Forest trust and is not able to solve the names.
- There are two possible solutions/workarounds:
- Change the "Allow Cross-Forest User Policy and Roaming User
Profiles"
policy to Enabled which was introduced in SP4
- Create a secondary zone for each domain on each one of the DNS
servers.

2. Sygate Personal Firewall v4.2.872 was installed on the Domain Controller.
Uninstalling the firewall resolved the LDAP hang.


Is only one machine giving this error? When did it start happening?

Try Userenv logging and repost with the log if the above stuff is not
helpful.

Buz Brodin
MCSE NT4 / Win2K
Microsoft Enterprise Domain Support

Get Secure! - www.microsoft.com/security

This posting is provided "as is" with no warranties and confers no rights.

Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.

 

[Guest]

cool man thanks!

i will check and see

-----Original Message-----
Here are some not as common causes of this error and things to look at:

1. - The problem could happen if the server is trying to apply policies and
profiles
across the Cross-Forest trust and is not able to solve the names.
- There are two possible solutions/workarounds:
- Change the "Allow Cross-Forest User Policy and Roaming User
Profiles"
policy to Enabled which was introduced in SP4
- Create a secondary zone for each domain on each one of the DNS
servers.

2. Sygate Personal Firewall v4.2.872 was installed on the Domain Controller.
Uninstalling the firewall resolved the LDAP hang.


Is only one machine giving this error? When did it start happening?

Try Userenv logging and repost with the log if the above stuff is not
helpful.

Buz Brodin
MCSE NT4 / Win2K
Microsoft Enterprise Domain Support

Get Secure! - www.microsoft.com/security

This posting is provided "as is" with no warranties and confers no rights.

Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.







.