I was wondering if anyone else has experienced the following and has a solution.

We have a PC set up to start MyPhoneExplorer automatically after login. This is so the operators at our radio base can restart the PCs and have everything they need start up without manual intervention. MyPhoneExplorer is configured to connect to a fixed IP which the phone picks up from a DHCP reservation.

What I am finding is maybe 50% of the time MyPhoneExplorer would not connect on start-up. I have narrowed the problem down to the Android phone not always responding to ARP requests in a timely fashion (if at all). The PC obviously has an empty ARP table after starting up, and MyPhoneExplorer will timeout prior to the Android phone eventually responding to the multiple ARP requests the OS sends.

What I am trying to work around the issue is to have task scheduler ping the Android's IP prior to starting MyPhoneExplorer. Early tests show this appears to be working. If this isn't reliable, my next attempt is to set a static ARP entry, but that isn't a good practise and I would rather avoid that.

Has anyone else experienced such an issue and has ideas? Is there any way to increase the timeout built into MyPhoneExplorer?