It seems "It's me" is the most popular port knocking client for windows…

Except… it sucks. It works for console-savvy users such as me, but, unsurprisingly, all my users (3 people) hate console windows. I know better than to force it upon them.

I would love to have a nice port knocker for Windows that would be windowed, have launchers, and be easily provisionable (i.e. I tell my user to paste some settings or import some file by double clicking it). To be honest, just not being console-based would be enough.

Edit: Please stop trying to convince me not to use port knocking. You're trying to solve a different problem than the problem port knocking solves. Whether port knocking is a good solution or not is irrelevant to this question.

  • Is scripting IM with a .bat file an option? A console window would pop up (presumably with some nice, user-friendly and -assuring messages), sure, but then go away with no actual interaction necessary. Or do you need a solution where your users can select which ports to knock on?
    – Kromey
    Apr 7, 2011 at 0:34
  • 1
    @ErikA: Not necessarily limited to "by obscurity". knockknock uses strong encryption to authenticate the requests.
    – user1686
    Apr 7, 2011 at 5:23
  • 2
    @ErikA: I already do. The failed attempts still pollute my logs and use up resources in other ways. Security through obscurity is insufficient, but it isn't unnecessary.
    – Ekevoo
    Apr 7, 2011 at 19:44
  • 1
    This is a question about clients, not servers. Changing the server is out of scope of this question by definition. That's all there is to this.
    – Ekevoo
    Nov 29, 2012 at 21:14
  • 1
    Trying to change the OP's environment is usually never a solution. In any case - I just want to add that there is no silver bullet to security. With that said - the client that was linked below was written with MFC (ugh) I think I will take it upon myself to write such an application in a more modern language. Mar 1, 2013 at 3:54

2 Answers 2


You should try this one: Windows Port Knocking Application.

It really suits well to my implementation of port knocking on my server! It has a simple GUI with basic options.

  • Good find! I did not know Sowell had put one together! @Ekevoo if you are still looking try this on (and accept the answer!) GUI based, FQDN resolutions, source available and Greg Sowell is a known and Mikrotik consultant with a known and reputable website. Trying it now for myself, I think this will fit your needs.
    – JoelAZ
    Aug 3, 2018 at 18:02
  • Unfortunately, the software currently supports up to 4 knocks (per one list item?), has timeout hardcoded, and may crash in certain circumstances (e.g. select "Description" in the list, press "Add/Update", press "Delete").
    – Faither
    Apr 26 at 3:40

You could use KnockKnock. It has a simple GUI to add the ports that you want to knock.

  • i.stack.imgur.com/n4xC8.png - this tool is buggy. My port numbers are corrupted between sessions :-( additionally you have to use an IP address. Hostnames (FQDN) not allowed.
    – Lord Loh.
    May 5, 2017 at 20:06
  • It seems it doesn't support TCP/UDP selection, though it comes with source files.
    – Faither
    Apr 26 at 3:30

Not the answer you're looking for? Browse other questions tagged or ask your own question.