Does anyone have an update regarding Windows 8.1 not being able to see the JS550 ad hoc wifi signal? Has anyone identified a good work around?

Submitted by hipkts2015 on Thu, 2015-02-19 10:46

Permalink

I just made this work only yesterday. Put this into a Google or Bing search. How to create Wireless Ad Hoc Internet Connection in Windows 8. It involves some "NETSH" commands and does work. Best Regards,

Submitted by hipkts2015 on Thu, 2015-02-19 10:48

Permalink

I may have not read the post correct. What I posted, will allow you to setup the Ad Hoc network on the Windows 8.1 machine. However, that page may help you find the info you require. Regards,

Submitted by Art on Thu, 2015-02-19 11:57

Permalink

Mike aka hipkts2015 brings up a good point: that with some special commands, it can work. In other words, for a few of our v1.x users--ones who are patient enough and have time--it may be an option. However...most aren't and don't and there's still some caveats. Our new v2.x WiFi JIB has a completely revamped wireless section that eliminates this tedium. We try not to sell tedium. We want our folks to plug in and go. I appreciate any usable updates to this conundrum with the v1.x WiFi hardware--and if there were a one-size fits most, with a clear and uncomplicated way to implement it I'm all ears. Cheers Art Renda Documentation Central Silverleaf Electronics (888) 741-0259

Submitted by Art on Thu, 2015-02-19 12:08

Permalink

Yes--one can set up the AdHoc network using the NETSH and other commands from a command line. However, that's only one end; as the broadcaster for an open network. Our units are secured, using a password scheme. Though uncomplicated, its still the minimum price for admission. And while a Win-8.1 PC can set up the Open (non-passworded) AdHoc connections via NETSH, it cannot be a secure network or be joined by anything but an open (unprotected) device. Pretty limited. In our context, the JIB's password scheme helps principally with device isolation (so one coach at a rally isn't mistaken for another when connecting. It can happen. Its not a 'safety' issue as much as confusion-prevention by way of a pass code. I have many hours trying this--and if you're able to both create the AdHoc net _and_ join it with the JIB (and have VMSpc function) I'll personally reward you! Free coffee, on me, made here at Documentation Central. What a deal, eh? Keep me posted ;-) Art Renda Documentation Central Silverleaf Electronics (888) 741-0259