Cursor makes it to slave but freezes followed by "Slave didn't respond

[Modern Times]

I've been using Input Director for awhile on the same 2 laptops (one running windows 7 and one running windows 10) and I've never had a problem until now.

When I move my mouse from the master system to the slave system, the cursor appears on the slave system with the rippling effect, but then won't move and I get the "Slave didn't respond "message.

I've uninstalled Input Director from both systems (deleting the configuration on both), disabled Windows Firewall on both systems (I'm having trouble getting Windows Firewall to work on the Master system), and reinstalled the latest version of Input Director, but still have the same issue.

Any suggestions would be greatly appreciated.

Harry

[Shane]

Hi,

This usually points to one of 2 issues:

1. The network traffic is blocked by a firewall (software on the end computer or on the router/modem itself)

2. One or both of the computers have 2 network interfaces (e.g. wired and wireless) and the traffic isn't being routed correctly.

To solve this try:

1. Open Input Director and switch to the "Global Preferences" tab

2. Click the "Change" button under Preferred Network Interface

3. From the pop up window, select the network common to both computers

Do this on both the master computer and slave computer.

Regs,

Shane.

[Modern Times]

Hi Shane,

Firewall is turned off on both systems, so wondering if there's something else that can be blocking Input Director?

Also, I checked and under the preferred network interface, the network and mask are identical.

I've uninstalled and reinstalled everything and still have the issue, but now get a message on the slave machine the 1st time I try to connect that an unauthorized computer is trying to connect and asks if it should switch to slave mode, which I do, but it still doesn't work.

I've attached screen shots of the Master & Slave configurations.

Really hoping there's a fix, as I'm totally dependent on Input Director to get through the day...:-) 

Thanks,

Harry

[Shane]

Hi,

Can you email screenshots of your master "Main" tab, slave "Slave Configuration" tab and the "Global Preferences" tab from both the master and slave systems. I'll see if I can work out what's happening.

Thanks,

Shane.

[Modern Times]

Thanks so much, Shane. Just emailed you the screen shots.

Harry

[Herb Gander]

Has there been a resolution to this issue?

[Shane]

Hi Herb,

This symptom can be caused for a number of different reasons. If you’re having problems, try following the steps I mentioned in the earlier post. If this doesn’t help, let me know and I’ll try and help.

Regs,

Shane.

[Herb Gander]

Thanks, Shane:

Did check the below and my situation is that Master system is desktop, wired to router, Windows 7. Slave is laptop, wireless to same router, Windows 10. Therefore I can't select the same network since Master is wired, Slave is wireless. Could that be the issue?

1. Open Input Director and switch to the "Global Preferences" tab

2. Click the "Change" button under Preferred Network Interface

3. From the pop up window, select the network common to both computers

[V@no]

On Monday, July 30, 2018 at 12:14:40 PM UTC-4, Herb Gander wrote:

Did check the below and my situation is that Master system is desktop, wired to router, Windows 7. Slave is laptop, wireless to same router, Windows 10. Therefore I can't select the same network since Master is wired, Slave is wireless. Could that be the issue?

I think you are mistaken network card with actual network...If both computers connected to the same router, chances are they are both on the same network even if they use different network cards. Input Director doesn't care how your computers connected to the network, as long as it knows which network card it needs to use to connect to other computer.

[bruno....@tapps.com.br]

I have the same problem, the IPs are on the same mask (same prefered network) and I have also disabled the firewalls on both machines, but no luck, same problem