Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
The server was unable to logon the Windows NT account 'firstname.lastname@example.org' due to the following error: <error description> The data is the error code.
|English: This information is only available to subscribers. An example of English, please!|
|Concepts to understand:|
What is FTP?
In the detailed view, the error messages says: "The stub received bad data".
Solution: When the ActiveDirectory Domain contains Windows Server 2008 R2 Servers and the server on which the FTP service is running is a Windows Server 2003 (of any Service Pack Level), the IIS 6.0 cannot authenticate Users in UPN Format (email@example.com). This is a known bug by Microsoft documented in ME956114 (a hotfix is available there).
Error: Logon failure: unknown user name or bad password - From a support forum: "It was suggested to me that the FTP service was attempting to start under the credentials of the administrator and it should be running as local system or network service. However, that was not the case but I fixed the problem by resetting the administrators password."
Error: "Logon failure: unknown user name or bad password." - I was seeing this when using domain accounts to log in instead of anonymous logins. It turns out that disabling NetBIOS over TCP/IP on the NIC servicing the site was the culprit. Everything worked again after re-enabling NBT.
ME323384 provides information on how to set up an FTP server in Windows Server 2003.
This event can occur if the Users group does not have the logon locally user right on the domain controller. See WITP74658 to solve this problem.
I received this message after demoting a Windows 2000 DC to a member server. After trying the Adsutil.vbs script solutions, I realized that anonymous password synchronizing only works locally. I changed my security user to point to my local anonymous user (IWAN_*****) and I was able to log in anonymously again.
I received this error from all attempts to logon to FTP after demoting a DC to a member server that has no anonymous access. ME310723 pointed out how to change the DefaultLogonDomain key using an administrative VBS in the Adminscripts set.
Error: Logon failure: unknown user name or bad password. - For a IIS 4.0, the IUSR_<computer> account's password is not synchronized between the FTP site and User Manager. Resynchronize the passwords. You may need to clear the "Enable Automatic Password Synchronization" checkbox in order to get this to work properly. See Microsoft article ME185377.
- Error: "The specified module could not be found" - See ME306450.
Message generated when someone tries to connect to an IIS FTP server as anonymous when this type of logon has been disabled.
Gregory R. Tellone
Error: Logon failure: unknown user name or bad password. - This can be caused if you have removed anonymous logon from IIS 5.x running on Windows 2000 Server and have not granted the "Log on locally" right to the username above. Fix - create a Security Group in Active Directory called, i.e. "FTP Users", add specific users to this group whom you want to grant FTP access. Follow directions in ME285806 to grant "Log on locally" right to this Active Directory Group. NOTE: If the FTP server is a Member Server or DC of Active Directory, follow the directions in ME285806. If this server is NOT a Member/DC of Active Directory, follow the same procedures but run "Local Security Settings" instead of "Domain Controller Security Policy".
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated