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

Can't get on my own LAN Server


slayo
 Share

Recommended Posts

Hello,


im trying to setup a LAN server for a couple of hours now and can't seem to get it running.


so that's what my murmur is saying:

<W>2014-09-16 01:14:27.759 Initializing settings from C:/Users/Slayer yo/AppData/Local/Mumble/Murmur/murmur.ini (basepath C:/Users/Slayer yo/AppData/Local/Mumble/Murmur)

<W>2014-09-16 01:14:27.762 OpenSSL: OpenSSL 1.0.1i 6 Aug 2014

<W>2014-09-16 01:14:27.768 SSL: CA certificate filter applied. Filtered size: 68, original size: 68

<W>2014-09-16 01:14:27.769 ServerDB: Opened SQLite database D:/Program Files/Mumble/murmur.sqlite

<W>2014-09-16 01:14:27.774 Murmur 1.3.0 (1.3.0~375~g6095134~snapshot) running on WinX64: Windows 7 Ultimate Edition Service Pack 1 x64 - 6.1.7601: Booting servers

<W>2014-09-16 01:14:27.876 1 => Server listening on [::]:64738

<W>2014-09-16 01:14:27.982 1 => Server listening on 0.0.0.0:64738

<W>2014-09-16 01:14:28.076 1 => Failed to bind UDP Socket to 0.0.0.0:64738

<W>2014-09-16 01:14:28.165 1 => Announcing server via bonjour

<W>2014-09-16 01:14:28.267 1 => Not registering server as public

 

if i try to connect via mumble to 127.0.0.1 or 0.0.0.0 i can see the server in my fav list with a ping of 0 but once i try to connect nothing happens.


i dont know whats wrong with it since i somehow see it running?


i hope somebody can help me with this i only need the server to run it in LAN


thanks in advance

Marvin

Link to comment
Share on other sites

  • 3 weeks later...
  • Administrators

2014-09-16 01:14:28.076 1 => Failed to bind UDP Socket to 0.0.0.0:64738

That indicates the issue.

Is that UDP already in use by any chance?

Does your network interface configuration or firewall maybe block UDP port listening?


You could try changing the port to listen on.

Link to comment
Share on other sites

 Share

×
×
  • Create New...