News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

ObiWiFi setup can't find 192.168.10.1/wifi

Started by kw2000, December 12, 2018, 06:27:05 PM

Previous topic - Next topic

kw2000

Hi all, I'm trying to setup the ObiWiFi 5G dongle on my Obi202 but cannot seem to access the admin page on the dongle itself. I updated the firmware on the Obi202 to OBi202-3-2-2-5921EX-332148940 but am still stuck on step 5. (I'm following these instructions https://www.obitalk.com/info/products/obiwifi)

Step 5 says "Wait 30 seconds (after connecting to the OBiWiFi_setup network). Then, open a browser window and visit http://192.168.10.1/wifi or try http://obiconnect.com/wifi"

when I type http://192.168.10.1/wifi into Chrome I get the following:

   This site can't be reached
   http://192.168.10.1/wifi is unreachable.
   Try running Windows Network Diagnostics.
   ERR_ADDRESS_UNREACHABLE

I then tried typing http://obiconnect.com/wifi into Chrome and got this:

   No Internet
   Try:

  •    Checking the network cables, modem, and router
  •    Reconnecting to Wi-Fi
  •    Running Windows Network Diagnostics
   DNS_PROBE_FINISHED_NO_INTERNET

Does anyone know what I might be doing wrong? Any help would be greatly appreciated.

Thanks!

SteveInWA

You didn't mention if you fully followed the instructions or not.  You must make a change specific to the OBi 202 model.  See the screenshot below.


kw2000

Whoops, my bad. Yes I followed the previous steps and ensured I enabled option 30#.

SteveInWA

I've found, after configuring the dongles on several devices in the past, that the easiest and least aggravating way to solve the problem is to first hook up the device via an Ethernet cable and get it attached to the OBiTALK web portal, then go into expert mode settings and manually enter the WiFi credentials, submit the settings, and let the device reboot.  Then, simply unplug the Ethernet cable, power-cycle the device one more time, and you're on-the-air.

See my screenshot below.  While you are there, change the DNS settings to use Google's DNS, to avoid problems with crappy ISP DNS redirects.  If you have some sort of anti-Google bias, then use the Quad9 DNS at 9.9.9.9

kw2000

This worked perfectly, thank you so much for your help!