More MSN mischief

I can connect to MSNs dispatch server easily, however, i cannot issue the INF command to the server, it just simply disconnects me. I can issue CVR messages and VER messages easily. However, it simply won't accept my INF request. I issue all the commands in the correct order, add carriage returns at the end (#13#10) and include the correct TrialID. However, this stumps me everytime! Please help! I've also tried connecting to using Telnet Client, i issue the commands like i do in my application, and the same thing happens! Why does it disconnect?

CVR 1 0x0409 win 4.10 i386 MSNMSGR 5.0.0544 MSMSGS

these messages go fine, but as soon as i try


the whole thing disconnects....
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

>Why does it disconnect?
It disconnect because you need to complete the authentication process firstly.
henrythackerAuthor Commented:
Apparently you can issue the INF command before you authenticate, and infact, you need to run the INF command first as that tells you what type of hash to use for generating passwords, IE MD5. So this command MUST come before the authentification, although its not essential apparently. Can you send me a list of commands which you issue to the messenger server which connects correctly, thanks, any help would be appreciate.
"INF (optional)
After the client and server agree on a protocol version, the client may send INF with a TrID and no parameters. This asks the server what form of authentication will be used.

The server will reply with an INF, the TrID, and the type of authentication system as the parameter. In protocol versions up to and including MSNP7, it is always MD5, so it's really pretty pointless. "

It looks like there is no such a command in ver8.
OWASP: Threats Fundamentals

Learn the top ten threats that are present in modern web-application development and how to protect your business from them.

I'm right. rtfm ;-)
"The INF command, which was optional in MSNP7, no longer exists in MSNP8. If you attempt to send it while logging in, you will be immediately disconnected."
As I advised you earlier, look attentively at the following link:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
henrythackerAuthor Commented:
Im sorry! as you pointed out, i was looking at totally the wrong version of the protocol, everything should work great now! thank you.. sorry for my stupidity!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.