TCP connection to 125.141.125.74 failed

<< < (18/26) > >>

Troyer:
There wasn't a firmware update available for my 200, but changing the DNSServer1 to 4.2.2.2 corrected the problem.

drgeoff:
Quote from: Troyer on November 05, 2017, 10:01:48 am

There wasn't a firmware update available for my 200, but changing the DNSServer1 to 4.2.2.2 corrected the problem.

How many times does it have to be said!!!???

This is not a DNS problem and changing DNS is not a lasting fix.

For an OBi200 you need firmware 3.2.1 (Build: 5757EX).  Currently the only way to get that is log into your Dashboard at obitalk.com and click the yellow triangle.

http://www.obitalk.com/forum/index.php?topic=13113.msg84139#msg84139

SteveInWA:
Quote from: drgeoff on November 05, 2017, 10:10:14 am


How many times does it have to be said!!!???



If only people with "write only memory" would stop posting the same nonsense again and again, but I guess that's too much to expect.

Brenda72:
I am confused by this.  I have an Obi100

What do I need to do to get my service working again?  Everyone is talking about the Obi200 but I have Obi100

SteveInWA:
Quote from: Brenda72 on November 06, 2017, 12:08:30 pm

I am confused by this.  I have an Obi100

What do I need to do to get my service working again?  Everyone is talking about the Obi200 but I have Obi100


READ:  http://www.obitalk.com/forum/index.php?topic=13113.msg84139#msg84139

Navigation

[0] Message Index

[#] Next page

[*] Previous page