My mumble repeatedly loses connection then reconnects a few seconds later with error message "Server connection failed: Server is not responding to TCP pings."
this happens on every mumble server
I have tried enabling and disabling TCP-only mode and QoS and neither one makes a difference
suggestions? It has been happening ever since I upgraded to windows 10
My mumble repeatedly loses connection then reconnects a few seconds later with error message "Server connection failed: Server is not responding to TCP pings."
this happens on every mumble server
I have tried enabling and disabling TCP-only mode and QoS and neither one makes a difference
suggestions? It has been happening ever since I upgraded to windows 10
open cmd -> ping google.com -t -> post result when disconnecting in mumble
open cmd -> ping google.com -t -> post result when disconnecting in mumble
save your certificate and reinstall mumble?
save your certificate and reinstall mumble?
Windows TCP/IP reset maybe?
in cmd:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
Networking isn't exactly my greatest area of expertise but that fixes half the basic issues I run into at work.
Windows TCP/IP reset maybe?
in cmd:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
Networking isn't exactly my greatest area of expertise but that fixes half the basic issues I run into at work.
Spusave your certificate and reinstall mumble?
EntropyTFWindows TCP/IP reset maybe?
in cmd:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
Networking isn't exactly my greatest area of expertise but that fixes half the basic issues I run into at work.
didn't help
[quote=Spu]save your certificate and reinstall mumble?[/quote]
[quote=EntropyTF]Windows TCP/IP reset maybe?
in cmd:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
Networking isn't exactly my greatest area of expertise but that fixes half the basic issues I run into at work.[/quote]
didn't help
If you can, ask the person who runs a server to check the logs next time you DC.
If you can, ask the person who runs a server to check the logs next time you DC.
quintoshopen cmd -> ping google.com -t -> post result when disconnecting in mumble
[quote=quintosh]open cmd -> ping google.com -t -> post result when disconnecting in mumble[/quote]
quintoshquintoshopen cmd -> ping google.com -t -> post result when disconnecting in mumble
please explain what pinging a completely different server is supposed to accomplish
[quote=quintosh][quote=quintosh]open cmd -> ping google.com -t -> post result when disconnecting in mumble[/quote][/quote]
please explain what pinging a completely different server is supposed to accomplish
lootquintoshquintoshopen cmd -> ping google.com -t -> post result when disconnecting in mumble
please explain what pinging a completely different server is supposed to accomplish
Maybe he's trying to diagnose an Internet connection loss as possible cause of the Mumble disconnections.
[quote=loot][quote=quintosh][quote=quintosh]open cmd -> ping google.com -t -> post result when disconnecting in mumble[/quote][/quote]
please explain what pinging a completely different server is supposed to accomplish[/quote]
Maybe he's trying to diagnose an Internet connection loss as possible cause of the Mumble disconnections.
lootquintoshquintoshopen cmd -> ping google.com -t -> post result when disconnecting in mumble
please explain what pinging a completely different server is supposed to accomplish
u said that it happens with every mumble server so presumably the issue is not related to the server you're trying to connect to
[quote=loot][quote=quintosh][quote=quintosh]open cmd -> ping google.com -t -> post result when disconnecting in mumble[/quote][/quote]
please explain what pinging a completely different server is supposed to accomplish[/quote]
u said that it happens with every mumble server so presumably the issue is not related to the server you're trying to connect to
you could try installing pingplotter to see if you don't have any ping spikes that might make you disconnect from mumble
you could try installing pingplotter to see if you don't have any ping spikes that might make you disconnect from mumble
1. Download WinMTR from https://sourceforge.net/projects/winmtr/
2. Unzip the WinMTR.zip file to the Desktop.
3. Run the WinMTR.exe If you get any errors make sure to right click>run as admin.
4. Type the IP address you want to trace in the "Host" field.
5. Click on "Start" and then connect to the server. Once you notice the connection issue, wait about 5 more minutes and click on "Stop".
6. Click on "Copy text to clipboard" and paste the results here.
1. Download WinMTR from https://sourceforge.net/projects/winmtr/
2. Unzip the WinMTR.zip file to the Desktop.
3. Run the WinMTR.exe If you get any errors make sure to right click>run as admin.
4. Type the IP address you want to trace in the "Host" field.
5. Click on "Start" and then connect to the server. Once you notice the connection issue, wait about 5 more minutes and click on "Stop".
6. Click on "Copy text to clipboard" and paste the results here.