General discussion

  • Creator
    Topic
  • #2076922

    Ed Bott’s Microsoft Challenge–8/31/00

    Locked

    by ebott ·

    A Windows 2000 network admin is baffled by an overload of Event Viewer errors. Can you help? The errors appear several times a day in the Application Log and always take the following format:

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

    The system in question is properly joined to its domain and has no problem accessing shared network resources. He can’t find any sign of this error in the Knowledge Base. I’ll give special preference to anyone who can provide links to comprehensive resources that he can use to decode other Event Viewer messages.

All Comments

  • Author
    Replies
    • #3779323

      Ed Bott’s Microsoft Challenge–8/31/00

      by jaystar ·

      In reply to Ed Bott’s Microsoft Challenge–8/31/00

      Dear ED,
      The following article was posted on TechNet May 16th, 2000
      http://support.microsoft.com/support/kb/articles/Q261/0/07.ASP

      I found it by searching for the return code in the text.

      From searching the TechNet site, it appears WIndows 2000 maps multiple errors to the 1000 event ID code. If this is the practice for other event codes, it maybe impracticle to try to generate a list of event codes to solutions w/o including descriptions with each event code.

      My links follow:
      http://www.technet.com
      http://www.microsoft.com/technet

      Good luck,
      Jay

    • #3779260

      Ed Bott’s Microsoft Challenge–8/31/00

      by ejsotillo ·

      In reply to Ed Bott’s Microsoft Challenge–8/31/00

      I would go straight to good old Dr. Watson (drwtsn32.exe) to get a little more inside info pertaining to the problem, from there take it to technet knowledge base or online knowledge base at microsoft.

    • #3779213

      Ed Bott’s Microsoft Challenge–8/31/00

      by jessed ·

      In reply to Ed Bott’s Microsoft Challenge–8/31/00

      Hmmm, tough one. I’d venture to say that if network browsing/domain and resource access isn’t a problem, then an unreachable DNS host isn’t the cause (as is thought by some), but, worth checking just to be sure. Perhaps some app that creates user accounts (such as IIS) was installed and then removed; the user accounts were deleted, but for some reason, they stuck in the registry somewhere. If Win2K were trying to audit the registry with the SAM, it may be the source of the entry.

      Try this, provided by JSI Inc.:
      To find the problem:
      1. I navigated to HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\Winlogon\GPExtension\{827…} and Added Value name ExtensionDebugLevel as a type REG_DWORD, setting it to 2. This turned on logging for Winlogon.

      2. At a CMD prompt, I typed:

      secedit /refreshpolicy machine_policy /enforce to create %SystemRoot%\Security\logs\Winlogon.log.

      http://www.jsiinc.com is by far the best resource I’ve come across for event log type troubleshooting, actually providing answers a lot of time

      -jd

    • #3787688

      Ed Bott’s Microsoft Challenge–8/31/00

      by jackieb ·

      In reply to Ed Bott’s Microsoft Challenge–8/31/00

      I did a little looking around for an answer to your question and the only thing I found quickly was this web site:
      http://www.globetrotting.com/winnt/eventviewer.htm

      It references using the NT resource kit to look up the error code. I loked at MS Support web site and the 1722 code listed there refers to an issue concerning server access. Perhaps another user (jessed) was on the right track when he mentioned that it could be a dns issue. Perhaps the dns is becoming unavailable at times, generating this error. This could be due to the network link to the server being too busy due to user loading resulting in an occasional inability to get a response from the dns. I know, everyone blames the network, but thats what I do for a living, andsometimes odd problems like this can be caused by network congestion, probably on the link to the server. Hope this helps. Jackie

    • #3787678

      Ed Bott’s Microsoft Challenge–8/31/00

      by chris ham ·

      In reply to Ed Bott’s Microsoft Challenge–8/31/00

      I had this error message for some of my client. When I set up first, I didn’t have any problem, but after user start using it the error message start show up. One difference I have is that it also show error message of “no netlogon server available or net path can not be reached” and log on using local cache. But after that user is joined to the domain and all the shared network resources are available to the user. The cause of the problem was some incompatbility problem with windows 2000, motherboard & NIC card. After I changed the NIC to another brand, I never so the error again.

    • #3787876

      Ed Bott’s Microsoft Challenge–8/31/00

      by smchargue ·

      In reply to Ed Bott’s Microsoft Challenge–8/31/00

      This behavior can occur if the address for the configured preferred DNS server on the client is invalid or unreachable.

      Please refer to http://support.microsoft.com/support/kb/articles/Q261/0/07.ASP

    • #3787795

      Ed Bott’s Microsoft Challenge–8/31/00

      by robw ·

      In reply to Ed Bott’s Microsoft Challenge–8/31/00

      From MS website

      Right-click My Network Places, and then click Properties.

      Right-click Local Area Connection, and then click Properties.

      Click Internet Protocol (TCP/IP), and then click Properties.

      Type the correct DNS address in the Preferred DNS server box

    • #3787741

      Ed Bott’s Microsoft Challenge–8/31/00

      by joe.mccoy ·

      In reply to Ed Bott’s Microsoft Challenge–8/31/00

      winsdows cannot determine the user or computer name. return value (1722)

      Your preffered DNS server address on this client maybe unreachable.

      To fix the problem:

      1. Right-click on My Network Places, goto Properties.

      2. Right-Click Local Area Connection, select Properties.

      3. Press Internet Protocol (TCP/IP) and Goto Properties.

      4. In the preffered DNS Server box, add the correct DNS server address.

      Note: Their are some other possible causes, This one here on average seems tobe the reason for the error.

    • #3786105

      Ed Bott’s Microsoft Challenge–8/31/00

      by hill ·

      In reply to Ed Bott’s Microsoft Challenge–8/31/00

      For one I stick to the KISS idea (keep it simple stupid), no the person is not stupid but sometimes we look in the all the wrong places and the code is even hidden from MICROSOFT. I tend to look in the current set up especially if the Net work is already in place befor the server so forgive simple mindedness. I now have a quest thanks! Here’s a question and a comment. 1st did the IT turn off each work station or isolte each work station and reboot the server to see if the error came back in theevent viewer? Also was there a server machine that might have been a BDC? Was there a NT work station that might have been running as a server before in the work place? Or did someone hide their profile and the server sees it and we can not? I’m on my way to code land.

    • #3785891

      Ed Bott’s Microsoft Challenge–8/31/00

      by saveurpc ·

      In reply to Ed Bott’s Microsoft Challenge–8/31/00

      The problem is that workstation did not have correct DNS infomation. I find some thins very interesting is some of the NIC cause the problem but some don’t.

      If you setup the machine with limit Ip port . you will get same error message.
      my solution is check if the station has set up any TCP/IP filtering. if yes! you have try to find out which TCP Or UDP port you need open. If nothing has been setup.
      I will try different NIC.

    • #3785832

      Ed Bott’s Microsoft Challenge–8/31/00

      by bill.parks ·

      In reply to Ed Bott’s Microsoft Challenge–8/31/00

      Uuummmmmm…did anyone understand what hill@jobe.net said???

    • #3732742

      Ed Bott’s Microsoft Challenge–8/31/00

      by johnk ·

      In reply to Ed Bott’s Microsoft Challenge–8/31/00

      Has he added/changed any applications? It appears to be in the user environment, and as it is appearing in the Application log this is the most likely place to start.

    • #3732584

      Ed Bott’s Microsoft Challenge–8/31/00

      by werner.froschauer ·

      In reply to Ed Bott’s Microsoft Challenge–8/31/00

      the problem could be, that the preferred DNS Server address is unreachable or wrong.
      to solve the problem you have to go to the Properties of the network-protocol and type the correct DNS server address.

    • #3864238

      Ed Bott’s Microsoft Challenge–8/31/00

      by ebott ·

      In reply to Ed Bott’s Microsoft Challenge–8/31/00

      This question was auto closed due to inactivity

Viewing 13 reply threads