OBi & Network & Homegroup - RESOLVED
LTN1:
Quote from: Dravial on March 29, 2015, 05:28:25 am
I think I will just go with this for a $5 solution as the computer is about 12 feet from the Router (w/ WiFi) anyway: http://www.ebay.com/itm/301399250734
I wonder if OBi would work with this instead of the computer or if you have to buy the OBi branded one...
That's a pretty good find. I don't know for sure if it will work with the OBi but I can't see why not? Perhaps others will know. Even if they don't, if you are brave enough to buy it and test...let the rest know if it works. The item does seem to have a 14-day return warranty if it doesn't work and I suppose shipping is pretty light to return.
If you ever get the chance though, I would eventually buy another OBi202 from Amazon...they have a great return policy for items that doesn't work properly--to see if this darn issue that you are facing is actually truly caused by a defect or if it is something else? I know that Steve's solution is the cheapest and quickest solution, but I like to always determine what the real issue is also. You at least know that I have mine on bridge mode for almost a week without any noticeable problems...but you also know that I started the bridge mode without ever turning auto-provisioning off.
drgeoff:
I'd put money (but not my life) on that NOT working.
USB dongles have a vendor and product pair of ID codes which the host device uses to recognise the dongle and where necessary load the appropriate driver. OBi ATAs are only programmed to recognised Obihai's own WiFi and Bluetooth dongles.
Dravial:
I figured. My intended use for the USB Receiver was on the PC - using it on OBi was a second thought. I will depopulate the LAN port on OBi since it does not play well with others if I can not get this resolved and put the USB received in the afflicted PC.
I have also followed up with e-mail support in case they have any ideas. I will let you know if they do.
Also: I even tried setting a static IP on OBi today as per N7AS via OBiTALK web portal / expert config / router settings / change DHCP to Static and the IP line under it to the IP it was assigned at the time. It worked for a while, then the computer went to sleep, and when it woke up, OBi would no longer play with it.
After doing this I could no longer make or receive calls, even though OBiTALK Web portal showed everything was functioning normally.
Deleting the IP in IPAddress and clicking the radio button back to 'OBiTALK Settings' while leaving the AddressingType to Static and allowing OBi to reboot has resolved the issue of making and receiving calls. (The Red Exclamations remain however).
N7AS:
When setting a Static IP on the OBi202, I would use 8.8.8.8 and 8.8.4.4 for the DNS Servers. I use these on all my devices.
Dravial:
I have absolutely no idea why you would do that, so I will not try to imitate you, but thanks for your input.
However after the computer on the LAN port of OBi went to sleep, and was awoken, with the last settings I described above, the LAN port was dead and it bounced a few times, but then finally connected.
I will leave it here for now until I find, if there is one, a better solution.
UPDATE: Once the computer sleeps overnight, and is woken the next morning, I have the same result as before: LAN PORT 'dies', computer goes from connecting to no connection over and over.
LTN1: Feel free to send me one Amazon, and I will test it. You can even send me a shipping label and I will send you this one for your trialing pleasure. I do not have the resources for that, hence why I am opting to an initially free phone alternative to start with, and so frustrated it will not work within my current setup. I treat my money differently then most, and I will leave it at that as that discussion is more political and of no relevance to the issue at hand.
Navigation
[0] Message Index
[#] Next page
[*] Previous page