Adium

Ticket #10146 (closed defect)

Opened 21 months ago

Last modified 11 months ago

MSN connection cycles on and off rapidly when behind corporate proxy

Reported by: mikeindustries Owned by: felipec
Milestone: Component: Service/MSN
Version: 1.3.2 Severity: normal
Keywords: msn,proxy,reading-error,microsoft Cc:
Patch Status:

Description

I am behind Microsoft's corporate proxy and Adium has no problem with my AIM account. Additionally, the MSN Messenger client has no problem with my MSN account. Adium, however, will connect to my MSN account just fine and then within a few minutes start disconnecting and then re-connecting like crazy. The connection usually only lasts a few seconds once it starts cycling. Would love to help debug this, but all I really know about the proxy is that it's an HTTP proxy over port 80. When the connection disconnects, the following is dumped to Adium's log: 

09:54:22: (Libpurple: msn) Connection error from Notification server (gateway.messenger.hotmail.com): Reading error
09:54:22: (Libpurple: msn) destroy httpconn (0xb6c5050)
09:54:22: (Libpurple: msn) C: NS 000: OUT
09:54:22: Connection Disconnected: gc=cf26380 (Connection error from Notification server: Reading error)
09:54:22: <ESPurpleMSNAccount:6e62570 1>:myemailaddress@live.com accountConnectionReportDisconnect: Connection error from Notification server: Reading error
09:54:22: (Libpurple: account) Disconnecting account 0x6e7f400
09:54:22: (Libpurple: connection) Disconnecting connection 0xcf26380
09:54:22: (Libpurple: connection) Deactivating keepalive.
09:54:22: (Libpurple: msn) destroy httpconn (0xb9cc920)
09:54:22: Disconnected: gc=cf26380
09:54:22: <ESPurpleMSNAccount:6e62570 1>:myemailaddress@live.com: Telling the core we disconnected
09:54:22: <ESPurpleMSNAccount:6e62570 1>:myemailaddress@live.com: Disconnected ("Connection error from Notification server: Reading error"): Automatically reconnecting in 5.000000 seconds (0 attempts performed)
09:54:22: (Libpurple: connection) Destroying connection 0xcf26380

Change History

Changed 21 months ago by mikeindustries

One more piece of data to this: I can keep a connection open flawlessly as long as no one else in the office is logged into their MSN Messenger account via Adium. As soon as multiple people in the same office try to connect to MSN via Adium, all hell breaks loose and the connection/disconnection cycle begin.

Does this suggest something that can be cured on the proxy side of things? I have no idea how Adium handles proxied connections.

Changed 21 months ago by jas8522

  • pending changed from 0 to 1
  • milestone set to Needs feedback from users

That does seem pretty likely. Please try the 1.3 AdiumBeta and post a debug log from that if the problem continues.

Changed 21 months ago by jas8522

  • component changed from Adium Core to MSN

Changed 21 months ago by mikeindustries

  • pending changed from 1 to 0

Ok, just tried same thing with the Adium 1.3 beta and got the same results. As soon as someone else in the office logs in, I get logged out and the following appears in the Debug Log: 

