This is a read-only archive of the Mumble forums.

This website archives and makes accessible historical state. It receives no updates or corrections. It is provided only to keep the information accessible as-is, under their old address.

For up-to-date information please refer to the Mumble website and its linked documentation and other resources. For support please refer to one of our other community/support channels.

Jump to content

Cannot connect to specific server.


Bubs92
 Share

Recommended Posts

I'm able to connect to many random servers, but not the one my friends and I use. I could connect to it just a week or so ago, then suddenly couldn't. I've tried many possible solutions suggested on forums, and finally got around to running a tracert command, but I don't know what I'm looking at. Can someone interpret this for me?


Tracing route to ec2-52-1-87-118.compute-1.amazonaws.com [52.1.87.118]

over a maximum of 30 hops:


1 <1 ms <1 ms <1 ms 192.168.1.1

2 * * * Request timed out.

3 51 ms 207 ms 206 ms host-145-6-220-24-static.midco.net [24.220.6.145

]

4 13 ms 11 ms 13 ms host-243-6-220-24-static.midco.net [24.220.6.243

]

5 11 ms 13 ms 11 ms host-63-182-220-24-static.midco.net [24.220.182.

63]

6 38 ms 48 ms 40 ms equinix01-chi1.amazon.com [206.223.119.98]

7 71 ms 72 ms 69 ms 54.240.229.72

8 74 ms 89 ms 74 ms 54.240.228.246

9 71 ms 73 ms 74 ms 54.240.229.189

10 74 ms 71 ms 71 ms 54.240.228.175

11 72 ms 83 ms 75 ms 54.239.109.96

12 71 ms 74 ms 72 ms 54.239.109.87

13 82 ms 89 ms 95 ms 54.239.110.34

14 63 ms 66 ms 67 ms 54.239.110.63

15 70 ms 69 ms 70 ms 205.251.245.246

16 * * * Request timed out.

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

20 * * * Request timed out.

21 * * * Request timed out.

22 * * * Request timed out.

23 * * * Request timed out.

24 * * * Request timed out.

25 * * * Request timed out.

26 * * * Request timed out.

27 * * * Request timed out.

28 * * * Request timed out.

29 * * * Request timed out.

30 * * * Request timed out.


Trace complete.

Link to comment
Share on other sites

There are many possibilities...


Are you able to click "Connect" when you highlight the server?

Is mumble giving you a message when you fail to connect?

Are you trying to connect via IP Address or DNS name?

Can the server admin check the server logs to see if they see you attempting to connect?

-If so, what message are they getting?

Have you changed computers or reinstalled your Operating System recently?

Link to comment
Share on other sites

  • 2 weeks later...

Yeah I'm having the same problem. Started two days ago, was talking on mumble, then I got disconnected and havn't been able to get back on. Even with the admins help.


If i start a virtual machine on my pc, and run mumble from there, it connects fine. Which would suggest the problem is with my Windows 8.1 / mumble install.


Tried re-installing mumble.

Reset winsock

Disabled windows firewall

I have no "anti-virus" installed

Nothing in my hosts file

Dns lookup is correct.

Tried renaming mumble.sqlite

Compared Tracert results with other users.


Console.txt log has no errors.

I can easily connect to other servers. (just not our private run mumble pi server)

And I can connect to the server in question from a virtual machine on the same pc.


Things left to try:

Re-install Windows

Link to comment
Share on other sites

Hi,


I'm having the same problem. Just 1 specific server I cannot connect to.


Things I've tried:

Start virtual machine and install mumble and connect from that: Works

Disable Firewall

Disable Anti Virus

Reset winsock

Reboot pc

Re-install mumble

Remove/Add server

Rename mumble.sqlite


It's a private server, and admin is sure he didn't ban anyone.

Link to comment
Share on other sites

 Share

×
×
  • Create New...