InputDirector process crashing

129 views
Skip to first unread message

Donny

unread,
Aug 18, 2017, 1:51:14 AM8/18/17
to Input Director
Hello.Got several PCs and laptops in my LAN. Got a strange problem with input director on some of my PCs. The app suddenly crashes and closes down. When you open it again it then seems to work fine then for no reason later on it closes down again. Sometimes when it closes, if you re-open it, it just closes down again after about 10 seconds.
This is happening on the master and slave systems both. I got another two systems that talk to each other on the same router but in another room...they are also having this issue.

I have a couple of laptops in another area of the house connected to a different router, they never get this issue.
Event logs dont show anything significant, just a software crash occurred. I tried capturing procmon logs on one of the crashing masters, theres so much stuff its hard to make head of tail of it. I did notice that on the crashing MASTER, procmon showed "UDP Receive" coming from my two other computers on the same LAN but NOT connected up to this PC as part of the InputDirector configuration...how is that?
On my laptops which are on a different router and working fine...there are no UDP Recieve or Send operations showing in Procmon.

Would be great if anyone can provide any help with this.

Have tried repairing the application aswell, no difference.

Don.

Shane

unread,
Aug 18, 2017, 2:09:18 AM8/18/17
to Input Director
Hi Don,

Are you running the latest (v1.4) of Input Director? Contact me and I'll see if I can help.

Regs,

Shane.

Electro Glyde

unread,
Oct 22, 2017, 1:17:59 AM10/22/17
to Input Director
I've still had this happen to me even with the 1.4 version. I have found that only the Master system front end will occasionally end without warning.

I am currently trying to use fixed IP addresses instead of host names in the Input Director settings to see if it is more reliable (no closing/crashing so far).

I am also testing Windows Firewall rules for the Input Director exe's such that each system will only allow communication with the Scope and IP addresses of these systems. So far so good. I do wish Input Director worked with IPv6 so I could get the best IPSec setup. I may even add some router IP/Port rules in the future.
Reply all
Reply to author
Forward
0 new messages