Hex Net won't connect (wireless) to (two) iOS devices ??? "heads up" iOS users
I've been using Hex Net for some time now with little or no Connection problems: either windows 7 or 10 on a laptop or my Ipad air ; both wireless or with vcds Mobile. In fact I had just used , 2 days earlier, the ipad with vcds mobile to reset some service settings.
Yesterday I upgraded / updated my Iphone . I was using a 4s from late 2011 ; I upgraded to a iphone X x-max (it was a big day). After I activated my new Iphone and did a apps transfer etc. , I wanted to connect to vcds with the hex net. I could not connect to the hex net with either the ipad or the iphone. No matter what I tried , either mode infrastructure or access point, wiFi showed the correct address of the hex-net or the home wifi address, but nothing would work. The message on the all white screen was "hex net can not find connection address" or something similar to that. (no home screen or log in / password landing page). Also, refreshing made no difference, nor did it even function.
I called tech support this morning and spoke with a very knowledgeable member of the RT team (she sounded like Kim Komando! - I hope that doesn't offend her) who was very thorough and helpful. She recommend a few diagnostics: Use the config cable and power up the hex net and go into hex net config utility and try to connect the vcds with either vcds or vcds mobile while using my windows lap-top. So, I did just that and hex net connected just fine: both wireless on the new iphone with vcds mobile and plugged into the windows laptop with vcds. I also did a update as long as I had the config utility going. Which she did mention, but thought that was not the problem. I wasn't completely surprised , since this all started when I activated my new iphone.
I then plugged it back into the car and had the same connection problem on both the Iphone and the Ipad with vcds mobile - No connection , no device found. I then wanted to try my theory: I reasoned that the two ios devices were now synced together since they both run current ios software 12.3.1 or something like that. The 4s iphone would only update to 9.3 or there about. And since I had no problem before the new phone, I reasoned that perhaps hex net was now trying to connect to TWO iOS devices at the same time! Even though I was only using one device at a time. The carriers are different as the ipad has verizon LTE, and the iphone is ATT . But, in settings you can choose the address you wish to connect to wifi or hex net address or the home att wifi . I mention this because maybe one is causing problems in the background (verizon LTE ? even though wifi selected ?? ) ; I really don't know, but wanted to mention it.
I then completely Powered OFF the ipad (the screen was dark before, but it was not completely powered off) and tried the iphone with vcds mobile in access point (green LEDs on the ends and amber in the middle) and boom, it connected right away to the landing sign in page! I then Powered OFF the iphone and turned on the ipad and had the same successful result: no problem connecting with vcds mobile on the ipad which went right to the sign in page. Both sign ins required me to go to settings and select the hex net address number (they were showing the home wifi address initially), but when selected all functioned as intended.
So, the "heads up" , and what I have discovered, is if you are using two iOS devices in the car or even in range of one another at home (a iphone and a ipad for example) and both are in low power mode with the screen dark and you choose to use one with the hex net , there seems to be a conflict with connecting to hex net wireless ; simply Power off completely one of the devices and all works as intended (no connection problems) ! I'm sure there is a way to set one or both of the devices so there is no conflict, but I have not discovered or know enough about the details to do that setting at this time. I suspect that even though the wifi or hex net address is selected, the verizon LTE is creating a problem in the "back ground" - just not sure.
And a big Thank you to the young lady (Edit , Dana) I spoke with this morning at RT support!!
I've been using Hex Net for some time now with little or no Connection problems: either windows 7 or 10 on a laptop or my Ipad air ; both wireless or with vcds Mobile. In fact I had just used , 2 days earlier, the ipad with vcds mobile to reset some service settings.
Yesterday I upgraded / updated my Iphone . I was using a 4s from late 2011 ; I upgraded to a iphone X x-max (it was a big day). After I activated my new Iphone and did a apps transfer etc. , I wanted to connect to vcds with the hex net. I could not connect to the hex net with either the ipad or the iphone. No matter what I tried , either mode infrastructure or access point, wiFi showed the correct address of the hex-net or the home wifi address, but nothing would work. The message on the all white screen was "hex net can not find connection address" or something similar to that. (no home screen or log in / password landing page). Also, refreshing made no difference, nor did it even function.
I called tech support this morning and spoke with a very knowledgeable member of the RT team (she sounded like Kim Komando! - I hope that doesn't offend her) who was very thorough and helpful. She recommend a few diagnostics: Use the config cable and power up the hex net and go into hex net config utility and try to connect the vcds with either vcds or vcds mobile while using my windows lap-top. So, I did just that and hex net connected just fine: both wireless on the new iphone with vcds mobile and plugged into the windows laptop with vcds. I also did a update as long as I had the config utility going. Which she did mention, but thought that was not the problem. I wasn't completely surprised , since this all started when I activated my new iphone.
I then plugged it back into the car and had the same connection problem on both the Iphone and the Ipad with vcds mobile - No connection , no device found. I then wanted to try my theory: I reasoned that the two ios devices were now synced together since they both run current ios software 12.3.1 or something like that. The 4s iphone would only update to 9.3 or there about. And since I had no problem before the new phone, I reasoned that perhaps hex net was now trying to connect to TWO iOS devices at the same time! Even though I was only using one device at a time. The carriers are different as the ipad has verizon LTE, and the iphone is ATT . But, in settings you can choose the address you wish to connect to wifi or hex net address or the home att wifi . I mention this because maybe one is causing problems in the background (verizon LTE ? even though wifi selected ?? ) ; I really don't know, but wanted to mention it.
I then completely Powered OFF the ipad (the screen was dark before, but it was not completely powered off) and tried the iphone with vcds mobile in access point (green LEDs on the ends and amber in the middle) and boom, it connected right away to the landing sign in page! I then Powered OFF the iphone and turned on the ipad and had the same successful result: no problem connecting with vcds mobile on the ipad which went right to the sign in page. Both sign ins required me to go to settings and select the hex net address number (they were showing the home wifi address initially), but when selected all functioned as intended.
So, the "heads up" , and what I have discovered, is if you are using two iOS devices in the car or even in range of one another at home (a iphone and a ipad for example) and both are in low power mode with the screen dark and you choose to use one with the hex net , there seems to be a conflict with connecting to hex net wireless ; simply Power off completely one of the devices and all works as intended (no connection problems) ! I'm sure there is a way to set one or both of the devices so there is no conflict, but I have not discovered or know enough about the details to do that setting at this time. I suspect that even though the wifi or hex net address is selected, the verizon LTE is creating a problem in the "back ground" - just not sure.
And a big Thank you to the young lady (Edit , Dana) I spoke with this morning at RT support!!
Last edited: