Mumble Hates Windows Vista

[clhdrums87]

I'm trying to run a mumble server from my computer.

I'm using Windows Vista Home Premium on a 64 bit processor. Trying to use Mumble 1.2.2

If I open the "backwards compatibility" mumble, i can use it just fine, but i can't connect to my server, which i'm fairly sure i've set up correctly (i'll get to that in a second). If I try to use the main mumble, it'll either freeze up right when I open it, or it'll be fine, until I press "connect" to bring up the options and it'll freeze up, the only way I can close out of it is right clicking the icon and clicking close.

Here's the error I get when trying to connect using the backwards compatible mumble-

2011-02-14 03:48:22.052 Initializing settings from H:/Mumble Server/Mumble/murmur.ini (basepath H:/Mumble Server/Mumble)

2011-02-14 03:48:22.070 SSL: Added CA certificates from system store 'Ca'

2011-02-14 03:48:22.078 SSL: Added CA certificates from system store 'Root'

2011-02-14 03:48:22.084 SSL: Added CA certificates from system store 'AuthRoot'

2011-02-14 03:48:22.092 ServerDB: Openend SQLite database H:/Mumble Server/Mumble/murmur.sqlite

2011-02-14 03:48:22.133 DBus registration succeeded

2011-02-14 03:48:22.137 MurmurIce: Endpoint "tcp -h 127.0.0.1 -p 6502" running

2011-02-14 03:48:22.137 Murmur 1.2.2 (1.2.2) running on Win: 6.0.6002.1: Booting servers

2011-02-14 03:48:22.213 1 => Server listening on [::]:64738

2011-02-14 03:48:22.284 1 => Server listening on 0.0.0.0:64738

2011-02-14 03:48:22.385 1 => Announcing server via bonjour

2011-02-14 03:48:22.467 1 => Not registering server as public

2011-02-14 03:48:37.399 1 => <1:(-1)> New connection: 192.168.2.2:52053

2011-02-14 03:48:37.400 Connection: Failed to add flow to QOS

2011-02-14 03:48:37.501 1 => <1:(-1)> Connection closed: Error during SSL handshake: error:1408A10B:SSL routines:SSL3_GET_CLIENT_HELLO:wrong version number [13]

2011-02-14 03:48:55.586 1 => <2:(-1)> New connection: (My ip here) 2011-02-14 03:48:55.668 1 => <2:(-1)> Connection closed: Error during SSL handshake: error:1408A10B:SSL routines:SSL3_GET_CLIENT_HELLO:wrong version number [13]

2011-02-14 04:03:24.885 1 => <3:(-1)> New connection: (My ip here)2011-02-14 04:03:24.977 1 => <3:(-1)> Connection closed: Error during SSL handshake: error:1408A10B:SSL routines:SSL3_GET_CLIENT_HELLO:wrong version number [13]

2011-02-14 04:03:58.767 1 => <4:(-1)> New connection: (My ip here)2011-02-14 04:03:58.848 1 => <4:(-1)> Connection closed: Error during SSL handshake: error:1408A10B:SSL routines:SSL3_GET_CLIENT_HELLO:wrong version number [13]

Any idea what's going on? Here's what my configuration settings look like-

# Path to database. If blank, will search for

# murmur.sqlite in default locations or create it if not found.

database=

# If you wish to use something other than SQLite, you'll need to set

the name

# of the database above, and also uncomment the below.

# Sticking with SQLite is strongly recommended, as it's the most

well tested

# and by far the fastest solution.

#

#dbDriver=QMYSQL

#dbUsername=

#dbPassword=

#dbHost=

#dbPort=

#dbPrefix=murmur_

#dbOpts=

# Murmur defaults to not using D-Bus. If you wish to use dbus, which

is one of the

# RPC methods available in murmur, please specify so here.

#

dbus=session

# Alternate service name. Only use if you are running distinct

# murmurd processes connected to the same D-Bus daemon.

#dbusservice=net.sourceforge.mumble.murmur

# If you want to use ZeroC Ice to communicate with Murmur, you need

# to specify the endpoint to use. Since there is no authentication

# with ICE, you should only use it if you trust all the users who

have

# shell access to your machine.

# Please see the ICE documentation on how to specify endpoints.

ice="tcp -h 127.0.0.1 -p 6502"

# Ice primarily uses local sockets. This means anyone who has a

# user account on your machine can connect to the Ice services.

