Adium

Ticket #8121 (closed defect: fixed)

Opened 2 years ago

Last modified 23 months ago

MSN won't connect under Leopard

Reported by: lozerTO Owned by: nobody
Milestone: Adium X 1.1.4 Component: Service/MSN
Version: 1.1.3 Severity: normal
Keywords: MSN reading error leopard 9a559 Cc:
Patch Status:

Description

Since I upgraded to Leopard 9a559, Adium will not connect to MSN, giving the error "Connection error from Notification server: Reading error"

It will connect to AIM and Google Talk, which are the only other two protocols I have tested.

I was first using 1.1.2, and tried upgrading to 1.1.3b, but still no luck.

I can connect perfectly using the Microsoft Messenger client.

Also, I was at first receiving this error under an upgrade installation of 9a559, however I have since done a clean install and I am encountering the same error.

Attachments

leopard_msn_debug.zip (79.9 KB) - added by MysticalOS 2 years ago.

Change History

  Changed 2 years ago by boredzo

What happens under the final release of 1.1.3 (which has been out for some time)?

  Changed 2 years ago by sbultez

Connect without any problem with 1.1.3 on 9A559

  Changed 2 years ago by lozerTO

Ok, I think I mixed things up, then... I think I had 1.1.3 prior, and accidentally downgraded to 1.1.3b, however the issue was the same.

  Changed 2 years ago by evands

Try the HTTP Connect option.

  Changed 2 years ago by Maeve

I was having exactly the same problem as of last night, only nothing has changed on my computer in the past few days. I'm still running the latest version of Tiger and 1.1.3. I got exactly the same error. I was connecting through HTTP, and turning that option off fixed it.

  Changed 2 years ago by edr1084

  • milestone set to Leopard

  Changed 2 years ago by jas8522

  • milestone changed from Leopard to Adium X 1.1.4

Did you try TroubleshootingTips? It would be good to hold on to the current prefs though so we can help figure out what the problem actually is, but at least that might create a workaround for now.

This has now been reported in GM 9a581 in #8178

  Changed 2 years ago by lozerTO

Hi,

I now have the GM 9a581 of Leopard and still the same problem. The Microsoft client works fine, however.

  Changed 2 years ago by camelludo

Hi there,

I have the same built and the same problem. It just does not connect...

  Changed 2 years ago by jas8522

Like I mentioned above, please try the TroubleshootingTips so we can help narrow this down... save your old prefs though!

  Changed 2 years ago by jas8522

  • summary changed from MSN won't connect under Leopard 9a559 to MSN won't connect under Leopard

  Changed 2 years ago by camelludo

done everything... Still the same...

  Changed 2 years ago by ricochet

I have exactly the same issues. Renaming preferences and retrying didn't change anything. Logging in as a new user and retrying, still the same issue.

Weird one this... I'm using the latest 1.1.3 freshly downloaded today.

  Changed 2 years ago by ricochet

Sorry, should have mentioned I'm running the official release of Leopard. I performed an upgrade install, MSN connection via Adium was working fine on Tiger prior to the install.

Thanks

  Changed 2 years ago by zacw

Hmm. A decent amount of people are reporting it. I'm able to connect with my MSN account on Leopard on 1.1.3 without issue.

Do any of you use a firewall program like LittleSnitch? Or have the OS X (or otherwise) firewall enabled?

  Changed 2 years ago by camelludo

little snitch uninstalled, firewall off...

  Changed 2 years ago by lozerTO

I have tried all of the troubleshooting steps (removed extras, deleted settings, tried under another user account) and no dice.

I have a Linksys WRT54G router. I may try connecting directly to see if that has anything to do with it.

  Changed 2 years ago by camelludo

Connection report for process: Adium (/Applications/Adium.app) Total: 1.4kB sent, 4.2kB received

