Can't connect in Infrastructure mode or AP

[stefdds]

Not that I'm aware of ; however, if att did some sort of a update I would have no idea.
As far as anything that I personally have done, no I never made any adjustments to it. Thanks Dave.


OK, news and update: I called att tech support and was pleasantly surprised how helpful they (he) was. He did state that att does block 3rd party apps. He did "see" the hex-net on the status list and did a IP pass through on my router. And did set manually the TCP and UDP ports ; although he stated that he opened them all, but did go back and do those two specifically. He stated all were now open.

However, the middle led still blinks red (infra. mode). So he thought there may be a problem with the HN. (??).

 

[Uwe]

However, the middle led still blinks red (infra. mode). So he thought there may be a problem with the HN. (??).

I doubt it, but if you would like to send it in to be tested (no charge for that) we'll give you an RMA.

-Uwe-

 

[Dana]

Two additional suggestions before we generate a RMA number include:

1) Try clearing out all of the old wireless profiles so you can start fresh.

Power it via USB, wait for the interface to finish booting and then press and hold the red button for roughly 50 seconds. When you hear 4 short beeps, release the button. It should confirm the reset with one long beep and the WiFI LED should be amber confirming AP mode.

Open VCIConfig and setup your router once more to see if the results change after saving the router profile.

2) I would try a different router if possible.

If that isn't possible I would enable a wireless hotspot on your phone, make sure the phone is broadcasting a 2.4GHz signal and then configure that using VCIConfig. As long as you do this in that order (Land based router followed by Cell phone) the HEX-NET should always default to the land based router as long as your wireless hotspot is off on the cell phone.

 

[stefdds]

Ok, I give that another try Dana. Thanks again.

@Dana , @Eric , @Uwe

EDIT: Ok, I plugged into usb, held red button (only took about 15 sec.) dbl. beep , let go of button, long beep. first led red/amber flashing , middle led green.
I did this three times as I was expecting a longer reset time.

Went into vconfig and cleared out all of my IP addresses (8 or 9 of them , all the same , "forget this network" delete.

clicked on wifi and my IP address, entered PW , it connected ; router configured (I think).

Unplugged from USB and went out to vehicle and plugged HN in. Waited about 20 seconds or more (it wasn't looking good, first led blinking green, but second led flashing red , third solid green) . Then middle led went green! But then it connected! Hallelujah! Its not a V2 anymore!

I learned more about TCP and UDP ports than I was really interested in, but here we are! Thanks again to all who commented.

 

[TTT]

So, what was wrong in the HN .....

 

[Eric]

Far be it from me to argue with success, but I think it's the first time I've seen someone's public IP in VCDS' Options->Test

 

[Uwe]

I think it's the first time I've seen someone's public IP in VCDS' Options->Test

Yeah, uhm... Why do I think AT&T reconfigured his router as a bridge?

-Uwe-

 

[stefdds]

I noticed that IP address also. It IS different than the one I had , it used to end in dot 65.

So, what was wrong in the HN .....

Nothing,

ATT blocked all third party apps for "security" they said. If I did not call them, I would never have known. It was also odd that opening the ports on my PC seemed to activate (?). But, when I did a online website that will test ports for you, it showed Closed.

For context : https://www.yougetsignal.com/tools/open-ports/

It also seemed to help to reboot/reset the HN and clear all the addresses from the Vconfig. list (per Dana's suggestion). Ie, start over as if the HN was new. Thanks again all!