Obi200 - How to Enable Web Management Access

<< < (4/4)

gelcom:
Quote from: azrobert on December 27, 2014, 08:48:55 am

If you have a Windows computer, can you ping 192.168.40.105 from the Command Prompt?


No I can't. I realized that if I try to access the Obi200 from a diferent subnet the access is denied but if I try to access it from the same subnet the access goes ok. For eg. if I try to connect to Obi200 from a 192.168.40.XXX everything goes OK but if I try to access it from any other subnet like 192.168.20.XXX the connection is broken.

This issue is not related to my network because if I try to access an Obi110 the connection goes OK from any subnet.

Maybe there is any restriction on Obi200 software to avoid access web admin from another subnet. Any ideas on how to 'release' that lock?

kind regards

SteveInWA:
There's nothing wrong with your OBi.  Just access it from the same subnet.  There is no reason to be trying to manage it from another subnet.  Your issue is caused by your own router configuration.

There's no reason to be concerned about using the OBiTALK portal to manage your device.  As long as you are using a strong password, it's highly unlikely that anyone could guess your user name and password.  To date, there has been no reported incident that I can recall, of someone hacking into an OBi device via the OBiTALK portal.  If you want to use Google Voice with your OBi, you must configure it via the OBiTALK portal -- you can't do it via the local web interface.

Edit:

It occurs to me that you may have the "access from WAN" setting disabled on your OBi (which was what I think you were asking about all along).

I haven't tested this today, but this setting is on a page that isn't usually looked at, and I see that, by default, the device disables WAN access to the web server.  Setting it up using the OBiTALK portal enables this access, so it's never been an issue for me.  See the screenshots below.  One is from the OBiTALK portal, and the other is from the local web server.

gelmce:
I have the exact same issue.
" Dialing ***0
  30#"
I get the message: Invalid option.

It seems that
 http://192.168.9.91
gets redirected to http://192.168.9.91/cgi-bin/login
which displays
"The requested URL was not found!"

 The LAN is not connected to the internet, so suggesting that I
" follow the instructions on this page after your Obi200 is hooked up to your router."
 (  http://www.obitalk.com/obinet/pg/obhdev/add )
does not work as it requires WWW internet access.

drgeoff:
Quote from: gelmce on November 04, 2017, 10:15:59 am

I have the exact same issue.
" Dialing ***0
  30#"
I get the message: Invalid option.

It seems that
 http://192.168.9.91
gets redirected to http://192.168.9.91/cgi-bin/login
which displays
"The requested URL was not found!"

 The LAN is not connected to the internet, so suggesting that I
" follow the instructions on this page after your Obi200 is hooked up to your router."
 (  http://www.obitalk.com/obinet/pg/obhdev/add )
does not work as it requires WWW internet access.



The ***0 30 stuff is ONLY APPLICABLE TO AN Obi202 or Obi302.  Those devices contain a router.  An OBi200 does not and web management access is always available via its single ethernet port.

Navigation

[0] Message Index

[*] Previous page