messenger.hotmail.com (207.46.96.153), Port 1863 (msnp), Protocol 6 (TCP), 0.5kB sent, 1.0kB received by2msg1104016.phx.gbl (207.46.110.27), Port 1863 (msnp), Protocol 6 (TCP), 132 Bytes sent, 389 Bytes received by2msg1204310.phx.gbl (207.46.110.84), Port 1863 (msnp), Protocol 6 (TCP), 134 Bytes sent, 389 Bytes received by2msg1204314.phx.gbl (207.46.110.88), Port 1863 (msnp), Protocol 6 (TCP), 137 Bytes sent, 389 Bytes received nexus.passport.com (65.54.179.216), Port 443 (https), Protocol 6 (TCP), 366 Bytes sent, 1.8kB received by2msg1104216.phx.gbl (207.46.110.69), Port 1863 (msnp), Protocol 6 (TCP), 139 Bytes sent, 389 Bytes received

  Changed 2 years ago by camelludo

anybody got any luck?

  Changed 2 years ago by mattr

I haven't been able to connect to MSN since installing Leopard (using 1.1.3) But I've just been able to connect from a different network.

Same MacBook, only difference is the ADSL router (working with a Belkin, not working at home with a D-Link).

  Changed 2 years ago by timewarp

Hi Guys, Same issue here I performed an upgrade install of Leopard (9A581) and now MSN will not login. The connecting icon spins for around 5 minutes then I get the error "Connection error from Notification server: Reading error".

MSN connection via Adium was working fine on Tiger prior to the install. I am using Adium version 1.1.3 r21175

Thanks guys! Hope we can get a fix up soon :)

  Changed 2 years ago by xfodder

this question is directed to all users not being able to connect using msn ... are you all using @hotmail accounts? im using a @live account and it connects fine for me

  Changed 2 years ago by mattr

I'm not using @hotmail, using an address with my own domain name... I was thinking it might be an MTU path discovery issue with Leopard since I've noticed a couple of other apps like Mail taking a while to connect sometimes, or disconnecting unexpectedly. But that probably doesn't explain why other apps like the Microsoft MSN client can connect OK. I tried lowering my MTU without any success.

  Changed 2 years ago by acidflash

I´m not using @hotmail either, it´s like mattr my own domain name.

  Changed 2 years ago by timperrett

I too am having the same problem.

Everything worked fine under Tiger, now under leopard I cant connect to MSN. Im using an @hotmail.co.uk address, but have also tried a .com account with no luck either.

I have tried creating a new user on the system, and that didnt work either. My GMail and ICQ accounts work without problem however. Pretty crazy! Is there anything else we can do to try and help debugging the problem?

  Changed 2 years ago by tjerkdb

I have the problem to. Adium dont connect under leopard. At least not on my home network. When i am on the road or at work adium connects perfectly to msn.

i worked trough the trouble shooting tips unfortunatly without succes.

I have a sitecom router at home and connect via wlan.

  Changed 2 years ago by jas8522

So far two people have reported that other networks work fine, just not using their home network. Anyone using a router where this problem is occurring, please try bypassing the router and plugging in directly to see if it is indeed a router caching/uPnP issue.

If the above suggestion works, then you could try resetting your router. Sometimes just unplugging it and plugging it back in works, but some routers store the routing info in NVRAM, meaning you either have to reset all the settings (usually hold down a reset button in the back for about 10-15 seconds).

It's possible that the Microsoft server is holding a connection with the router which is forwarding to an old IP address, since after the install of Leopard it likely requested a brand new lease, and your router *might* have kept the forwarding table entry for the old IP. Seems like a long shot, but it would explain why some are having this problem and others aren't.

  Changed 2 years ago by MysticalOS

Also a note that leopard firewall if it is set to block incommon connections, msn likes to do a lot of incommon checks uncommon to other messengers. This would probably break msn. Same would break it if you set it to specify app permissions and you accidentally put adium on the "do not allow incoming connections" setting.

Also, try keeping the following ports open on router itself. 1863 and 6891-6900

  Changed 2 years ago by tjerkdb

i tried to reset the router and opening the above mentioned ports. Unfortunatly no luck.

I cant connect my macbook pro directly to the landline becouse the route doubles as a modem, and unfortunatly my macbook pro doesnt have a modem included

  Changed 2 years ago by MysticalOS

What are 10.5's firewall settings under "security" in system preferences?

  Changed 2 years ago by tjerkdb

