TCP connection to 125.141.125.74 failed
GPz1100:
Ryan,
Good find. It's surprising this server dns change wasn't staggered or done over a weekend. I guess the way the pbx or simonics connects to gv is different from the way obi does it. Chances are by morning all the cached records will be expired and everything will work again without any changes.
Lensor:
Thank you Mike (FireSQer) and Ryan_Chicago! The DNS change worked here :)!
I'm not a networking expert but felt something about the dns, perhaps a propagation issue, might have been to blame...
I've changed my devices to use the Comodo DNS as suggested by Ryan and both my devices are up and running again!
Happy days!
L
NikTalk:
The OBI202 boxes started working automatically this morning. Looks like Obi updated them.
The Obi101 was still not working with the "backing up" message persisting.
Using advice from FireSQer and Ryan_Chicago, I changed the DNS manually and the OBI101 box started working again. Success!
rfryar:
Stopped working for my obi last night. Tried both DNS servers with no luck.
Tried:
4.2.2.2
8.8.4.4
[Edit] Magically it started working now. I assume Google changed what IPs pointed and various servers were lagged behind.
Rick
Ryan_Chicago:
All credit is due to @SteveInWA and @FireSQer
Without their helpful insight I would not have guessed this was a DNS issue.
It's a bit difficult to pin down the stale records as it seems like Google is using a fairly large round-robin pool of IP addresses for the XMPP servers, for which I believe the FQDNs are:
xmpp-server.l.google.com
alt1.xmpp-server.l.google.com
alt2.xmpp-server.l.google.com
alt3.xmpp-server.l.google.com
alt4.xmpp-server.l.google.com
@rfryar: last night I also tested the Level3 DNS (e.g. 4.2.2.1-.4) and unfortunately they were also returning stale DNS records just like the RCN DNS servers.
Navigation
[0] Message Index
[#] Next page
[*] Previous page