Login failed for user '401hk'. Reason: could not find a login matching the name provided. [CLIENT: 220.180.111.229]

Question

1.00/5 (2 votes)

See more:

SQL-Server-2014

We have a Microsoft Azure virtual instance and over there we have installed the SQL Server 2014 Express edition. While investigating a issue we found below logs in windows event viewer in application section.

Login failed for user '401hk'. Reason: Could not find a login matching the name provided. [CLIENT: 220.180.111.229]

We observed that there are around 5250 such request in last 24 hours and consuming CPU. The IP and Login name is changing after some requests and all IPs (i.e. 220.180.111.229 ) are locating to China. 
Is it kind of SQL attack? If yes then how to prevent it on Azure(without blocking countries)?

What I have tried:

We have blocked the port 1433 but still got the logs in event viewer.

Posted 8-Apr-17 3:32am

swapnilsonawane123

Updated 9-Apr-17 19:47pm

Add a Solution

Comments

Bryian Tan 8-Apr-17 9:58am

have you try the server level firewall rules to limit the SQL access from certain IP addresses?

Azure portal: Azure SQL Database server-level firewall rules | Microsoft Docs[^]

In your case, you should try database-level firewall
Overview of SQL Database firewall rules | Microsoft Docs[^]

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

swapnilsonawane123 · Accepted Answer · 2017-04-09T19:46:00

Solution 1

The issue got resolved after blocking the port 1433 (sql server) from azure portal.

Posted 9-Apr-17 19:46pm

swapnilsonawane123