I've done everything I can think of...
All the usual, updates to the meta pidgin, verified I can access the MSN account, but at CMD an NSLOOKUP on messenger.hotmail.com returns nothing...
Seems that MS has integrated messenger with their Live Essentials thus making messenger.hotmail.com:11004 no longer connect capable.
I've searched the forums for a reference and it seems I'm the first, so if anyone else has issue and a fix, please post it or the link or what should be in Account>Advanced>Server, Port and/or "HTTP Method Server" maybe?
Because even using it, I get "Connection error from Notification Server. Error resolving gateway messenger.hotmail.com:11004"
You are here
Pidgin: anybody else getting messenger.hotmail.com:11004 from MSN?
June 25, 2012 - 10:50am
#1
Pidgin: anybody else getting messenger.hotmail.com:11004 from MSN?
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
MSN on Pidgin is working fine for me. I'm not a heavy user user of the MSN messaging protocol, but from time to time I have to communicate with clients over it.
---My current Pidgin/MSN connection settings are as follow---
This are the default settings. Perhaps you are still using an outdated version of pidgin or for some reason you changed the port. Give these settings a try.
-Sever: messenger.hotmail.com
-Port: 1863
-HTTP Method Server: gateway.messenger.hotmail.com
--I don't use the HTTP method [not checked]
---Connection as shown on CMD/NETSTAT---
baymsg1030121.gateway.edge.messenger.live.com:1863 ESTABLISHED
SevenFactors, it was the gateway that was failing.
After only changing the
Server: messenger.hotmail.com
…to…
Server: baymsg1030121.gateway.edge.messenger.live.com
…did it connect successfully!!!
Thank you very much for your feedback!
BTW, this new gateway change has helped several of my co-workers too!
Living can be hazardous to your health, you may die from it.
~Phil Sergent
If that was the case then perhaps all you had to do was enable the HTTP method.
Anyways, glad to have been of help ^_^