18:20:54: (Libpurple: msn) Connection error from Notification server (gateway.messenger.hotmail.com): Reading error
18:20:54: (Libpurple: msn) C: NS 000: OUT
18:20:54: Connection Disconnected: gc=8368d10 (Connection error from Notification server:
Reading error)
18:20:54: <ESPurpleMSNAccount:6f65680 1>:myemailaddress@live.com accountConnectionReportDisconnect: Connection error from Notification server:
Reading error
18:20:54: (Libpurple: account) Disconnecting account 0x7e27f70
18:20:54: (Libpurple: connection) Disconnecting connection 0x8368d10
18:20:54: (Libpurple: connection) Deactivating keepalive.
18:20:54: (Libpurple: msn) destroy httpconn (0x9c2a7c0)
18:20:54: Disconnected: gc=8368d10
18:20:54: <ESPurpleMSNAccount:6f65680 1>:myemailaddress@live.com: Telling the core we disconnected
18:20:54: <ESPurpleMSNAccount:6f65680 1>:myemailaddress@live.com: Disconnected ("Connection error from Notification server:
Reading error"): Automatically reconnecting in 5.000000 seconds (0 attempts performed)
18:20:54: (Libpurple: connection) Destroying connection 0x8368d10

Changed 21 months ago by jas8522

  • pending changed from 0 to 1

If you have access to a Windows or Linux installation, please try this with  Pidgin and let us know if the problem exists there as well.

Changed 21 months ago by mikeindustries

  • pending changed from 1 to 0

Unfortunately I don't, however, I ran WireShark and below is the dump. What do you make of the HTTP 500 error at the end? Is this the MSN Messenger server or the proxy server spitting this out? Seems bad for a client to be able to reliably cause a 500 error. Thanks much for the help here... 

POST http://gateway.messenger.hotmail.com/gateway/gateway.dll?Action=open&Server=NS&IP=gateway.messenger.hotmail.com HTTP/1.1
Accept: */*
Accept-Language: en-us
User-Agent: MSMSGS
Host: gateway.messenger.hotmail.com
Proxy-Connection: Keep-Alive
Connection: Keep-Alive
Pragma: no-cache
Content-Type: application/x-msn-messenger
Content-Length: 24

VER 1 MSNP9 MSNP8 CVR0
HTTP/1.1 200 OK
Via: 1.1 OURPROXYSERVER
Connection: Keep-Alive
Proxy-Connection: Keep-Alive
Content-Length: 24
Date: Wed, 18 Jun 2008 17:43:46 GMT
Content-Type: application/x-msn-messenger
X-MSN-Messenger: SessionID=705699597.615685438; GW-IP=207.46.106.114
X-MSN-Host: BY1MSG2093120.gateway.edge.messenger.live.com
X-MSNSERVER: BY1MSG2093120

VER 1 MSNP9 MSNP8 CVR0
POST http://207.46.106.114/gateway/gateway.dll?SessionID=705699597.615685438 HTTP/1.1
Accept: */*
Accept-Language: en-us
User-Agent: MSMSGS
Host: 207.46.106.114
Proxy-Connection: Keep-Alive
Connection: Keep-Alive
Pragma: no-cache
Content-Type: application/x-msn-messenger
Content-Length: 76

CVR 2 0x0409 winnt 5.1 i386 MSNMSGR 6.0.0602 MSMSGS myemailaddress@live.com
HTTP/1.1 200 OK
Via: 1.1 OURPROXYSERVER
Connection: Keep-Alive
Proxy-Connection: Keep-Alive
Content-Length: 174
Date: Wed, 18 Jun 2008 17:43:46 GMT
Content-Type: application/x-msn-messenger
X-MSN-Messenger: SessionID=705699597.1433970900; GW-IP=207.46.106.114
X-MSN-Host: BY1MSG2093120.gateway.edge.messenger.live.com
X-MSNSERVER: BY1MSG2093120

CVR 2 8.5.1302 8.5.1302 8.1.0178 http://msgr.dlservice.microsoft.com/download/5/6/4/5646481F-33EF-4B08-AF00-4904F7677B89/EN/Install_WLMessenger.exe http://messenger.msn.com
POST http://207.46.106.114/gateway/gateway.dll?SessionID=705699597.1433970900 HTTP/1.1
Accept: */*
Accept-Language: en-us
User-Agent: MSMSGS
Host: 207.46.106.114
Proxy-Connection: Keep-Alive
Connection: Keep-Alive
Pragma: no-cache
Content-Type: application/x-msn-messenger
Content-Length: 36

USR 3 TWN I myemailaddress@live.com
HTTP/1.1 200 OK
Via: 1.1 OURPROXYSERVER
Connection: Keep-Alive
Proxy-Connection: Keep-Alive
Content-Length: 192
Date: Wed, 18 Jun 2008 17:43:46 GMT
Content-Type: application/x-msn-messenger
X-MSN-Messenger: SessionID=705699597.58241894; GW-IP=207.46.106.114
X-MSN-Host: BY1MSG2093120.gateway.edge.messenger.live.com
X-MSNSERVER: BY1MSG2093120

USR 3 TWN S ct=1213811027,rver=5.0.3270.0,wp=FS_40SEC_0_COMPACT,lc=1033,id=507,ru=http:%2F%2Fmessenger.msn.com,tw=0,kpp=1,kv=4,ver=2.1.6000.1,rn=1lgjBfIL,tpf=b0735e3a873dfb5e75054465196398e0
POST http://207.46.106.114/gateway/gateway.dll?Action=poll&SessionID=705699597.58241894 HTTP/1.1
Accept: */*
Accept-Language: en-us
User-Agent: MSMSGS
Host: 207.46.106.114
Proxy-Connection: Keep-Alive
Connection: Keep-Alive
Pragma: no-cache
Content-Type: application/x-msn-messenger
Content-Length: 0

HTTP/1.1 200 OK
Via: 1.1 OURPROXYSERVER
Connection: Keep-Alive
Proxy-Connection: Keep-Alive
Content-Length: 0
Date: Wed, 18 Jun 2008 17:43:48 GMT
Content-Type: application/x-msn-messenger
X-MSN-Messenger: SessionID=705699597.243430145; GW-IP=207.46.106.114
X-MSN-Host: BY1MSG2093120.gateway.edge.messenger.live.com
X-MSNSERVER: BY1MSG2093120

POST http://207.46.106.114/gateway/gateway.dll?Action=poll&SessionID=705699597.243430145 HTTP/1.1
Accept: */*
Accept-Language: en-us
User-Agent: MSMSGS
Host: 207.46.106.114
Proxy-Connection: Keep-Alive
Connection: Keep-Alive
Pragma: no-cache
Content-Type: application/x-msn-messenger
Content-Length: 0

HTTP/1.1 200 OK
Via: 1.1 OURPROXYSERVER
Connection: Keep-Alive
Proxy-Connection: Keep-Alive
Content-Length: 0
Date: Wed, 18 Jun 2008 17:43:50 GMT
Content-Type: application/x-msn-messenger
X-MSN-Messenger: SessionID=705699597.1377851858; GW-IP=207.46.106.114
X-MSN-Host: BY1MSG2093120.gateway.edge.messenger.live.com
X-MSNSERVER: BY1MSG2093120

POST http://207.46.106.114/gateway/gateway.dll?Action=poll&SessionID=705699597.1377851858 HTTP/1.1
Accept: */*
Accept-Language: en-us
User-Agent: MSMSGS
Host: 207.46.106.114
Proxy-Connection: Keep-Alive
Connection: Keep-Alive
Pragma: no-cache
Content-Type: application/x-msn-messenger
Content-Length: 0

HTTP/1.1 200 OK
Via: 1.1 OURPROXYSERVER
Connection: Keep-Alive
Proxy-Connection: Keep-Alive
Content-Length: 0
Date: Wed, 18 Jun 2008 17:43:52 GMT
Content-Type: application/x-msn-messenger
X-MSN-Messenger: SessionID=705699597.1579439534; GW-IP=207.46.106.114
X-MSN-Host: BY1MSG2093120.gateway.edge.messenger.live.com
X-MSNSERVER: BY1MSG2093120

POST http://207.46.106.114/gateway/gateway.dll?SessionID=705699597.1579439534 HTTP/1.1
Accept: */*
Accept-Language: en-us
User-Agent: MSMSGS
Host: 207.46.106.114
Proxy-Connection: Keep-Alive
Connection: Keep-Alive
Pragma: no-cache
Content-Type: application/x-msn-messenger
Content-Length: 5

OUT
HTTP/1.1 500 Internal Server Error
Via: 1.1 OURPROXYSERVER
Connection: Keep-Alive
Proxy-Connection: Keep-Alive
Content-Length: 0
Date: Wed, 18 Jun 2008 17:43:53 GMT
Content-Type: application/x-msn-messenger
X-MSN-Messenger: SessionID=705699597.0; GW-IP=207.46.106.16;Session=close
X-MSN-Host: BY1MSG2145205.gateway.edge.messenger.live.com
X-MSNSERVER: BY1MSG2145205

Changed 21 months ago by maynardcm

i finally gave up. seems that msn is causing all kinds of issues with adium. proteus seems to work ok. the interface sucks, but at least you don't get the boot. try that and see if you still get the same networking errors. mine (see ticket 9978) have stopped.

Changed 19 months ago by Robby

  • pending changed from 0 to 1

Please try the  1.3.1b1 beta, the problem could possible be resolved.

Changed 18 months ago by mikeindustries

  • pending changed from 1 to 0

Just checked in 1.3.1b1... not fixed. Same behavior. Essentially, when two clients are trying to use MSN Messenger service via Adium from behind the same corporate proxy, Adium causes the notification server to Error 500, and then boots the users off: 

09:54:22: Connection Disconnected: gc=16e10af0 (Error on notification server:
Internal Server Error)
09:54:22: <ESPurpleMSNAccount:5032a0 1>:passport@mdavidson.com accountConnectionReportDisconnect: Error on notification server:
Internal Server Error

Changed 18 months ago by Robby

  • owner changed from nobody to felipec
  • component changed from MSN to msn-pecan
  • milestone changed from Needs feedback from users to Adium 1.3.2

Ok, thanks for reporting back! :)

Changed 18 months ago by Robby

  • version changed from 1.2.5 to 1.3.1b1

Changed 18 months ago by jas8522

  • milestone changed from Adium 1.3.2 to Waiting on msn-pecan

Changed 18 months ago by felipec

  • status changed from new to assigned

Interesting.

Can you get a netdump of how Proteus (or anything that works) is using the http method? That would be very useful.

Changed 18 months ago by mikeindustries

Happy to. How do I do a "netdump" though? Is this built into OS X?

Changed 18 months ago by felipec

You just posted one :) With wireshark.

Changed 18 months ago by mikeindustries

Cool. felipec, I just sent you a dump to your gmail address.

Changed 18 months ago by felipec

Yeap, I got it.

How about 1.3.2? Does it works for you?

I have your dump in my to-do list for msn-pecan, but since it's not used in Adium anymore it's not a high-priority right now =/

Changed 17 months ago by anonymous

  • milestone Waiting on msn-pecan deleted

Milestone Waiting on msn-pecan deleted

Changed 17 months ago by Robby

  • status changed from assigned to closed
  • resolution set to wontfix

We are not using MSN-Pecan at the moment. Please update to 1.3.2 which features MSNp15.

Changed 17 months ago by mikeindustries

Should this really be marked as "wontfix", considering it happens with Pecan and non-Pecan implementations of Adium?

Changed 17 months ago by Robby

  • status changed from closed to reopened
  • resolution wontfix deleted
  • milestone set to Waiting on libpurple

You never answered felipec's question so how were we to know that this is still a problem for you in 1.3.2?

Changed 17 months ago by Robby

  • component changed from msn-pecan to MSN

Changed 17 months ago by mikeindustries

Ah, sorry about that. Must not have gotten the e-mail notification of that message. Yes, it still happens in 1.3.2.

Changed 17 months ago by Robby

  • version changed from 1.3.1b1 to 1.3.2

Ok, no worries. :)
I'm afraid we can't do much about the problem. It lies in the hands of the Pidgin developers who maintain libpurple.

Changed 11 months ago by zacw

  • status changed from new to closed

Closing all "waiting on libpurple" tickets. There's no reason to keep them around as open, and largely go ignored anyway. File a ticket at  http://developer.pidgin.im for any functionality you want to see.

Changed 11 months ago by anonymous

  • milestone Waiting on libpurple deleted

Milestone Waiting on libpurple deleted

Note: See TracTickets for help on using tickets.