MSN will not connect after upgrade to Leopard (DNS)

[acidflash]

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

The same error as in Ticket #8121

It works with ICQ to connect.

[acidflash]

It should be Component: MSN not Adium Core.. My bad.

[jas8522]

#8121 (build doesn't matter, in fact I doubt this is Leopard specific at all as many of us are using it fine with MSN on Leopard.

[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

[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 with no luck.

I have tried creating a new user on the system too, and that didnt work either. My GMail and ICQ accounts still work without problem however.

Any idea when there might be a solution to this?

[boredzo]

Multiple users are reporting this on feedback. Just in case the build *does* matter, let's declare this ticket as the ticket for MSN-doesn't-connect-on-Leopard.

At least one of those users report that Microsoft Messenger is able to connect.

[zacw]

Well, just because they're reporting it doesn't quite mean that it's the problem.

MSN client itself might be (and probably is, since we're still using an old version of communications) a newer server location, which is resolving. The issue, as it boiled down in the ticket this is a duplicate of, is that there is a problem with some DNS resolution in Leopard.

[jas8522]

I have to agree with zac on this... as it's a DNS issue, the Microsoft Messenger client must simply be hard coding IP's in as a backup to the names. Alternative to that solution, is there a DNS lookup that can be done by specifying the DNS server? If so, then we could just have a fallback wherein all DNS lookups are done by OpenDNS (mentioned above) or even make that the default.

I know for a fact that many ISP's have bad DNS server where some names simply disappear for 24 hours or more. Because of this, the OpenDNS solution *could* prevent a few extra connectivity tickets for multiple protocols...

So basically unless someone wants to put this in as a workaround, then since this is not an Adium bug, it should probably be closed...

[jas8522]

Well... libpurple is in C, so according to the host  man pages you can specify the server as an argument. Perhaps libpurple should specify the OpenDNS servers to use them for lookup rather than the locally provided server... anyone else have any thoughts on this?

[jas8522]

Either way this likely won't be done for 1.1.4

Since this is a task for the libpurple code, going to set to waiting on libpurple for now.

[pascalpt]

I can't connect since installing leopard retail but it doesn't seem related to DNS resolution. The name hasn't changed in ages and neither has the address it resolves to. The Windows box sitting next to my mac has the same settings in Trillian and everything works fine (and so did the mac when Tiger was installed). When I try to connect to MSN, it says "connecting" for at least 2 minutes and then it fails with a "read error". I'm not sure we're chasing the right problem here by waiting for libpurple to change something.

[jas8522]

pascalpt: guaranteed it's a DNS problem. You can read through #8121 (mentioned above) for a huge list of people for whom this was fixed by adjusting their DNS servers or HOSTS file. At least try using the OpenDNS servers like was suggested above as a solution before trying to claim this is not the problem!

Trillian could very easily be specifying a particular name server to use for DNS resolution, thereby bypassing your local DNS server configuration. That is the exact fix that I'm suggesting above, but it needs to be added to libpurple, as it handles all connectivity, including DNS resolution.

[pascalpt]

I stand corrected. After reading the other ticket, I tried changing my router settings to relay the ISP's DNS (instead of itself) and everything works fine. It's weird that MSN is the only protocol and adium the only application affected by this but it does point to a problem with leopard.

[arrava]

Was same problem. the resolution is absolutely trivial - change the server in adium to messenger.live.com. farewell to hotmail :)

[kaxor]

I have this same problem. Have tried changing the server in adium to messenger.live.com to no success

[arrava]

Worked for me one day, then ... not worked. By testing different IM software and checking with Little Snitch their behaviour, I found out, that this IS Adium problem, not Leopard. the rest messengers (tested: Proteus, Mercury Messenger, Jbuddy Messenger pro) I found out, that ONLY Adium was unable to work with DNS issues. I have an office network with internal DNS servers, I can not put external DNS server (frankly speaking I can - I do have rights, but others - can't) specially for Adium, because the rest of software is working PERFECTLY, but Adium's MSN - not (other protocols working fine). Using AdiumX 1.2svn (found in inet)

[zacw]

What hosts are the other programs trying to connect on?

[arrava]

messenger.hotmail.com *.phx.gbl contacts.msn.com loginnet.passport.com omega.contacts.msn.com by2msg.....mixer.edge.messenger.live.com

sometimes directly to mseenger.live.com

Adiumx goes same way (almost) inc:

login.live.com by1msg...gateway.edge.messenger.live.com

but it takes more time, than for Live Messenger 6.0.3, and it requires external DNS to be mentioned in the network settings of OS (I use OpenDNS as well)

[tnaseem]

I was having the same problem, but have a workaround. I've documented it here:  http://www.naseem.co.uk/tips/leopard-problems-connecting-to-windows-live-messenger-using-adium/

Basically, you need to add the following to your /etc/hosts file:

65.54.179.216 nexus.passport.com 65.54.239.20 messenger.hotmail.com 65.54.183.203 login.live.com

And that should do the trick.

[tnaseem]

Sorry, there should be linebreaks in between each host in the above comment. They were removed once I hit 'submit' :)

[arrava]

when I try to add it, the result is:

sh: syntax error near unexpected token `&'

[jas8522]

#8404 has more details about this and shows that it affects those using protocols other than MSN as well.

[boredzo]

#8404 is not the same problem.

[gnosis]

I was having the same issue with the Reading error. Tried everything on this thread (and others) without success. Then I remembered I had turned on "connect through HTTP" to get around a firewall issue during a trip. Unchecked that and now I'm connecting fine.

Don't know if that will work for anyone else but it may help to narrow down the problem.

[echevil]

i am having the issue too, but only in one of my MSN accounts. I have a @live.com and a @hotmail.com account that works fine but my @msn.com account which have most of the contacts have the same loggin error. However, if i keep trying, there's a small chance that I can log in successfully.

[jas8522]

#9100 also had a couple people posting that seemed to have the same problem as this. If I am correct about that then the debug log will indicate failure with something similar to:

16:37:19: ************ youraccount@gmail.com --step-- 5
16:37:20: (Libpurple: dns) DNS query for 'loginnet.passport.com' queued
16:37:20: Performing DNS resolve: loginnet.passport.com:443
16:37:25: (Libpurple: msn) servconn read error, len: 0 error: Unknown error: 0
16:37:25: (Libpurple: msn) Connection error from Notification server (207.46.111.43): Reading error
16:37:25: (Libpurple: msn) C: NS 000: OUT
16:37:25: Connection Disconnected: gc=103d91a0 (Connection error from Notification server: Reading error)
16:37:25: <ESPurpleMSNAccount:cf61960 1>:youraccount@gmail.com accountConnectionReportDisconnect: Connection error from Notification server: Reading error
16:37:25: (Libpurple: account) Disconnecting account 0x103d2e80
16:37:25: (Libpurple: connection) Disconnecting connection 0x103d91a0
16:37:25: (Libpurple: msn) destroy httpconn (0x103d9680)
16:37:25: Disconnected: gc=103d91a0
16:37:25: <ESPurpleMSNAccount:cf61960 1>:youraccount@gmail.com: Telling the core we disconnected
16:37:25: <ESPurpleMSNAccount:cf61960 1>:youraccount@gmail.com: Disconnected ("Connection error from Notification server:

When this problem occurs.

[boredzo]

 Apple resolved the problem in Mac OS X 10.5.3 by reverting to the Tiger behavior of using A records, not SRV records, to look up names.

So, this problem should no longer exist for anybody on Mac OS X 10.5.3. If it does, it probably isn't DNS-related and is therefore not relevant to this ticket.

[anonymous]

Milestone Waiting on Apple deleted