ejabberd - Comments for "pyMSNt Failed to connect to MSN servers"

same here, any ideas? thx and

gewuerzwiesel — Fri, 17 Oct 2008 11:51:08 +0000

same here, any ideas?

thx and greets
weasel

still no success

ashish — Thu, 09 Oct 2008 07:32:48 +0000

5248 is in ejabber.cfg
1863 is in src/legacy/msn/msn.py

What should be the ports in the above files for MSN ?
Any other possibility?
The error remains: Failed to connect to MSN servers: [Failure instance: Traceback: exceptions.Exception, Timeout ]

no, via 5248 aim gateway

evadim — Mon, 18 Aug 2008 20:26:44 +0000

no, via 5248 aim gateway connect to ejabberd, via 1863 aim gateway connect to aim network

Changes done

ashish — Mon, 18 Aug 2008 13:29:22 +0000

src/legacy/msn/msn.py : remove CVR0 on line 113.

This is how the files look now:
MSN_PROTOCOL_VERSION = "MSNP11" # protocol version
MSN_PORT = 1863 # default dispatch server port
MSN_MAX_MESSAGE = 1664 # max message length
MSN_CVR_STR = "0x040c winnt 5.1 i386 MSNMSGR 7.0.0777 msmsgs"
MSN_AVATAR_GUID = "{A4268EEC-FEC5-49E5-95C3-F126696BDBF6}"
MSN_MSNFTP_GUID = "{5D3E02AB-6190-11D3-BBBB-00C04F795683}"
MSN_MAXINT = 2**31 - 1

What is the significance of the MSN_PORT = 1863, is it related to the port in configuration file "ejabber.cfg" (MSN Port = 5248)?

same error

ashish — Mon, 18 Aug 2008 04:54:21 +0000

Is there any other possibility? I tried that but still the same error. Do you need any other info which might be causing this ?

hmm...

evadim — Wed, 13 Aug 2008 09:15:55 +0000

looks like PyMSN-transport error
PyMSNt - problem with CVR0 in version string
http://groups.google.com/group/py-transports/browse_thread/thread/8e3583...

Same error

ashish — Wed, 13 Aug 2008 06:16:02 +0000

I have ejabber 1.1.4 on centos.
No firewall. All other transports are working.
It is only MSN transport which is giving the error:
msn.jabber.aress.net: Failed to connect to MSN servers: [Failure instance: Traceback: exceptions.Exception, Timeout
]

I have PyMSNt 0.11.3
I have tried to change the default port of MSN aswell.
Any other suggestions ???

same problem, setting up my

gewuerzwiesel — Mon, 21 Jul 2008 11:55:52 +0000

same problem,

setting up my public-rootserver ip doesn't work...

so, what next?
thx for help

greets

Thanks a lot

vetetix — Wed, 09 Jul 2008 23:09:35 +0000

I had the same problem, which I wasn't able to solve for the last 2 or 3 months, and you gave me the solution. Thanks a lot.

The answer was finally found

droopy — Wed, 04 Jun 2008 13:27:01 +0000

The answer was finally found :)

I had this problem last week. It turns out that the meaning of one of
the lines in the config file has changed slightly.

The part I had to change is below.

127.0.0.1

My server is behind a NAT firewall and I had the Host set to my public
IP address. After the upgrade I had to change it to my internal
RFC1918 address (192.168.x.x.)

Hope that helps.

--
Kelly Hays
XMPP:kelly.h...@jkhfamily.org