Event id 1053 "Windows cannot detrmine the user or computer 2

Event ID 1053 - Userenv

Symptoms: your w2k/xp clients may receive this Event ID 1053 - Windows cannot determine the user or computer name. (<error description>). Group Policy processing aborted. Or error: "The specified user does not exist."

Resolutions: 1. Make sure that your internal DNS server is the server for the domain you are logging in to.
2. Verify the DNS Settings. This will occur if your DNS server is unable to resolve information about your domain.
3. Delete the problem computer from DNS records and re-create it.


Found this on google. Good luck.

Glen A. Johnson
If you're from the Illinois, Wisconsin or Florida area, check out Tek-Tips in Chicago IL
To get the best answers to your questions, check out faq950-5848

there is a hotfix for win2003 for this issue as well if youre running 2003 (or SP1 includes the fix)...you should also be getting one or two other userenv events along with that though....


Check this=======================================

Domain Controllers:
MAKE SURE IF THERE ARE MULTIPLE NICs ONLY 1 IS ENABLED...THIS IS VERY IMPORTANT

DNS:
PDCe points to himself and himself only for DNS
replica DCs point to PDC for preferred, themselves as alternates (for simple standardization)
clients in site with PDCe point to PDCe for preferred DNS, and replicas as alternates
clients in remotes sites point to their local DC for DNS, and other DCs as alternates

GigaBit NIC:
Set to 100MB/full (or 10MB/full if using 10MB switches)
Ensure DNS config is correct as shown above
Ensure advanced tcp/ip proeprties has netbios over tcp/ip enabled (unless you get dhcp address) on WINS tab
ensure advanced tcp/ip properties on DNS tab ONLY has a dns server address(es), append primary and connection specific suffixes, append the parent suffix of the primary dns suffix, and register this connections addresses in DNS set in...all else should be blank and/or unchecked



Other:
Linksys is full of crap and trying to get more money for support calls...using a router for DNS is a very bad idea when using AD....it is most likely your issue as well....which leads back to DNS config...don;t trust junk....MS DNS is designed to work beautifully with AD....AD tends to break when using any other DNS server (QIP tends to break trust paths, BIND tends to jack with kerberos, etc.)

the router will have no concept of the _msdcs zone, and in addition, it likely will not know what an SRV record is, not to mention proper placement....



the hotfix is not your answer here if you're using the router for DHCP and DNS....you MUST move at least DNS back to the DCs.

technically, you need to be doing everything outlined in here...it should do the trick for you.


-Brandon Wilson
MCSE00/03, MCSA:Messaging, MCSA03, A+
almost got a paragraph there