the last time the msn servers moved and the ssl connect failed error occured, someone fixed it by updating the passport server ip if i recall correcty...
the last time the msn servers moved and the ssl connect failed error occured, someone fixed it by updating the passport server ip if i recall correcty...
These are the IPs I am currently using. the dispatch IP HAS CHANGED in respect to the original IP used in the 0.3 source code.
(I couldn't use the CODE tags, it screwed up the way it displays)Quote:
#define Dispatch_IP IP(65,54,239,20)
#define Nexus_IP IP(65,54,179,216)
#define Passport_IP IP(65,54,183,197)
#define Msn_IP IP(65,4,15,61)
I now get all the way to the SSL part and still get the SSL authentication error, so its not the certificate.
I have tried all possible IPs that MSN could be using and got the same SSL error (I even restored back to the original SSL certificate that was in the source code).
So its not the certificate and its not the ip settings.
It may still be the IPs. That or the version of the MSN protocol that Beup supports, is not supported by Microsoft servers anymore, which I haven't seen anything official saying so. They are up to MSNP15 atm with WLM I think, Beup uses MSNP9, a shade above the MSNP(rotocol)8 that I believe is the lowest still supported.
When a client connects with the msn servers and begins the connection process, after initial "handshaking" and deciding on a protocol to both use, the MSN servers actually send the i.p. address of a passport server to connect to. Beup itself doesn't pick this up and use it, but instead uses the hard coded methodolgy we can see in the source. I am wondering if the servers send back different IPs depending on whichever protocol that client proposes it can use.
I don't have the coding nous yet to have Beup spew out that information (that it is receiving from the msn servers) on the screen to verify we are using, or have the right passport server I.P.
I was trying the other way around, wireless packet sniffing to pluck the tcp information as it travels between router and DS however that is seeming to be more quite a convoluted process.
The best thing i think is for us to do a new msn client, at least that way we will know where everything is, so that next time they change the ip we can do it easily, we can use palib to start it, but i dont know any programming so i need serious help, we can make the interface and the program as simple as possible, even without Display pictures, just text, if we do that then we will make a new msn, we must try hard and i know that it is possible to do, as HtheB created the wonderfull beup.
Antonio Zea aka Kevinc created and coded Beup. HtheB created a skin, added dldi patch, and plastered his name all over it and tried to win the neoflash competition with it. According to Kevinc himself, there was virtually no change to the source.Quote:
Originally Posted by madeinair
http://www.neoflash.com/forum/index.....html#msg28597 < very interesting reading.
I think you are spot on with the idea for a redesign, one that separates the client from the connection code to make it more updateable as Microsoft will continue to make old protocols obsolete, and change servers at a whim.
As to the desire for most up to date source code for Beup, the latest source available is not too far off the version last released by HtheB , the only real difference I can see is the addition of a splash screen (a requirement to enter neoflash competition) and the clock fix. As to functionality it gets to exactly the same point as the non source released version, SSL Authentication failed.
Now, Frigolit, the guy who updated the i.p. addresses last time this happened, in April 2007, has been working on it, changing i.p. addresses and ssl certificated with out much luck. I would like to know how he does it, as I think he is doing it onthe main file or at least the binaries, as he has mentioned not having access to the source of the latest version, yet his release was a patched version of it. >
http://www.digitalfractions.net/
Hi, apologies if this doesn't help at all, but I was thinking...
There are programs out there for PC like Trillian and the like which you input your MSN information (and various other IM accounts information) into and it connects you to your IM accounts. While it's not the same thing, don't those programs require the same information as you do in order to connect to MSN? Maybe there's a way to figure out what you need to connect with Beup by looking at those things, if any are open source, or if any of the coders want to talk about it.
Good luck to those trying to repair MSN on the DS!
so does msn on ds work or not? im confused...
Wait , so i have been following this thread since it started. I thought madeinair was going to fix it , with a whole new release? he had a list of things he was going to do. and if you read back in the forum you see people have posted info about the msn servers. Look back and you might find something that would help . :P
Oh and i was looking and i found this
http://gbatemp.net/index.php?showtop...&#entry1254856
Looks like he might be doing something...
The problem is that i dont know anything about c++ and i wish i did know, the other problem is that i looked everywhere for the ip or url of the new servers but it seems that no one knows, on the other hand, pidgin still works even though it was build before the error of ssl connection, i think pidgin used something called dns which locates the ip and automatically changes it, the only problem now is that beup was not made for dns and automatic ip, this means that we have to change all beup source meaning make a new one because all the files depend on each other, this means that we have to make a new one but now the thing is that i dont know how to make one, if anyone knows alot about programing then this can be done, other than that i think there is nothing to do than use a computer for msn.:(