TCP connection to 125.141.125.74 failed

<< < (5/26) > >>

jeeva:
I have two obi200 devices in two different homes. Only one of them is failing and so I tried the adding the ips on it, but no luck and it's been an hour.

[EDIT] Of course it starts to work after I post this.

mikeb0:
My OBi200 is still down, unable to make / receive calls...
Tried both configuration thru the obitalk web site and locally with the new DNS server IPs, 4.2.2.2 and 8.8.4.4. Nothing seems to work.

Is there a fix coming? If not, I may have to do the unthinkable and buy a Vonage box. :/
Yes, this is the first time in years, but I cannot afford to be down for days on end like this.

GPz1100:
Something still not right.

Reverted back to opendns, same error

Try the following

8.8.8.8 = fail
4.2.2.2 = fail
ISP's dns = fail

What's strange, trying the commodo servers fails too now.

Edit:  Seems to connect after a minute or two using comodo dns... And only comodo.  

This is very strange because one would expect dns propagation to be completed by now, especially to google dns servers.  This issue started ~1600 Central time (UTC -5)  for us yesterday.

mikeb0:
The IP address my OBi200 is trying to use has changed...
It went from 74.125.132.125 to 209.85.234.125, but still fails:
Backing Off (1s):TCP connection to 125.234.85.209 failed

Did a reverse lookup on the address to find the domain name (FQDN):
root@rhel6:~ # dig +short -x 209.85.234.125
jn-in-f125.1e100.net.

Then did forward lookups on the name to see if the IP address matched.
The name returns two possible IP addresses, and the order changes depending on which DNS server I query:
root@rhel6:~ # dig +short a jn-in-f125.1e100.net @4.2.2.2
209.85.234.125
216.239.38.125
root@rhel6:~ # dig +short a jn-in-f125.1e100.net @8.8.4.4
216.239.38.125
209.85.234.125
root@rhel6:~ # dig +short a jn-in-f125.1e100.net @8.8.8.8
209.85.234.125
216.239.38.125
root@rhel6:~ # dig +short a jn-in-f125.1e100.net [note: my personal DNS server]
216.239.38.125
209.85.234.125

Still not working...

[Update: modified DNS Server 1 to 4.2.2.2 and left DNS Server 2 blank in OBi Expert Configuration, reconfigured Voice Service Provider SP1, and it's working again... making and receiving calls.]

GPz1100:
^^209.85.234.125 comes back to google @ iplocation.net .

Few minutes following a reboot (with comodo servers) on the obi202, one sp shows connected while the other backing off.  After another reboot both are connected.  I'm leaving well enough alone at this point.

My guess is there's more to it than simple dns resolution.

Navigation

[0] Message Index

[#] Next page

[*] Previous page