MSN connection problems in pidgin 2.3.0

[vadillo]

I cant get connected to pidgin this is may log file

[vadillo]

Output

[datallah]

This looks like a network problem. Do you have a software firewall or something?

[vadillo]

I don't think so cos i've been able to get connected using pidgin on the same net without problems, an also i've installed the same version in my house PC on other net and gave me the same problem.

[vadillo]

Replying to vadillo:

I don't think so cos i've been able to get connected using pidgin on the same net without problems, an also i've installed the same version in my house PC on other net and gave me the same problem.

[xabin]

This is happening to me too. Was connected with 2.2.3 to MSN before installing 2.3.0, so it's not a network problem. Pidgin connects successfully, buddies start showing up in the list, then I get disconnected immediately with "Connection error from Notification server: Reading error".

[Rabbs]

Replying to xabin:

This is happening to me too. Was connected with 2.2.3 to MSN before installing 2.3.0, so it's not a network problem. Pidgin connects successfully, buddies start showing up in the list, then I get disconnected immediately with "Connection error from Notification server: Reading error".

Confirming this error. Exact same thing happening to me on win XP x86. Tried on two different computers, with two different WLM accounts, same problem on both. Downgrading to 2.2.x makes it work like a charm again.

[okravetz]

Same here, but this is the error I get: "Unable to authenticate .NET Messenger Service"

[vadillo]

I got connected today, did you fix something?, i did it on the same net, the same version.

[holymist]

I'm also unable to connect to MSN at all with 2.3.0. Going back to 2.2.2 works fine, MSN connects and is happy. I'm using windows pidgin following the instructions to make it portable (renaming the file to pidgin-portable.exe).

[Alejo]

same error here...

[nosnilmot]

Fix for this issue

[nosnilmot]

I think I've fixed this, but I've heard one report without details that the patch doesn't help. If any of you are able to confirm one way or the another it would be appreciated.

The patch is attached - if you don't know how to apply / test a source patch don't worry about it.

[Abyss]

I would like to see this update put into an actual compiled format now. I am unable to apply patches, I just use the precompiled Win32 version. :/

I have the exact same problem, and the difference for me is waht the email is. It works for my old account AbysBlackrose?(@)gmail.com but does not work for Abyss(@)voidInput.com

[nosnilmot]

The plan is to provide a new release soon after we've verified the fixes are actually good enough.

If you are willing to help test, I put a Windows replacement MSN protocol plugin up here that you could try: http://pidgin.im/~nosnilmot/2.3.0-msnfix/libmsn.dll

To use it, take a backup copy of C:\Program Files\Pidgin\plugins\libmsn.dll and put the file from above in it's place.

For reference, the issues observed so far are not related directly to what your account name is, but are related to the friendly names your buddies have, so they may be different on different accounts.

[Alejo]

nosnilmot... i cant log in now... but i have to accept all mi contacts again? :S

[Abyss]

I tried it out. well, trying it out. The moment I turned Pidgin back on, I got some Sync issues, with the name that was working, but when I clicked yes through them, I had no other problems with that.

I renabled the account that was having issues, and it gave the same Sync issue, but after hitting yes, everything worked fine.

So, on my Win XP system, running Pidgin 2.3.0, and your patch, it works fine. :) Thanks for your help!

[Alejo]

isnt working well... i open a conversation and it opens like if im talking in 2 conversations with 1 contact

[nosnilmot]

Replying to Alejo:

isnt working well... i open a conversation and it opens like if im talking in 2 conversations with 1 contact

I'm sorry, I don't understand what you are describing. Maybe you could provide a screenshot?

[Hannes Rannes]

The updated libmsn.dll doesn't work. I just get the message, that my e-mail adress or password is incorrect. I tried it with the libmsn.dll from Pidgin 2.2.2 and I can connect with MSN again. Writing with buddys works also fine.

[nosnilmot]

Replying to Hannes Rannes:

The updated libmsn.dll doesn't work. I just get the message, that my e-mail adress or password is incorrect. I tried it with the libmsn.dll from Pidgin 2.2.2 and I can connect with MSN again. Writing with buddys works also fine.

*sigh* oh what fun 2.3.0 has been. How long is your password?

[Hannes Rannes]

It is 16 characters long, containing digits, lower and upper case letters and special characters. ;)

[nosnilmot]

Replying to Hannes Rannes:

It is 16 characters long, containing digits, lower and upper case letters and special characters. ;)

OK, I put a new build for you to try, if you wouldn't mind, at http://pidgin.im/~nosnilmot/2.3.0-msnfix/libmsn.dll

If that one doesn't work, try http://pidgin.im/~nosnilmot/2.3.0-msnfix/libmsn.dll-pwdgt16 (rename it to libmsn.dll)

[Rabbs]

Replying to nosnilmot:

OK, I put a new build for you to try, if you wouldn't mind, at http://pidgin.im/~nosnilmot/2.3.0-msnfix/libmsn.dll If that one doesn't work, try http://pidgin.im/~nosnilmot/2.3.0-msnfix/libmsn.dll-pwdgt16 (rename it to libmsn.dll)

First one does not work for me, second one works properly though.

[rancor]

I can verify that http://pidgin.im/~nosnilmot/2.3.0-msnfix/libmsn.dll-pwdgt16 did solved the problem. I also using a very strong password with a lot of mixed chars and I could not connect to MSN after the upgrade to 2.3.0

[Hannes Rannes]