# You can set a plaintext "secret" on the Ice conntection, and

# any script attempting to access must then have this secret.

#icesecret=

# How many login attempts do we tolerate from one IP

# inside a given timeframe before we ban the connection?

# Note that this is global (shared between all virtual servers), and

that

# it counts both successfull and unsuccessfull connection attempts.

# Set either Attempts or Timeframe to 0 to disable.

#autobanAttempts = 10

#autobanTimeframe = 120

#autobanTime = 300

# Murmur default to logging to murmur.log. If you leave this blank,

# murmur will log to the console (linux) or through message boxes

(win32).

#logfile=murmur.log

# If set, murmur will write its process ID to this file.

#pidfile=

# The below will be used as defaults for new configured servers.

# If you're just running one server (the default), it's easier to

# configure it here than through D-Bus or Ice.

#

# Welcome message sent to clients when they connect

welcometext="

Welcome to The Epic Delve Murmur.

/>Enjoy your stay!

"

# Port to bind TCP and UDP sockets to

port=64738

# Specific IP or hostname to bind to.

# If this is left blank (default), murmur will bind to all available

addresses.

#host=

# Password to join server

#serverpassword=

# Maximum bandwidth (in bits per second) clients are allowed

# to send speech at.

bandwidth=72000

# Maximum number of concurrent clients allowed.

users=100

# Regular expression used to validate channel names

# (note that you have to escape backslashes with \ )

#channelname=[ \\-=\\w\\#\\[\\]\\{\\}\\(\\)\\@\\|]+

# Regular expression used to validate user names

# (note that you have to escape backslashes with \ )

#username=[-=\\w\\[\\]\\{\\}\\(\\)\\@\\|\\.]+

# Maximum length of text messages in characters. 0 for no limit.

#textmessagelength=5000

# Maximum length of text messages in characters, with image data. 0

for no limit.

#imagemessagelength=131072

# Allow clients to use HTML in messages, user comments and channel

descriptions?

#allowhtml=true

# Murmur retains the per-server log entries in an internal database

which

# allows it to be accessed over D-Bus/ICE.

# How many days should such entries be kept?

#logdays=31

# To enable public server registration, the serverpassword must be

blank, and

# this must all be filled out.

# The password here is used to create a registry for the server

name; subsequent

# updates will need the same password. Don't lose your password.

# The URL is your own website, and only set the registerHostname for

static IP

# addresses.

#

#registerName=The Epic Delve

registerPassword=samtron

#registerUrl=www.theepicdelve.com

#registerHostname=theepicdelve.dyndns.org

# To enable bonjour service discovery uncomment the following line.

# To change the name announced by bonjour adjust the registerName

variable.

# See http://developer.apple.com/networking/bonjour/index.html for

more information

# about bonjour.

#bonjour=True

# If you have a proper SSL certificate, you can provide the

filenames here.

#sslCert=

#sslKey=

# If murmur is started as root, which user should it switch to?

# This option is ignored if murmur isn't started with root

privileges.

#uname=

# If this options is enabled, only clients which have a certificate

are allowed

# to connect.

#certrequired=False

# You can configure any of the configuration options for Ice here.

We recommend

# leave the defaults as they are.

# Please note that this section has to be last in the configuration

file.

#

[ice]

Ice.Warn.UnknownProperties=1

Ice.MessageSizeMax=65536

[hacst]

1.1.X and 1.2.X protocols and encryption are incompatible. We never shipped the 1.1.X server with the 1.2.X binaries so unless you have downloaded it seperately it is expected that the backwards compatible client (read 1.1.X only client) is unable to connect.

The 1.2.2 client should work on your local server though. If it freezes right when you open it that usually hints at driver issues. Try updating sound and video drivers. If it freezes on connect: Have you tried connecting to a public server on the web. Same freezeups there? Not that it should freeze in any case...

You could also try whether using 1.2.3 helps. We just published the third release candidate and expect to release the final soon so its safe to use.

[clhdrums87]

I've connected to a web server before (via link on their web page) and everything worked fine.

But it's when I try to run the actual mumble application is when it freezes. I just checked to make sure my audio and video drivers are up to date and it's fine. Could there be a problem with my microsoft lifecam drivers? I know some programs won't work right when those drivers are on your computer.

I tried the newer 1.2.3 and there's still the same freeze up when I start it. When I close out of it and go back into it, sometimes i'll work fine until I connect. Any ideas?

Thanks for your help