Long Connection Delay

[lesterley]

When I first started using Mumble this past year, I was able to connect instantly to our local server on our home network. About a month ago I began experiencing long delays (~30 seconds) every time I try to connect. I have the most recent version of Mumble installed (1.5.735) and I'm on Windows 11 (10.0.22631). Any thoughts on what might be causing this?

[Krzmbrzl]

What is the general network latency between your client's machine and the server's?

Might the server have issues when accessing the database (by default a SQLite database), I.e. might there be an issue with slow filesystem access on your server:

[michael-robertson]

Hi @Krzmbrzl
Husband Unit checking in. I run mumble-server.exe with all default config on my PC. Latency would be basically zero. Both gaming rigs are about a year old, connect directly to router with ethernet. Private network.
SQLite file present and intact. SSD, no filesystem issues that I know of.
No delay when connecting client to server on same machine (unsurprisingly). Same for @lesterley until recently. No changes except Windows Updates.
The mumble-server.log file shows expected connection, but does not indicate any possible cause. Perhaps there is a debug loglevel I can put in the config?

[Krzmbrzl]

Okay so the issue also appears when the sever is run on the same machine as the client? And it used to work fine, but after a Windows update, it now has this long delay?

Is some sort of Antivirus interfering with the network traffic or with Mumble itself?

[lesterley]

Well, I managed to fix the problem by connecting directly to the host computer's (Michael's) IP address, rather than the named server that I had been using.

Thank you for your help, @Krzmbrzl

[Krzmbrzl]

Hm, okay then there seems to have been some issue with the DNS resolver. Anyway, glad to hear it's working again 👍

[michael-robertson]

Yeah, I think it's Bonjour how it discovers servers on the local network? Dunno.
All I know is that the PC's name shows up automatically in the mumble interface in the "LAN" group, and it used to connect quickly, but now it takes 30 seconds to resolve it. We just worked around it by putting an explicit "<IP>:<port>" as a favorite.
The IP addresses for the PCs are reserved on the router, and don't change, so the actual problem is still a mystery.