IPBan v1.3.5 releases: Monitors failed logins and bans ip addresses
- For Windows, IPBan is supported on Windows Server 2008 or equivalent or newer. Windows XP and Server 2003 are NOT supported.
- Extract the IPBan.zip (inside is IPBanWindows.zip) file to a place on your computer. Right click on all the extracted files and select properties. Make sure to select “unblock” if the option is available.
- You MUST make this change to the local security policy to ensure IP addresses show up: Change Local Security Policy -> Local Policies -> Audit Policy and turn failure logging on for “audit account logon events” and “audit logon events”. From an admin command prompt: auditpol /set /category:”Logon/Logoff” /success:enable /failure:enable
- For Windows Server 2008 or equivalent, you should disable NTLM logins and only allow NTLM2 logins. On Windows Server 2008, there is no way to get the ip address of NTLM logins. Use secpol -> local policies -> security options -> network security restrict NTLM incoming NTLM traffic -> deny all accounts.
- To run as a Windows service run “sc create IPBAN type= own start= auto binPath= c:\path\to\service\IPBan.exe DisplayName= IPBAN”. The service needs a file system, event viewer, and firewall access, so please run as SYSTEM to ensure permissions.
- To run as a console app, simply run IPBan.exe and watch console output.
- If you want to run and debug code in Visual Studio, make sure to run Visual Studio as administrator. Visual Studio 2017 or newer is required, along with .net core 2.1.1. The community edition is free.
- IPBan is currently supported on Ubuntu 16.X – 18.X. For other Linux or MAC, you may need to adjust some of the instructions and add config file entries for the appropriate log files to parse.
- SSH into your server as root. If using another admin account name, substitute all root user instances with your account name.
- On Windows, add an error message in case program is run without administrator permissions.
Author: Jeff Johnson