Yes, the second one (pwdgt16) works. I didn't try the other one.

[nosnilmot@…]

(In [41b4d75b70555daf78b3c5701a59453027ca57e7]) Something is wrong about the way we truncate overlength passwords, and apparently it's not as simple as truncating prior to encoding, so just drop this for now. References #4066, #4103

[ryansteed]

Replying to nosnilmot:

The plan is to provide a new release soon after we've verified the fixes are actually good enough. If you are willing to help test, I put a Windows replacement MSN protocol plugin up here that you could try: http://pidgin.im/~nosnilmot/2.3.0-msnfix/libmsn.dll To use it, take a backup copy of C:\Program Files\Pidgin\plugins\libmsn.dll and put the file from above in it's place. For reference, the issues observed so far are not related directly to what your account name is, but are related to the friendly names your buddies have, so they may be different on different accounts.

This version has resolved my authentication issue: passwords with special characters would be denied. These are the only characters I've verified up to now: !@#$.

Thanks!!!

[parabola]

Replying to ryansteed:

Replying to nosnilmot:

The plan is to provide a new release soon after we've verified the fixes are actually good enough. If you are willing to help test, I put a Windows replacement MSN protocol plugin up here that you could try: http://pidgin.im/~nosnilmot/2.3.0-msnfix/libmsn.dll To use it, take a backup copy of C:\Program Files\Pidgin\plugins\libmsn.dll and put the file from above in it's place. For reference, the issues observed so far are not related directly to what your account name is, but are related to the friendly names your buddies have, so they may be different on different accounts.

This version has resolved my authentication issue: passwords with special characters would be denied. These are the only characters I've verified up to now: !@#$. Thanks!!!

Worked for MSN, i'm having the same issue with gtalk..

[okravetz]

confirming that (http://pidgin.im/~nosnilmot/2.3.0-msnfix/libmsn.dll) works for me, too (using special chars @ and $). Didn't try pwdgt16.

[vadillo]

confirming that (http://pidgin.im/~nosnilmot/2.3.0-msnfix/libmsn.dll) works for me, too I'm hearing that the same problem its happening on Linux too. it's that true?.

[the_glu]

Yes, I'm on linux (archlinux), and I have the problem too. Long password and specials chars.

[terrex]

I can confirm your patch also fix it on ubuntu 7.10 amd64.

[TehWan]

I cannot connect using either of the two libraries (however, I do not get an unknown error message anymore, so it somehow works) because it tells me my password is invalid (when it isn't). I have a 16-character password (MSN doesn't allow more =P) with special characters such as but not limited to %.

I am on Windows XP.

[RazielJaTier]

After reading this thread it seemed to me that having symbols in your password was causing the problem. As a test, I just changed my password on my account. I was able to connect without any further problems and without updating to the development MSN plugin.

Here are the special characters that were in my old password. My new password is limited to letters and numbers. #@()

[Rabbs]

Replying to RazielJaTier:

After reading this thread it seemed to me that having symbols in your password was causing the problem. As a test, I just changed my password on my account. I was able to connect without any further problems and without updating to the development MSN plugin. Here are the special characters that were in my old password. My new password is limited to letters and numbers. #@()

I can not connect with pidgin 2.3.0 using the original msn plugin, and I have no special symbols in my password (numbers and letters, 13 characters long)

[nosnilmot]

In an attempt to prevent the spread of misinformation, there is nothing wrong with having 'special' characters in your password. Pidgin 2.3.0 simply has a number of bugs in the MSN code that cause problems for some people when connecting.

[candsadvertising]

I tried to apply the patch (pidgin-2.3.0-msn-fname.patch) on Suse 10.2 AMD64, but I got the following error when running make:

user.c: In function 'msn_user_set_friendly_name':

user.c:129: error: expected expression before 'const'

user.c:133: error: expected expression before 'if'

user.c:128: warning: unused variable 'cmdproc'

make[5]: *** [user.lo] Error 1

etc..

I'm not a developer, so this is likely my fault. I downloaded the patch, and then cut and paste the patch over lines 126 thru 141 of user.c, checked permissions were the same, then ran configure and make again.

Can anyone tell me if I did something wrong? Thanks in advance for your help.

[nosnilmot]

Replying to candsadvertising:

I'm not a developer, so this is likely my fault. I downloaded the patch, and then cut and paste the patch over lines 126 thru 141 of user.c, checked permissions were the same, then ran configure and make again.

That's not how to apply the patch. You should put it in the top level of the source directory (pidgin-2.3.0) and do: patch -p0 < pidgin-2.3.0-msn-fname.patch

I also put an updated patch that fixes a couple of other MSN problems too that could be applied in a similar way here: http://pidgin.im/~nosnilmot/2.3.0-msnfix/pidgin-2.3.0-msn-allfixes.patch

[candsadvertising]

Thanks very much for your help, it is worked perfectly this time.

[Navarr]

Verification that (http://pidgin.im/~nosnilmot/2.3.0-msnfix/libmsn.dll) works here. (Windows Vista Home Premium). Should definently be included with the next version.

[aaron_w]

(http://pidgin.im/~nosnilmot/2.3.0-msnfix/libmsn.dll) worked for me. I can login to my MSN messenger account now. Windows XP Pro 2002 SP2.

Thanks very much.

[TehWan]

Woo, the new release of your dll now works.

Thanks a lot.

[nosnilmot]

Pidgin 2.3.1 is out including the fix for this