Constantly losing connection

[Thermopyle]

I've got two Vista computers that have no problem with most network
tasks like file transfers, etc.

I'm constantly getting errors from Input Director that the hostname of
the slave PC can't be resolved. I then have to click the Scan Slaves
button on the Master Config tab...sometimes have to click it multiple
times.

If my mouse is on the slave, sometimes I can't get it back to the
Master without using the hotkey. The Mater rejects the attempt to
bring it back via a screen-edge transition.

Was running 1.08, just tried moving to 1.09 beta...didnt help.

[sh...@inputdirector.com]

Hi,

Input Director relies on the local Windows DNS client to resolve
hostnames. So, if you cannot 'ping' your slave from the master (or
vice-versa) then Input Director will have the same sorts of problem.

Its sounds like there might be a problem with your network setup?
Maybe somebody here (with better knowledge about Windows DNS problems)
can help?

If your IP addresses are statically allocated, then you can use those
in lieu of hostnames in Input Director.

Regs,

Shane.

[Dustin Wyatt]

I've not had any network connectivity issues besides Input Director.
I'm constantly doing file transfers to this PC as it's a home server,
and never run into problems. I also remote desktop into it all the
time with no problems.

Additionally, I wonder about it being a network problem because as I
mentioned, sometimes, I'll have focus on the slave machine and all of
a sudden the Master will have a red checkmark by the slaves name on
the config tab...but I'm still using the mouse/keyboard on the slave
machine. It just won't let me move back to the Master without using
the keyboard shortcut to do so.

Prior to trying out Input Director, I was using Synergy which also
never had problems with this. In fact I can activate synergy now and
use it for extended periods of time, switch back to Input Director and
it's back to the intermittent hostname resolving issues.

[sh...@inputdirector.com]

Dustin,

Just to rule anything else out - temporarily edit the slave(s) and put
their ip addresses in and see if that fixes the problem or whether
there is another underlying problem.

Regs,

Shane.