Interesting that you mention that, I tried that, and it might of worked. But I was also using an earlier version of JMRI on a different user account. So I just deleted the up to date version and installed an earlier one on the dispatcher's account. It magically started working...
I'm beginning to realize that Windows 10 and sound decoders have a lot in common. There are so many things you have to change in order to get them to work the way you want.
Did anything change from when it used to work to now? I had this problem with one of my computers and it was a firewall issue. The developer of Engine Driver posts at the JMRI group and is very helpful.
Gary
How do I do that? Also, remember that the computer can run trains just fine and that the Withrottle used to work fine.
Since you had USB issues, the port may have changed. Make sure the port assignment matches what is in the throttle config.
Modeling BNSF and Milwaukee Road in SW Wisconsin
I tried some stuff from the JMRI website, but it didn't really help. I will check out that link though.
I can't really add anything helpful. I first set up Engine driver and Wi throttle about three years ago and never had to diagnose anything since it still works every time.
I wonder if there were any security changes on your network or firewall?
Maybe dump everything and set it up from scratch?
http://jmri.sourceforge.net/help/en/package/jmri/jmrit/withrottle/UserInterface.shtml
I assume you have read through any help at the JMRI site?
Good Luck, Ed
So yeah. First it was the NCE usb issue and I figured that out, as well as a major recent powercab issue. Now it is Withrottle. It used to work fine, but as of a couple weeks ago, it doesn't. The server "broadcasts" an IP address, but niether IOS nor Android will connect. And the Withrottle server won't recognize that they are there either. JMRI throttles work just fine and I can run trains direct from the computer. I think that is all. Any ideas?