- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The issue I have is I cannot connect to my friends mumble server.
I was on it at night, went to bed, woke up, cant connect.
I can connect to other mumble servers but not this one.
The message I get is : "Server connection failed: Connection timed out"
I had the host delete me and re-add me. I wasnt banned. Certificate isnt an issue.
I have updated, rebooted and restarted. Still nothing.
Running tracert I get this:
Tracing route to mumble.organizedcrayons.com [92.242.140.21]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms FIOS_Quantum_Gateway.fios-router.home [192.168.1.1]
2 41 ms 18 ms 19 ms lo0-100.WASHDC-VFTTP-328.verizon-gni.net [108.51.128.1]
3 22 ms 19 ms 23 ms T1-11-0-1.WASHDC-LCR-22.verizon-gni.net [100.41.134.50]
4 * * * Request timed out.
5 25 ms 19 ms 25 ms 0.ae4.BR1.IAD8.ALTER.NET [140.222.227.9]
6 24 ms 19 ms 19 ms tbd.BR1.IAD8.ALTER.NET [204.148.11.177]
7 36 ms 53 ms 38 ms et-7-1-0.atl11.ip4.gtt.net [89.149.181.13]
8 38 ms 32 ms 33 ms ip4.gtt.net [173.205.52.18]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
And it continues with timed out message.
I'm assuming its an issue on Verizon's side of things. I've read of others having a similar issue and having to deal with Verizon for hours on the phone having to continually reexplain everything to new people. I would REALLY like to avoid that.
Any advice on what to do or who to talk to or even how to word it would be greatly appreciated!
Solved! Go to Correct Answer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well, its fixed now. Your comment on that you couldnt find it was made me think, I asked what the server info was again and the server name was different than what I had in there. I honestly have no idea how it changed, i never changed it, but I'm in now.
I thank you for all your help!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is this still not working for you? I get the following traceroute:
Target Name: 92.242.140.21
IP: 92.242.140.21
Date/Time: 7/5/2016 7:56:34 AM - 7/5/2016 7:57:34 AM
Hop Sent PL% Min Max Avg Host Name / [IP]
1 25 0 0.39 0.55 0.46 lan-if.inside.local [192.168.3.1]
2 25 0 2.99 15.79 4.87 lo0-100.CLPPVA-VFTTP-304.verizon-gni.net [72.86.37.1]
3 25 0 3.05 7.96 5.35 B3304.CLPPVA-LCR-22.verizon-gni.net [130.81.221.134]
4 25 100 0 0 0 [-]
5 25 0 3.13 7.99 6.05 0.ae8.BR1.IAD8.ALTER.NET [140.222.233.153]
6 25 0 5.58 10.47 7.02 tbd.BR1.IAD8.ALTER.NET [204.148.11.177]
7 25 0 15.64 18.04 16.89 et-7-1-0.atl11.ip4.gtt.net [89.149.181.13]
8 25 0 18.07 20.58 19.40 ip4.gtt.net [173.205.52.18]
9 25 100 0 0 0 92.242.140.21 [92.242.140.21]
So I take a bit different path, but still end up with the same last couple hops (at 7 and 8). The IP 92.242.140.21 itself isn't returning pings, which is not unusal really. I turn ping echos off on any server I deploy. The domain, mumble.organizedcrayons.com, doesn't exist as far as I can tell, so I assume this is being run with dynamic DNS. The server doesn't appear to be up, now.
It appears that the ping got out of Verizon's network and into GTT's network (for both of our traces). I don't think Verizon's network is the issue. GTT makes sense since the reverse DNS lookup on 92.242.140.21 resolves to:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yep still doesnt work for me.
Is there anything I can do to correct this? Someone I can email or something?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The server name mumble.organizedcrayons.com still doesn't resolve to an IP address and I still can't ping 92.242.140.21, but that could be either because there is no server at that IP address or there is a server and it's configured to not repond to pings and traceroutes. (That's not unusual for servers.)
That "* * *" you see in your traceroute means that the last hop means just that - either the server isn't there or it doesn't allow ping/traceroute requests.
When I lookup the domain, organizedcrayons.com, I get:
host: organizedcrayons.com
type: A
ip: 162.255.119.249
class: IN
ttl: 1800
host: organizedcrayons.com
type: SOA
mname: dns1.registrar-servers.com
rname: hostmaster.registrar-servers.com
serial: 2016070201
refresh: 43200
retry: 3600
expire: 604800
minimum-ttl: 3601
which is nothing like the IP address you have in your traceroute. Is it possible the mumble server was renamed, moved or at the very least, switched ports? You might want to email the owner of that particular mumble server and see if it's up. Unless you know other people are getting into it, I suspect the server itself is having issues. I don't think Verizon can do anything about this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well, its fixed now. Your comment on that you couldnt find it was made me think, I asked what the server info was again and the server name was different than what I had in there. I honestly have no idea how it changed, i never changed it, but I'm in now.
I thank you for all your help!!!