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

problem with murmur since windows update nov 11


RngdQC
 Share

Recommended Posts

2014-11-12 18:29:57.185 1 => Server listening on [::]:64738

2014-11-12 18:29:57.191 1 => Server: TCP Listen on 0.0.0.0:64738 failed: The address is protected

2014-11-12 18:29:57.196 1 => Stopped


i get this message, and i had a windows update yesterday.. about 14 updates if i remember.

i tried uninstall and reinstall.. tried different ports.. nothing works..

been using murmur for about a year without any problems, but now, i cannot make it work.


EDIT: i also happen to have a minecraft server which i play with coworkers once in a while. it works flawlessly.


EDIT2: this is what i get if i change the port to anything else than the default one.


2014-11-12 19:56:56.104 1 => Server listening on [::]:65313

2014-11-12 19:56:56.111 1 => Server listening on 0.0.0.0:65313

2014-11-12 19:56:56.117 1 => Failed to bind UDP Socket to 0.0.0.0:65313

2014-11-12 19:56:56.122 Bonjour: Failed to load dnssd.dll

2014-11-12 19:56:56.129 1 => Not registering server as public

Link to comment
Share on other sites

 

saw that post already, and did everything suggested, did not help at all. i googled, and looked at every possible option i could have found. that's why i posted here. this place lacks serious moderators with potential to help around. such a shame, cause mumble is a great tool for casual gamers like me. and for hardcore gamers i'd guess.

Link to comment
Share on other sites

Sounds like the port is in use or protected. Did you accidentally forbid it to open ports in the firewall? Does another running application use those ports?

 

i did not touch anything, like i said, windows update happened, and then nothing was working anymore.

the day before everything was working. it was working for over a year. i checked if it was used with the cmd command, and there was nothing with the port in the list. how would i see if windows firewall blocks that port? is there a quick way to search for a rule that windows firewall made with port numbers?

Link to comment
Share on other sites

now i get this


2014-11-16 11:50:13.193 Initializing settings from C:/Program Files/Mumble/murmur.ini (basepath C:/Program Files/Mumble)

2014-11-16 11:50:13.196 OpenSSL: OpenSSL 1.0.1i 6 Aug 2014

2014-11-16 11:50:13.246 SSL: CA certificate filter applied. Filtered size: 700, original size: 700

2014-11-16 11:50:13.247 ServerDB: Opened SQLite database C:/Users/Rene/murmur.sqlite

2014-11-16 11:50:13.251 MurmurIce: Endpoint "tcp -h 127.0.0.1 -p 6502" running

2014-11-16 11:50:13.251 Murmur 1.3.0 (1.3.0~465~g78d7198~snapshot) running on WinX64: Windows 7 Home Premium Edition Service Pack 1 x64 - 6.1.7601: Booting servers

2014-11-16 11:50:13.261 1 => Server listening on [::]:64738

2014-11-16 11:50:13.268 1 => Server listening on 0.0.0.0:64738

2014-11-16 11:50:13.274 1 => Failed to bind UDP Socket to 0.0.0.0:64738

2014-11-16 11:50:13.278 Bonjour: Failed to load dnssd.dll

2014-11-16 11:50:13.285 1 => Not registering server as public

Link to comment
Share on other sites

  • Administrators

Just did a small experiment and didn't allow murmur to pass the firewall when windows asked about it:

2014-11-16 17:46:04.493 Murmur 1.3.0 (Compiled Nov 10 2014 00:05:06) running on Win: Windows 8 Professional x64 - 6.2.9200: Booting servers

2014-11-16 17:46:04.511 1 => Server listening on [::]:64738

2014-11-16 17:46:04.516 1 => Server listening on 0.0.0.0:64738

2014-11-16 17:46:04.522 1 => Failed to bind UDP Socket to 0.0.0.0:64738

2014-11-16 17:46:04.546 1 => Not registering server as public

Looks like you issue to me. When the program is changed (e.g. due to an update) Windows can notice that and ask for renewed permission to let it through the firewall. Maybe you accidentally dismissed that dialog? Should've look something like this.

http://d0t.dbclan.de/dump/WindowsFirewallMurmur.png


You can fix this by opening the windows firewall configuration and deleting the inbound "deny" rules for murmur it created:

http://d0t.dbclan.de/dump/WindowsFirewallMurmurConfig.png


When you start murmur after that it should pop up the dialog and ask you again.


Hope that helps.

Link to comment
Share on other sites

there is no denied rules for murmur nor mumble in there. it's the first thing i checked. i'm not a pro, but i'm not a noob either. like i said, pretty much any simple easy way to fix this have been tried. anything i could google about has been tried. this is one annoying problem. and i blame microsoft for it lol

Link to comment
Share on other sites

FIXED: going back to 1.2.8 fixed everything. windows firewall asked me to add murmur to exceptions. and boom everything works. that will teach me to try and help by testing beta versions. i guess the combination of beta and windows update on the 11th fucked up everything.

Link to comment
Share on other sites

ok, i restored to default windows firewall settings. uninstalled mumble. used ccleaner to clean the computer. including the registry thingy. then restarted the computer. then installed mumble/murmur. then BOOM it works.


my guess is that tomorrow or soon enough i'll come back saying it's not working again. WTF is wrong with mumble?

Link to comment
Share on other sites

  • Administrators

Kinda doubtful it's something about Murmur to be honest. We'd see a lot more reports for something you can repro so easily. Unfortunately I don't really have a good idea about what besides firewall (3rd party or windows) or some other process taking the ports it could be. I guess it could be some network driver issue or 3rd party network optimizer tool.

Link to comment
Share on other sites

Kinda doubtful it's something about Murmur to be honest. We'd see a lot more reports for something you can repro so easily. Unfortunately I don't really have a good idea about what besides firewall (3rd party or windows) or some other process taking the ports it could be. I guess it could be some network driver issue or 3rd party network optimizer tool.

 


i use microsoft security essentials, windows firewall. no 3rd party software.. been using this server for about a year now. and since the security update, about 14 updates, nov the 11th, everything was fucked.. but so far, it's working without any problem. 2 days in a row.

Edited by RngdQC
Link to comment
Share on other sites

Unfortunately today's Software stacks are so complex that there are countless possibilities for stupid unlikely breakage...let's hope your issue is gone for good.

 

it comes back every 3 or 4 days. repeating the steps i posted work. it's just annoying to do it over and over again.

Link to comment
Share on other sites

i use default settings for murmur. hopefully this will be fixed by chance in the new and upcoming 64 bit version.

 

This probably isn't a murmur/mumble thing alone. It's interacting with something else. Do you have any anti-virus software or anti malware stuff running?

Link to comment
Share on other sites

i use default settings for murmur. hopefully this will be fixed by chance in the new and upcoming 64 bit version.

 

This probably isn't a murmur/mumble thing alone. It's interacting with something else. Do you have any anti-virus software or anti malware stuff running?

 

i responded twice to this question already. please read the previous posts.

Link to comment
Share on other sites

 Share

×
×
  • Create New...