"Slave failed to respond", but appears to work

4,080 views
Skip to first unread message

Daniel Wolf

unread,
Aug 23, 2010, 11:10:56 AM8/23/10
to Input Director
Hello!

I installed Input Director on a machine with WinXP 32bit SP3 (master)
and another with Win7 64bit (slave).
When I move the cursor out of the master PC's screen, everything seems
to work: it moves to the slave PC's screen, where it shows the ripple
effect. There I can move the cursor and click things. But after a few
seconds (whatever I configure under "Time to wait for a slave to
respond"), the cursor jumps back to the master PC and an error message
sais: "Input Director: Slave failed to respond", "Slave system ...
failed to respond. Do you want to skip this slave?"

So it seems to me that the master PC can send information to the slave
(because the mouse cursor works on the slave machine), but the slave
cannot answer (because the master cancels the remote control and shows
an error message after the timeout).

Additional information: both PCs are connected to the same switch.
Both PCs' firewalls are deactivated. Neither PC has a VPN client
running. Either PC can ping the other one without any problems, either
by name or by IP. The slave is configured to "Allow any computers to
take control".

Does anybody have an idea what might be wrong?

Thanks in advance
Daniel

Daniel Wolf

unread,
Aug 24, 2010, 6:05:18 AM8/24/10
to Input Director
PS: I forgot to mention that I installed the latest version, 1.2.2.

Shane

unread,
Aug 24, 2010, 9:33:58 PM8/24/10
to Input Director
Hi Daniel,

It definitely sounds like a comms issues from the slave to the master.
Does either system also have a wireless card/connection?

Open Input Director and switch to the "Global Preferences" tab - hit
the "Change" button under Preferred Network Interface and select your
primary network interface (do this even if there is only one option
here). Repeat the process on both the master and the slave. Does this
help?

Regs,

Shane




Daniel Wolf

unread,
Aug 25, 2010, 3:55:50 AM8/25/10
to Input Director
Hi Shane,

> Open Input Director and switch to the "Global Preferences" tab - hit
> the "Change" button under Preferred Network Interface and select your
> primary network interface (do this even if there is only one option
> here). Repeat the process on both the master and the slave. Does this
> help?

Thanks for your answer. I tried it, selecting the Gigabit Network
Connection in both cases. To be on the safe side, I restarted both
program instances. The problem still exists.

Best regards,
Daniel

Tutunkommon

unread,
Aug 27, 2010, 2:24:51 PM8/27/10
to Input Director
Hmmm... Don't see my earlier post, but I have the same problem with a
pair of computers that I have been using for several months. Both are
on 1.2.2 The master is WinXP and the Slave is Win7 64bit.

I did install LogMeIn Hamachi on both machines about 1 month ago, but
that didn't seem to affect anything at the time. I rebooted both
machines today, and an hour or so later, ID stopped working with the
same symptoms.

I shut down LogMeIn and killed anything remaining in the task manager,
but it did not make a difference.

I also tried setting ID to use the LogMeIn network adapter as
preferred but that didn't help either.

I hope a solution is found soon. I almost can't function anymore w/o
ID on my setup, since I have arranged my desk around having this
working. =^)

If there is any troubleshooting I can do to help, let me know.

--Joe Jansen

Tutunkommon

unread,
Aug 27, 2010, 1:53:19 PM8/27/10
to Input Director
Oddly, I am having the same problem. Same setup (WinXP 32 master and
Win7 64bit Slave). The difference is that it was working fine for
several months, and now today, for no apparent reason, it stopped
working. I beleive the only thing I did was reboot the slave machine.

Does ID do stealth updates? (ie: update itself in the background
without notifying me). I cannot figure out what would have changed to
make it stop working...

Tutunkommon

unread,
Aug 27, 2010, 4:10:29 PM8/27/10
to Input Director

One more reply. I figured out the problem. Windows firewall on the
master had the exceptions screwed up somehow. I added port 31234 TCP
and UDP (I think UDP was the only one I needed) to the exception list
and it started working again.

Something weird had happened to Win Firewall too. When I tried to
open it it said it was disabled b/c the service was not running, and
would I like to start it. I did, and added the port and it started
working.

Hope this helps.

--Joe Jansen

Simon S

unread,
Aug 9, 2016, 8:11:36 AM8/9/16
to Input Director, joe.j...@gmail.com
Hi,

This helped (on Windows 10 - I know, not supported, but it worked until last week)!  If I turn Public Network firewall off on the Master (under Turn Windows Firewall On or Off), and keep Private Network firewall on, it works.

So, the problem is with the Public Firewall settings, but it's not ideal to keep this off. Experiments continue, but I'd be greatful for any input...

Simon S

unread,
Aug 9, 2016, 8:29:20 AM8/9/16
to Input Director, joe.j...@gmail.com
Uninstalled and upgraded to 1.4 - same problem sadly
Reply all
Reply to author
Forward
0 new messages