Article ID: 263208
Article Last Modified on 2/27/2007
APPLIES TO
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Professional Edition
- Microsoft Windows 2000 Server
This article was previously published under Q263208
SYMPTOMS
When you try to connect to a computer, the connection may not work. In the client System event log, you may also receive one or more event ID 3034 event messages that have a source of MRxSmb (MRxSmb is the SMB mini-redirector that has secure SMB capabilities in Windows 2000). In the "Data" section of the event message, the last DWORD value in the list, ordered by WORDS, is 80090322.
CAUSE
The event 3034 error message with the specific status code of 80090322 (SEC_E_WRONG_PRINCIPAL) indicates that the client tried to connect to the server with a computer name that is different from the actual computer name of the server.
You may also receive event 3034 event messages if two computers accidentally register the same IP address in the Domain Name System (DNS). In that case, the A record for the computer that hasthe incorrect IP address should be deleted in DNS.
RESOLUTION
This problem is typically the result of a host name resolution issue. If it is, on the client computer, use the ping command to verify that the IP address that the client is using for the server is correct. For information about the ping command, see Windows Help. If the IP address is not correct, you must determine where the incorrect address comes from, and then contact your network administrator. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
200525 Using NSlookup.exe
MORE INFORMATION
If the server is linked to the network by using remote access functionality and Point-to-Point Tunneling Protocol (PPTP), and you are using dynamic Domain Name System (DDNS), this issue may occur until the server's DNS entry has been replicated across the available DNS servers.
Keywords: kbappdev kbdns kbperformance kbprb kbsmb KB263208
