Syspeace 2.10. x86 brute force protection windows server

Editors' review

May 17, 2016

Download Syspeace 2.10. x86 brute force protection windows server

My winforms ReportViwer failed to connect to the Report server. The server is on a win 2008 server R2.
Both client and server computers are not on any domain, but connected to the same wifi network. I disabled loopback check as MSFT kb suggested (
Does anyone know how to solve this logon issue?
Log Name: Security

Source: Microsoft-Windows-Security-Auditing

Date: 2/10/2010 7:34:06 PM

Event ID: 4625

Task Category: Logon

Level: Information

Keywords: Audit Failure

User: N/A

Computer: serverName


An account failed to log on.


Security ID: NULL SID

Account Name: -

Account Domain: -

Logon ID: 0x0

Logon Type: 3

Account For Which Logon Failed:

Security ID: NULL SID

Account Name: reportUser

Account Domain: serverName

Failure Information:

Failure Reason: Unknown user name or bad password.

Status: 0xc000006d

Sub Status: 0xc000006a

Process Information:

Caller Process ID: 0x0

Caller Process Name: -

Network Information:

Workstation Name: 123-PC

Source Network Address: -

Source Port: -

Detailed Authentication Information:

Logon Process: NtLmSsp

Authentication Package: NTLM

Transited Services: -

Package Name (NTLM only): -

Key Length: 0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.

- Transited services indicate which intermediate services have participated in this logon request.

- Package name indicates which sub-protocol was used among the NTLM protocols.

- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

Event Xml:

Event xmlns=


Provider Name=Microsoft-Windows-Security-Auditing Guid={54849625-5478-4994-A5BA-3E3B0328C30D} /







TimeCreated SystemTime=2010-02-11T00:34:06.646670900Z /


Correlation /

Execution ProcessID=476 ThreadID=528 /



Security /



Data Name=SubjectUserSidS-1-0-0/Data

Data Name=SubjectUserName-/Data

Data Name=SubjectDomainName-/Data

Data Name=SubjectLogonId0x0/Data

Data Name=TargetUserSidS-1-0-0/Data

Data Name=TargetUserNamereportUser/Data

Data Name=TargetDomainNameserverName/Data

Data Name=Status0xc000006d/Data

Data Name=FailureReason%%2313/Data

Data Name=SubStatus0xc000006a/Data

Data Name=LogonType3/Data

Data Name=LogonProcessNameNtLmSsp /Data

Data Name=AuthenticationPackageNameNTLM/Data

Data Name=WorkstationName123-PC/Data

Data Name=TransmittedServices-/Data

Data Name=LmPackageName-/Data

Data Name=KeyLength0/Data

Data Name=ProcessId0x0/Data

Data Name=ProcessName-/Data

Data Name=IpAddress-/Data

Data Name=IpPort-/Data