Solved

cracker using KSecDD

Posted on 2000-05-18
9
1,230 Views
Last Modified: 2013-12-28
We have 2 NT4 servers with public IP addresses and no firewall.
Someone is trying to crack accounts on these servers. We can see lots of failure messages in the security event logs. They are always from a different domain, different username, different password but with the same logon type = 3 (Network) and logon process = KSecDD (Security Device Driver). What does it mean ? How could we stop these cracking attempts ?

We plan to install a firewall but we would like to find a solution before it.
TIA for any information.
0
Comment
Question by:lde
  • 3
  • 3
  • 2
  • +1
9 Comments
 
LVL 6

Accepted Solution

by:
setiawan earned 150 total points
ID: 2820654
Hi Ide,

becareful, not to share some folder on your server with full access if your server published to internet.

Before you setting your firewall
I suggest you install the latest service pack for your NT Server from MS site.

hope this helps.

  danny
0
 
LVL 86

Expert Comment

by:jkr
ID: 2820940
0
 

Expert Comment

by:vbadier
ID: 2824324
Hi

What about your server? Domain controler or stand-alone?

Regarding your errors, they might be domain controler, because , as i know, logon type 2 and Logon process = User32 are for local security authentification, but the process KsecDD and the Logon type 3 are used for domain authentification.

So, actually, in my opinion, the cracker is stoped by the normal logon athentification.

Sorry not able to help you more for the moment.

Regard's
0
Portable, direct connect server access

The ATEN CV211 connects a laptop directly to any server allowing you instant access to perform data maintenance and local operations, for quick troubleshooting, updating, service and repair.

 

Expert Comment

by:vbadier
ID: 2824331
Sorry, What you could do is enable network monitoring and store trame. Then when reviewing the trame, you could know more about who is attempting to go in (like his IP adress). Then you can lock this particular ip adress.

Hope this help.
0
 

Expert Comment

by:vbadier
ID: 2824370
Sorry, What you could do is enable network monitoring and store trame. Then when reviewing the trame, you could know more about who is attempting to go in (like his IP adress). Then you can lock this particular ip adress.

Hope this help.
0
 

Author Comment

by:lde
ID: 2843213
Thank you all.
It looks like we had forgotten shared folders on the servers. The cracker used a software to try logins on these shared folders.
Now, we have unshared and it's over.
0
 

Author Comment

by:lde
ID: 2843220
Comment accepted as answer
0
 

Author Comment

by:lde
ID: 2843221
Thanks to setiawan.
We had forgotten shared folders.
0
 
LVL 6

Expert Comment

by:setiawan
ID: 2843258
You're welcome
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

If you need to start windows update installation remotely or as a scheduled task you will find this very helpful.
Learn how to PXE Boot both BIOS & UEFI machines with DHCP Policies and Custom Vendor Classes
This is used to tweak the memory usage for your computer, it is used for servers more so than workstations but just be careful editing registry settings as it may cause irreversible results. I hold no responsibility for anything you do to the regist…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

685 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question