Hi, I don’‘t really see what’‘s wrong here. The bad request is a reply to the vcard request which, yes, is not permitted right now because we don’‘t support vcards. =) (most clients don’'t seem to bother asking before trying vcard requests, theoretically one would actually do a disco request)
Am I to assume though that you aren ot properly logging in to MSN? I keep seeing smatterings of “MSN isn’'t working, MSN screwed us again!” messages, but then someone found on their website where they actually said “we are experiencing an outage”. So yeah. =)
I don’‘t have enough experience with MSN, moreover I don’‘t have enough experience with Transports provided by Jabber Server, but i’'m the user who need the problem to be resolved.
I can provide you as much information as you want and I can.
Transport is available at disco. User can be registered via transport but user can’'t log in to the MSN network.
I looked for log in order to find out is it problem trivial or not. Maybe something with permissions or settings. That was a reason why i have posted log with error code which i can’'t locate as user environment problem.
Hrm. There is a chance that MSN “changed something” and just messed us up. Anyone else having login issues with MSN that aren’'t related to typing in the wrong username/password?
… i have been able to login … but I am writing my own client so … I dont know about the vcard thing … but for me … if I do provide a valid username and pass … it does log me in …
It’‘s kind of interesting that some folk are seeing it and some aren’‘t. For example, one of my test accounts sees it every time, relentlessly. Typically have to connect once from a real msn client and then connect again before I actually get logged in. Whereas my main account hasn’'t had any problems what-so-ever.
I have problems loggin into the msn transport using a passport.com account. I can register with my regular hotmail account with no problems. However, when i use my @passport.com account with the msn transport, the transport says i have correctly registered but the status shows “disconnected”. In the admin console, the last login date=never. No errors are displayed to the client or the server. This account works fine with the microsoft msn client.
I have problems loggin into the msn transport using a passport.net account. I can register with my regular hotmail account with no problems. However, when i use my @passport.net account with the msn transport, the transport says i have correctly registered but the status shows “disconnected”. In the admin console, the last login date=never. No errors are displayed to the client or the server. This account works fine with the microsoft msn client.
That is very interesting information! Hrm… I wonder if passport.net accounts connect in a different manner for whatever reason.
Sorry, i meant passport.com. I had .net on the brain. Regardless of my typo, i will create a msn account without a hotmail.com or passport.com address from microsoft and see what happens.
Seems my problem was not with the passport.com account. The problem is when i register, it registers successfully but in a disconnected state. I have to close the client and reopen for the msn transport to become active. Restarting the msn transport seemed to work too. Very strange.