Weird packet loss issue

[tellytart]

I'm seeing a very strange issue, and hoping someone can shed some light.

Setup:

Both myself and a friend are running mumble servers, both binding to IPv4 and IPv6 addresses. Both servers are available to the internet, and friends can connect to both servers without problems.

However, when I'm not connected to a server, my local mumble client is showing a ping time to my friend's server on both IPv4 and IPv6, but I'm getting 100% packet loss to my server (different machine, and am using the local lan IPv4 address), yet I can still connect to my server, and I do start getting ping statistics once connected.

The windows firewall is disabled on my server, and I've tried disabling the firewall on my desktop machine, but still have the same symptoms!

Attached - 2 screenshots - the connection window when I'm not connected to my server, and the connection window when I am connected.

 

Connection window when not connected to my server

Connection window when I am connected to my server

[tellytart]

Well, I seem to have found an answer to the issue. I was running mumble server 1.2.2 and client 1.2.2. Upgrading the client to 1.2.3 RC 2 didn't fix the issue, but upgrading the server to 1.2.3 RC 2 did! Most odd!

[rawnar]

Just a small question are you able to ping your own server from a command line using the "ping" command. I had the same problem when I was running murmur on a server that was not replying to a ping request. Probably mumble was using the standard ping request when it was not connected to the server.

[tellytart]

Yes, I can ping the server using the command line, both IPv4 and IPv6. And as I mentioned above, the problem went away when I upgraded the server and client to 1.2.3RC2.