in setting under security -> firewall -> allow all incomming connections

  Changed 2 years ago by acidflash

I have reset my router with default settings, but no luck. I will try later today with a static IP direct to internet, and see if it will work out.

Changed 2 years ago by MysticalOS

  Changed 2 years ago by MysticalOS

Attached a debug that shows several connection attempts, all unsuccessful except for ONE in first log actually got through. It appears to be hanging on retrieving of contact list. It gets a partial packet but does not retrieve the rest successfully. I suspect the ones it's working for have smaller buddylists.

  Changed 2 years ago by MysticalOS

PS. I debugged using 1.2svn r21352

  Changed 2 years ago by jas8522

MysticalOS that debug log may not help, as 1.2svn currently uses new MSNP14 support (you'll notice personal messages).

A current bug in that code is that login on MSN takes about 2-3 minutes... try leaving it for a while and see if it always logs you in, but just after a long period of time.

  Changed 2 years ago by Lempa

I'm having this problem through my Router (Zyxel P-320W Wireless) and i just tried to plugin the ethernet cable directly to the ADSL modem and it worked!

I'm going to try resetting my router now and see if that helps.

(I haven't changed anything on my router since Tiger and the ports are forwarded corerctly btw.)

  Changed 2 years ago by jas8522

MysticalOS:  This build of the 1.1 branch has the debug window enabled and can be used to grab a debug log for this particular problem, whereas trunk may not encounter the same issue due to the different protocol and connectivity. I just built this on Leopard a few minutes ago from revision [21352] of the branch.

  Changed 2 years ago by Lempa

It get's stuck on trying to resolve the DNS names, so i added the IPs for: nexus.passport.com, messenger.hotmail.com and login.live.com to my /etc/hosts and now it can connect.

  Changed 2 years ago by jas8522

For those who don't know how to do this, you can run the following commands in terminal to accomplish this:

sudo su (enter your pass) cp /etc/hosts /etc/hosts.bak echo 207.46.96.153 messenger.htmail.com >> /etc/hosts echo 65.54.179.216 nexus.passport.com >> /etc/hosts echo 65.54.179.203 login.live.com >> /etc/hosts

So this appears to be a DNS Issue, I wonder what could have changed in Leopard that some routers are supplying DNS info correctly and some are not...

Those IP's above are likely different depending on your geographical region however, so you might have to find them yourself...

  Changed 2 years ago by jas8522

WikiFormatting :P

sudo su (enter your pass)
cp /etc/hosts /etc/hosts.bak
echo 207.46.96.153 messenger.htmail.com >> /etc/hosts
echo 65.54.179.216 nexus.passport.com >> /etc/hosts
echo 65.54.179.203 login.live.com >> /etc/hosts

  Changed 2 years ago by jas8522

I wonder if Leopard changed or updated the DNS Lookup function such that older router firmware might not respond properly to it?

lozerTO: I'm very familiar with the WRT54G ... have you updated your firmware in a while? That could solve this as well, if that is indeed the problem.

  Changed 2 years ago by MysticalOS

or just change to opendns.org which works around a lot of dns issues with my ISPs crappy dns resolution.

  Changed 2 years ago by acidflash

I have try out 10 different DNS server now. So i don´t think the problem is there, or have i wrong?

  Changed 2 years ago by cthree

sh-3.2# echo 65.54.239.210 messenger.hotmail.com >> /etc/hosts
sh-3.2# echo 65.54.179.216 nexus.passport.com >> /etc/hosts
sh-3.2# echo 65.54.183.203 login.live.com >> /etc/hosts

Solved it for me.

Just ping those names and use the IP address it shows for each.

  Changed 2 years ago by timewarp

Apple just released this fix:  http://docs.info.apple.com/article.html?artnum=306804

Unfortunately it hasn't fixed the problem :(

About the Login & Keychain Update 1.0 The Login & Keychain Update 1.0 for Mac OS X 10.5 Leopard is recommended for all Leopard installations. It addresses issues you may encounter when:

Logging in with an account originally created in Mac OS X 10.1 or earlier that has a password of 8 or more characters. Connecting to some 802.11b/g wireless networks. Changing the password of a FileVault-protected account.

  Changed 2 years ago by acidflash

It works.. Yay.. Something with the resolv in Leopard thats **** this up.

  Changed 2 years ago by acidflash

This solve the problem for me. Backup the settings in your Library/Application Support/Adium 2.0 then erase the catalog. Make sure you have shutdown the program first. After that run:

echo 65.54.183.203 login.live.com >> /etc/hosts
echo 65.54.179.216 nexus.passport.com >> /etc/hosts
echo 65.54.183.203 login.live.com >> /etc/hosts

as root (sudo -s). Then startup the program and fill your information out and hope for the best.

follow-up: ↓ 50   Changed 2 years ago by tjerkdb

It worked for me too altough the signon process takes realy long now (dont know if it is related) Make sure to ping the servers yourself and not copy past the ip adress mentioned above. I belief they differ based on location.

  Changed 2 years ago by camelludo

can someone write down what to do step by step, so that "idiots" like me can figure out what to do? I'm totally lost here. Thanks...

in reply to: ↑ 48   Changed 2 years ago by acidflash

Replying to acidflash:

echo 65.54.239.210 messenger.hotmail.com >> /etc/hosts
echo 65.54.179.216 nexus.passport.com >> /etc/hosts
echo 65.54.183.203 login.live.com >> /etc/hosts

I did write login.live.com two times..

follow-up: ↓ 52   Changed 2 years ago by camelludo

where do I write those lines? In terminal?

in reply to: ↑ 51   Changed 2 years ago by acidflash

Replying to camelludo:

where do I write those lines? In terminal?

Yha.

  Changed 2 years ago by camelludo

What am I doing wrong??? Help me out here, won't you?


Last login: Sun Oct 28 01:34:54 on console Macintosh:~ camelludo$ echo 65.54.183.203 login.live.com >> /etc/hosts -bash: /etc/hosts: Permission denied Macintosh:~ camelludo$ echo 65.54.179.216 nexus.passport.com >> /etc/hosts -bash: /etc/hosts: Permission denied Macintosh:~ camelludo$ echo 65.54.183.203 login.live.com >> /etc/hosts -bash: /etc/hosts: Permission denied Macintosh:~ camelludo$ sudo su (mypassword) -bash: syntax error near unexpected token `(' Macintosh:~ camelludo$ sudo su (mypassword) cp /etc/hosts /etc/hosts.bak sh-3.2# echo 65.54.239.210 messenger.hotmail.com >> /etc/hosts -bash: syntax error near unexpected token `(' Macintosh:~ camelludo$ sh-3.2# echo 65.54.179.216 nexus.passport.com >> /etc/hosts -bash: /etc/hosts: Permission denied Macintosh:~ camelludo$ sh-3.2# echo 65.54.183.203 login.live.com >> /etc/hosts -bash: /etc/hosts: Permission denied Macintosh:~ camelludo$ sudo su mypassword cp /etc/hosts /etc/hosts.bak sh-3.2# echo 65.54.239.210 messenger.hotmail.com >> /etc/hosts -bash: /etc/hosts: Permission denied Macintosh:~ camelludo$ sh-3.2# echo 65.54.179.216 nexus.passport.com >> /etc/hosts -bash: /etc/hosts: Permission denied Macintosh:~ camelludo$ sh-3.2# echo 65.54.183.203 login.live.com >> /etc/hosts -bash: /etc/hosts: Permission denied Macintosh:~ camelludo$ sudo su (mypassword) cp /etc/hosts /etc/hosts.bak echo 207.46.96.153 messenger.htmail.com >> /etc/hosts echo 65.54.179.216 nexus.passport.com >> /etc/hosts echo 65.54.179.203 login.live.com >> /etc/hosts -bash: syntax error near unexpected token `('

  Changed 2 years ago by acidflash

First of, you need to run: sudo -s Then write you password. After that you can edit hosts.

If you want to check you have put in the information after you have run the three echo commands, you just writes nano /etc/hosts

  Changed 2 years ago by camelludo

Does this look wright to you guys? 'Cause it doesn't work.. .................. Last login: Sun Oct 28 02:32:35 on ttys000 Macintosh:~ camelludo$ sudo -s Password: bash-3.2# echo 65.54.239.210 messenger.hotmail.com >> /etc/hosts bash-3.2# echo 65.54.179.216 nexus.passport.com >> /etc/hosts bash-3.2# echo 65.54.183.203 login.live.com >> /etc/hosts bash-3.2# nano /etc/hosts bash-3.2#

  Changed 2 years ago by camelludo

ok I did connect. That took super long but I did. Thank you guys. Especially you ACIDFLASH! Hope this issue gets solved naturally by an update or sth.

follow-ups: ↓ 58 ↓ 60   Changed 2 years ago by atari

It's quite easy to fix that problem:

No change in /etc/hosts needed.

Set your own DNS-Servers, under Network "Advanced..." --> DNS e.g.

4.2.2.2 & 141.1.1.1

Normally only your Router will be listet.

then:

sudo dscacheutil -flushcache

After this, start Adium and enjoy ;)

in reply to: ↑ 57   Changed 2 years ago by acidflash

Thanks alot atari, that solve the problem fast. But the thing is, why did those DNS server works and not the another around the world?

  Changed 2 years ago by atari

You can use any other Nameserver you like, I don't know what is buggy with Leopard-DNS-Adium, but this definetly helps

in reply to: ↑ 57   Changed 2 years ago by timewarp

Replying to atari:

It's quite easy to fix that problem: No change in /etc/hosts needed. Set your own DNS-Servers, under Network "Advanced..." --> DNS e.g. {{{ 4.2.2.2 & 141.1.1.1 }}} Normally only your Router will be listet. then: {{{ sudo dscacheutil -flushcache }}} After this, start Adium and enjoy ;)

This worked! Thank you Atari!!

  Changed 2 years ago by mattr

And it's not just Adium that's affected. I just changed my router's config so it publishes my ISP's DNS server via DHCP (instead of itself) and: - Adium connects to MSN again (and it's fast) - Mail no longer has a 20-30 second delay before sending a new email - Safari (seems) faster

  Changed 2 years ago by MysticalOS

open dns:

208.67.222.222

208.67.220.220

 http://www.opendns.org

test the configuration.

 http://welcome.opendns.org

seeing as this issue is resolved as a bug in leopard though and how it handles dns queries to routers, there isn't anything to be fixed on adium end besides the slow login issue.

  Changed 2 years ago by jas8522

  • status changed from new to closed
  • resolution set to fixed

Yes that definitely seems to be the case, thanks everyone!

MysticalOS and anyone else using 1.2svn can track the slow login issue here: #8133 and almost equivalently  #p3610

Marking as fixed as it sounds the most accurate, even though this was not an actual Adium patch/fix.

  Changed 2 years ago by evands

atari's fix fixed subversion in 10.5 for me, too; it wasn't able to resolve svn.adiumx.com while a 10.4 machine on the same network with the same configuration had no problems. This does seem to be a 10.5 DNS bug.

in reply to: ↑ description   Changed 2 years ago by PhilipR

I tried this Terminal thing... before, I was able to connect with ICQ, not with MSN. Now, I am not able to connect to either ICQ or MSN. So things got worse. Can anyone please help me??? I have no idea what to do and how Terminal works. I was just following the steps described here. Thanks :-)

in reply to: ↑ description   Changed 2 years ago by PhilipR

oh... it worked now. I just took about ages to connect. Now I am connected with both, ICQ and MSN. Thanks!

  Changed 23 months ago by Richy

Please can you help me? it is not working at all. Every attepmt i have results in permission denied

Richies-Macbook-Pro:~ richieagarwal$ sudo -s *password* echo 65.54.239.210 messenger.hotmail.com >> /etc/hosts echo 65.54.179.216 nexus.passport.com >> /etc/hosts echo 65.54.183.203 login.live.com >> /etc/hosts -bash: /etc/hosts: Permission denied

What do i do???

please help, Thank you

  Changed 23 months ago by Richy

i live in new zealand by the way, thats in the pacific

Note: See TracTickets for help on using tickets.