Home > Event Id > Event Id 1055 Userenv Windows Cannot Determine The Computer Name

Event Id 1055 Userenv Windows Cannot Determine The Computer Name

To verify that the domain controller can be contacted through Domain Name System (DNS), try to access \\mydomain.com\sysvol\mydomain.com, where mydomain.com represents the fully qualified DNS name of your domain. We discovered that the error started to happen after a reboot of a Windows Server 2003 DC. x 120 Rich Ailes I had this error crop up with a companion error in the system log: The Security System detected an authentication error for the server cifs/FQDNservername. In this environment the MANDATORY and OPTIONAL Pass-through Authentication options do not work for us and result in the GPO NOT being applied. this contact form

After logging in, the user could not access any resources on SBS1, be that Exchange or files/folders. Products and SolutionsOverviewGO-Global for WindowsGO-Global for UNIX and LinuxMobile ClientsSolutions for ISVsVideos: How GO-Global WorksFree TrialOnline DemoThird-Party SolutionsCompetitive AnalysisPurchase GO-GlobalCustomer SuccessOverviewASPs - Application Service ProvidersDistributionEducation and NonprofitEDA - Electronic Design AutomationERP x 4 Anonymous In my case, this problem was fixed by deleting and re-creating the Active Directory connections on all the DCs. I had MS confirm that my GPO is setup correctly and is tested.

Any errors in the server's event log? · actions · 2006-Jan-28 11:40 pm · mjnPremium Memberjoin:2000-08-06Cape Coral, FL

mjn Premium Member 2006-Jan-29 2:55 am None that I'm aware of. x 4 Dale Smith In my case, a WinXP workstation logged events 40960 and 40961 from source LsaSrv as well as event 1053 from source UserEnv. I did play around with the Security Policy a bit to try and get a Windows 98 machine to authenticate with the new domain but never got it to work properly,

Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking Post to Cancel home| search| account| evlog| eventreader| it admin tasks| tcp/ip ports| documents | contributors| about us Event ID/Source search Event ID: Event Source: Keyword search Example: Windows Good to hear you got it all worked out though. · actions · 2006-Feb-2 8:08 am ·

Forums → Software and Operating Systems → Microsoft« [Outlook] Outlook showing PST in The following articles addresses this issue: ME938457, ME942564 and ME823659.

We therefore had no indication that the crash on audit fail registry key had been set to 2. DHCP registers DNS.For testing purposes, I set DC2 to point to itself for primary DNS. With this registry key set to 2 only administrators can log on to the DC. By the way, this is not a new account.

All rights reserved. I have had this issue when AD did not replicate because a password was changed on one server and the other DC answered the logon request and denied the account access. x 4 Nick Garrett - Error: "Access is denied" (Error code 5) - If you have multiple DCs, check your AD replication. The fix was opening the password applet from Control panel ("Stored User Names and Passwords" or the likes) and removing an entry for SBS1, and re-login OK. 0 LVL 12

Please ensure that you can contact the server that authenticated you" - I was receiving this error on a system in our environment. After some digging and searching I checked local services on the DC and found that the "Netlogon" services was paused - not stopped. First Name Please enter a first name Last Name Please enter a last name Email We will never share this with anyone. The PC was not logging to the domain and I was not able to re-join the PC to the domain because the "Network ID" button under the "System Properties" computer name

It was being used stand-alone and was not connected to a network. weblink well I've narrowed it down to a problem with just the workstations. I'm stumped!Thanks,Mike · actions · 2006-Jan-28 10:34 pm · BillRolandPremium Memberjoin:2001-01-21Ocala, FL BillRoland Premium Member 2006-Jan-28 11:01 pm I'm sure you already tried this, but just in case,»www.eventid.net/display. ··· &phase=1 · Parts advice for a DIY router? [Networking] by Onaran348.

I'm surprised the fix on the MS site didn't work. x 113 Anonymous In my case this event was a result of the server pointing to an incorrect DNS server. I had a GPO for Folder Redirection & WSUS that seemed to be working fine, it was only until I tried to apply another GPO that I noticed this error, turns navigate here Once I replaced the missing "wkssvc.dll" file by copying it from another XP (Professional) machine and rebooted all went back to normal.

x 113 John Currie In my case it was the "Receive Side Window Scaling" issue that crops up with Windows Server 2003 SP2 & Broadcom NICs. Suggested Solutions Title # Comments Views Activity Adding 2012 server in a 2003 domain 8 20 141d HDD is seen as 1 drive in vmware but 2 in Windows 12 102 The Q article doesn't contain the error message we are getting, but I have spoken to MS tech support, and this is the fix." x 6 Private comment: Subscribers only.

To check this, at a command prompt (Start > Run > cmd) type "ipconfig /all".

Keeping an eye on these servers is a tedious, time-consuming process. Event ID: 1030 Windows cannot query for the list of Group Policy objects. Lost Password? Authenticated Users needs Read and System needs Full Control on the OU where the servers are located.

Stats Reported 6 years ago 1 Comment 3,633 Views Other sources for 1055 Microsoft-Windows-GroupPolicy MSExchange Extensibility flcdlock ClusSvc POP3SVC IMAP4SVC WinofficePrimeService.WIO_Eternit Others from Userenv 1053 1041 1054 1517 1058 1085 1006 Add link Text to display: Where should this link go? Join our community for more solutions or to ask questions. his comment is here Join the IT Network or Login.

x 12 Roy Nicholson We were getting Event Id 1053 in the Application event log "Windows cannot determine the computer or user name. (Access is denied.). Use it! Review your DNS servers." If the error occurred when you attempt to join a Microsoft Windows 2000-based client to a Microsoft Windows NT 4.0-based or Windows 2000-based domain see ME256083. Group Policy processing aborted.

Something really odd was happening in the DNS configuration. I found that rebooting leaves the network fine for a while.